Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

de(4) [bsd man page]

DE(4)							     Kernel Interfaces Manual							     DE(4)

NAME
de - DEC DEUNA 10 Mb/s Ethernet interface SYNOPSIS
/sys/conf/SYSTEM: NDE de_controllers # DEUNA DESCRIPTION
The de interface provides access to a 10 Mb/s Ethernet network through a Digital Equipment UNIBUS Network Adapter (DEUNA). Each of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl. The de interface employs the address resolution protocol described in arp(4P) to dynamically map between Internet and Ethernet addresses on the local network. The interface normally tries to use a ``trailer'' encapsulation to minimize copying data on input and output. The use of trailers is nego- tiated with ARP. This negotiation may be disabled, on a per-interface basis, by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl. DIAGNOSTICS
de%d: hardware address %s. This is a normal autoconfiguration message noting the 6 byte physical ethernet address of the adapter. de%d: oerror, flags=%b tdrerr=%b (len=%d). The hardware indicated an error in transmitting a packet to the cable. The status and error flags are reported. de%d: ierror, flags=%b lenerr=%b (len=%d). The hardware indicated an error in reading a packet from the cable. The status and error flags are reported. de%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped. de%d: buffer unavailable. The interface received more packets than it had buffers allocated to receive them. de%d: address change failed, csr0=%b csr1=%b. The interface was unable to reprogram its physical ethernet address. This may happen with very early models of the interface. This facility is used only when the controller is not the first network interface configured for XNS. The following messages indicate a probable hardware error performing the indicated operation during autoconfiguration or initialization. The two control and status registers should indicate the nature of the failure. See the hardware manual for details. de%d: reset failed, csr0=%b csr1=%b. de%d: ppcb failed, csr0=%b csr1=%b. de%d: read addr failed, csr0=%b csr1=%b. de%d: wtring failed, csr0=%b csr1=%b. de%d: wtmode failed, csr0=%b csr1=%b. SEE ALSO
intro(4N), inet(4F), arp(4P) 3rd Berkeley Distribution August 20, 1987 DE(4)

Check Out this Related Man Page

xna(4)							     Kernel Interfaces Manual							    xna(4)

Name
       xna - DEBNI and DEMNA Ethernet interfaces

Syntax
       device xna0 at vaxbi? node? vector xnaintr (DEBNI)
       device xna0 at xmi? node? vector xnaintr (DEMNA)

Description
       The  driver provides access to a 10 Mbytes Ethernet network through the DEBNI and DEMNA adapters.  The DEBNI is an Ethernet to BI bus.  The
       DEMNA is an Ethernet to XMI adapter.

       The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl.  The driver employs the Address  Resolution  Protocol,	as
       described in to map dynamically between Internet and Ethernet addresses on the local network.

       The  driver normally tries to use a trailer encapsulation to minimize copying data on input and output.	This can be disabled for an inter-
       face by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.  Trailers are used only for packets destined for Internet hosts.

       The SIOCSPHYSADDR ioctl can be used to change the physical address of the adapter and SIOCRPHYSADDR  can  be  used  to  read  its  physical
       address.   SIOCADDMULTI	and  SIOCDELMULTI can be used to add or delete multicast addresses.  The driver supports a maximum of 12 multicast
       addresses. The argument to the latter ioctls is a pointer to an ``ifreq'' structure found in

       SIOCRDCTRS and SIOCRDZCTRS ioctls can be used to read or read and clear network counters. The argument  to  the	latter	two  ioctls  is  a
       pointer to a counter structure ``ctrreq'' found in

       The ioctls SIOCENABLBACK and SIOCDISABLBACK can be used to enable and disable the interface loopback mode.

Restrictions
       The PUP protocol family is not supported.

Diagnostics
       xna%d: port self-test failed:<register list>
       Adapter did not pass the power-up self-test during autoconfiguration time. The port attachment fails.

       xna%d: couldn't allocate...
       The driver was unable to allocate memory for adapter data structures.  The port attachment fails.

       xna%d: port probe failed:<register list>
       The driver was unable to bring the adapter into the initialized state.  The port attachment fails.

       xna%d: port init failed:<register list>
       The driver failed to prepare the adapter for runtime use.

       xna%d: port state changed, resetting:<register list>
       The adapter issued a port state change interrupt. The port state is reset.

       xna%d: port reset failed
       The driver was unable to bring the adapter into the initialized state during a port reset.

       xna%d: command failed, error code:<error code>
       The adapter port command failed. The error code gives reason for failure.

       xna%d: couldn't handle af%d
       A packet with an undefined protocol type has been sent to the adapter.

       xna%d: addmulti failed, multicast list full
       Too many multicast requests have been made.

See Also
       arp(4p), inet(4f), intro(4n)

																	    xna(4)
Man Page

Featured Tech Videos