Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!csn!boulder!alumni!plotkin From: plotkin@alumni.cs.Colorado.EDU (Leo Classic) Subject: ed0: device timeout, freebsd cslip Message-ID: <CECt8C.29o@Colorado.EDU> Keywords: freebsd snail turtle slug Sender: news@Colorado.EDU (USENET News System) Organization: University of Colorado, Boulder References: <J5SHBHSK@math.fu-berlin.de> <1993Oct3.020559.16808@zen.void.oz.au> Date: Mon, 4 Oct 1993 03:48:11 GMT Lines: 63 In article <1993Oct3.020559.16808@zen.void.oz.au> sjg@zen.void.oz.au (Simon J. Gerraty) writes: >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. I had the same problem with my D-Link DE100 (ne1000 clone) 'running' FreeBSD EPSILON. (386/33DX. Gastropods can't run.) I suspect the problem was caused by an invalid shared memory address for this card. I deleted the iomem 0xXXXXX from the ed0 definition and re-compiled. Worked like a charm! Incidentally, I've seen a 3c503 which became unhappy when paired with a 8900c video card in one cheap no name clone. 3com tech support told me to disable shared memory and DMA, and it started working. Maybe reconfiguring your card for the new IRQ and base address disturbed the magic voodoo which made the cards coexist in harmony with your particular motherboard chipset. You could try to restore the cosmic ballance by re-compiling the kernel with the old IRQ, base address and iomem address and the ethernet card back the way it was. If that fails, break out the black candles and the goat. Oh yes, if you have a thinnet network make sure you re-attached the BNC after ripping your card out to reconfigure it for the new IRQ and base memory. OB QUESTION: is anyone else getting simply glacial CSLIP performance from FreeBSD epsilon? With 386BSD 0.1 I had about 1.1k/sec ftp, with NetBSD 0.9 the lowest I've seen is 1.3k/ sec. FreeBSD provides a consistent and stunning .6k/sec. Even Linux pl13 gives .8k/sec! I know I'm using the computing equivalent of a 1 inch penis, but .6k/sec CSLIP with recognized 16550A UARTs, ~5 MIPS and a perfectly clean phone line? I think I could get better throughput by using tree sloths as the transport layer. Not that I'm complaining too loudly, any performance at all out of a stable OS beats the 2 hour uptimes I got with Linux. --leo p.s. Hats off to the FreeBSD team for making the kernel source avaliable separately from all the other spew in the epsilon release. Nothing like having to ftp 1000 gigabytes of effluvium at .6k/sec to configure a usable kernel. -- -- Leo plotkin@alumni.cs.colorado.edu "There is a fine line between gross and brilliant" -- me, on coding. /* Gross, make brilliant later */ -- Andrew Boardman