fxp(4)

NAME

fxp - Intel EtherExpress PRO/100 Ethernet device driver

SYNOPSIS

To compile this driver into the kernel, place the  following
lines in your
kernel configuration file:
      device miibus
      device fxp
Alternatively,  to load the driver as a module at boot time,
place the
following line in loader.conf(5):
      if_fxp_load="YES"

DESCRIPTION

The fxp driver provides support for Ethernet adapters based

on the Intel
i82557, i82558, i82559, i82550, and i82562 chips.

The fxp driver supports the following media types:

autoselect Enable autoselection of the media type

and options

10baseT/UTP Set 10Mbps operation

100baseTX Set 100Mbps (Fast Ethernet) operation

The fxp driver supports the following media options:

full-duplex Set full duplex operation

Note that 100baseTX media type is not available on the

Pro/10. For further information on configuring this device, see ifcon

fig(8).

The fxp driver supports reception and transmission of ex

tended frames for
vlan(4). This capability of fxp can be controlled by means

of the
vlanmtu parameter to ifconfig(8).

The fxp driver also supports a special link option:

link0 Some chip revisions have loadable microcode which can

be used to

reduce the interrupt load on the host cpu. Not all

boards have
microcode support. Setting the link0 flag with if

config(8) will
download the microcode to the chip if it is avail

able.

HARDWARE

Adapters supported by the fxp driver include:

+o Intel EtherExpress PRO/10
+o Intel InBusiness 10/100
+o Intel PRO/100B / EtherExpressPRO/100 B PCI Adapter
+o Intel PRO/100+ Management Adapter
+o Intel PRO/100 VE Desktop Adapter
+o Intel PRO/100 M Desktop Adapter
+o Intel PRO/100 S Desktop, Server and Dual-Port Server

Adapters
+o Contec C-NET(PI)-100TX (PC-98)
+o NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX

(PC-98)
+o NEC PC-9821X-B06 (PC-98)
+o Many on-board network interfaces on Intel motherboards

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 mbuf's

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: Ethernet address ff:ff:ff:ff:ff:ff In some Alpha's

(AXPpci and
Multia) you must tell the driver to use (slower) I/O rather

than memory
to access the card. Create, if it does not yet exist, and

add to the
file /boot/device.hints the line ``hint.fxp.0.pre

fer_iomap="0"''.

fxp%d: Microcode loaded, int_delay: %d usec bundle_max: %d

The chip has
successfully downloaded the microcode, and changed the pa

rameterized values to the given settings.

SEE ALSO

arp(4), miibus(4), netintro(4), ng_ether(4), polling(4),

vlan(4),
ifconfig(8)

HISTORY

The fxp device driver first appeared in FreeBSD 2.1.

AUTHORS

The fxp device driver was written by David Greenman. It has

then been
updated to use the busdma API and made endian-clean by

Maxime Henrion.
This manual page was written by David E. O'Brien.

BSD July 16, 2005

BSD