ne(4) [netbsd man page]
NE(4) BSD Kernel Interfaces Manual NE(4) NAME
ne -- NE2000 and compatible Ethernet cards device driver SYNOPSIS
ISA boards ne0 at isa? port 0x280 irq 9 ne1 at isa? port 0x300 irq 10 ne* at isapnp? MCA boards ne* at mca? slot ? PCI boards ne* at pci? dev ? function ? PCMCIA ne* at pcmcia? function ? acorn32 ne* at podulebus? amiga ne* at zbus0 # AriadneII, X-surf amigappc ne* at zbus0 # AriadneII, X-surf atari ne0 at mainbus0 # EtherNEC on Atari ROM cartridge slot evbarm ne0 at obio? addr 0x0e000200 intr 5 # on-board Asix AX88796 evbsh3 ne0 at mainbus? # Realtek RTL8019AS x68k ne* at intio0 addr 0xece300 intr 249 # Nereid Ethernet ne* at intio0 addr 0xeceb00 intr 248 # Nereid Ethernet neptune0 at intio0 addr 0xece000 intr 249 # Neptune-X neptune1 at intio0 addr 0xece400 intr 249 # Neptune-X at alt. addr. ne* at neptune? addr 0x300 DESCRIPTION
The ne device driver supports NE2000 and compatible (including NE1000) Ethernet cards. While the original NE2000 is designed for ISA bus, the compatible Realtek 8019 chip is widely used on various local busses and ne driver also supports such devices on various machines. MEDIA SELECTION
The Realtek 8019 (ISA, ISAPnP, some PCMCIA) and Realtek 8029 (PCI) NE2000-compatible Ethernet chips include support for software media selec- tion. If one of these chips is detected by the driver, the list of supported media will be displayed. For all other chips supported by the ne driver, media selection must be performed either via card jumper settings or by vendor-supplied con- figuration programs. DIAGNOSTICS
ne0: where did the card go? The driver found the card, but was unable to make the card respond to complete the configuration sequence. SEE ALSO
ifmedia(4), intro(4), isa(4), isapnp(4), mca(4), pci(4), pcmcia(4), ifconfig(8) BSD
April 3, 2010 BSD
Check Out this Related Man Page
EC(4) BSD Kernel Interfaces Manual EC(4) NAME
ec -- driver for 3Com EtherLink II (3c503) ISA bus Ethernet cards SYNOPSIS
ec0 at isa? port 0x250 iomem 0xd8000 irq 9 DESCRIPTION
The ec device driver supports 3Com EtherLink II (3c503) Ethernet cards for ISA bus which are based on the National Semiconductor DP8390/WD83C690 Ethernet interface chips. MEDIA SELECTION
The EtherLink II supports two media types on a single card. All support the AUI media type. The other media is either BNC or UTP behind a transceiver. Software cannot differentiate between BNC and UTP cards. To enable the AUI media, select the 10base5 or aui media type with ifconfig(8)'s media directive. To select the other media (BNC or UTP), select the 10base2 or bnc media type. DIAGNOSTICS
ec0: wildcarded IRQ is not allowed The IRQ was wildcarded in the kernel configuration file. This is not supported. ec0: invalid IRQ <n>, must be 3, 4, 5, or 9 An IRQ other than the above IRQ values was specified in the kernel configuration file. The EtherLink II hardware only supports the above listed IRQ values. ec0: failed to clear shared memory at offset <off> The memory test was unable to clear shared the interface's shared memory region. This often indicates that the card is configured at a con- flicting iomem address. ec0: warning - receiver ring buffer overrun The DP8390 Ethernet chip used by this board implements a shared-memory ring-buffer to store incoming packets. The 3c503 usually has only 8K bytes of shared memory. This is only enough room for about 4 full-size (1500 byte) packets. This can sometimes be a problem, especially on the original 3c503, because these boards' shared-memory access speed is quite slow; typically only about 1MB/second. The overhead of this slow memory access, and the fact that there is only room for 4 full-sized packets means that the ring-buffer will occasionally overrun. When an overrun occurs, the board must be reset to avoid a lockup problem in early revision DP8390 Ethernet chips. Resetting the board causes all of the data in the ring-buffer to be lost, requiring the data to be retransmitted/received, congesting the board further. Because of this, maximum throughput on these boards is only about 400-600K bytes per second. This problem is exacerbated by NFS because the 8-bit boards lack sufficient packet buffer memory to support the default 8K byte packets that NFS and other protocols use as their default. If these cards must be used with NFS, use the mount_nfs(8) -r and -w options in /etc/fstab to limit NFS's packet size. 4K (4096) byte packets generally work. SEE ALSO
ifmedia(4), intro(4), isa(4), ifconfig(8), mount_nfs(8) BSD
October 20, 1997 BSD