On Mon, Nov 27, 2006 at 12:39:09PM -0500, Kevin Mark wrote: > On Mon, Nov 27, 2006 at 08:29:56AM -0600, Martin McCormick wrote: > > > This 2.6.5 kernel has a number of modules for audio and > > various things and those modules all make without a problem. > > After doing "make modules_install," I got /lib/modules/2.6.5 > > and depmod gave me modules.dep in that directory along with the > > subdirectories for all the modules. What I didn't get is a new > > /etc/modules. I am probably looking in the wrong place, but I > > can't even find much documentation as to how that file actually > > gets there. The file, itself, has comments at the top which are > > the same wording found in the man page as to what it is used for, > > etc. As an experiment, I renamed /etc/modules to something else > > and the new kernel complained about the missing /etc/modules file > > so 2.6.5 kernels do need /etc/modules.... > There are various things that determine what modules are loaded at boot > time: > - its compiled into the kernel > - its included in /etc/modules > - its loaded by a program like 'discover' > - its loaded by udev > From my recollection, I just added the name of whatever kernel modules I > needed to the /etc/modules file whenever a module was not being loaded. > cheers, > Kev
Personally, I use modconf so that I get some hints on what parameters a module needs (that and the kernel docs for that kernel). Modconf puts the module name in /etc/modules and the parameters in the correct spot in /etc as well. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
