diff options
| author | Frans Pop <elendil@planet.nl> | 2007-08-19 16:12:27 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2007-08-19 16:12:27 +0000 |
| commit | dd80f0962ce039272f59630f91f8bf2b681b965b (patch) | |
| tree | ad8d4c6ef25fb184eeb168e4a93ce5610cc1f33a /nl/hardware | |
| parent | 20fa74d11ec37811e10aa874d07d35bcceaa5550 (diff) | |
| download | installation-guide-dd80f0962ce039272f59630f91f8bf2b681b965b.zip | |
Update untranslated documents
Diffstat (limited to 'nl/hardware')
| -rw-r--r-- | nl/hardware/network-cards.xml | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/nl/hardware/network-cards.xml b/nl/hardware/network-cards.xml index 87dff40bc..dc50402bb 100644 --- a/nl/hardware/network-cards.xml +++ b/nl/hardware/network-cards.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 43693 untranslated --> +<!-- original version: 48981 untranslated --> <sect1 id="network-cards"> <title>Network Connectivity Hardware</title> @@ -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> |