Slackware 9.0 and loading modules on boot

[TheHeadRoach]

On my slack box several modules are loaded by default when the system boots up. There are no lines in either /etc/modules.conf or /etc/rc.d/rc.modules that are uncommented. How then are they loaded?

It's not a big problem, just curious to know how my slack box works.

[mdwatts]

The kernel's boot and hardware detection process does load required modules for certain hardware if found and the module exists.

[serz]

The modules should be loaded by the rc.modules boot script. Check the other boot scripts for "modprobe", maybe some script there is loading them upl

[mdwatts]

It is always a good idea to review your installed kernel documentation in /usr/src/linux/Documentation. Besides the following, there are other text files that explain about the kernel etc.


Enable loadable module support
CONFIG_MODULES
Kernel modules are small pieces of compiled code which can be
inserted in or removed from the running kernel, using the programs
insmod and rmmod. This is described in the file
<file:Documentation/modules.txt>, including the fact that you have
to say "make modules" in order to compile the modules that you chose
during kernel configuration. Modules can be device drivers, file
systems, binary executable formats, and so on. If you think that you
may want to make use of modules with this kernel in the future, then
say Y here. If unsure, say Y.

Set version information on all symbols for modules
CONFIG_MODVERSIONS
Usually, modules have to be recompiled whenever you switch to a new
kernel. Saying Y here makes it possible, and safe, to use the
same modules even after compiling a new kernel; this requires the
program modprobe. All the software needed for module support is in
the modutils package (check the file <file:Documentation/Changes>
for location and latest version). NOTE: if you say Y here but don't
have the program genksyms (which is also contained in the above
mentioned modutils package), then the building of your kernel will
fail. If you are going to use modules that are generated from
non-kernel sources, you would benefit from this option. Otherwise
it's not that important. So, N ought to be a safe bet.

Kernel module loader support
CONFIG_KMOD
Normally when you have selected some drivers and/or file systems to
be created as loadable modules, you also have the responsibility to
load the corresponding modules (using the programs insmod or
modprobe) before you can use them. If you say Y here however, the
kernel will be able to load modules for itself: when a part of the
kernel needs a module, it runs modprobe with the appropriate
arguments, thereby loading the module if it is available. (This is a
replacement for kerneld.) Say Y here and read about configuring it
in <file:Documentation/kmod.txt>.

[Darkbolt]

Actually out of the box slackware loads little/no modules, in order for it to modprobe the modules you want at boot time, you have to uncomment them in rc.modules

It does have all the fundamental things compiled into the kernel I believe, and it has other modules loading in things li ke rc.netdevice, rc.pcmcia, and I believe rc.serial.

This all goes back to the whole 'do it yourself' stuff with slackware....You want it to load something at boot, you open up your favorite text editor, and start uncommenting ;)