*BSD News Article 72027


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!newsgate.duke.edu!news.mathworks.com!fu-berlin.de!news.belwue.de!news.uni-stuttgart.de!uniol!uni-erlangen.de!news.tu-chemnitz.de!irz401!orion.sax.de!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Switching Ethernet Cards
Date: 25 Jun 1996 21:22:16 GMT
Organization: Private BSD site, Dresden
Lines: 30
Message-ID: <4qpla8$juf@uriah.heep.sax.de>
References: <roy-1906961616510001@206.53.164.230>
  <31C8E5A7.6AEC@www.play-hookey.com> <roy-2006961101470001@206.53.164.230>
  <4qjoag$4ds@uriah.heep.sax.de> <4qki69$nb0@samba.rahul.net>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E

Dennis Holmes <dholmes@rahul.net> wrote:

> interrupt for the ethernet card.  I always get the same result: the card is
> probed at boot time, but "ed0: device timeout" is reported whenever I try to
> use it.

Hmm, that's strange.

> Also, I borrowed a WD8003E card and got the same result.  I'm not sure I
> had all the jumpers set correctly though, as I have no documentation for
> that card.  It was reported correctly at boot time.  That one has AUI and
> coax connectors, so I had a transciever and 10baseT cable attached to the
> AUI port.  The IRQ jumper pins are labelled, so I'm reasonably confident
> that part was correct.

Software or hardware configurable WD8003?  For the soft version, you
need an EZsetup program from SMC in order to activate the AUI port.
The hard-configurable version has got two jumpers next to the fat
voltage doubler (big ``blackbox'' in the middle of the card).

Of course, a mis-selected interface port (AUI vs. BNC vs. UTP) will
also cause the "device timeout" message, as well as a broken on-board
transceiver.  (That's the most common hardware failure on many cards.)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)