Kernel module

From ArchWiki
Revision as of 19:42, 9 June 2011 by Kynikos (talk | contribs) ({{Codeline|/sbin/modprobe}}: content taken from the Italian article; reorganized sections according to the action performed instead of the command used)
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 – فارسی

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#)

This article will cover the methods for managing kernel modules.


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.


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

# modprobe module_name


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


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).



Blacklisting modules

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.

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.

Note: 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 these methods.

Using files in Template:Filename

You can blacklist modules using the Template:Codeline keyword:


Alternatively, one can force nothing to be installed to "blacklist" that module and any that depend on it:


Using kernel command line

You can also blacklist modules on the kernel command line using the following syntax:


For example using GRUB:






The Template:Codeline 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.


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