systemd-modules-load.service(8) [v7 man page]

SYSTEMD-MODULES-LOAD.SERVICE(8) 			   systemd-modules-load.service 			   SYSTEMD-MODULES-LOAD.SERVICE(8)

NAME

       systemd-modules-load.service, systemd-modules-load - Load kernel modules at boot

SYNOPSIS

       systemd-modules-load.service

       /lib/systemd/systemd-modules-load

DESCRIPTION

       systemd-modules-load.service is an early boot service that loads kernel modules based on static configuration.

       See modules-load.d(5) for information about the configuration of this service.

KERNEL COMMAND LINE

       systemd-modules-load.service understands the following kernel command line parameters:

       modules_load=, rd.modules_load=
	   Takes a comma-separated list of kernel modules to statically load during early boot. The option prefixed with "rd."	is read by the
	   initial RAM disk only.

SEE ALSO

       systemd(1), modules-load.d(5),

systemd 237													   SYSTEMD-MODULES-LOAD.SERVICE(8)

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

NAME

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

SYNOPSIS

       /etc/modules-load.d/*.conf

       /run/modules-load.d/*.conf

       /usr/lib/modules-load.d/*.conf

DESCRIPTION

       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.

CONFIGURATION FORMAT

       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.

       Each configuration file shall be named in the style of program.conf. Files in /etc/ override files with the same name in /usr/lib/ and
       /run/. Files in /run/ override files with the same name in /usr/lib/. Packages should install their configuration files in /usr/lib/, files
       in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed from vendor
       packages.

       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 /etc/modules-load.d/ bearing the same filename.

EXAMPLE

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

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

SEE ALSO

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

systemd 208															 MODULES-LOAD.D(5)