![]() ![]() # modprobe module_name parameter_name=parameter_value Using files in /etc/modprobe.d/įiles 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. Parameters are specified on command line using simple key=value assignments: The basic way to pass parameters to a module is using the modprobe command. If the module is built into the kernel, the kernel command line must be used and other methods will not work. To pass a parameter to a kernel module, you can pass them manually with modprobe or assure certain parameters are always applied using a modprobe configuration file or by using the kernel command line. # rmmod module_name Setting module options one that is not installed in /usr/lib/modules/$(uname -r)/): Check manually if this path exists when modprobe failed to determine if this is the case. Note: If you have upgraded your kernel but have not yet rebooted, modprobe will fail with no error message and exit with code 1, because the path /usr/lib/modules/$(uname -r)/ no longer exists. Kernel modules are handled by tools provided by kmod package. booster: see Booster#Early module loading.dracut: see Dracut#Early kernel module loading.Early module loading depend on the initramfs generator used: The initramfs image may not contain the kernel modules asked for in /etc/modules-load.d/, it also may lack the files that have been set in that folder. etc/modules-load.d/nf # Load virtio_net.ko at boot Empty lines and lines whose first non-whitespace character is # or are ignored. Configuration files simply contain a list of kernel modules names to load, separated by newlines. Each configuration file is named in the style of /etc/modules-load.d/ nf. Kernel modules can be explicitly listed in files under /etc/modules-load.d/ for systemd to load them during boot. 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 modules loading is handled automatically by udev, so if you do not 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. $ modprobe -show-depends module_name Automatic module loading List the dependencies of a module (or alias), including the module itself: To display the configuration of a particular module: To display the comprehensive configuration of all the modules: To list the options that are set for a loaded module: To show what kernel modules are currently loaded: Note: Module names often use underscores ( _) or dashes ( -) however, those symbols are interchangeable when using the modprobe command and in configuration files in /etc/modprobe.d/.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |