From 69611d4d725fb13a0f812ee9adaea45d4aa80c19 Mon Sep 17 00:00:00 2001
From: Frans Pop <elendil@planet.nl>
Date: Sat, 6 Jan 2007 09:22:54 +0000
Subject: Document new option to blacklist kernel modules

---
 en/boot-installer/parameters.xml | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

(limited to 'en/boot-installer')

diff --git a/en/boot-installer/parameters.xml b/en/boot-installer/parameters.xml
index 58667cb6d..f216eba28 100644
--- a/en/boot-installer/parameters.xml
+++ b/en/boot-installer/parameters.xml
@@ -508,6 +508,34 @@ to use the BNC (coax) connector and IRQ 10, you would pass:
 3c509.xcvr=3 3c509.irq=10
 </screen></informalexample>
 
+</para>
+   </sect3>
+
+   <sect3 id="module-parms"><title>Blacklisting kernel modules</title>
+<para>
+
+Sometimes it may be necessary to blacklist a module to prevent it from
+being loaded automatically by the kernel and udev. One reason could be that
+a particular module causes problems with your hardware. The kernel also
+sometimes lists two different drivers for the same device. This can cause
+the device to not work correctly if the drivers conflict or if the wrong
+driver is loaded first.
+
+</para><para>
+
+You can blacklist a module using the following syntax:
+<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>.
+This will cause the module to be blacklisted in
+<filename>/etc/modprobe.d/blacklist.local</filename> both during the
+installation and for the installed system.
+
+</para><para>
+
+Note that a module may still be loaded by the installation system itself.
+You can prevent that from happening by running the installation in expert
+mode and unselecting the module from the list of modules displayed during
+the hardware detection phases.
+
 </para>
    </sect3>
   </sect2>
-- 
cgit v1.2.3