From owner-freebsd-mobile@FreeBSD.ORG Mon Aug 23 02:32:37 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 EB02116A4CE for ; Mon, 23 Aug 2004 02:32:37 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4A6F43D1D for ; Mon, 23 Aug 2004 02:32:37 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Sun, 22 Aug 2004 19:32:37 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id B0BD85D09; Sun, 22 Aug 2004 19:32:31 -0700 (PDT) To: Gary Kline In-reply-to: Your message of "Sun, 22 Aug 2004 17:41:55 PDT." <20040823004155.GA61085@thought.org> Date: Sun, 22 Aug 2004 19:32:31 -0700 From: "Kevin Oberman" Message-Id: <20040823023231.B0BD85D09@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: Mon, 23 Aug 2004 02:32:38 -0000 > Date: Sun, 22 Aug 2004 17:41:55 -0700 > From: Gary Kline > > On Sun, Aug 22, 2004 at 04:39:22PM -0700, Kevin Oberman wrote: > > 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. > > > I'm surprised that you had to actually dig into the code > to figure this out. (Altho lots of times reading tthe source > is drastically easier than wading thru obscure man pages: > *sigh*) > > Hm. Just checked NOTES; ISA, eh? well, you said this was > a strange one. > > Two questions if you're still at-keyboard at 17:30-18:00. > First, is there a way to unload the csa *.ko via cmdline? > Second, where should this be posted? I'll add things to > the FBSD laptop site in the 600E section; but anywhere > else? If you loaded the module, you can use kldunload to unload it. If it's in the kernel, you need to re-build the kernel. (If that's the case, you can edit your config file and re-build as follows: cd /usr/src make -DMODULES_WITH_WORLD buildkernel KERNCONF=your_config_file make -DMODULES_WITH_WORLD reinstallkernel KERNCONF=your_config_file This will only rebuild te kernel and not the modules (which are not affected by a config change) and install the newly built kernel OVER the old one so the modules are still there. It also leaves kernel.old unchanged. It will save a LOT of time on slower systems like the 600E. I'm not sure of other places to add the information. This message gets it into the mail archives, though. -- 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