MirBSD manpage: fxp(4)
FXP(4) BSD Programmer's Manual FXP(4)
fxp - Intel EtherExpress PRO/100 Ethernet driver
fxp* at pci? dev ? function ?
fxp* at cardbus? dev ? function ?
icsphy* at mii? phy ?
inphy* at mii? phy ?
nsphy* at mii? phy ?
The fxp device driver supports the Intel EtherExpress 100 family of Eth-
ernet cards based on the i82557, i82558, i82559 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:
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
Other models of Intel network cards are supported by the ie(4) and iy(4)
drivers. 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 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 sup-
ported by both the inphy(4) and nsphy(4) drivers.
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).
arp(4), cardbus(4), icsphy(4), ie(4), ifmedia(4), inphy(4), intro(4),
iophy(4), iy(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.
MirBSD #10-current April 28, 1998 1