[sclug-general] Probing Modules

[Leroy Everett]

Probing Modules One of the strengths of Linux is that the kernel - the core operating code - can be built in either a monolithic or modular configuration. If you've recompiled your kernel, eliminating all unnecessary modules and building those that remain directly into the kernel, you've built a monolithic kernel. If, on the other hand, you've built loadable module support into the kernel and have left many necessary drivers as modules, your kernel is modular. Most current distributions, by default, build loadable modules that are used only "on demand." modprobe is a Linux core command to load specific modules. If the command is executed without options, modprobe will attempt to load the specified module and all other modules upon which it depends. The convention for modprobe is:     modprobe [options] [modules] The options for modprobe are: Option Action -a Load all listed modules, not just the first one. -l [pattern] List all the existing modules. May be combined with -t to specify a module type. -r Remove specified modules and all others on which they depend -t type Load only a specific type of module. So, for example, if your sound card isn't working the first time you boot your system, you might try modprobe to be sure that the sound modules have actually loaded.     modprobe sound These modules make it possible to keep the size of your kernel to a minimum. It's a useful approach to kernel size and can be made more useful from understanding the modprobe command.