summaryrefslogtreecommitdiff
path: root/nl/boot-installer/parameters.xml
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2007-01-06 20:09:48 +0000
committerFrans Pop <elendil@planet.nl>2007-01-06 20:09:48 +0000
commit647535722c848a87e1753ac99ab30343af451811 (patch)
tree0eb074f5de4695d7ebe16f74d844122119fcdbe2 /nl/boot-installer/parameters.xml
parent5a0523f29e8a55e8b888f2b8b2d1b23e9b8c731b (diff)
downloadinstallation-guide-647535722c848a87e1753ac99ab30343af451811.zip
Update of untranslated files
Diffstat (limited to 'nl/boot-installer/parameters.xml')
-rw-r--r--nl/boot-installer/parameters.xml34
1 files changed, 32 insertions, 2 deletions
diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml
index 8d4826bda..1259462c8 100644
--- a/nl/boot-installer/parameters.xml
+++ b/nl/boot-installer/parameters.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 43730 untranslated -->
+<!-- original version: 43912 untranslated -->
<sect1 id="boot-parms"><title>Boot Parameters</title>
<para>
@@ -471,7 +471,8 @@ See <xref linkend="pkgsel"/> for additional information.
</sect3>
- <sect3 id="module-parms"><title>Passing parameters to kernel modules</title>
+ <sect3 id="module-parms">
+ <title>Passing parameters to kernel modules</title>
<para>
If drivers are compiled into the kernel, you can pass parameters to them
@@ -510,5 +511,34 @@ to use the BNC (coax) connector and IRQ 10, you would pass:
</para>
</sect3>
+
+ <sect3 id="module-blacklist">
+ <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>
</sect1>