modules-load.d(5) — Linux manual page


MODULES-LOAD.D(5)            modules-load.d            MODULES-LOAD.D(5)

NAME         top

       modules-load.d - Configure kernel modules to load at boot

SYNOPSIS         top


DESCRIPTION         top

       systemd-modules-load.service(8) reads files from the above
       directories which contain kernel modules to load during boot in a
       static list. Each configuration file is named in the style of
       /etc/modules-load.d/program.conf. Note that it is usually a
       better idea to rely on the automatic module loading by PCI IDs,
       USB IDs, DMI IDs or similar triggers encoded in the kernel
       modules themselves instead of static configuration like this. In
       fact, most modern kernel modules are prepared for automatic
       loading already.


       The configuration files should 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.


       Configuration files are read from directories in /etc/, /run/,
       /usr/local/lib/, and /usr/lib/, in order of precedence, as listed
       in the SYNOPSIS section above. Files must have the ".conf"
       extension. Files in /etc/ override files with the same name in
       /run/, /usr/local/lib/, and /usr/lib/. Files in /run/ override
       files with the same name under /usr/.

       All configuration files are sorted by their filename in
       lexicographic order, regardless of which of the directories they
       reside in. If multiple files specify the same option, the entry
       in the file with the lexicographically latest name will take
       precedence. Thus, the configuration in a certain file may either
       be replaced completely (by placing a file with the same name in a
       directory with higher priority), or individual settings might be
       changed (by specifying additional settings in a file with a
       different name that is ordered later).

       Packages should install their configuration files in /usr/lib/
       (distribution packages) or /usr/local/lib/ (local installs).
       Files in /etc/ are reserved for the local administrator, who may
       use this logic to override the configuration files installed by
       vendor packages. It is recommended to prefix all filenames with a
       two-digit number and a dash, to simplify the ordering of the

       If the administrator wants to disable a configuration file
       supplied by the vendor, the recommended way is to place a symlink
       to /dev/null in the configuration directory in /etc/, with the
       same filename as the vendor configuration file. If the vendor
       configuration file is included in the initrd image, the image has
       to be regenerated.

EXAMPLE         top

       Example 1. /etc/modules-load.d/virtio-net.conf example:

           # Load virtio-net.ko at boot

SEE ALSO         top

       systemd(1), systemd-modules-load.service(8), systemd-delta(1),

COLOPHON         top

       This page is part of the systemd (systemd system and service
       manager) project.  Information about the project can be found at
       ⟨⟩.  If you have
       a bug report for this manual page, see
       This page was obtained from the project's upstream Git repository
       ⟨⟩ on 2023-12-22.  (At that
       time, the date of the most recent commit that was found in the
       repository was 2023-12-22.)  If you discover any rendering
       problems in this HTML version of the page, or you believe there
       is a better or more up-to-date source for the page, or you have
       corrections or improvements to the information in this COLOPHON
       (which is not part of the original manual page), send a mail to

systemd 255                                            MODULES-LOAD.D(5)

Pages that refer to this page: sysctl.d(5)systemd.directives(7)systemd.index(7)systemd-modules-load.service(8)