Re: sound compiled into kernel as opposed to a module

On 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

Re: sound compiled into kernel as opposed to a module (SOLVED)

eave 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 > Subject: Re: sound compiled into kernel as opposed

Re: sound compiled into kernel as opposed to a module

es 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: > Subject:

RE: sound compiled into kernel as opposed to a module

. 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/kern

Re: sound compiled into kernel as opposed to a module

<[EMAIL PROTECTED]> > > Cc: debian-user > > 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 insm

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 informat