Skip site navigation (1)Skip section navigation (2)

FreeBSD Man Pages

Man Page or Keyword Search:
Man Architecture
Apropos Keyword Search (all sections) Output format
home | help
LNC(4)		     FreeBSD/i386 Kernel Interfaces Manual		LNC(4)

NAME
     lnc -- AMD	Lance/PCnet Ethernet device driver

SYNOPSIS
     device lnc0 at isa? port 0x280 irq	10 drq 0

DESCRIPTION
     The lnc driver provides support for the AMD family	of Lance/PCnet Ether-
     net NICs including	the Am7990 and Am79C960.  The Ethernet cards supported
     by	the lnc	interface are:

	   Novell NE2100
	   Novell NE32-VL
	   Isolan BICC
	   Digital DEPCA
	   Hewlett Packard Vectra 486/66XM
	   Hewlett Packard Vectra XU
	   Diamond HomeFree

DIAGNOSTICS
     lnc%d: Framing error  A framing error occurred.  This means a CRC error
     also occurred.  This caused the driver to drop the	packet that contained
     the framing error.

     lnc%d: Receive CRC	error  The received Ethernet frame failed the CRC
     checksum.	This caused the	driver to drop the packet that failed the
     checksum.

     lnc%d: Packet dropped, no mbufs  The driver ran out of mbuf's.  This may
     suggest a resource	problem.

     lnc%d: Couldn't allocate memory for NIC  This is a	fatal error.  The
     driver will not attach to the card	under this circumstance.

     lnc%d: Memory allocated above 16Mb	limit  ISA and ESIA cards require
     bounce buffers for	DMA transfers above 16mb.  The Am7990 and Am79C960
     only have 24 address lines	and so can only	access the lower 16Mb of phys-
     ical memory.  The lnc driver assumes the memory it	allocates is within
     the lower 16Mb range.  This is not	a very valid assumption	but there's
     nothing that can be done about it yet.  For shared	memory NICs this isn't
     relevant.

     lnc%d: Device timeout -- Resetting	 The device has	stopped	responding to
     the network, or there is a	problem	with the network connection (cable).
     Make sure the network connection in use is	the same one the card is con-
     figured for.

     lnc%d: Transmit late collision  --	Net error?
     lnc%d: Loss of carrier during transmit -- Net error?
     lnc%d: Transmit of	packet failed after 16 attempts	-- TDR = %d
     lnc%d: Heartbeat error -- SQE test	failed
     lnc%d: Babble error - more	than 1519 bytes	transmitted
     lnc%d: Missed packet -- no	receive	buffer
     lnc%d: Memory error  -- Resetting
     lnc%d: Couldn't get mbuf for transmit packet -- Resetting
     lnc%d: Receive buffer error
     lnc%d: Receive overflow error
     lnc%d: Receive interrupt with buffer still	owned by controller --
     Resetting
     lnc%d: Receive interrupt but not start of packet -- Resetting
     lnc%d: Start of packet found before end of	previous in receive ring --
     Resetting
     lnc%d: End	of received packet not found --	Resetting
     lnc%d: Transmit interrupt with buffer still owned by controller --
     Resetting
     lnc%d: Transmit interrupt but not start of	packet -- Resetting
     lnc%d: Start of packet found before end of	previous in transmit ring --
     Resetting
     lnc%d: End	of transmitted packet not found	-- Resetting
     lnc%d: Transmit buffer error -- Resetting
     lnc%d: Transmit underflow error --	Resetting

BUGS
     This driver has the potential of being the	most verbose of	any of the
     Ethernet device drivers.

SEE ALSO
     arp(4), netintro(4), ng_ether(4), ifconfig(8)

HISTORY
     The lnc device driver first appeared in FreeBSD 2.2.

AUTHORS
     The lnc device driver was written by Paul Richards.  Support for the AMD
     PCHome phone-line based network added by Robert Watson.  This manual page
     was written by David E. O'Brien.

FreeBSD	9.3		       January 19, 1997			   FreeBSD 9.3

NAME | SYNOPSIS | DESCRIPTION | DIAGNOSTICS | BUGS | SEE ALSO | HISTORY | AUTHORS

Want to link to this manual page? Use this URL:
<http://www.freebsd.org/cgi/man.cgi?query=lnc&sektion=4&manpath=FreeBSD+4.5-RELEASE>

home | help