[[Wikipedia:Loadable_kernel_module|Kernel modules]] are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system.

[[Wikipedia:Loadable_kernel_module|Kernel modules]] are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system.

Line 21:

Line 17:

== Overview ==

== Overview ==

−

To create a kernel module, you can read [http://tldp.org/LDP/lkmpg/2.6/html/index.html this guide]. A module can be configured to be build-in or loadable. To dynamically load or remove a module, it has to be configured as a loadable module in the kernel configuration (the line related to the module will therefore display the letter {{ic|M}}).

+

To create a kernel module, you can read [http://tldp.org/LDP/lkmpg/2.6/html/index.html The Linux Kernel Module Programming Guide]. A module can be configured as built-in or loadable. To dynamically load or remove a module, it has to be configured as a loadable module in the kernel configuration (the line related to the module will therefore display the letter {{ic|M}}).

Modules are stored in {{ic|/usr/lib/modules/''kernel_release''}}. You can use the command {{ic|uname -r}} to get your current kernel release version.

Modules are stored in {{ic|/usr/lib/modules/''kernel_release''}}. You can use the command {{ic|uname -r}} to get your current kernel release version.

−

{{Note|Module names often use underscores ({{ic|_}}) or dashes ({{ic|-}}), however those symbols are interchangeable both when using the {{ic|modprobe}} command and in configuration files in {{ic|/etc/modprobe.d/}}.}}

+

{{Note|Module names often use underscores ({{ic|_}}) or dashes ({{ic|-}}); however, those symbols are interchangeable, both when using the {{ic|modprobe}} command and in configuration files in {{ic|/etc/modprobe.d/}}.}}

== Obtaining information ==

== Obtaining information ==

Line 55:

Line 51:

== Configuration ==

== Configuration ==

−

Today, all necessary module loading is handled automatically by [[udev]], so if you don't want/need to use any out-of-tree kernel modules, there is no need to put modules that should be loaded at boot in any configuration file. However, there are cases where you might want to load an extra module during the boot process, or blacklist another one for your computer to function properly.

+

Today, all necessary module loading is handled automatically by [[udev]], so if you do not want or need to use any out-of-tree kernel modules, there is no need to put modules that should be loaded at boot in any configuration file. However, there are cases where you might want to load an extra module during the boot process, or blacklist another one for your computer to function properly.

=== Loading ===

=== Loading ===

Line 67:

Line 63:

See {{ic|modules-load.d(5)}} for more details.

See {{ic|modules-load.d(5)}} for more details.

−

=== Configure module options ===

+

=== Setting module options ===

−

To pass a parameter to a kernel module you can use a modprobe conf file or use the kernel command line.

+

To pass a parameter to a kernel module, you can use a modprobe configuration file or use the kernel command line.

==== Using files in /etc/modprobe.d/ ====

==== Using files in /etc/modprobe.d/ ====

−

Files in {{ic|/etc/modprobe.d/}} directory can be used to pass module settings to [[udev]], which will use {{ic|modprobe}} to manage the loading of the modules during system boot. Configuration files in this directory can have any name, given that they end with the {{ic|.conf}} extension. The syntax is:

+

Files in {{ic|/etc/modprobe.d/}} directory can be used to pass module settings to [[udev]], which will use {{ic|modprobe}} to manage the loading of the modules during system boot. Configuration files in this directory can have any name, given that they end with the {{ic|.conf}} extension. The syntax is:

{{hc|/etc/modprobe.d/myfilename.conf|2=

{{hc|/etc/modprobe.d/myfilename.conf|2=

options modname parametername=parametervalue}}

options modname parametername=parametervalue}}

Line 80:

Line 76:

{{hc|/etc/modprobe.d/thinkfan.conf|2=

{{hc|/etc/modprobe.d/thinkfan.conf|2=

−

# On Thinkpads, this lets the 'thinkfan' daemon control fan speed

+

# On ThinkPads, this lets the 'thinkfan' daemon control fan speed

options thinkpad_acpi fan_control=1}}

options thinkpad_acpi fan_control=1}}

−

{{Note|If any of the affected modules is loaded from the init ramdisk, then you will need to add the appropriate {{ic|.conf}} file to FILES in [[mkinitcpio.conf]], so that it will be included in the ramdisk.}}

+

{{Note|If any of the affected modules is loaded from the initramfs, then you will need to add the appropriate {{ic|.conf}} file to {{ic|FILES}} in {{ic|/etc/[[mkinitcpio.conf]]}} or use the {{ic|modconf}} [[Mkinitcpio.conf#HOOKS|hook]], so that it will be included in the initramfs.}}

==== Using kernel command line ====

==== Using kernel command line ====

−

If the module is built into the kernel, you can also pass options to the module using the kernel command line. For all common bootloaders the following syntax is correct:

+

If the module is built into the kernel, you can also pass options to the module using the kernel command line. For all common bootloaders, the following syntax is correct:

modname.parametername=parametercontents

modname.parametername=parametercontents

Line 104:

Line 100:

alias mymod really_long_module_name}}

alias mymod really_long_module_name}}

−

Some modules have aliases which are used to autoload them when they are needed by an application. Disabling these aliases can prevent auto-loading, but will still allow the modules to be manually loaded.

+

Some modules have aliases which are used to automatically load them when they are needed by an application. Disabling these aliases can prevent automatic loading but will still allow the modules to be manually loaded.

{{hc|/etc/modprobe.d/modprobe.conf|

{{hc|/etc/modprobe.d/modprobe.conf|

Line 114:

Line 110:

Blacklisting, in the context of kernel modules, is a mechanism to prevent the kernel module from loading. This could be useful if, for example, the associated hardware is not needed, or if loading that module causes problems: for instance there may be two kernel modules that try to control the same piece of hardware, and loading them together would result in a conflict.

Blacklisting, in the context of kernel modules, is a mechanism to prevent the kernel module from loading. This could be useful if, for example, the associated hardware is not needed, or if loading that module causes problems: for instance there may be two kernel modules that try to control the same piece of hardware, and loading them together would result in a conflict.

−

Some modules are loaded as part of the [[initramfs]]. {{ic|mkinitcpio -M}} will print out all autodetected modules: to prevent the initramfs from loading some of those modules, blacklist them in {{ic|/etc/modprobe.d/modprobe.conf}}. Running {{ic|mkinitcpio -v}} will list all modules pulled in by the various hooks (e.g. filesystem hook, SCSI hook, etc.). Remember to add that {{ic|.conf}} file to the FILES section in {{ic|/etc/mkinitcpio.conf}} (if you have not done so already) and rebuild the initramfs once you have blacklisted the modules, and to reboot afterwards.

+

Some modules are loaded as part of the [[initramfs]]. {{ic|mkinitcpio -M}} will print out all automatically detected modules: to prevent the initramfs from loading some of those modules, blacklist them in {{ic|/etc/modprobe.d/modprobe.conf}}. Running {{ic|mkinitcpio -v}} will list all modules pulled in by the various hooks (e.g. {{ic|filesystems}} hook, {{ic|block}} hook, etc.). Remember to add that {{ic|.conf}} file to the {{ic|FILES}} section in {{ic|/etc/mkinitcpio.conf}}, if you have not done so already, and rebuild the initramfs once you have blacklisted the modules, and reboot afterwards.

==== Using files in /etc/modprobe.d/ ====

==== Using files in /etc/modprobe.d/ ====

Line 141:

Line 137:

You can also blacklist modules from the bootloader.

You can also blacklist modules from the bootloader.

−

Simply add {{ic|1=modprobe.blacklist=modname1,modname2,modname3}} to your bootloader's kernel line, as described in [[Kernel_parameters#When_starting_the_kernel|Kernel Parameters]].

+

Simply add {{ic|1=modprobe.blacklist=modname1,modname2,modname3}} to your bootloader's kernel line, as described in [[Kernel parameters]].

{{Note|When you are blacklisting more than one module, note that they are separated by commas only. Spaces or anything else might presumably break the syntax.}}

{{Note|When you are blacklisting more than one module, note that they are separated by commas only. Spaces or anything else might presumably break the syntax.}}

Line 215:

Line 211:

brightness_switch_enabled=Y - brightness_switch_enabled: (bool)

brightness_switch_enabled=Y - brightness_switch_enabled: (bool)

use_bios_initial_backlight=Y - use_bios_initial_backlight: (bool)}}

use_bios_initial_backlight=Y - use_bios_initial_backlight: (bool)}}

+

+

+

The following is a variation of the previous function that includes a full description for each parameter. The output is formatted a little differently and uses more colors.

Overview

To create a kernel module, you can read The Linux Kernel Module Programming Guide. A module can be configured as built-in or loadable. To dynamically load or remove a module, it has to be configured as a loadable module in the kernel configuration (the line related to the module will therefore display the letter M).

Modules are stored in /usr/lib/modules/kernel_release. You can use the command uname -r to get your current kernel release version.

Note: Module names often use underscores (_) or dashes (-); however, those symbols are interchangeable, both when using the modprobe command and in configuration files in /etc/modprobe.d/.

Obtaining information

To show what kernel modules are currently loaded:

$ lsmod

To show information about a module:

$ modinfo module_name

To list the options that are set for a loaded module:

$ systool -v -m module_name

To display the comprehensive configuration of all the modules:

$ modprobe -c | less

To display the configuration of a particular module:

$ modprobe -c | grep module_name

List the dependencies of a module (or alias), including the module itself:

$ modprobe --show-depends module_name

Configuration

Today, all necessary module loading is handled automatically by udev, so if you do not want or need to use any out-of-tree kernel modules, there is no need to put modules that should be loaded at boot in any configuration file. However, there are cases where you might want to load an extra module during the boot process, or blacklist another one for your computer to function properly.

Loading

Extra kernel modules to be loaded during boot are configured as a static list in files under /etc/modules-load.d/. Each configuration file is named in the style of /etc/modules-load.d/<program>.conf. Configuration files simply contain a list of kernel module names to load, separated by newlines. Empty lines and lines whose first non-whitespace character is # or ; are ignored.

/etc/modules-load.d/virtio-net.conf

# Load virtio-net.ko at boot
virtio-net

See modules-load.d(5) for more details.

Setting module options

To pass a parameter to a kernel module, you can use a modprobe configuration file or use the kernel command line.

Using files in /etc/modprobe.d/

Files in /etc/modprobe.d/ directory can be used to pass module settings to udev, which will use modprobe to manage the loading of the modules during system boot. Configuration files in this directory can have any name, given that they end with the .conf extension. The syntax is:

Note: If any of the affected modules is loaded from the initramfs, then you will need to add the appropriate .conf file to FILES in /etc/mkinitcpio.conf or use the modconfhook, so that it will be included in the initramfs.

Using kernel command line

If the module is built into the kernel, you can also pass options to the module using the kernel command line. For all common bootloaders, the following syntax is correct:

Aliasing

Aliases are alternate names for a module. For example: alias my-mod really_long_modulename means you can use modprobe my-mod instead of modprobe really_long_modulename. You can also use shell-style wildcards, so alias my-mod* really_long_modulename means that modprobe my-mod-something has the same effect. Create an alias:

/etc/modprobe.d/myalias.conf

alias mymod really_long_module_name

Some modules have aliases which are used to automatically load them when they are needed by an application. Disabling these aliases can prevent automatic loading but will still allow the modules to be manually loaded.

/etc/modprobe.d/modprobe.conf

# Prevent Bluetooth autoload
alias net-pf-31 off

Blacklisting

Blacklisting, in the context of kernel modules, is a mechanism to prevent the kernel module from loading. This could be useful if, for example, the associated hardware is not needed, or if loading that module causes problems: for instance there may be two kernel modules that try to control the same piece of hardware, and loading them together would result in a conflict.

Some modules are loaded as part of the initramfs. mkinitcpio -M will print out all automatically detected modules: to prevent the initramfs from loading some of those modules, blacklist them in /etc/modprobe.d/modprobe.conf. Running mkinitcpio -v will list all modules pulled in by the various hooks (e.g. filesystems hook, block hook, etc.). Remember to add that .conf file to the FILES section in /etc/mkinitcpio.conf, if you have not done so already, and rebuild the initramfs once you have blacklisted the modules, and reboot afterwards.

Using files in /etc/modprobe.d/

Create a .conf file inside /etc/modprobe.d/ and append a line for each module you want to blacklist, using the blacklist keyword. If for example you want to prevent the pcspkr module from loading:

/etc/modprobe.d/nobeep.conf

# Do not load the 'pcspkr' module on boot.
blacklist pcspkr

Note: The blacklist command will blacklist a module so that it will not be loaded automatically, but the module may be loaded if another non-blacklisted module depends on it or if it is loaded manually.

However, there is a workaround for this behaviour; the install command instructs modprobe to run a custom command instead of inserting the module in the kernel as normal, so you can force the module to always fail loading with:

/etc/modprobe.d/blacklist.conf

...
install module_name /bin/false
...

This will effectively blacklist that module and any other that depends on it.

Using kernel command line

Tip: This can be very useful if a broken module makes it impossible to boot your system.

You can also blacklist modules from the bootloader.

Simply add modprobe.blacklist=modname1,modname2,modname3 to your bootloader's kernel line, as described in Kernel parameters.

Note: When you are blacklisting more than one module, note that they are separated by commas only. Spaces or anything else might presumably break the syntax.

Manual module handling

Kernel modules are handled by tools provided by kmod package. You can use these tools manually.

To load a module:

# modprobe module_name

To unload a module:

# modprobe -r module_name

Or, alternatively:

# rmmod module_name

Tips and tricks

Bash function to list module parameters

Here is a nice bash function to be run as root that will show a list of all the currently loaded modules and all of their parameters, including the current value of the parameter. It uses /proc/modules to retrieve the current list of loaded modules, then access the module file directly with modinfo to grab a description of the module and descriptions for each param (if available), finally it accesses the sysfs filesystem to grab the actual parameter names and currently loaded values.