Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!umcp-cs!chris From: chris@umcp-cs.UUCP (Chris Torek) Newsgroups: net.unix,net.lan,net.dcom,net.unix-wizards Subject: Re: deuna driver problems Message-ID: <811@umcp-cs.UUCP> Date: Thu, 11-Jul-85 19:17:07 EDT Article-I.D.: umcp-cs.811 Posted: Thu Jul 11 19:17:07 1985 Date-Received: Sat, 13-Jul-85 10:32:01 EDT References: <127@rpics.UUCP> <1003@ulysses.UUCP> Distribution: net Organization: U of Maryland, Computer Science Dept., College Park, MD Lines: 26 Xref: watmath net.unix:5021 net.lan:913 net.dcom:1097 net.unix-wizards:13804 > > 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=4081csr1=586 > > de0: rdphyad failed, csr0=4082 csr1=506< " > ... 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. While there indeed were bugs in the 4.2 ifconfig flag setting code, that shouldn't have affected the DEUNA; clearly there is a bug in that version of the driver. (The IFF_RUNNING bit is an internal bit that really means it has Unibus maps. It should be set at initialization and cleared during Unibus reset. (Actually IFF_RUNNING is an internal flag per driver, but that's what it's supposed to mean.)) -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251) UUCP: seismo!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland