From 647535722c848a87e1753ac99ab30343af451811 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Sat, 6 Jan 2007 20:09:48 +0000 Subject: Update of untranslated files --- nl/boot-installer/parameters.xml | 34 ++++++++++++++++++++++++++++++++-- 1 file changed, 32 insertions(+), 2 deletions(-) (limited to 'nl/boot-installer/parameters.xml') 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 @@ - + Boot Parameters @@ -471,7 +471,8 @@ See for additional information. - Passing parameters to kernel modules + + Passing parameters to kernel modules If drivers are compiled into the kernel, you can pass parameters to them @@ -508,6 +509,35 @@ to use the BNC (coax) connector and IRQ 10, you would pass: 3c509.xcvr=3 3c509.irq=10 + + + + + Blacklisting kernel modules + + +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. + + + +You can blacklist a module using the following syntax: +module_name.blacklist=yes. +This will cause the module to be blacklisted in +/etc/modprobe.d/blacklist.local both during the +installation and for the installed system. + + + +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. + -- cgit v1.2.3