FXP(4) OpenBSD Programmer's Manual FXP(4)
NAME
fxp - Intel EtherExpress PRO/100 10/100 Ethernet device
SYNOPSIS
fxp* at pci?
fxp* at cardbus?
icsphy* at mii?
inphy* at mii?
nsphy* at mii?
DESCRIPTION
The fxp device driver supports the Intel EtherExpress 100 family of Eth-
ernet cards based on various revisions of the i82557, i82558, i82559,
i82559S, i82550, i82551, and i82562 chipsets. These come in several dif-
ferent varieties, including dual-port cards, and as built-in Ethernet so-
lutions on certain motherboards. This includes, among others, the fol-
lowing models:
Intel EtherExpress PRO/100 PCI
Intel EtherExpress PRO/100B PCI
Intel EtherExpress PRO/100+ PCI
Intel EtherExpress PRO/100 Dual-Port PCI
Intel PRO/100 CardBus II PC Card
Intel PRO/100 VE
Intel PRO/100 VM
Intel PRO/100 M
This list is not exhaustive. In particular, the fxp driver should sup-
port any card by any manufacturer which is based on one of the aforemen-
tioned chipsets.
The following media types and options (as given to ifconfig(8)) are sup-
ported:
media autoselect
Enable autoselection of the media type and options (default).
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 10Mbps operation and force full-duplex.
media 10baseT mediaopt half-duplex
Set 10Mbps operation and force half-duplex.
If no media options are present, the fxp driver places the card into au-
toselect mode.
These cards also come with a variety of PHYs. Models exist with PHYs
supported by both the inphy(4) and nsphy(4) drivers.
FILES
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.
DIAGNOSTICS
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: failed loadfirmware of file %s: errno %d The device is able to do
interrupt coalescing but required firmware file is missing.
SEE ALSO
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)
HISTORY
The fxp device driver first appeared in OpenBSD 2.2.
AUTHORS
The fxp device driver was written by David Greenman. This manual page
was written by David E. O'Brien.
OpenBSD 4.0 April 28, 1998 2