1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
|
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->
<sect2 id="network-cards">
<title>Network Connectivity Hardware</title>
<para>
Almost any network interface card (NIC) supported by the Linux kernel
should also be supported by the installation system; modular drivers
should normally be loaded automatically.
<phrase arch="x86">This includes most PCI and PCMCIA cards.</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 arch="s390">
The list of supported network devices is:
<itemizedlist>
<listitem><para>
Channel to Channel (CTC) and ESCON connection (real or emulated)
</para></listitem>
<listitem><para>
OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)
</para></listitem>
<listitem><para>
OSA-Express in QDIO mode, HiperSockets and Guest-LANs
</para></listitem>
</itemizedlist>
</para>
<para arch="arm">
On &arch-title;, most built-in Ethernet devices are supported and modules
for additional PCI and USB devices are provided. The major exception is
the IXP4xx platform (featuring devices such as the Linksys NSLU2) which
needs a proprietary microcode for the operation of its built-in Ethernet
device. Unofficial images for Linksys NSLU2 with this proprietary
microcode can be obtained from the <ulink
url="&url-slug-firmware;">Slug-Firmware site</ulink>.
</para><para arch="x86">
ISDN is supported, but not during the installation.
</para>
<sect3 condition="supports-wireless" id="nics-wireless">
<title>Wireless Network Cards</title>
<para>
Wireless networking is in general supported as well and a growing number of
wireless adapters are supported by the official Linux kernel, although many
of them do require firmware to be loaded. If firmware is needed, the installer
will prompt you to load firmware. See <xref linkend="loading-firmware"/>
for detailed information on how to load firmware during the installation.
</para><para>
Wireless NICs that are not supported by the official Linux kernel can generally
be made to work under &debian;, but are not supported during the installation.
</para><para>
Support for encrypted wireless during installation is currently limited to WEP.
If your access point uses stronger encryption, it cannot be used during the
installation process.
</para><para>
If there is a problem with wireless and
is no other NIC you can use during the installation, it is still
possible to install &debian; using a full CD-ROM or DVD image. Select the
option to not configure a network and install using only the packages
available from the CD/DVD. You can then install the driver and firmware you
need after the installation is completed (after the reboot) and configure
your network manually.
</para><para>
In some cases the driver you need may not be available as a Debian package.
You will then have to look if there is source code available in the internet
and compile the driver yourself. How to do this is outside the scope of this
manual.
<phrase arch="x86">If no Linux driver is available, your last resort is to
use the <classname>ndiswrapper</classname> package, which allows you to use
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>
|
