DOH!!! Here's another one for the tech horror stories.
Some advice: Always make sure that your speakers are plugged in before testing your sound card. It can save you hours of head banging. I figure that it was probably working while compiled in kernel as well. Oh well, I guess I'll leave it as a module. *sigh* Sometimes I wonder if I'm in the right profession... -- Charles Lewis [EMAIL PROTECTED] > From: Charles Lewis <[EMAIL PROTECTED]> > Date: Tue, 20 Mar 2001 13:26:13 -0800 > To: debian-user <debian-user@lists.debian.org> > Subject: Re: sound compiled into kernel as opposed to a module > Resent-From: debian-user@lists.debian.org > Resent-Date: Tue, 20 Mar 2001 13:24:17 -0600 > > As I am running sid, I have the latest modutils. > > Also, in /usr/src/linux/drivers/sound/Makefile, notice the following line: > > obj-$(CONFIG_SOUND_ES1371) += es1371.o ac97_codec.o > > es1371.o and ac97_codec.o are successfully loading, but no sign of sound.o > > I'm not intimate with Makefile, but it appears to me that sound.o is not > being associated with es1371 (although I did notice in conjunction with > other modules) > > Now I'm wondering if debian tinkered with the linux kernel source for 2.4.2. > I think I'll trying downloading the kernel source from another location. > > > -- > Charles Lewis > [EMAIL PROTECTED] > 817-556-4720 > > >> From: "Martin Marconcini" <[EMAIL PROTECTED]> >> Date: Tue, 20 Mar 2001 16:05:00 -0300 >> To: "Sebastiaan" <[EMAIL PROTECTED]>, "Charles Lewis" >> <[EMAIL PROTECTED]> >> Cc: <debian-user@lists.debian.org> >> Subject: RE: sound compiled into kernel as opposed to a module >> Resent-From: debian-user@lists.debian.org >> Resent-Date: Tue, 20 Mar 2001 12:58:15 -0600 >> >> Please nothe that without the New version of modutils you won't be able to >> load modules properly, because in 2.4.2 the structure of /lib/modules >> changed the way it's accesed. >> >> Remember that. >> >> Unless you want to load modules manually every restart... >> >> But it is a must to upgrade modutils. >> >> Regards, >> >> Martin Marconcini. >> >> -----Original Message----- >> From: Sebastiaan [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, March 20, 2001 3:56 PM >> To: Charles Lewis >> Cc: debian-user@lists.debian.org >> Subject: Re: sound compiled into kernel as opposed to a module >> >> >> Hm, it does exist in >> /lib/modules/2.4.2/kernel/drivers/sound/sound.o >> >> but soundlow.o is not there. >> For my card (gravis ultrasound) it is enough to run >> modprobe sound >> insmod gus <parms> >> >> If you just switched to 2.4.2, be aware that you need a newer >> version of modutils. >> If you already have this, walk through your configuration again, sound.o >> really exists in 2.4.2. >> >> Greetz, >> Sebastiaan >> >> >> On Tue, 20 Mar 2001, Charles Lewis wrote: >> >>> hrm... ok, recompiled kernel with es1371 as module. modprobe sound >> returns: >>> >>> modprobe: Can't locate module sound >>> >>> In fact, sound.o does not exist anywhere. I'm running 2.4.2. Has something >>> changed since 2.2.x? >>> >>> -- >>> Charles Lewis >>> [EMAIL PROTECTED] >>> 817-556-4720 >>> >>> >>>> From: Sebastiaan <[EMAIL PROTECTED]> >>>> Date: Tue, 20 Mar 2001 19:28:41 +0100 (CET) >>>> To: Charles Lewis <[EMAIL PROTECTED]> >>>> Cc: debian-user <debian-user@lists.debian.org> >>>> Subject: Re: sound compiled into kernel as opposed to a module >>>> >>>> Hi, >>>> >>>> my opinion is that it is better to compile drivers as modules. When a >>>> device is messed up, you can rmmod and insmod the driver, and sometimes >> it >>>> works again. >>>> >>>> For info about your driver, read the kernel source documents in >>>> /usr/src/linux/Documents/sound/es1371 >>>> >>>> Usually there is useful information in there, but not in that document. >>>> >>>> Generally you do: >>>> modprobe sound >>>> insmod soundlow >>>> insmod soudcore >>>> insmod sound >>>> insmod es1371 >>>> >>>> (perhaps just 'modprobe sound' and 'insmod es1371' will work too) >>>> then you should be able to cat to /dev/dsp. >>>> >>>> Hope it helps >>>> Sebastiaan >>>> >>>> >>>> On Tue, 20 Mar 2001, Charles Lewis wrote: >>>> >>>>> I have a es1371 card and I've compiled support into the kernel (not as >> a >>>>> module). How does the install process differ? Before all I had to do >> was go >>>>> into modconf and select it. Now I'm not sure what to do. >>>>> >>>>> It is detecting the card on bootup. I see it in /proc/devices and >>>>> /proc/interrupts but if I cat something to /dev/dsp, I don't get any >> sound. >>>>> What else do I need to do to make it work? >>>>> >>>>> -- >>>>> Charles Lewis >>>>> [EMAIL PROTECTED] >>>>> 817-556-4720 >>>>> >>>>> >>>>> >>>>> -- >>>>> To UNSUBSCRIBE, email to [EMAIL PROTECTED] >>>>> with a subject of "unsubscribe". Trouble? Contact >> [EMAIL PROTECTED] >>>>> >>>>> >>>> >>>> >>> >>> >> >> >> -- >> To UNSUBSCRIBE, email to [EMAIL PROTECTED] >> with a subject of "unsubscribe". Trouble? Contact >> [EMAIL PROTECTED] >> >> >> -- >> To UNSUBSCRIBE, email to [EMAIL PROTECTED] >> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >> >> > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >