2 .\" Copyright (c) 1994, David Greenman
3 .\" All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
13 .\" 3. All advertising materials mentioning features or use of this software
14 .\" must display the following acknowledgement:
15 .\" This product includes software developed by David Greenman.
16 .\" 4. The name of the author may not be used to endorse or promote products
17 .\" derived from this software without specific prior written permission.
19 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
20 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
23 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
24 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
25 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
28 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
38 .Nd "NE-2000 and WD-80x3 Ethernet driver"
40 To compile this driver into the kernel,
41 place the following lines in your
42 kernel configuration file:
43 .Bd -ragged -offset indent
48 Alternatively, to load the driver as a
49 module at boot time, place the following line in
51 .Bd -literal -offset indent
57 driver provides support for 8 and 16bit Ethernet cards that are based on
58 the National Semiconductor DS8390 and similar NICs manufactured by
62 driver also supports many PC Card chips which interface via MII to a PHY.
63 Axiom's AX88790, AX88190 and AX88190A;
64 DLink's DL10019 and DL10022; and
65 Tamarack's TC5299J chips all support internal or external MII/PHY combinations.
66 Realtek's PCI and ISA RTL80x9-based cards are also supported.
67 For these chipsets, autonegotiation and status reporting are supported.
69 In addition to the standard port and IRQ specifications, the
71 driver also supports a number of
73 which can force 8/16bit mode, enable/disable multi-buffering, and select the default
74 interface type (AUI/BNC, and for cards with twisted pair, AUI/10BaseT).
78 are a bit field, and are summarized as follows:
79 .Bl -tag -width indent
82 On those cards which support it, this flag causes the transceiver to
83 be disabled and the AUI connection to be used by default.
86 This flag forces the card to 8bit mode regardless of how the
87 card identifies itself.
88 This may be needed for some clones which incorrectly
89 identify themselves as 16bit, even though they only have an 8bit interface.
90 This flag takes precedence over force 16bit mode.
93 This flag forces the card to 16bit mode regardless of how the
94 card identifies itself.
95 This may be needed for some clones which incorrectly
96 identify themselves as 8bit, even though they have a 16bit ISA interface.
98 Disable transmitter multi-buffering.
99 This flag disables the use of multiple
100 transmit buffers and may be necessary in rare cases where packets are sent out
101 faster than a machine on the other end can handle (as evidenced by severe packet
105 :-)) machines have terrible Ethernet performance
106 and simply cannot cope with 1100K+ data rates.
107 Use of this flag also provides
108 one more packet worth of receiver buffering, and on 8bit cards, this may help
109 reduce receiver lossage.
112 When using a 3c503 card, the AUI connection may be selected by specifying the
116 (BNC is the default).
120 driver supports the following Ethernet NICs:
124 3Com 3c503 Etherlink II
125 .Pq Cd "options ED_3C503"
129 Accton EN1644 (old model), EN1646 (old model), EN2203 (old model) (110pin)
132 Accton EN2212/EN2216/UE2216
134 Allied Telesis CentreCOM LA100-PCM_V2
136 Allied Telesis LA-98 (flags 0x000000) (PC-98)
138 Allied Telesis SIC-98, SIC-98NOTE (110pin), SIU-98 (flags 0x600000) (PC-98)
140 Allied Telesis SIU-98-D (flags 0x610000) (PC-98)
142 AmbiCom 10BaseT card (8002, 8002T, 8010 and 8610)
144 Bay Networks NETGEAR FA410TXC Fast Ethernet
146 Belkin F5D5020 PC Card Fast Ethernet
148 Billionton LM5LT-10B Ethernet/Modem PC Card
150 Billionton LNT-10TB, LNT-10TN Ethernet PC Card
152 Bromax iPort 10/100 Ethernet PC Card
154 Bromax iPort 10 Ethernet PC Card
156 Buffalo LPC2-CLT, LPC3-CLT, LPC3-CLX, LPC4-TX, LPC-CTX PC Card
158 Buffalo LPC-CF-CLT CF Card
166 Contec C-NET(98), RT-1007(98), C-NET(9N) (110pin) (flags 0xa00000) (PC-98)
168 Contec C-NET(98)E-A, C-NET(98)L-A, C-NET(98)P (flags 0x300000) (PC-98)
170 Corega Ether98-T (flags 0x000000) (PC-98)
172 Corega Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD PCC-T/Fether II TXD
174 Corega LAPCCTXD (TC5299J)
182 D-Link DE-298, DE-298P (flags 0x500000) (PC-98)
184 D-Link DE-660, DE-660+
186 D-Link IC-CARD/IC-CARD+ Ethernet
188 ELECOM LD-98P (flags 0x500000) (PC-98)
190 ELECOM LD-BDN, LD-NW801G (flags 0x200000) (PC-98)
192 ELECOM Laneed LD-CDL/TX, LD-CDF, LD-CDS, LD-10/100CD, LD-CDWA (DP83902A)
194 Hawking PN652TX PC Card (AX88790)
196 HP PC Lan+ 27247B and 27252A
197 .Pq Cd "options ED_HPP"
199 IBM Creditcard Ethernet I/II
201 ICM AD-ET2-T, DT-ET-25, DT-ET-T5, IF-2766ET, IF-2771ET, NB-ET-T (110pin)
202 (flags 0x500000) (PC-98)
204 I-O DATA LA/T-98, LA/T-98SB, LA2/T-98, ET/T-98 (flags 0x900000) (PC-98)
210 Kansai KLA-98C/T (flags 0x900000) (PC-98)
212 Kingston KNE-PC2, CIO10T, KNE-PCM/x Ethernet
216 Linksys EC2T/PCMPC100/PCM100, PCMLM56
218 Linksys EtherFast 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 V2)
220 Logitec LAN-98T (flags 0xb00000) (PC-98)
222 MACNICA Ethernet ME1 for JEIDA
224 MACNICA ME98 (flags 0x900000) (PC-98)
226 MACNICA NE2098 (flags 0x400000) (PC-98)
228 MELCO EGY-98 (flags 0x300000) (PC-98)
230 MELCO LGH-98, LGY-98, LGY-98-N (110pin), IND-SP, IND-SS (flags 0x400000) (PC-98)
234 MELCO LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX
236 NDC Ethernet Instant-Link
238 NEC PC-9801-77, PC-9801-78 (flags 0x910000) (PC-98)
240 NEC PC-9801-107, PC-9801-108 (flags 0x800000) (PC-98)
242 National Semiconductor InfoMover NE4100
248 Network Everywhere Ethernet 10BaseT PC Card
250 Networld 98X3 (flags 0xd00000) (PC-98)
252 Networld EC-98X, EP-98X (flags 0xd10000) (PC-98)
254 New Media LANSurfer 10+56 Ethernet/Modem
258 Novell NE1000/NE2000/NE2100
262 PLANEX EN-2298-C (flags 0x200000) (PC-98)
264 PLANEX EN-2298P-T, EN-2298-T (flags 0x500000) (PC-98)
268 Psion 10/100 LANGLOBAL Combine iT
274 Relia Combo-L/M-56k PC Card
280 SMC EtherEZ98 (flags 0x000000) (PC-98)
282 SMC WD8003E/WD8003EBT/WD8003S/WD8003SBT/WD8003W/WD8013EBT/WD8013W and clones
284 SMC EZCard PC Card, 8040-TX, 8041-TX (AX88x90), 8041-TX V.2 (TC5299J)
286 Socket LP-E, ES-1000 Ethernet/Serial, LP-E CF, LP-FE CF
288 Surecom EtherPerfect EP-427
292 TDK 3000/3400/5670 Fast Ethernet/Modem
294 TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card
296 TDK DFL5610WS Ethernet/Modem PC Card
298 Telecom Device SuperSocket RE450T
300 Toshiba LANCT00A PC Card
309 C-Bus, ISA, PCI and PC Card devices are supported.
313 driver does not support the following Ethernet NICs:
317 Mitsubishi LAN Adapter B8895
321 .It "ed%d: failed to clear shared memory at %x - check configuration."
322 When the card was probed at system boot time, the
324 driver found that it could not clear the card's shared memory.
325 This is most commonly
326 caused by a BIOS extension ROM being configured in the same address space as the
327 Ethernet card's shared memory.
328 Either find the offending card and change its BIOS
329 ROM to be at an address that does not conflict, or change the
332 that the card's shared memory is mapped at a
333 non-conflicting address.
334 .It "ed%d: Invalid irq configuration (%d) must be 2-5 for 3c503."
335 The IRQ number that was specified in the
337 file is not valid for the 3Com 3c503 card.
338 The 3c503 can only be assigned to IRQs 2 through 5.
339 .It "ed%d: Cannot find start of RAM."
340 .It "ed%d: Cannot find any RAM, start : %d, x = %d."
341 The probe of a Gateway card was unsuccessful in configuring the card's packet memory.
342 This likely indicates that the card was improperly recognized as a Gateway or that
343 the card is defective.
344 .It "ed: packets buffered, but transmitter idle."
345 Indicates a logic problem in the driver.
347 .It "ed%d: device timeout"
348 Indicates that an expected transmitter interrupt did not occur.
350 interrupt conflict with another card on the ISA bus.
351 This condition could also be caused if the kernel is configured for a
352 different IRQ channel than the one the card is actually using.
353 If that is the case, you will have to either reconfigure the card
354 using a DOS utility or set the jumpers on the card appropriately.
355 .It "ed%d: NIC memory corrupt - invalid packet length %d."
356 Indicates that a packet was received with a packet length that was either larger than
357 the maximum size or smaller than the minimum size allowed by the IEEE 802.3 standard.
359 caused by a conflict with another card on the ISA bus, but in some cases may also
360 indicate faulty cabling.
361 .It "ed%d: remote transmit DMA failed to complete."
362 This indicates that a programmed I/O transfer to an NE1000 or NE2000 style card
363 has failed to properly complete.
364 Usually caused by the ISA bus speed being set
366 .It "ed%d: Invalid irq configuration (%ld) must be %s for %s"
367 Indicates the device has a different IRQ than supported or expected.
368 .It "ed%d: Cannot locate my ports!"
369 The device is using a different I/O port than the driver knows about.
370 .It "ed%d: Cannot extract MAC address"
371 Attempts to get the MAC address failed.
372 .It "ed%d: Missing mii!"
373 Probing for an MII bus has failed.
374 This indicates a coding error in the PC Card attachment, because a PHY
375 is required for the chips that generate this error message.
388 device driver first appeared in
393 device driver and this manual page were written by
396 Early revision DS8390 chips have problems.
397 They lock up whenever the receive
398 ring-buffer overflows.
399 They occasionally switch the byte order
400 of the length field in the packet ring header (several different causes
401 of this related to an off-by-one byte alignment) - resulting in
402 .Qq Li "NIC memory corrupt - invalid packet length"
405 whenever these problems occur, but otherwise there is no problem with
406 recovering from these conditions.
408 The NIC memory access to 3Com and Novell cards is much slower than it is on
409 WD/SMC cards; it is less than 1MB/second on 8bit boards and less than 2MB/second
411 This can lead to ring-buffer overruns resulting in
412 dropped packets during heavy network traffic.
414 The Mitsubishi B8895 PC Card uses a DP83902, but its ASIC part is
416 Neither the NE2000 nor the WD83x0 drivers work with this card.
420 driver is a bit too aggressive about resetting the card whenever any bad
421 packets are received.
422 As a result, it may throw out some good packets which
423 have been received but not yet transferred from the card to main memory.
427 driver is slow by today's standards.
429 PC Card attachment supports the D-Link DMF650TX LAN/Modem card's Ethernet
430 port only at this time.
432 Some devices supported by
434 do not generate the link state change events used by
438 If you have problems with
440 not starting and the device is always attached to the network it may
441 be possible to work around this by changing