4.3BSD/usr/man/man4/ix.4

.\" Copyright (c) 1986 Regents of the University of California.
.\" All rights reserved.  The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\"
.\"	@(#)ix.4	6.2 (Berkeley) 5/16/86
.\"
.TH IX 4 "May 16, 1986"
.UC 5
.SH NAME
ix \- Interlan Np100 10 Mb/s Ethernet interface
.SH SYNOPSIS
.B "device np0 at uba0 csr 166000 vector npintr"
.SH DESCRIPTION
The
.I ix
interface provides access to a 10 Mb/s Ethernet network through
an Interlan Np100 controller used as a link-layer interface.
.PP
This interface is unusual in that it requires loading firmware
into the controller before it may be used as a network interface.
This is accomplished by opening a character special device,
and writing data to it.
A program to load the image is provided in /usr/src/new/np100.
The sequence of commands would be:
.nf

	# ./npload np.image [/dev/np<board #> if other than np00]
	# sleep 10
	# ifconfig ix0 ...
.fi
.PP
Each of the host's network addresses
is specified at boot time with an SIOCSIFADDR
ioctl.  The
.I ix
interface employs the address resolution protocol described in
.IR arp (4P)
to dynamically map between Internet and Ethernet addresses on the local
network.
.PP
The interface normally tries to use a ``trailer'' encapsulation
to minimize copying data on input and output.
The use of trailers is negotiated with ARP.
This negotiation may be disabled, on a per-interface basis,
by setting the IFF_NOTRAILERS
flag with an SIOCSIFFLAGS ioctl.
.SH DIAGNOSTICS
\fBix%d: Req failed, cmd %x, stat %x, ust error %x,%x\fP.
The firmware in the controller refused to honor a request from
.UX
in initializing packet level communications.
The board may need to be reset and reloaded.
Or, you may not have allowed enough time between loading the board
and issuing the request to begin unix network operation.
.PP
\fBix%d: can't initialize\fP.
The interface was unable to obtain unibus resources required for operation.
.PP
\fBix%d: failed to reinitialize DLA module\fP.
The interface got sick after attempting to reprogram its physical
ethernet address.  Try reloading the firmware.
The attempt is made only when this interfaces is not the first
one configured for XNS.
.PP
\fBix%d: can't handle af%d\fP.  The interface was handed
a message with addresses formatted in an unsuitable address
family; the packet was dropped.
.PP
\fBix%d: stray xmit interrupt, npreq=%x\fP.
This may happen if the board is reloaded while network processes are still
running.
.PP
\fBixrint: cqe error %x, %x, %x\fP.
This will result if an 
.IR ifconfig (8c)
request is made at an inopportune time, such as not allowing
enough time after loading the firmware.
After 100 such errors are logged, the unix network driver will
shut itself down, saying:
.PP
\fBixrint: shutting down unix dla\fP.
The recourse is to reload the firmware and allow more time.
.SH SEE ALSO
intro(4N), inet(4F), arp(4P), np(4).