On Wednesday 04 November 2009 20:02:03 Canek Peláez Valdés wrote:
> On Wed, Nov 4, 2009 at 11:30 AM, Grant <emailgrant@gmail.com> wrote:
> >>> But I get the warning about "Module snd_hda_intel not found" which is
> >>> the built-in chip.
> >>
> >> That's because you don't have that module, it's built into the kernel.
> >> This also means the the options lines in alsa.conf will not do anything.
> >
> > OK, so I need to build them as modules, or I need to change those
> > lines in alsa.conf?  If I can avoid building them as modules I'd like
> > to.  How can those lines be written when the drivers are built into
> > the kernel?
> 
> You pass the parameters in the kernel boot line. For examen, in my
> grub.conf I have:
> 
> title Gentoo Linux (linux-2.6.31.5)
> root (hd0,3)
> kernel /boot/kernel-2.6.31.5 root=/dev/sda4 quiet udev
> splash=silent,fadein,theme:natural_gentoo CONSOLE=/dev/tty1
> iwlagn.swcrypto=1 snd-hda-intel.model=basic
> initrd /boot/initrd-2.6.31.5
> 
> I have two parameters for my built-in modules: for the iwlagn module,
> the parameter swcrypto=1, and for the snd-hda-intel the parameter
> model= basic. In general, for a built-in module called "module", you
> pass the parameter "parm" with value "val" this way:
> 
> module.parm=val
> 
> As of now, in my laptop I have *all* my modules built-in. In other
> machines, I have modules where there is no other option (like nvidia
> drivers, LIRC, ndiswrapper, stuff like that).

I used to have my alsa drivers which are different to the OP, built in the 
kernel.  For years on end.  Then alsasound stop working - something like 5 
kernels back, can't recall exactly.  I had to build alsa separately as 
modules.  Haven't tried to go back to building them in the kernel again.

YMMV.
-- 
Regards,
Mick