Should I compile the sound card module into the kernel?

[BlvdKing]

Right now I am having problems with my sound card (Creative AWE 64). The kernel can't load the module because it says that the sound card is busy or something like that. I am going to compile kernel 2.4.1 today. Should I compile the sound card driver as a module or directly into the kernel? What works best?

Also, where can I get a really good guide on how to compile the kernel, besides the NHF? Whenever I follow the NHF, I get module errors.

Thanks!

[whiterabbit]

I would compile it directly into the kernel. You will find much happiness and prosperity with this path of enlightment. Someone else can elate to you all the superfine technical specifics of *why* but I know end results, and they make me happy. Go kernel! I'll look thru my links and see if I can find a good link on kernel recompiling 4 U.

[BlvdKing]

Thanks whiterabbit. I can't see myself having problems compiling the driver into the kernel. Anyone else think the sound card driver should be compiled into the kernel? What about other drivers?

[Ig0r]

There are only two reasons why you shouldn't put a driver in your kernel.

1) The driver requires insmod options (my soundcard driver needs to be told to enable the joystick port; BTTV driver doesn't correctly detect my tv card, has to be told which one)

2) The driver is for a device that you don't normally have connected, but still need (zipdrive perhaps)

Otherwise, put it all in the kernel.

[The King Ant]

As said above, there are some things that should be modules; ethernet cards drivers, for example, so you can switch from 10/100 full/half duplex, etc.

There are some things that should be in the kernel; SCSI card drivers that you need to boot into Linux (so you don't have to both with passing lilo weird parameters to load a module).

There are some things that don't matter much either way; sound card drivers.

It's really just a preference. I tend to compile as much as I can into my kernel.