From owner-freebsd-mobile@FreeBSD.ORG Sun Aug 22 23:39:22 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C749316A4CE for ; Sun, 22 Aug 2004 23:39:22 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7CB043D3F for ; Sun, 22 Aug 2004 23:39:22 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Sun, 22 Aug 2004 16:39:22 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4B0885D04; Sun, 22 Aug 2004 16:39:22 -0700 (PDT) To: Gary Kline In-reply-to: Your message of "Wed, 18 Aug 2004 15:28:53 PDT." <20040818222853.GA63743@thought.org> Date: Sun, 22 Aug 2004 16:39:22 -0700 From: "Kevin Oberman" Message-Id: <20040822233922.4B0885D04@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: 600E Audio problem (Solved!) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Aug 2004 23:39:22 -0000 Got it! And, boy, do I feel dumb. It turns out that the device in the 600E is a CS432X device and that device uses the mss driver. So just modify your kernel config to include: device sound device snd_mss And make sure that snd_csa is NOT present as it will see another audio component and try to connect to it as a CS4610. This would block the mss driver from finding the audio chip. It's amazing what you find when you actually take the time to read the source for the drivers. To summarize, either include devices sound and snd_mss in your kernel or load the snd_mss module. Do not include snd_csa! Add the following to your /boot/device.hints file: hint.pcm.0.flags="0x10" That should do the trick. There is no need to edit /sys/conf/files. It should probe as: pcm0: at port 0x220,0x233,0x388-0x38b,0x530-0x537 irq 5 drq 0,1 on isa0 pcm0: [GIANT-LOCKED] Let me know how it works for you. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634