Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ec(4) [netbsd man page]

EC(4)							   BSD Kernel Interfaces Manual 						     EC(4)

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

Check Out this Related Man Page

DE(4)							   BSD Kernel Interfaces Manual 						     DE(4)

de -- DEC DC21x4x Ethernet device driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device de Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_de_load="YES" DESCRIPTION
The de driver provides support for the Ethernet adapters based on the Digital Equipment DC21x4x based self-contained Ethernet and Fast Ether- net chips. The de driver supports the following media types: autoselect Enable autoselection of the media type and options 10baseT/UTP Set 10Mbps operation on the 10baseT port 10base2/BNC Set 10Mbps operation on the BNC port 10base5/AUI Set 10Mbps operation on the AUI port 100baseTX Set 100Mbps (Fast Ethernet) operation 100baseFX Set 100Mbps operation 100baseT4 Set 100Mbps operation (4-pair cat-3 cable) The de driver supports the following media options: full-duplex Set full duplex operation Note that the media types available depend on the particular card in use. Some cards are explicitly programmed to a particular media type by a setup utility and are not changeable. Use the ifconfig(8) command and in particular the -m flag to list the supported media types for your particular card. The old ``ifconfig linkN'' method of configuration is not supported. HARDWARE
Adapters supported by the de driver include: o Adaptec ANA-6944/TX o Cogent EM100FX and EM440TX o Corega FastEther PCI-TX o D-Link DFE-500TX o DEC DE435, DEC DE450, and DEC DE500 o ELECOM LD-PCI2T, LD-PCITS o I-O DATA LA2/T-PCI o SMC Etherpower 8432, 9332 and 9334 o ZNYX ZX3xx DIAGNOSTICS
de%d: waking device from sleep/snooze mode The 21041 and 21140A chips support suspending the operation of the card. de%d: error: desired IRQ of %d does not match device's actual IRQ of %d The device probe detected that the board is configured for a differ- ent interrupt than the one specified in the kernel configuration file. de%d: not configured; limit of %d reached or exceeded There is a limit of 32 de devices allowed in a single machine. de%d: not configured; 21040 pass 2.0 required (%d.%d found) de%d: not configured; 21140 pass 1.1 required (%d.%d found) Certain revisions of the chipset are not supported by this driver. SEE ALSO
altq(4), arp(4), netintro(4), ng_ether(4), ifconfig(8) AUTHORS
The de device driver was written by Matt Thomas. This manual page was written by David E. O'Brien. BSD
July 16, 2005 BSD
Man Page