fxp - Intel EtherExpress PRO/100 Ethernet device driver

CONTENTS

Synopsis
Description
Hardware
Diagnostics
See Also
History
Authors

To compile this driver into the kernel, place the following lines in your kernel configuration file:

.Cd device miibus


.Cd 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"

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 ifconfig(8).

The fxp driver supports reception and transmission of extended 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 ifconfig(8) will download the microcode to the chip if it is available.

Adapters supported by the fxp driver include:

• Intel EtherExpress PRO/10
• Intel InBusiness 10/100
• Intel PRO/100B / EtherExpressPRO/100 B PCI Adapter
• Intel PRO/100+ Management Adapter
• Intel PRO/100 VE Desktop Adapter
• Intel PRO/100 M Desktop Adapter
• Intel PRO/100 S Desktop, Server and Dual-Port Server Adapters
• Contec C-NET(PI)-100TX (PC-98)
• NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)
• NEC PC-9821X-B06 (PC-98)
• Many on-board network interfaces on Intel motherboards

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.prefer_iomap= 0".
fxp%d: Microcode loaded, int_delay: %d usec bundle_max: %d	The chip has successfully downloaded the microcode, and changed the parameterized values to the given settings.

arp(4), miibus(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8)

The fxp device driver first appeared in
.Fx 2.1 .

.An -nosplit The fxp device driver was written by
.An David Greenman . It has then been updated to use the busdma API and made endian-clean by
.An Maxime Henrion . This manual page was written by
.An David E. O’Brien .

Search for    or go to Top of page |  Section 4 |  Main Index

Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.