Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xe(4) [debian man page]

XE(4)							   BSD Kernel Interfaces Manual 						     XE(4)

NAME
xe -- Xircom PCMCIA Ethernet device driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device xe Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_xe_load="YES" DESCRIPTION
The xe driver supports PCMCIA Ethernet adapters based on Xircom CE2- and CE3-class hardware. This includes devices made by Xircom along with various OEM manufacturers. Please note that the xe driver only supports PCMCIA cards and their Ethernet functions. xe does not support the on-board modem device located on some version of the Ethernet/modem combo cards. In particular, Xircom RealPort2 cards are not supported by this driver. The xe driver supports the following media types: autoselect Enable autoselection of media type and options. 10Base2/BNC Select 10Mbps operation on a BNC coaxial connector. 10BaseT/UTP Select 10Mbps operation on a RJ-45 connector. 100BaseTX Select 100Mbps operation. Note that 100BaseTX operation is not available on CE2-class cards, while the 10Base2/BNC mode is only available on CE2-class cards. Full- duplex operation is currently not supported. For more information on configuring network interface devices, see ifconfig(8). HARDWARE
The xe driver supports the following cards: o Xircom CreditCard Ethernet (PS-CE2-10) o Xircom CreditCard Ethernet + Modem 28 (PS-CEM-28) o Xircom CreditCard Ethernet + Modem 33 (CEM33) o Xircom CreditCard 10/100 (CE3, CE3B) o Xircom CreditCard Ethernet 10/100 + Modem 56 (CEM56) o Xircom RealPort Ethernet 10 (RE10) o Xircom RealPort Ethernet 10/100 (RE100) o Xircom RealPort Ethernet 10/100 + Modem 56 (REM56, REM56G) o Accton Fast EtherCard-16 (EN2226) o Compaq Microcom CPQ550 Ethernet/Modem PC Card o Compaq Netelligent 10/100 PC Card (CPQ-10/100) o Intel EtherExpress Pro/100 PC Card Mobile Adapter 16 (Pro/100 M16A) o Intel EtherExpress Pro/100 LAN/Modem PC Card Adapter (Pro/100 M16B) Other similar devices using the same hardware may also be supported. DIAGNOSTICS
xe%d: Cannot allocate ioport xe%d: Cannot allocate irq A fatal initialization error occurred while attempting to allocate system resources for the card. xe%d: Unable to fix your %s combo card A fatal initialization error occurred while attempting to attach an Ethernet/modem combo card. xe%d: watchdog timeout: resetting card The card failed to generate an interrupt acknowledging a transmitted packet. May indicate a PCMCIA configuration problem. xe%d: no carrier The card has lost all contact with the network; this usually indicates a cable problem. SEE ALSO
pccard(4), ifconfig(8) HISTORY
The xe driver first appeared in FreeBSD 3.3. AUTHORS
The xe device driver was written by Scott Mitchell <rsm@FreeBSD.org>. This manual page was written by Scott Mitchell <rsm@FreeBSD.org>, and Tom Rhodes <trhodes@FreeBSD.org>. BUGS
Supported devices will fail to attach on some machines using the NEWCARD PC Card framework. Automatic media selection is usually unreliable. BSD
July 16, 2005 BSD

Check Out this Related Man Page

TL(4)							   BSD Kernel Interfaces Manual 						     TL(4)

NAME
tl -- Texas Instruments ThunderLAN Ethernet device driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device tl Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_tl_load="YES" DESCRIPTION
The tl driver provides support for PCI Ethernet adapters based on the Texas Instruments ThunderLAN Ethernet controller chip. The ThunderLAN controller has a standard MII interface that supports up to 32 physical interface devices (PHYs). It also has a built-in 10baseT PHY hardwired at MII address 31, which may be used in some 10Mbps-only hardware configurations. In 100Mbps configurations, a National Semiconductor DP83840A or other MII-compliant PHY may be attached to the ThunderLAN's MII bus. If a DP83840A or equivalent is available, the ThunderLAN chip can operate at either 100Mbps or 10Mbps in either half-duplex or full-duplex modes. The ThunderLAN's built-in PHY and the DP83840A also support autonegotiation. The tl driver supports the following media types: autoselect Enable autoselection of the media type and options. Note that this option is only available on those PHYs that support autonegotiation. Also, the PHY will not advertise those modes that have been explicitly disabled using the following media options. 10baseT/UTP Set 10Mbps operation. 100baseTX Set 100Mbps (Fast Ethernet) operation. 10base5/AUI Enable AUI/BNC interface (useful only with the built-in PHY). The tl driver supports the following media options: full-duplex Force full duplex operation. half-duplex Force half duplex operation. hw-loopback Enable hardware loopback mode. Note that the 100baseTX media type is only available if supported by the PHY. For more information on configuring this device, see ifconfig(8). HARDWARE
The tl driver supports Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large number of Compaq PCI Ethernet adapters. Also supported are: o Olicom OC-2135/2138 10/100 TX UTP adapter o Olicom OC-2325/OC-2326 10/100 TX UTP adapter o Racore 8148 10baseT/100baseTX/100baseFX adapter o Racore 8165 10/100baseTX adapter The tl driver also supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq Deskpro desktop machines including: o Compaq Netelligent 10 o Compaq Netelligent 10 T PCI UTP/Coax o Compaq Netelligent 10/100 o Compaq Netelligent 10/100 Dual-Port o Compaq Netelligent 10/100 Proliant o Compaq Netelligent 10/100 TX Embedded UTP o Compaq Netelligent 10/100 TX UTP o Compaq NetFlex 3P o Compaq NetFlex 3P Integrated o Compaq NetFlex 3P w/BNC DIAGNOSTICS
tl%d: couldn't map memory A fatal initialization error has occurred. tl%d: couldn't map interrupt A fatal initialization error has occurred. tl%d: device timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). tl%d: no memory for rx list The driver failed to allocate an mbuf for the receiver ring. tl%d: no memory for tx list The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. SEE ALSO
arp(4), miibus(4), netintro(4), ng_ether(4), ifconfig(8) HISTORY
The tl device driver first appeared in FreeBSD 2.2. AUTHORS
The tl driver was written by Bill Paul <wpaul@ctr.columbia.edu>. BSD
July 16, 2005 BSD
Man Page