Kernel modules are object files that contain code to extend the kernel of an operating system. Kernel modules are used to add support for new hardware and/or filesystems, or for adding system calls. Modules can be built into the kernel or compiled as loadable kernel modules.
Most modern Gentoo installations will use a device manager, such as udev, to automatically load and manage kernel modules, thus module loading will often need no particular configuration.
Gentoo installs, except from Gentoo Prefix, have the virtual/dev-manager virtual package in the system set, which often resolves to virtual/udev by default. virtual/udev has an "any of many" dependency on sys-fs/udev, and sys-apps/systemd (or the depreciated sys-fs/eudev).
About Loadable kernel modules
Many Loadable kernel modules (LKMs) may also be compiled "in-kernel". See configuring a kernel on how to select either built-in and LKM options.
Using LKMs can result in a smaller kernel memory footprint, by not having unneeded modules loaded: modules can be loaded on demand by udev (for example DVB drivers for a DVB stick). Compile-in-kernel code will not be able to be reloaded while the kernel is running, but LKMs can sometimes be used to solve certain issues, by unloading and reloading them.
Using a module rather than building code into the kernel also permits the setting of module-specific parameters, through the /etc/modprobe.d file - see man /etc/modprobe.d.
Modules needed early in the boot process may require an update of the initramfs after a kernel update or recompilation (e.g. filesystem drivers for filesystems used for boot). Some LKMs may incur a slight performance penalty over built-in code, due to the addition of an API layer and slightly more memory usage.
Beware of file system module X located on a partition formatted with X (unbootable system at worst).
Managing kernel modules
View running modules
To list currently loaded modules, run lsmod.
To see all modules built into the currently running kernel:
cat /lib/modules/$(uname -r)/modules.builtin
List available modules
To see all the modules available to be loaded:
find /lib/modules/$(uname -r) -type f -name '*.ko*'
Load specific modules during boot
Occasionally, modules other than those automatically loaded are desired. Loadable modules can be defined in .conf files in the /etc/modules-load.d/ directory in order to load them during the init portion of the system boot process. Each module is listed one per-line. For example:
tun e1000e brcmfmac
To prevent a module from loading, add it by name to a file in /etc/modprobe.d/ and precede each module name with the
blacklist uhci_hcd blacklist nvidia
More information on module blacklisting via /etc/modprobe.d/ can be found by reading the modprobe.d(5) man page:
man 5 modprobe.d
Alternatively, kernel modules can be blacklisted from the secondary bootloader (see GRUB2, systemd-boot, etc.) via parameters passed to the kernel from the kernel command-line. For example, to blacklist the evbug.ko, nvidiafb.ko, and nvidia.ko kernel modules using command-line parameters:
More details on backlisting via kernel command-line parameters can be found in the upstream kernel documentation (search for module_blacklist).
A module can be loaded or unloaded manually by the modprobe command. For example, to unload the
nvidia module and load the
nouveau module, run:
modprobe -r nvidia
See man modprobe.
Going completely "module-less"
This is an advanced topic and not recommended for general use. Modules, in general, make certain drivers easier to load. Also, it is possible to reload a misbehaving driver without reboot by removing and reloading the driver module.
If, for some reason, there is a desire to have a completely module-less system, disable loadable module support in the kernel configuration (making sure to build-in any required drivers/features, of course). Setting
CONFIG_MODULES=n will disable loadable module support:
[ ] Enable loadable module support ----
With a module-less kernel, it is possible to dispense the userspace programs that manage loadable modules (e.g. lsmod, modprobe, etc). To do this, remove
kmod support from packages that use it, and also remove the sys-apps/kmod package. Because sys-apps/kmod is part of the system set, it must first be removed from the set before it can be unmerged.
-kmod to the system's USE flags in /etc/portage/make.conf.
Next, rebuild installed packages without kmod support:
emerge --ask --deep --newuse --update --verbose @world
Follow any special instructions given by rebuilt packages (for example, if udev was rebuilt, then restart it according to the instructions in the emerge output).
-*sys-apps/kmod to /etc/portage/profile/packages (create the profile directory and packages file if they don't exist). This removes the sys-apps/kmod package from the system set.
Then unmerge the sys-apps/kmod package:
If the above command doesn't remove kmod, then some package still depends on it even with the
-kmod USE flag set. Run emerge -pvc sys-apps/kmod to find out which package still depends on kmod.
If a kernel was installed with modules, then also remove the /lib/modules/<kernel-version> directory. Since the kernel was built without any loadable modules, there won't be anything useful in there anymore.
When using a genkernel generated initramfs, it may be necessary to add
nomodules to the kernel command line in the system's bootloader (e.g. GRUB) configuration so that the initramfs does not waste any time looking for modules to load.
Kernel modules fail to automatically load
Ensure that CONFIG_MODPROBE_PATH points to the correct location for the modprobe binary:
- Kernel — the core of the operating system.