Show Table of Contents
31.6.2. Loading a Customized Module - Persistent Changes
If you want to ensure that a kernel module is always loaded with specific settings, modify an existing or newly-created file in the
/etc/modprobe.d/ directory with a line in the following format.
~]# options <module_name> [parameter=value]
where [parameter=value] represents a list of customized parameters available to that module.
The following procedure illustrates the recommended steps for loading a kernel module with custom parameters on the
b43 module for Open Firmware for wireless networks, ensuring that changes persist between module reloads.
Procedure 31.2. Loading a Kernel Module with Custom Parameters - Persistent Changes
- Add the following line to the
/etc/modprobe.d/openfwwf.conffile, which ensures that theb43module is always loaded with QoS and hardware-accelerated cryptography disabled:options b43 nohwcrypt=1 qos=0 - Verify whether the module is not already loaded into the kernel by running the following command:
~]# lsmod|grep ^b43 ~]#
Note that the output of the command in this example indicates that the module is currently not loaded into the kernel. - If the module is already loaded into the kernel, you must unload the module and all its dependencies before proceeding with the next step. See Section 31.4, “Unloading a Module” for instructions on how to safely unload it.
- Load the
b43module by running the following command:~]#
modprobe b43
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.