Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!cass.ma02.bull.com!syd.bull.oz.au!melb.bull.oz.au!zen!sjg From: sjg@zen.void.oz.au (Simon J. Gerraty) Subject: Re: ed0: device timeout Organization: Zen programming... References: <J5SHBHSK@math.fu-berlin.de> Message-ID: <1993Oct3.020559.16808@zen.void.oz.au> Date: Sun, 3 Oct 1993 02:05:59 GMT Lines: 33 rickrac@knock1.mgh.harvard.edu (Jimmy Rearick) writes: >I keep getting this error message when my FreeBSD system boots. > ed0: device timeout >What could be causing this? I can't connect to anything on our network. >Thanks. I have the same problem with ed0 (and a WD8003E). I had assumed it was simply lack of receiving a packet on the ethernet - my machine is currently alone on the net. Jim's comments blow that theory though. My only other theory was that I had the IRQ set wrong (set by a jumper on the WD8003 and I have no doco so I'm guessing. If anyone has docs for an old 8bit WD8003E please mail me). I believe that the IRQ for the 3C503 is set by software though. If correct then this theory dies too. I know my IO address is ok as the device is probed and attached ok: Sep 12 17:47:57 zen /386bsd: ed0ed0: address 00:00:c0:dc:60:10, type WD8003E (8bit) Sep 12 17:47:57 zen /386bsd: at 0x280-0x29f irq 10 maddr 0xd0000 msize 8192 on isa That ed0ed0: bit bugs me too, but the printf's look ok. So if any one has solved the device timeout I'd love to hear too as my other machine is comming back next week and I'll want NFS running. --sjg -- Simon J. Gerraty <sjg@zen.void.oz.au> #include <disclaimer> /* imagine something _very_ witty here */