This article will cover the methods for managing kernel modules.
The Template:Filename directory can be used to pass module settings to udev. You can use configuration files with any name in the directory, but Template:Filename is the defacto standard for general settings.
Blacklisting when referring to Kernel modules is a mechanism to stop the kernel module loading. This is either when the associated hardware is not required to be used, or loading that module causes problems.
For example there may be a two kernel modules, that if they get loaded together try to control the same piece of hardware resulting in a conflict.
You can blacklist modules using the Template:Codeline keyword:
You can also blacklist modules on the kernel command line using the following syntax:
The "blacklist" option blacklists modules loaded by that name only. But if some other module depends on that module, that module will get loaded because blacklisting does not match dependent modules.
Alternatively, one can force nothing to be installed to "blacklist" that module and any that depend on it:
Some modules are loaded as part of the initramfs. Template:Codeline will print out all autodetected modules. To avoid initramfs from loading those modules you wish to blacklist, then blacklist them in Template:Filename. Running Template:Codeline will list all modules pulled in by the various hooks (i.e. filesystem hook, SCSI hook, etc). Remember to rebuild initramfs once you've blacklisted the modules.
The following commands can help determine the dependencies of a module from the module itself.
- Format the contents of Template:Filename and show what kernel modules are currently loaded:
$ modinfo MODULE_1
- Use Template:Codeline to show information about Template:Codeline (including aliases and install commands):
$ modprobe --show-depends MODULE_2