summaryrefslogtreecommitdiff
path: root/en/hardware/network-cards.xml
diff options
context:
space:
mode:
Diffstat (limited to 'en/hardware/network-cards.xml')
-rw-r--r--en/hardware/network-cards.xml87
1 files changed, 2 insertions, 85 deletions
diff --git a/en/hardware/network-cards.xml b/en/hardware/network-cards.xml
index cd1b059ce..692d38202 100644
--- a/en/hardware/network-cards.xml
+++ b/en/hardware/network-cards.xml
@@ -13,40 +13,9 @@ should normally be loaded automatically.
PCMCIA/Express Cards on laptops.</phrase>
<phrase arch="i386">Many older ISA cards are supported as well.</phrase>
-</para><para arch="sparc">
-
-This includes a lot of generic PCI cards (for systems that have PCI) and
-the following NICs from Sun:
-
-<itemizedlist>
-<listitem><para>
-
-Sun LANCE
-
-</para></listitem>
-<listitem><para>
-
-Sun Happy Meal
-
-</para></listitem>
-<listitem><para>
-
-Sun BigMAC
-
-</para></listitem>
-<listitem><para>
-
-Sun QuadEthernet
-
-</para></listitem>
-<listitem><para>
-
-MyriCOM Gigabit Ethernet
-
-</para></listitem>
-</itemizedlist>
+</para>
-</para><para arch="s390">
+<para arch="s390">
The list of supported network devices is:
@@ -123,56 +92,4 @@ a Windows driver.</phrase>
</para>
</sect3>
- <sect3 arch="sparc" id="nics-sparc-trouble">
- <title>Known Issues for &arch-title;</title>
-<para>
-
-There are a couple of issues with specific network cards that are worth
-mentioning here.
-
-</para>
-
- <sect4><title>Conflict between tulip and dfme drivers</title>
-<!-- BTS: #334104; may also affect other arches, but most common on sparc -->
-<para>
-
-<!-- BTS: #334104; may also affect other arches, but most common on sparc -->
-There are various PCI network cards that have the same PCI identification,
-but are supported by related, but different drivers. Some cards work with
-the <literal>tulip</literal> driver, others with the <literal>dfme</literal>
-driver. Because they have the same identification, the kernel cannot
-distinguish between them and it is not certain which driver will be loaded.
-If this happens to be the wrong one, the NIC may not work, or work badly.
-
-</para><para>
-
-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"/>.
-
-</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>
- </sect4>
-
- <sect4><title>Sun B100 blade</title>
-<!-- BTS: #384549; should be checked for kernels >2.6.18 -->
-<para>
-
-The <literal>cassini</literal> network driver does not work with Sun B100
-blade systems.
-
-</para>
- </sect4>
- </sect3>
</sect2>