Kernel module

From ArchWiki
Revision as of 10:22, 2 July 2011 by Gadget3000 (talk | contribs) (Options)
Jump to navigation Jump to search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

This article covers the various methods for operating with kernel modules.


Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Kernel module#)

For a module to be recognized as such, it has to be compiled as a module in the kernel configuration (the line related to the module will therefore display the letter M).

Modules are stored in Template:Filename (use the command Template:Codeline to print your current kernel release).

The Template:Codeline command handles the addition and removal of modules from the Linux kernel.

The Template:Filename directory can be used to pass module settings to udev, which will use Template:Codeline to manage the loading of the modules during system boot. You can use configuration files with any name in the directory, given that they end with the Template:Filename extension. It is not recommended to use the Template:Filename file, since it will be likely deprecated in the future (see Template:Codeline).

Note: Module names often use underscores ("_") or dashes ("-"), however those symbols are interchangeable both when using the Template:Codeline command and in configuration files in Template:Filename.


To manually load (or add) a module, run:

# modprobe module_name

For informations on loading modules automatically at system boot, see rc.conf.


Occasionally you could need to remove (or unload) a module; in this case use the following command:

# modprobe -r module_name

Or, alternatively:

# rmmod module_name


If you want to display the comprehensive configuration of all the modules you can use the command:

$ modprobe -c 

Since the output of that command will probably turn out to be very long, you should better page it with:

$ modprobe -c | more

To display the configuration of a particular module, use:

$ modprobe -c | grep module_name


To pass a parameter to a kernel module, you can use a modprobe conf file.

Using files in Template:Filename

To pass options to a modulle using modprobe config files, a .conf file with any name (you can even use modprobe.conf) needs to be placed in /etc/modprobe.d/ with this syntax: Template:File for example: Template:File


Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Kernel module#)



Blacklisting, when referring to Kernel modules, is a mechanism to prevent the kernel module from loading. This could be useful if for example the associated hardware is not required to be used, 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. Template:Codeline will print out all autodetected modules: to prevent initramfs from loading some of those modules, blacklist them in Template:Filename. Running Template:Codeline will list all modules pulled in by the various hooks (e.g. filesystem hook, SCSI hook, etc.). Remember to rebuild initramfs once you have blacklisted the modules.

Tip: A clearer list of all autodetected modules can be obtained with:
mkinitcpio -M | sed 1d | sort -u
Warning: Blacklisting modules in rc.conf has been obsoleted and no longer works in initscripts 2011.06.1-1, so you'll have to use one of the following methods.

Using files in Template:Filename

Create a Template:Filename file inside Template:Filename and append a line for each module you want to blacklist, using the Template:Codeline keyword. If for example you want to prevent the Template:Codeline module from loading:


Note: The Template:Codeline command will blacklist a module so that it will not be loaded automatically, but 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 Template:Codeline 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:


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

Using kernel command line

Tip: This is useful in an emergency where a broken module makes it impossible to boot your system.

You can also blacklist modules on the kernel command line (e.g. in GRUB, LILO or Syslinux) using the following syntax:




Examples using GRUB




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:
$ lsmod
$ modinfo MODULE_1
$ modprobe --show-depends MODULE_2

See also