Kernel modules are object files that contain code to extend the kernel of 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.
Compile-in-kernel modules vs Loadable kernel modules (LKMs)
This page is meant to help picking between compile-in-kernel (
<*>) and compile-as-module (
<M>) when configuring a kernel.
- Is loadable without reboot (at least most of them).
- Results in smaller kernel memory footprint (when the module is not loaded).
- Can be loaded on demand by udev (for example DVB drivers for DVB stick).
- Allows easy reloading of kernel drivers in case of module crash.
- Allows specifying module-specific parameters in /etc/conf.d/modules
Using a module:
- May require an update of the initramfs for modules needed early in the boot process (i.e. filesystem drivers).
- May result in performance losses 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).
Loadable kernel modules
Loadable modules can be defined in the /etc/conf.d/modules file in order to load modules to the kernel during the init process.
To avoid a module from loading, add it to a file in /etc/modprobe.d/:
blacklist uhci_hcd blacklist nvidia
See the automatic module loading section in the systemd article for module loading when using systemd.
A module can be load or unload manually by the modprobe command. For example, to unload the
nvidia module and load the
nouveau module, run:
modprobe -r nvidia
To list currently loaded modules, run lsmod.
Going completely module-less
If, for some reason, you want to have a completely module-less system, you can disable loadable module support in your 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, you may also wish to dispense with the userspace programs that manage loadable modules (e.g. lsmod, modprobe, etc). To do this, you'll need to remove kmod support from packages that use it, and you'll need to unmerge kmod and the virtual virtual/modutils package(s). Because modutils is part of the system set, it first must 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).
-*virtual/modutils to /etc/portage/profile/packages (create the "profile" directory and "packages" file if they don't exist). This removes the virtual/modutils virtual package from the system set.
Then unmerge modutils and kmod packages:
If the above command only removes modutils, then some package still depends on kmod even with the
-kmod USE flag set. You can run equery depends kmod to find out which package still depends on kmod.
If you previously had a kernel installed with modules, then you'll also want to remove the /lib/modules/<kernel-version> directory. Since you've built your kernel 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.