summaryrefslogtreecommitdiff
path: root/en
diff options
context:
space:
mode:
Diffstat (limited to 'en')
-rw-r--r--en/hardware/network-cards.xml10
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>