OpenBSD manual page server

Manual Page Search Parameters
FXP(4) Device Drivers Manual FXP(4)

fxp — Intel EtherExpress PRO/100 10/100 Ethernet device

fxp* at pci?
fxp* at cardbus?
icsphy* at mii?
inphy* at mii?
iophy* at mii?
nsphy* at mii?

The fxp device driver supports the Intel EtherExpress 100 family of Ethernet cards based on various revisions of the i82557, i82558, i82559, i82559S, i82550, i82551, and i82562 chipsets. These come in several different varieties, including dual-port cards, and as built-in Ethernet solutions on certain motherboards. This includes, among others, the following models:

This list is not exhaustive. In particular, the fxp driver should support any card by any manufacturer which is based on one of the aforementioned chipsets.

The following media types and options (as given to ifconfig(8)) are supported:

autoselect
Enable autoselection of the media type and options (default).
100baseTX mediaopt full-duplex
Set 100Mbps (Fast Ethernet) operation and force full-duplex mode.
100baseTX mediaopt half-duplex
Set 100Mbps (Fast Ethernet) operation and force half-duplex mode.
10baseT mediaopt full-duplex
Set 10Mbps operation and force full-duplex.
10baseT mediaopt half-duplex
Set 10Mbps operation and force half-duplex.

If no media options are present, the fxp driver places the card into autoselect mode.

Some devices are able to do interrupt coalescing but it requires firmware updating. The following firmware files are potentially loaded on demand when an interface is brought up:

/etc/firmware/fxp-d101a
 
/etc/firmware/fxp-d101b0
 
/etc/firmware/fxp-d101ma
 
/etc/firmware/fxp-d101s
 
/etc/firmware/fxp-d102
 
/etc/firmware/fxp-d102c
 
/etc/firmware/fxp-d102e
 

If a file is missing, the driver attempts to operate anyway.

fxp%d: couldn't map memory
A fatal initialization error has occurred.
fxp%d: couldn't map interrupt
A fatal initialization error has occurred.
fxp%d: Failed to malloc memory
There are not enough mbufs available for allocation.
fxp%d: device timeout
The device has stopped responding to the network, or there is a problem with the network connection (cable).
fxp%d: error %d, could not read firmware %s
The device is able to do interrupt coalescing but required firmware file is missing.

arp(4), cardbus(4), icsphy(4), ifmedia(4), inphy(4), intro(4), iophy(4), netintro(4), nsphy(4), pci(4), hostname.if(5), ifconfig(8)

The fxp device driver first appeared in OpenBSD 2.2.

The fxp device driver was written by David Greenman. This manual page was written by David E. O'Brien.

August 31, 2007 OpenBSD-5.1