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, 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. Now I have a Geforce4
video card and must run insmod NVdriver each time after I boot up as xdm
fails until I have done this.
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. Modules-HOWTO has a
lot of interesting information but, unless I missed it, no instructions
regarding on requiring modules to load during bootup.
The Linux kernel is so compact there is no reason not to load everything
I need at bootup so the real advantage of the module concept must be to
allow third parties to add functions to the kernel - e.g. the NVdriver.
Would someone please point out what I have been too blind to see.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
- Re: Modules Dont Load At Startup Thomas H. George,,,
- Re: Modules Dont Load At Startup Russell
- Re: Modules Dont Load At Startup Michelle Konzack
- Re: Modules Dont Load At Startup Greg Madden
- Re: Modules Dont Load At Startup David Z Maze
- Re: Modules Dont Load At Startup - THANKS Thomas H. George