1.\" $NetBSD: ix.4,v 1.4 1997/10/19 13:00:53 mrg Exp $ 2.\" 3.\" Copyright (c) 1986, 1991, 1993 4.\" The Regents of the University of California. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" from: @(#)ix.4 8.1 (Berkeley) 6/5/93 35.\" 36.Dd June 5, 1993 37.Dt IX 4 vax 38.Os BSD 4.2 39.Sh NAME 40.Nm ix 41.Nd Interlan Np100 10 Mb/s Ethernet interface 42.Sh SYNOPSIS 43.Cd "device np0 at uba0 csr 166000 vector npintr" 44.Sh DESCRIPTION 45The 46.Nm ix 47interface provides access to a 10 Mb/s Ethernet network through 48an Interlan Np100 controller used as a link-layer interface. 49.Pp 50This interface is unusual in that it requires loading firmware 51into the controller before it may be used as a network interface. 52This is accomplished by opening a character special device, 53and writing data to it. 54A program to load the image is provided in 55.Pa /usr/src/new/np100 . 56The sequence of commands would be: 57.Bd -literal -offset indent 58# ./npload np.image [/dev/np<board #> if other than np00] 59# sleep 10 60# ifconfig ix0 ... 61.Ed 62.Pp 63Each of the host's network addresses 64is specified at boot time with an 65.Dv SIOCSIFADDR 66.Xr ioctl 2 . 67The 68.Nm ix 69interface employs the address resolution protocol described in 70.Xr arp 4 71to dynamically map between Internet and Ethernet addresses on the local 72network. 73.Pp 74The interface normally tries to use a 75.Dq trailer 76encapsulation 77to minimize copying data on input and output. 78The use of trailers is negotiated with 79.Tn ARP . 80This negotiation may be disabled, on a per-interface basis, 81by setting the 82.Dv IFF_NOTRAILERS 83flag with an 84.Dv SIOCSIFFLAGS 85.Xr ioctl . 86.Sh DIAGNOSTICS 87.Bl -diag 88.It "ix%d: Req failed, cmd %x, stat %x, ust error %x,%x." 89The firmware in the controller refused to honor a request from 90.Tn UNIX 91in initializing packet level communications. 92The board may need to be reset and reloaded. 93Or, you may not have allowed enough time between loading the board 94and issuing the request to begin unix network operation. 95.Pp 96.It ix%d: can't initialize. 97The interface was unable to obtain unibus resources required for operation. 98.Pp 99.It ix%d: failed to reinitialize DLA module. 100The interface got sick after attempting to reprogram its physical 101ethernet address. Try reloading the firmware. 102The attempt is made only when this interfaces is not the first 103one configured for 104.Tn XNS . 105.Pp 106.It ix%d: can't handle af%d. 107The interface was handed 108a message with addresses formatted in an unsuitable address 109family; the packet was dropped. 110.Pp 111.It ix%d: stray xmit interrupt, npreq=%x. 112This may happen if the board is reloaded while network processes are still 113running. 114.Pp 115.It ixrint: cqe error %x, %x, %x. 116This will result if an 117.Xr ifconfig 8 118request is made at an inopportune time, such as not allowing 119enough time after loading the firmware. 120After 100 such errors are logged, the unix network driver will 121shut itself down, saying: 122.Pp 123.It ixrint: shutting down unix dla. 124The recourse is to reload the firmware and allow more time. 125.El 126.Sh SEE ALSO 127.Xr netintro 4 , 128.Xr inet 4 , 129.Xr arp 4 , 130.Xr np 4 . 131.Sh HISTORY 132The 133.Nm 134driver appeared in 135.Bx 4.3 . 136