OpenBSD manual page server

Manual Page Search Parameters

WX(4)                     OpenBSD Programmer's Manual                    WX(4)

NAME
     wx - Intel Gigabit Ethernet driver

SYNOPSIS
     wx* at pci? dev ? function ?

DESCRIPTION
     The wx driver provides support for Intel Gigabit Ethernet PCI cards based
     on the i82452 chipset such as the Intel Pro/1000, PRO1000F, and PRO1000T
     Gigabit Server Adapter.

     Various models support the following media types and options (as given to
     ifconfig(8)) are supported:

           media autoselect
                Enable autoselection of media type and options.  Note that
                this media type is only available with adapters that have ex-
                ternal PHYs or built-in autonegotiation logic.

           media 1000baseSX mediaopt full-duplex
                Set 1000Mbps (Gigabit Ethernet) operation on fiber and force
                full-duplex mode.

           media 1000baseSX
                Set 1000Mbps (Gigabit Ethernet) operation on fiber.

           media 1000baseTX
                Set 1000Mbps (Gigabit Ethernet) operation on copper.

           media 100baseTX mediaopt full-duplex
                Set 100Mbps (Fast Ethernet) operation and force full-duplex
                mode.

           media 100baseTX mediaopt half-duplex
                Set 100Mbps (Fast Ethernet) operation and force half-duplex
                mode.

           media 10baseT mediaopt full-duplex
                Set 10baseT (UTP) operation and force full-duplex mode.

           media 10baseT mediaopt half-duplex
                Set 10baseT (UTP) operation and force half-duplex mode.

     For more information on configuring this device, see ifconfig(8). To view
     a list of media types and options supported by your card try ifconfig -m
     <device>. For example, ifconfig -m wx0.

DIAGNOSTICS
     wx%d: can't map registers  A fatal initialization error has occurred.

     wx%d: couldn't map interrupt  A fatal initialization error has occurred.

     wx%d: couldn't establish interrupt  The device failed to allocate an in-
     terrupt (irq) line.

     wx%d: len (%lx) over a page for the receive ring  The size of the receive
     ring is larger than the hardware page size.

     wx%d: could not allocate rcv descriptors  The device failed to allocate
     memory for the receive descriptors.

     wx%d: rcv descriptors not 4KB aligned  The memory management system re-

     turned memory for the receive descriptors that was not aligned correctly.

     wx%d: len (%lx) over a page for the xmit ring  The size of the transmit
     ring is larger than the hardware page size.

     wx%d: could not allocate xmt descriptors  The device failed to allocate
     memory for the transmit descriptors.

     wx%d: xmt descriptors not 4KB aligned  The memory management system re-
     turned memory for the transmit descriptors that was not aligned correct-
     ly.

     wx%d: failed to do common attach (%d)  The operating system independent
     section of the device driver initialization failed.

     wx%d: link intr 0x%x  The device has sensed a change in its link to the
     network.

     wx%d: packet with errors (%x)
     wx%d: receive descriptor with no mbuf
     wx%d: lost sync with partial packet
     wx%d: null mbuf in gc

     wx%d: excess collisions  The device has dropped a packet because too many
     collisions were seen when trying to send it.

     wx%d: lost carrier  The device has lost link integrity with the network,
     most likely a cabling problem.

     wx%d: nactive < 0?
     wx%d: swdpio did not clear

     wx%d: link never came up  The device never saw the link to the network
     established.

     wx%d: device timeout  The device has stopped responding to the network,
     or there is a problem with the network connection (cable).

     wx%d: could not re-init device  An error occurred when trying to reset
     the device.

     wx%d: could not set up rbufs

SEE ALSO
     arp(4), ifmedia(4), netintro(4), ifconfig(8)

AUTHORS
     The wx driver was written by Matthew Jacob <mjacob@freebsd.org>.

HISTORY
     OpenBSD support for the wx device driver first appeared in OpenBSD 2.7.

BUGS
     The wx device driver does not recover well from link-up/link-down events.

OpenBSD 3.0                    January 29, 2000                              2