slack kernel modules obfuscation?!?!

Sammy2ooo · 02-27-2004, 07:38 AM

Hi

i am using slack 9.1 and i am quit happy with it.

But i dont understand within the slack boot concept is how the hell thise kernel modules are getting loaded. modules.conf, modprobe.conf are empty.What about this hotplug things???!??!
I have googled for it, and have also searched this board for it, with no result :|

Please shed some light on this, wanna learn more about hardware and kernel things....

Mogwa_ · 02-27-2004, 08:20 AM

which modules are loaded and ill see if i can help.

by default the kernel has module autoloading built in so if it finds some thing it needs it will load the module it needs.

Sammy2ooo · 02-28-2004, 12:29 PM

This are my loaded modules

Code:

 0 19:24:29 root@uranos:~ $ lsmod
Module                  Size  Used by    Tainted: P  
nvidia               1965152   6  (autoclean)
snd-pcm-oss            37252   1 
snd-mixer-oss          11992   0  [snd-pcm-oss]
8139too                15240   1 
mii                     2304   0  [8139too]
crc32                   2880   0  [8139too]
uhci                   24496   0  (unused)
ehci-hcd               16872   0  (unused)
usbcore                58400   1  [uhci ehci-hcd]
snd-cmipci             17760   1 
snd-pcm                55904   0  [snd-pcm-oss snd-cmipci]
snd-page-alloc          6004   0  [snd-pcm]
snd-opl3-lib            5764   0  [snd-cmipci]
snd-hwdep               4672   0  [snd-opl3-lib]
snd-timer              13252   0  [snd-pcm snd-opl3-lib]
snd-mpu401-uart         3136   0  [snd-cmipci]
snd-rawmidi            12512   0  [snd-mpu401-uart]
snd-seq-device          3920   0  [snd-opl3-lib snd-rawmidi]
snd                    27460   0  [snd-pcm-oss snd-mixer-oss snd-cmipci snd-pcm                                                       snd-opl3-lib snd-hwdep snd-timer snd-mpu401-uart snd-rawmidi snd-seq-device]
soundcore               3332   7  [snd]
ide-scsi                9424   0 
agpgart                39576   3

Greets

gnashley · 02-28-2004, 01:11 PM

study the scripts in /etc/rc.d rc.modules is where the modules are loaded, unless they are put in modules.conf, which gets read first.
After the kernel finishes loading (look for 'VFS' in dmesg) init is started. inti starts by reading /etc/inittab then starts running the scripts in /etc/rc.d
Thart's where all the action takes place. If you do a 'ps -x' you can see the order in which the processes are started.