diff options
| author | Frans Pop <elendil@planet.nl> | 2007-08-19 07:21:15 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2007-08-19 07:21:15 +0000 |
| commit | 20fa74d11ec37811e10aa874d07d35bcceaa5550 (patch) | |
| tree | 1c421297b7d8dd8da17171a3513039958a38abc6 /en/hardware | |
| parent | d293dddb1a4b2448273a963aaf32df287efbc5d8 (diff) | |
| download | installation-guide-20fa74d11ec37811e10aa874d07d35bcceaa5550.zip | |
Mention blacklisting of the wrong module as the preferred solution
Diffstat (limited to 'en/hardware')
| -rw-r--r-- | en/hardware/network-cards.xml | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/en/hardware/network-cards.xml b/en/hardware/network-cards.xml index 9d0499d4e..3fc5d69bb 100644 --- a/en/hardware/network-cards.xml +++ b/en/hardware/network-cards.xml @@ -180,12 +180,18 @@ If this happens to be the wrong one, the NIC may not work, or work badly. This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. +You can prevent this issue by blacklisting the wrong driver module as +described in <xref linkend="module-blacklist"/>. -During the installation the solution is to switch to a shell and unload the -wrong driver module using +</para><para> + +An alternative solution during the installation is to switch to a shell +and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. +Note that the wrong module may then still be loaded when the system is +rebooted. </para> </sect3> |