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
54 .Sh DEPRECATION NOTICE
57 driver is not present in
60 See https://github.com/freebsd/fcp/blob/master/fcp-0101.md for more
65 driver provides support for 8 and 16bit Ethernet cards that are based on
66 the National Semiconductor DS8390 and similar NICs manufactured by
70 driver also supports many PC Card chips which interface via MII to a PHY.
71 Axiom's AX88790, AX88190 and AX88190A;
72 DLink's DL10019 and DL10022; and
73 Tamarack's TC5299J chips all support internal or external MII/PHY combinations.
74 Realtek's PCI and ISA RTL80x9-based cards are also supported.
75 For these chipsets, autonegotiation and status reporting are supported.
77 In addition to the standard port and IRQ specifications, the
79 driver also supports a number of
81 which can force 8/16bit mode, enable/disable multi-buffering, and select the default
82 interface type (AUI/BNC, and for cards with twisted pair, AUI/10BaseT).
86 are a bit field, and are summarized as follows:
87 .Bl -tag -width indent
90 On those cards which support it, this flag causes the transceiver to
91 be disabled and the AUI connection to be used by default.
94 This flag forces the card to 8bit mode regardless of how the
95 card identifies itself.
96 This may be needed for some clones which incorrectly
97 identify themselves as 16bit, even though they only have an 8bit interface.
98 This flag takes precedence over force 16bit mode.
101 This flag forces the card to 16bit mode regardless of how the
102 card identifies itself.
103 This may be needed for some clones which incorrectly
104 identify themselves as 8bit, even though they have a 16bit ISA interface.
106 Disable transmitter multi-buffering.
107 This flag disables the use of multiple
108 transmit buffers and may be necessary in rare cases where packets are sent out
109 faster than a machine on the other end can handle (as evidenced by severe packet
113 :-)) machines have terrible Ethernet performance
114 and simply cannot cope with 1100K+ data rates.
115 Use of this flag also provides
116 one more packet worth of receiver buffering, and on 8bit cards, this may help
117 reduce receiver lossage.
120 When using a 3c503 card, the AUI connection may be selected by specifying the
124 (BNC is the default).
128 driver supports the following Ethernet NICs:
132 3Com 3c503 Etherlink II
133 .Pq Cd "options ED_3C503"
137 Accton EN1644 (old model), EN1646 (old model), EN2203 (old model) (110pin)
140 Accton EN2212/EN2216/UE2216
142 Allied Telesis CentreCOM LA100-PCM_V2
144 AmbiCom 10BaseT card (8002, 8002T, 8010 and 8610)
146 Bay Networks NETGEAR FA410TXC Fast Ethernet
148 Belkin F5D5020 PC Card Fast Ethernet
150 Billionton LM5LT-10B Ethernet/Modem PC Card
152 Billionton LNT-10TB, LNT-10TN Ethernet PC Card
154 Bromax iPort 10/100 Ethernet PC Card
156 Bromax iPort 10 Ethernet PC Card
158 Buffalo LPC2-CLT, LPC3-CLT, LPC3-CLX, LPC4-TX, LPC-CTX PC Card
160 Buffalo LPC-CF-CLT CF Card
168 Corega Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD PCC-T/Fether II TXD
170 Corega LAPCCTXD (TC5299J)
178 D-Link DE-660, DE-660+
180 D-Link IC-CARD/IC-CARD+ Ethernet
182 ELECOM Laneed LD-CDL/TX, LD-CDF, LD-CDS, LD-10/100CD, LD-CDWA (DP83902A)
184 Hawking PN652TX PC Card (AX88790)
186 HP PC Lan+ 27247B and 27252A
187 .Pq Cd "options ED_HPP"
189 IBM Creditcard Ethernet I/II
195 Kingston KNE-PC2, CIO10T, KNE-PCM/x Ethernet
199 Linksys EC2T/PCMPC100/PCM100, PCMLM56
201 Linksys EtherFast 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 V2)
203 MACNICA Ethernet ME1 for JEIDA
207 MELCO LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX
209 NDC Ethernet Instant-Link
211 National Semiconductor InfoMover NE4100
217 Network Everywhere Ethernet 10BaseT PC Card
219 New Media LANSurfer 10+56 Ethernet/Modem
223 Novell NE1000/NE2000/NE2100
229 Psion 10/100 LANGLOBAL Combine iT
235 Relia Combo-L/M-56k PC Card
241 SMC WD8003E/WD8003EBT/WD8003S/WD8003SBT/WD8003W/WD8013EBT/WD8013W and clones
243 SMC EZCard PC Card, 8040-TX, 8041-TX (AX88x90), 8041-TX V.2 (TC5299J)
245 Socket LP-E, ES-1000 Ethernet/Serial, LP-E CF, LP-FE CF
247 Surecom EtherPerfect EP-427
251 TDK 3000/3400/5670 Fast Ethernet/Modem
253 TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card
255 TDK DFL5610WS Ethernet/Modem PC Card
257 Telecom Device SuperSocket RE450T
259 Toshiba LANCT00A PC Card
268 ISA, PCI and PC Card devices are supported.
272 driver does not support the following Ethernet NICs:
276 Mitsubishi LAN Adapter B8895
280 .It "ed%d: failed to clear shared memory at %x - check configuration."
281 When the card was probed at system boot time, the
283 driver found that it could not clear the card's shared memory.
284 This is most commonly
285 caused by a BIOS extension ROM being configured in the same address space as the
286 Ethernet card's shared memory.
287 Either find the offending card and change its BIOS
288 ROM to be at an address that does not conflict, or change the
291 that the card's shared memory is mapped at a
292 non-conflicting address.
293 .It "ed%d: Invalid irq configuration (%d) must be 2-5 for 3c503."
294 The IRQ number that was specified in the
296 file is not valid for the 3Com 3c503 card.
297 The 3c503 can only be assigned to IRQs 2 through 5.
298 .It "ed%d: Cannot find start of RAM."
299 .It "ed%d: Cannot find any RAM, start : %d, x = %d."
300 The probe of a Gateway card was unsuccessful in configuring the card's packet memory.
301 This likely indicates that the card was improperly recognized as a Gateway or that
302 the card is defective.
303 .It "ed: packets buffered, but transmitter idle."
304 Indicates a logic problem in the driver.
306 .It "ed%d: device timeout"
307 Indicates that an expected transmitter interrupt did not occur.
309 interrupt conflict with another card on the ISA bus.
310 This condition could also be caused if the kernel is configured for a
311 different IRQ channel than the one the card is actually using.
312 If that is the case, you will have to either reconfigure the card
313 using a DOS utility or set the jumpers on the card appropriately.
314 .It "ed%d: NIC memory corrupt - invalid packet length %d."
315 Indicates that a packet was received with a packet length that was either larger than
316 the maximum size or smaller than the minimum size allowed by the IEEE 802.3 standard.
318 caused by a conflict with another card on the ISA bus, but in some cases may also
319 indicate faulty cabling.
320 .It "ed%d: remote transmit DMA failed to complete."
321 This indicates that a programmed I/O transfer to an NE1000 or NE2000 style card
322 has failed to properly complete.
323 Usually caused by the ISA bus speed being set
325 .It "ed%d: Invalid irq configuration (%ld) must be %s for %s"
326 Indicates the device has a different IRQ than supported or expected.
327 .It "ed%d: Cannot locate my ports!"
328 The device is using a different I/O port than the driver knows about.
329 .It "ed%d: Cannot extract MAC address"
330 Attempts to get the MAC address failed.
331 .It "ed%d: Missing mii!"
332 Probing for an MII bus has failed.
333 This indicates a coding error in the PC Card attachment, because a PHY
334 is required for the chips that generate this error message.
347 device driver first appeared in
352 device driver and this manual page were written by
355 Early revision DS8390 chips have problems.
356 They lock up whenever the receive
357 ring-buffer overflows.
358 They occasionally switch the byte order
359 of the length field in the packet ring header (several different causes
360 of this related to an off-by-one byte alignment) - resulting in
361 .Qq Li "NIC memory corrupt - invalid packet length"
364 whenever these problems occur, but otherwise there is no problem with
365 recovering from these conditions.
367 The NIC memory access to 3Com and Novell cards is much slower than it is on
368 WD/SMC cards; it is less than 1MB/second on 8bit boards and less than 2MB/second
370 This can lead to ring-buffer overruns resulting in
371 dropped packets during heavy network traffic.
373 The Mitsubishi B8895 PC Card uses a DP83902, but its ASIC part is
375 Neither the NE2000 nor the WD83x0 drivers work with this card.
379 driver is a bit too aggressive about resetting the card whenever any bad
380 packets are received.
381 As a result, it may throw out some good packets which
382 have been received but not yet transferred from the card to main memory.
386 driver is slow by today's standards.
388 PC Card attachment supports the D-Link DMF650TX LAN/Modem card's Ethernet
389 port only at this time.
391 Some devices supported by
393 do not generate the link state change events used by
397 If you have problems with
399 not starting and the device is always attached to the network it may
400 be possible to work around this by changing