GX(4) Kernel Interfaces Manual GX(4) NAME gx -- Intel Pro/1000 gigabit ethernet driver SYNOPSIS device miibus device gx DESCRIPTION The gx driver provides support for NICs based on the Intel 82542 and 82543 gigabit ethernet controller chips. Both fiber and copper variants of the cards are supported. The 82542 supports TBI (ten bit interface), while the 82543 supports the GMII transceivers, which means it can be used with either copper or 1000ba- seX fiber applications. Both boards support VLAN tagging/insertion and the 82543 additionally supports TCP/IP checksum offload. The 82543-T cards use the Marvell 10/100/1000 copper gigabit tranceiver chip, which supports autonegotiation of 10, 100 and 1000mbps modes in full or half duplex, however half duplex 1000mbps is not suppoorted. The driver also supports jumbo frames, which can be configured via the in- terface MTU setting. Selecting an MTU larger than 1500 bytes with the if- config(8) utility configures the adapter to receive and transmit jumbo frames. Using jumbo frames can greatly improve performance for certain tasks, such as file transfers and data streaming. The gx driver supports the following media types: autoselect Enable autoselection of the media type and options. User can manually override the autoselected mode by adding media op- tions to rc.conf(5). 10baseT/UTP Set 10Mbps operation. The ifconfig(8)'s mediaopt option can also be used to select either full-duplex or half-duplex modes. 100baseTX Set 100Mbps (fast ethernet) operation. The ifconfig(8)'s mediaopt option can also be used to select either full-duplex or half-duplex modes. 1000baseTX Set 1000baseTX operation over twisted pair. Only full-duplex mode is supported. The gx driver supports the following media options: full-duplex Force full duplex operation. half-duplex Force half duplex operation. The gx driver also supports one special link option for 1000baseTX cards: link0 With 1000baseTX cards, establishing a link between two ports re- quires that one port be configured as a master and the other a slave. With autonegotiation, the master/slave settings should be chosen automatically. Setting the link0 flag with ifconfig(8) will force the link up instead. For more information on configuring this device, see ifconfig(8). DIAGNOSTICS gx%d: couldn't map memory A fatal initialization error has occurred. gx%d: couldn't map interrupt A fatal initialization error has occurred. gx%d: couldn't setup irq A fatal initialization error has occurred. gx%d: failed to read station address A fatal initialization error has oc- curred. gx%d: no memory for list buffers! The driver failed to allocate memory for per-device instance information during initialization. gx%d: failed to enable memory mapping! The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-mas- ter slot. gx%d: GMII/MII, PHY not detected The MII probe routines failed to detect the PHY. This might happen if miibus is not configured. gx%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). gx%d: mbuf allocation failed -- packet dropped The driver could not allo- cate a mbuf for the receive ring. gx%d: cluster allocation failed -- packet dropped The driver could not al- locate a mbuf cluster for the receive ring. gx%d: link down The link status changed from up to down. gx%d: link up The link status changed from down to up. SEE ALSO arp(4), netintro(4), ng_ether(4), vlan(4), ifconfig(8) HISTORY The gx device driver first appeared in FreeBSD 4.5. AUTHORS The gx driver was written by Jonathan Lemon <jlemon@FreeBSD.org>. FreeBSD 4.9 October 17, 2001 GX(4)
NAME | SYNOPSIS | DESCRIPTION | DIAGNOSTICS | SEE ALSO | HISTORY | AUTHORS
Want to link to this manual page? Use this URL:
<https://man.FreeBSD.org/cgi/man.cgi?query=gx&sektion=4&manpath=FreeBSD+4.9-RELEASE>