Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ulysses.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!smb
From: smb@ulysses.UUCP (Steven Bellovin)
Newsgroups: net.unix,net.lan,net.dcom,net.unix-wizards
Subject: Re: deuna driver problems
Message-ID: <1003@ulysses.UUCP>
Date: Wed, 10-Jul-85 18:50:25 EDT
Article-I.D.: ulysses.1003
Posted: Wed Jul 10 18:50:25 1985
Date-Received: Fri, 12-Jul-85 02:29:56 EDT
References: <127@rpics.UUCP>
Distribution: net
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 26
Xref: watmath net.unix:5004 net.lan:910 net.dcom:1094 net.unix-wizards:13777

> I have Lou Salkind's@NYU driver in my 4.2 system and I am having
> some difficulties.....
> 
> When I plug it into our normal 3com tranceivers during boot after
> it finds the interface it states:
> 
> 	"de0: pcbb failed, csr0=4081 csr1=586
> 	 de0: rdphyad failed, csr0=4082 csr1=506< "
> 
> and continues until multiuser...
> 
> When I plug it into our wonderul H4000 DEC tranceivers it finds the
> interface and hangs, the lights on the board seem to indicate
> that it is hanging on a read.
> 
The DEUNA will not work at all with 3Com transceivers.  The 3Com units
are Ethernet 1.0, and hence lack the "heartbeat" signal on the collision
lines; the DEUNA objects strongly to the lack of such a signal.

It's less clear why the H4000s don't work; I'm pretty sure they will fail
if they're not connected to a properly-termianted coax.  Also note that
there are bugs in ifconfig's flag-setting that do horrible things to
DEUNAs; although I can't fully explain the mechanism, I can testify that
fixing ifconfig made some weird behavior on some DEUNAs go away.  It had
to do with resetting the RUNNING bit, so the initialization routine was
entered twice.