Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!news1.erols.com!news.enteract.com!enteract.com!kdulzo From: Kevin Dulzo <kdulzo@enteract.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: ed0: device timeout (help) Date: Fri, 19 Apr 1996 10:58:14 -0500 Organization: EnterAct, L.L.C. Lines: 55 Message-ID: <Pine.BSF.3.91.960419105319.12453A-100000@enteract.com> References: <4l695g$sup@river.biddeford.com> NNTP-Posting-Host: enteract.com Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <4l695g$sup@river.biddeford.com> On 18 Apr 1996, george p swanton wrote: > > I'm feeling a little feeble-minded for not being able to > outhink some transistors and bits but I cant recall how > to do this correctly. > > I'm getting 'ed0: device timeout' during boot and cant > get the (ethernet) netwoking working... > [unecessary info cut] > ed0: flags 8863<up,br,not,ru,si,mul (abreviated)> MTU 1500 > inet 204.120.68.11 netmask 0xffffff00 broadcast 204.120.68.255 > ether 00:00:C0:0f:26:43 > lo0: flags 8009<up,loop,mul> MTU 16384 > inet 127.0.0.1 netmask 0xff000000 > add net 224.0.0.0: gateway unix1.hve.com > writeing to routing socket: file exists > add host unix1.hve.com: gateway localhost: file exists > starting routing deamons: routed ed0: device timeout > ^^^^^^^^^^^^^^^^^^^^ > This is probably simple but I'm afraid maybe so am I... > What might I have done to offend it? > > Help is appreciated, email would not burden the rest of the > world with more traffic... > > Thanks > gps > swanton@river.biddeford.com > > > It's been awhile so if I'm wrong someone correct me. Your device doesn't have any conflicts especially if 'ifconfig' was able to up the interface (i.e. ed0:...<up,...> netinfo...). but the way to verify is to watch your boot sequence and/or use 'dmesg' to verify the probe results. But "ed0:devidce timeout" in my experience, assuming the device is ok at boot, means it cannot access the network (no connection/bad connection). If the probe is ok -- check the cables/ports. Kevin Dulzo New Image Consulting PC/Mac Support Networking Support kdulzo@enteract.com