"Thomas H. George,,," <[EMAIL PROTECTED]> writes: > It is certainly elementary but it baffles me. Although I have > compiled my kernel with module support set to load modules as needed > and run make modules and make modules_install,
(Depending on what you're doing, you may find it easier/better to use kernel-package, which builds installable Debian packages from kernel source. It also makes it much more straightforward to build module packages that are distributed separately from the main kernel, including the ALSA sound driver, the lm-sensors hardware monitoring package, and the OpenAFS network file system.) > certain modules never loaded when needed. For example, the sound > card module never loaded at startup so I always ended up building it > into the kernel. For things where the kernel has an option for lots of things that provide the same interface (which network card, which sound card, etc.) it won't automatically load something without prodding. There might be hints in your system logs about which modules are attempting to be loaded; you can probably add aliases for these under /etc/modutils. > I know I have overlooked something basic, but what? My O'Reilly > Debian book discusses config.modules which has been replaced by > modules.config which starts with a warning I am not to edit it. You can create or edit a file under /etc/modutils and run update-modules to regenerate your modules.conf file. > Modules-HOWTO has a lot of interesting information but, unless I > missed it, no instructions regarding on requiring modules to load > during bootup. ...or, edit /etc/modules; it's a plain-text file that has a listing of modules to load at boot time, one to a line. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ "Theoretical politics is interesting. Politicking should be illegal." -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
