1.\" $OpenBSD: xl.4,v 1.48 2013/08/14 06:32:35 jmc Exp $ 2.\" 3.\" Copyright (c) 1997, 1998 4.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by Bill Paul. 17.\" 4. Neither the name of the author nor the names of any co-contributors 18.\" may be used to endorse or promote products derived from this software 19.\" without specific prior written permission. 20.\" 21.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND 22.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 23.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 24.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD 25.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 26.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 27.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 28.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 29.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 30.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 31.\" THE POSSIBILITY OF SUCH DAMAGE. 32.\" 33.\" $FreeBSD: xl.4,v 1.1 1998/08/16 17:19:58 wpaul Exp $ 34.\" 35.Dd $Mdocdate: August 14 2013 $ 36.Dt XL 4 37.Os 38.Sh NAME 39.Nm xl 40.Nd 3Com EtherLink XL and Fast EtherLink XL 10/100 Ethernet device 41.Sh SYNOPSIS 42.Cd "xl* at pci?" 43.Cd "xl* at cardbus?" 44.Cd "amphy* at mii?" 45.Cd "bmtphy* at mii?" 46.Cd "exphy* at mii?" 47.Cd "nsphy* at mii?" 48.Cd "tqphy* at mii?" 49.Sh DESCRIPTION 50The 51.Nm 52device driver supports the 3Com EtherLink XL and Fast EtherLink XL family 53of Ethernet cards, and embedded controllers based on the 3Com 54.Dq boomerang 55and 56.Dq cyclone 57bus master EtherLink XL chips. 58This includes, among others, the following models: 59.Pp 60.Bl -tag -width 3CXXXXX -offset indent -compact 61.It 3C555 62EtherLink XL Mini PCI 63.It 3C556 64EtherLink XL Mini PCI 65.It 3C556B 66EtherLink XL Mini PCI 67.It 3C575 6810/100 LAN CardBus PC Card 69.It 3C656 7010/100 LAN+Modem CardBus PC Card 71.It 3C900 72EtherLink XL PCI 73.It 3C900B 74EtherLink XL PCI 75.It 3C905 76Fast EtherLink XL PCI 77.It 3C905B 78Fast EtherLink XL PCI 79.It 3C905C 80Fast EtherLink XL PCI 81.It 3C980 82Fast EtherLink Server NIC 83.It 3CSOHO 84OfficeConnect Fast Ethernet NIC 85.It 9201 86NVIDIA nForce2 integrated 3Com 9201 (nForce2-ST, nForce2-GT) 87.It 920BEMB 883c920B-EMB-WNM Integrated Fast Ethernet. 89.El 90.Pp 91Category 3, 4 or 5 unshielded twisted-pair (UTP) cable should be used for 92RJ-45 (10baseT), thick Ethernet coaxial (RG59 B/U, 50 ohm) for AUI/DIX, 93and thin Ethernet coaxial (RG58 A/U or C/U, 50 ohm +/- 4) for BNC (10base2). 94Some 3Com NICs also support MII connectors (switchable 10/100Mbps UTP). 95The 3C905B-FX and other similar cards are capable of 100Mbps over fiber. 96.Pp 97Hardware receive IP/TCP/UDP checksum offload for IPv4 is supported on the 3C905B. 98.Pp 99The 100.Nm 101driver additionally supports Wake on LAN (WoL). 102See 103.Xr arp 8 104and 105.Xr ifconfig 8 106for more details. 107.Pp 108The following media types and options (as given to 109.Xr ifconfig 8 ) 110are supported: 111.Bl -tag -width xxx -offset indent 112.It Cm media No autoselect 113Enable autoselection of media type and options. 114Note that this media type is only available with 115adapters that have external PHYs or built-in autonegotiation logic. 116For 3C900 and 3C900B adapters, the driver 117will choose the mode specified in the EEPROM. 118This can be changed by adding media options to the appropriate 119.Xr hostname.if 5 120file. 121.It Cm media No 100baseFX Cm mediaopt No full-duplex 122For those cards that support it, force full-duplex 100Mbps operation over fiber. 123.It Cm media No 100baseFX Cm mediaopt No half-duplex 124For those cards that support it, force half-duplex 100Mbps operation over fiber. 125.It Cm media No 100baseTX Cm mediaopt No full-duplex 126Set 100Mbps (Fast Ethernet) operation and force full-duplex mode. 127.It Cm media No 100baseTX Cm mediaopt No half-duplex 128Set 100Mbps (Fast Ethernet) operation and force half-duplex mode. 129.It Cm media No 10baseT Cm mediaopt No full-duplex 130Set 10baseT (UTP) operation and force full-duplex mode. 131.It Cm media No 10baseT Cm mediaopt No half-duplex 132Set 10baseT (UTP) operation and force half-duplex mode. 133.It Cm media No 10base5 134Set 10base5 (thick-net) operation (half-duplex only). 135.It Cm media No 10base2 136Set 10base2 (thin-net) operation (half-duplex only). 137.El 138.Pp 139For more information on configuring this device, see 140.Xr ifconfig 8 . 141To view a list of media types and options supported by this card try 142.Ic ifconfig <device> media . 143For example, 144.Ic ifconfig xl0 media . 145.Sh DIAGNOSTICS 146.Bl -diag 147.It "xl0: couldn't map memory" 148A fatal initialization error has occurred. 149.It "xl0: couldn't map interrupt" 150A fatal initialization error has occurred. 151.It "xl0: device timeout" 152The device has stopped responding to the network, or there is a problem with 153the network connection (cable). 154.It "xl0: no memory for rx list" 155The driver failed to allocate an mbuf for the receiver ring. 156.It "xl0: no memory for tx list" 157The driver failed to allocate an mbuf for the transmitter ring when 158allocating a pad buffer or collapsing an mbuf chain into a cluster. 159.It "xl0: command never completed!" 160Some commands issued to the 3C90x ASIC take time to complete: the 161driver is supposed to wait until the 162.Dq command in progress 163bit in the status register clears before continuing. 164In some instances, this bit may not clear. 165To avoid getting caught in an infinite wait loop, 166the driver only polls the bit a finite number of times before 167giving up, at which point it issues this message. 168This message may be printed during driver initialization on slower machines. 169If this message appears but the driver continues to function normally, the 170message can probably be ignored. 171.It "xl0: WARNING: no media options bits set in the media options register!" 172This warning may appear when using the driver on some Dell Latitude 173docking stations with built-in 3C905-TX adapters. 174For whatever the reason, the 175.Dq MII available 176bit in the media options register on 177this particular equipment is not set, even though it should be (the 1783C905-TX always uses an external PHY transceiver). 179The driver will 180attempt to guess the proper media type based on the PCI device ID word. 181The driver makes a lot of noise about this condition because 182the author considers it a manufacturing defect. 183.El 184.Sh SEE ALSO 185.Xr amphy 4 , 186.Xr arp 4 , 187.Xr bmtphy 4 , 188.Xr cardbus 4 , 189.Xr exphy 4 , 190.Xr ifmedia 4 , 191.Xr intro 4 , 192.Xr netintro 4 , 193.Xr nsphy 4 , 194.Xr tqphy 4 , 195.Xr hostname.if 5 , 196.Xr ifconfig 8 197.Sh HISTORY 198The 199.Nm 200device driver first appeared in 201.Fx 3.0 . 202.Ox 203support was added in 204.Ox 2.4 . 205.Sh AUTHORS 206The 207.Nm 208driver was written by 209.An Bill Paul Aq Mt wpaul@ctr.columbia.edu . 210