From 33bf629eef2697aa2845e32d3eab0bb87740d1f0 Mon Sep 17 00:00:00 2001 From: puneetse <22071208+puneetse@users.noreply.github.com> Date: Thu, 8 Nov 2018 16:43:37 -0800 Subject: [PATCH 1/8] Inital commit of kernel modules page A page describing kernel modules and loading out-of-tree kernel modules --- .../guides/maintenance/kernel-modules.rst | 186 ++++++++++++++++++ 1 file changed, 186 insertions(+) create mode 100644 source/clear-linux/guides/maintenance/kernel-modules.rst diff --git a/source/clear-linux/guides/maintenance/kernel-modules.rst b/source/clear-linux/guides/maintenance/kernel-modules.rst new file mode 100644 index 00000000..1dde5a8a --- /dev/null +++ b/source/clear-linux/guides/maintenance/kernel-modules.rst @@ -0,0 +1,186 @@ +.. _kernel-modules: + +Kernel Modules +############## +Kernel modules are additional pieces of software capable of interacting with +the kernel to add functionality, such as a hardware driver. Kernel modules +may already be part of the Linux source tree (in-tree) or may come from an +external source, such as a directly from vendor (out-of-tree). + +In many cases kernel modules are already available through |CL|. +In other cases, a kernel module may not exist but can be requested to be +enabled in the |CL| kernel. Finally, a situation may call for manually +building and loading out-of-tree kernels. + +.. contents:: :local: + :depth: 2 + + + +Adding a kernel module to a Clear Linux system +********************************************** +Using an existing module is significantly easier to maintain and retains +signature verification of the |CL| kernel. For more information on |CL| +security practices, see the :ref:`security` page. + + +Check if the module is already available through Clear Linux +=========================================================== +|CL| comes with many upstream kernel modules available for use. If +you require a kernel module, be sure to check whether it is already available in |CL| first. + + +You can search for kernel modules using the :command:`swupd search` command. +See :ref:`swupd-search` for more information. + + +Consider requesting the module be added to |CL| +=============================================== +If the kernel module you're needing is open source and likely to be useful to +others, consider submitting a request to add or enable to the |CL| kernel. + +You can make enhancement requests to the |CL| distribution `on GitHub`_ . + + + +Building and loading out-of-tree modules +======================================== +In some cases you may need an out-of-tree kernel module that is not able +to be made available through |CL|. + +.. note:: + + You can build and load out-of-tree kernel modules however secure boot must be + disabled, kernel module integrity checking must be disabled, and you are + responsible for building the module against new versions of the Linux kernel. + + Any time the kernel is upgraded on your Clear Linux system, you will + need to rebuild your out-of-tree modules. + + +This approach works well for individual development or testing. +For a more scalable and customizable approach, consider using the +`mixer tool`_ to provide a custom kernel and updates. + + +Building modules +---------------- + +#. From a |CL| system, ensure you are running the native kernel. + Currently only kernel-native bundle is enabled to build and load + out-of-tree modules + + .. code-block:: bash + + $ uname -r + 4.17.YY-XXX.native + + Ensure *.native* is in the kernel name + +#. Install the `linux-dev` bundle to obtain the kernel headers, which are + required for compiling kernel modules + + .. code-block:: bash + + sudo swupd bundle-add linux-dev + +#. Follow instructions from the kernel module source code to compile the + kernel module + + +Disable kernel and module signature verification +------------------------------------------------ + +#. Disable Secure Boot in your BIOS or EFI you have enabled it. The loading of + new out-of-tree modules modifies the signatures Secure Boot relies on for + trust. + + +#. Disable signature checking for the kernel by modifying the kernel boot + parameters and reboot the system. + + All kernel modules from |CL| have been signed to enforce kernel security. + However, out-of-tree modules break this chain of trust so this mechanism + needs to be disabled. + + .. code-block:: bash + + sudo mkdir -p /etc/kernel/cmdline.d + sudo echo “module.sig_unenforce” > /etc/kernel/cmdline.d/load-modules.conf + +#. Update the boot manager and reboot the system to implement the changed + kernel parameters. + + .. code-block:: bash + + sudo clr-boot-manager update + sudo reboot + + +#. After rebooting, out-of-tree modules can be manually loaded with + :command:`modprobe` command. + + .. code-block:: bash + + sudo modprobe ${module_name} + + + +Optional: Use `modprobe` to specify module options and aliases +-------------------------------------------------------------- + +The :command:`modprobe` command can be used to load a module and set options. + +Because :command:`modprobe` can add or remove more than one module, due to +modules having dependencies, a method of specifying what options are +to be used with individual modules is useful. This can be done with +configuration files under the :file:`/etc/modprobe.d` directory. + + .. code-block:: bash + + sudo mkdir /etc/modprobe.d + +All files underneath the :file:`/etc/modprobe.d` directory +which end with the :file:`.conf` extension specify module options to use when +loading. This can also be used to create convenient aliases for modules or +they can override the normal loading behavior altogether for those with +special requirements. + +You can find more info on module loading in the modprobe.d manual page: + + .. code-block:: bash + + man modprobe.d + + + +Optional: Configure kernel modules to load at boot +-------------------------------------------------- + +The :file:`/etc/modules-load.d` configuration directory can be used to +specify kernel modules that should be automatically loaded at boot. + + .. code-block:: bash + + sudo mkdir /etc/modules-load.d + + +All files underneath the :file:`/etc/modules-load.d` directory +which end with the :file:`.conf` extension contain a list of module names +of aliases (one per line) to load at boot. + + +You can find more info on module loading in the modprobe.d manual page: + + .. code-block:: bash + + man modules-load.d + + + + + + +.. _`on GitHub`: https://github.com/clearlinux/distribution +.. _`mixer tool`: https://clearlinux.org/features/mixer-tool + From 92b30e53496cfe2ec2d078756f29cec311031cc3 Mon Sep 17 00:00:00 2001 From: puneetse <22071208+puneetse@users.noreply.github.com> Date: Fri, 9 Nov 2018 14:18:38 -0800 Subject: [PATCH 2/8] Fix typo and misc header formatting changes --- .../guides/maintenance/kernel-modules.rst | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/source/clear-linux/guides/maintenance/kernel-modules.rst b/source/clear-linux/guides/maintenance/kernel-modules.rst index 1dde5a8a..8f397d34 100644 --- a/source/clear-linux/guides/maintenance/kernel-modules.rst +++ b/source/clear-linux/guides/maintenance/kernel-modules.rst @@ -25,7 +25,7 @@ security practices, see the :ref:`security` page. Check if the module is already available through Clear Linux -=========================================================== +============================================================ |CL| comes with many upstream kernel modules available for use. If you require a kernel module, be sure to check whether it is already available in |CL| first. @@ -63,17 +63,17 @@ For a more scalable and customizable approach, consider using the `mixer tool`_ to provide a custom kernel and updates. -Building modules ----------------- +Building kernel modules +----------------------- -#. From a |CL| system, ensure you are running the native kernel. - Currently only kernel-native bundle is enabled to build and load - out-of-tree modules +#. From a |CL| system, ensure you are running the *native* kernel. + Currently only the native kernel is enabled to build and load + out-of-tree modules. .. code-block:: bash $ uname -r - 4.17.YY-XXX.native + 4.XX.YY-ZZZZ.native Ensure *.native* is in the kernel name @@ -88,8 +88,8 @@ Building modules kernel module -Disable kernel and module signature verification ------------------------------------------------- +Loading kernel modules +---------------------- #. Disable Secure Boot in your BIOS or EFI you have enabled it. The loading of new out-of-tree modules modifies the signatures Secure Boot relies on for @@ -170,7 +170,7 @@ which end with the :file:`.conf` extension contain a list of module names of aliases (one per line) to load at boot. -You can find more info on module loading in the modprobe.d manual page: +You can find more info on module loading in the modules-load.d manual page: .. code-block:: bash From 68d078ee4c4a5bc92ecce5522d437674ac6fac35 Mon Sep 17 00:00:00 2001 From: puneetse <22071208+puneetse@users.noreply.github.com> Date: Fri, 9 Nov 2018 14:21:21 -0800 Subject: [PATCH 3/8] Fix silly quotes --- source/clear-linux/guides/maintenance/kernel-modules.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/clear-linux/guides/maintenance/kernel-modules.rst b/source/clear-linux/guides/maintenance/kernel-modules.rst index 8f397d34..58f0bce9 100644 --- a/source/clear-linux/guides/maintenance/kernel-modules.rst +++ b/source/clear-linux/guides/maintenance/kernel-modules.rst @@ -106,7 +106,7 @@ Loading kernel modules .. code-block:: bash sudo mkdir -p /etc/kernel/cmdline.d - sudo echo “module.sig_unenforce” > /etc/kernel/cmdline.d/load-modules.conf + sudo echo "module.sig_unenforce" > /etc/kernel/cmdline.d/load-modules.conf #. Update the boot manager and reboot the system to implement the changed kernel parameters. From ac4c4433051369341199b2b1cb54fd1a1e6555ae Mon Sep 17 00:00:00 2001 From: puneetse <22071208+puneetse@users.noreply.github.com> Date: Tue, 13 Nov 2018 17:39:56 -0800 Subject: [PATCH 4/8] Add kernel-modules to TOC --- source/clear-linux/guides/maintenance/maintenance.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/source/clear-linux/guides/maintenance/maintenance.rst b/source/clear-linux/guides/maintenance/maintenance.rst index 712e3844..d03b02b8 100644 --- a/source/clear-linux/guides/maintenance/maintenance.rst +++ b/source/clear-linux/guides/maintenance/maintenance.rst @@ -15,6 +15,7 @@ completed. enable-user-space swupd-guide bulk-provision + kernel-modules mixer mixin validate-signatures From 54f7bb9c10d2205a48672b05226f18def1a41f12 Mon Sep 17 00:00:00 2001 From: puneetse <22071208+puneetse@users.noreply.github.com> Date: Wed, 14 Nov 2018 13:52:45 -0800 Subject: [PATCH 5/8] Revised with suggestions from @bwarden and @miguelinux --- .../guides/maintenance/kernel-modules.rst | 34 +++++++++++-------- 1 file changed, 20 insertions(+), 14 deletions(-) diff --git a/source/clear-linux/guides/maintenance/kernel-modules.rst b/source/clear-linux/guides/maintenance/kernel-modules.rst index 58f0bce9..94a7842e 100644 --- a/source/clear-linux/guides/maintenance/kernel-modules.rst +++ b/source/clear-linux/guides/maintenance/kernel-modules.rst @@ -2,15 +2,15 @@ Kernel Modules ############## -Kernel modules are additional pieces of software capable of interacting with -the kernel to add functionality, such as a hardware driver. Kernel modules -may already be part of the Linux source tree (in-tree) or may come from an -external source, such as a directly from vendor (out-of-tree). +Kernel modules are additional pieces of software capable of being inserted +into the Linux kernel to add functionality, such as a hardware driver. +Kernel modules may already be part of the Linux source tree (in-tree) or may +come from an external source, such as a directly from vendor (out-of-tree). In many cases kernel modules are already available through |CL|. In other cases, a kernel module may not exist but can be requested to be enabled in the |CL| kernel. Finally, a situation may call for manually -building and loading out-of-tree kernels. +building and loading out-of-tree kernel modules. .. contents:: :local: :depth: 2 @@ -30,14 +30,17 @@ Check if the module is already available through Clear Linux you require a kernel module, be sure to check whether it is already available in |CL| first. -You can search for kernel modules using the :command:`swupd search` command. +You can search for kernel module file names, which end with the :file:`.ko` +file extension, using the :command:`swupd search` command. For example: +:command:`sudo swupd search ${module_name}.ko`. See :ref:`swupd-search` for more information. Consider requesting the module be added to |CL| =============================================== -If the kernel module you're needing is open source and likely to be useful to -others, consider submitting a request to add or enable to the |CL| kernel. +If the kernel module you're needing is already already open source +(e.g. in the Linux upstream) and likely to be useful to others, +consider submitting a request to add or enable to the |CL| kernel. You can make enhancement requests to the |CL| distribution `on GitHub`_ . @@ -91,9 +94,9 @@ Building kernel modules Loading kernel modules ---------------------- -#. Disable Secure Boot in your BIOS or EFI you have enabled it. The loading of - new out-of-tree modules modifies the signatures Secure Boot relies on for - trust. +#. Disable Secure Boot in your system's UEFI settings, if you have enabled it. + The loading of new out-of-tree modules modifies the signatures Secure Boot + relies on for trust. #. Disable signature checking for the kernel by modifying the kernel boot @@ -106,7 +109,7 @@ Loading kernel modules .. code-block:: bash sudo mkdir -p /etc/kernel/cmdline.d - sudo echo "module.sig_unenforce" > /etc/kernel/cmdline.d/load-modules.conf + echo "module.sig_unenforce" | sudo tee /etc/kernel/cmdline.d/allow-unsigned-modules.conf #. Update the boot manager and reboot the system to implement the changed kernel parameters. @@ -116,13 +119,16 @@ Loading kernel modules sudo clr-boot-manager update sudo reboot + .. note:: + The :command:`clr-boot-manager update` command does not return any console output if success. + #. After rebooting, out-of-tree modules can be manually loaded with - :command:`modprobe` command. + :command:`insmod` command. .. code-block:: bash - sudo modprobe ${module_name} + sudo insmod ${path_to_module} From 6c900602eb884115ae343b922a13bbbff8f230ce Mon Sep 17 00:00:00 2001 From: puneetse <22071208+puneetse@users.noreply.github.com> Date: Fri, 16 Nov 2018 10:22:35 -0800 Subject: [PATCH 6/8] Add a sentence to end of intro Add a sentence to end of intro to complete describe the contents of te doucment and better transition --- source/clear-linux/guides/maintenance/kernel-modules.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/source/clear-linux/guides/maintenance/kernel-modules.rst b/source/clear-linux/guides/maintenance/kernel-modules.rst index 94a7842e..92623caf 100644 --- a/source/clear-linux/guides/maintenance/kernel-modules.rst +++ b/source/clear-linux/guides/maintenance/kernel-modules.rst @@ -7,10 +7,13 @@ into the Linux kernel to add functionality, such as a hardware driver. Kernel modules may already be part of the Linux source tree (in-tree) or may come from an external source, such as a directly from vendor (out-of-tree). -In many cases kernel modules are already available through |CL|. +In many cases kernel modules are already available through |CL-ATTR|. In other cases, a kernel module may not exist but can be requested to be enabled in the |CL| kernel. Finally, a situation may call for manually building and loading out-of-tree kernel modules. +The document will describe evaluating each of these scenarios. + + .. contents:: :local: :depth: 2 From 03b01078291e2859f7b4a4e1ae2d0b32ff223483 Mon Sep 17 00:00:00 2001 From: Kevin Putnam Date: Tue, 27 Nov 2018 10:55:03 -0800 Subject: [PATCH 7/8] Updates to titles and content --- .../guides/maintenance/kernel-modules.rst | 132 ++++++++---------- 1 file changed, 56 insertions(+), 76 deletions(-) diff --git a/source/clear-linux/guides/maintenance/kernel-modules.rst b/source/clear-linux/guides/maintenance/kernel-modules.rst index 92623caf..569db618 100644 --- a/source/clear-linux/guides/maintenance/kernel-modules.rst +++ b/source/clear-linux/guides/maintenance/kernel-modules.rst @@ -1,105 +1,94 @@ .. _kernel-modules: -Kernel Modules -############## +Add Kernel Modules +################## + Kernel modules are additional pieces of software capable of being inserted into the Linux kernel to add functionality, such as a hardware driver. Kernel modules may already be part of the Linux source tree (in-tree) or may come from an external source, such as a directly from vendor (out-of-tree). -In many cases kernel modules are already available through |CL-ATTR|. -In other cases, a kernel module may not exist but can be requested to be -enabled in the |CL| kernel. Finally, a situation may call for manually -building and loading out-of-tree kernel modules. -The document will describe evaluating each of these scenarios. - - +In cases where drivers beyond those enabled by default in |CL-ATTR| are +needed it may be necessary to: .. contents:: :local: - :depth: 2 + :depth: 1 + :backlinks: top +Check if the module is available through |CL| +============================================= - -Adding a kernel module to a Clear Linux system -********************************************** Using an existing module is significantly easier to maintain and retains signature verification of the |CL| kernel. For more information on |CL| security practices, see the :ref:`security` page. - -Check if the module is already available through Clear Linux -============================================================ |CL| comes with many upstream kernel modules available for use. If you require a kernel module, be sure to check whether it is already available in |CL| first. - You can search for kernel module file names, which end with the :file:`.ko` file extension, using the :command:`swupd search` command. For example: :command:`sudo swupd search ${module_name}.ko`. See :ref:`swupd-search` for more information. +Request the module be added to |CL| +=================================== -Consider requesting the module be added to |CL| -=============================================== -If the kernel module you're needing is already already open source +If the kernel module you need is already already open source (e.g. in the Linux upstream) and likely to be useful to others, -consider submitting a request to add or enable to the |CL| kernel. +consider submitting a request to add or enable in the |CL| kernel. -You can make enhancement requests to the |CL| distribution `on GitHub`_ . +Make enhancement requests to the |CL| distribution `on GitHub`_ . +Build and load an out-of-tree module +==================================== +In some cases you may need an out-of-tree kernel module that is not +available through |CL|. -Building and loading out-of-tree modules -======================================== -In some cases you may need an out-of-tree kernel module that is not able -to be made available through |CL|. +You can build and load out-of-tree kernel modules, however secure boot +must be disabled, kernel module integrity checking must be disabled, and +you are responsible for building the module against new versions of the +Linux kernel. .. note:: - You can build and load out-of-tree kernel modules however secure boot must be - disabled, kernel module integrity checking must be disabled, and you are - responsible for building the module against new versions of the Linux kernel. - Any time the kernel is upgraded on your Clear Linux system, you will need to rebuild your out-of-tree modules. - This approach works well for individual development or testing. For a more scalable and customizable approach, consider using the `mixer tool`_ to provide a custom kernel and updates. - -Building kernel modules ------------------------ +Build kernel module +------------------- #. From a |CL| system, ensure you are running the *native* kernel. Currently only the native kernel is enabled to build and load out-of-tree modules. - .. code-block:: bash + .. code-block:: bash - $ uname -r - 4.XX.YY-ZZZZ.native - - Ensure *.native* is in the kernel name + $ uname -r + 4.XX.YY-ZZZZ.native + # Ensure *.native* is in the kernel name #. Install the `linux-dev` bundle to obtain the kernel headers, which are required for compiling kernel modules - .. code-block:: bash + .. code-block:: bash - sudo swupd bundle-add linux-dev + sudo swupd bundle-add linux-dev #. Follow instructions from the kernel module source code to compile the kernel module -Loading kernel modules ----------------------- +Load kernel module +------------------ -#. Disable Secure Boot in your system's UEFI settings, if you have enabled it. - The loading of new out-of-tree modules modifies the signatures Secure Boot - relies on for trust. +#. Disable Secure Boot in your system's UEFI settings, if you have enabled + it. The loading of new out-of-tree modules modifies the signatures Secure + Boot relies on for trust. #. Disable signature checking for the kernel by modifying the kernel boot @@ -109,45 +98,46 @@ Loading kernel modules However, out-of-tree modules break this chain of trust so this mechanism needs to be disabled. - .. code-block:: bash + .. code-block:: bash - sudo mkdir -p /etc/kernel/cmdline.d - echo "module.sig_unenforce" | sudo tee /etc/kernel/cmdline.d/allow-unsigned-modules.conf + sudo mkdir -p /etc/kernel/cmdline.d + echo "module.sig_unenforce" | sudo tee /etc/kernel/cmdline.d/allow-unsigned-modules.conf #. Update the boot manager and reboot the system to implement the changed kernel parameters. - .. code-block:: bash + .. code-block:: bash sudo clr-boot-manager update sudo reboot - .. note:: - The :command:`clr-boot-manager update` command does not return any console output if success. + .. note:: + + :command:`clr-boot-manager update` does not return any + console output if successful. #. After rebooting, out-of-tree modules can be manually loaded with - :command:`insmod` command. + :command:`insmod`. - .. code-block:: bash - - sudo insmod ${path_to_module} + .. code-block:: bash + sudo insmod ${path_to_module} Optional: Use `modprobe` to specify module options and aliases -------------------------------------------------------------- -The :command:`modprobe` command can be used to load a module and set options. +Use :command:`modprobe` to load a module and set options. Because :command:`modprobe` can add or remove more than one module, due to modules having dependencies, a method of specifying what options are to be used with individual modules is useful. This can be done with configuration files under the :file:`/etc/modprobe.d` directory. - .. code-block:: bash +.. code-block:: bash - sudo mkdir /etc/modprobe.d + sudo mkdir /etc/modprobe.d All files underneath the :file:`/etc/modprobe.d` directory which end with the :file:`.conf` extension specify module options to use when @@ -157,11 +147,9 @@ special requirements. You can find more info on module loading in the modprobe.d manual page: - .. code-block:: bash - - man modprobe.d - +.. code-block:: bash + man modprobe.d Optional: Configure kernel modules to load at boot -------------------------------------------------- @@ -169,27 +157,19 @@ Optional: Configure kernel modules to load at boot The :file:`/etc/modules-load.d` configuration directory can be used to specify kernel modules that should be automatically loaded at boot. - .. code-block:: bash - - sudo mkdir /etc/modules-load.d +.. code-block:: bash + sudo mkdir /etc/modules-load.d All files underneath the :file:`/etc/modules-load.d` directory which end with the :file:`.conf` extension contain a list of module names of aliases (one per line) to load at boot. - You can find more info on module loading in the modules-load.d manual page: - .. code-block:: bash - - man modules-load.d - - - - +.. code-block:: bash + man modules-load.d .. _`on GitHub`: https://github.com/clearlinux/distribution -.. _`mixer tool`: https://clearlinux.org/features/mixer-tool - +.. _`mixer tool`: https://clearlinux.org/features/mixer-tool \ No newline at end of file From 77f5c1594adb2c34cead56f24f6e94716302dfac Mon Sep 17 00:00:00 2001 From: Kevin Putnam Date: Tue, 27 Nov 2018 12:01:52 -0800 Subject: [PATCH 8/8] fixed grammar and wording --- .../guides/maintenance/kernel-modules.rst | 27 ++++++++++--------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/source/clear-linux/guides/maintenance/kernel-modules.rst b/source/clear-linux/guides/maintenance/kernel-modules.rst index 569db618..5390f554 100644 --- a/source/clear-linux/guides/maintenance/kernel-modules.rst +++ b/source/clear-linux/guides/maintenance/kernel-modules.rst @@ -1,12 +1,12 @@ .. _kernel-modules: -Add Kernel Modules +Add kernel modules ################## Kernel modules are additional pieces of software capable of being inserted into the Linux kernel to add functionality, such as a hardware driver. Kernel modules may already be part of the Linux source tree (in-tree) or may -come from an external source, such as a directly from vendor (out-of-tree). +come from an external source, such as directly from a vendor (out-of-tree). In cases where drivers beyond those enabled by default in |CL-ATTR| are needed it may be necessary to: @@ -33,7 +33,7 @@ See :ref:`swupd-search` for more information. Request the module be added to |CL| =================================== -If the kernel module you need is already already open source +If the kernel module you need is already open source (e.g. in the Linux upstream) and likely to be useful to others, consider submitting a request to add or enable in the |CL| kernel. @@ -45,10 +45,11 @@ Build and load an out-of-tree module In some cases you may need an out-of-tree kernel module that is not available through |CL|. -You can build and load out-of-tree kernel modules, however secure boot -must be disabled, kernel module integrity checking must be disabled, and -you are responsible for building the module against new versions of the -Linux kernel. +You can build and load out-of-tree kernel modules, however you must: + +* disable secure boot +* disable kernel module integrity checking +* build the module against new versions of the Linux kernel .. note:: @@ -73,14 +74,14 @@ Build kernel module # Ensure *.native* is in the kernel name #. Install the `linux-dev` bundle to obtain the kernel headers, which are - required for compiling kernel modules + required for compiling kernel modules. .. code-block:: bash sudo swupd bundle-add linux-dev #. Follow instructions from the kernel module source code to compile the - kernel module + kernel module. Load kernel module @@ -140,7 +141,7 @@ configuration files under the :file:`/etc/modprobe.d` directory. sudo mkdir /etc/modprobe.d All files underneath the :file:`/etc/modprobe.d` directory -which end with the :file:`.conf` extension specify module options to use when +that end with the :file:`.conf` extension specify module options to use when loading. This can also be used to create convenient aliases for modules or they can override the normal loading behavior altogether for those with special requirements. @@ -154,15 +155,15 @@ You can find more info on module loading in the modprobe.d manual page: Optional: Configure kernel modules to load at boot -------------------------------------------------- -The :file:`/etc/modules-load.d` configuration directory can be used to -specify kernel modules that should be automatically loaded at boot. +Use the :file:`/etc/modules-load.d` configuration directory to +specify kernel modules to load automatically at boot. .. code-block:: bash sudo mkdir /etc/modules-load.d All files underneath the :file:`/etc/modules-load.d` directory -which end with the :file:`.conf` extension contain a list of module names +that end with the :file:`.conf` extension contain a list of module names of aliases (one per line) to load at boot. You can find more info on module loading in the modules-load.d manual page: