*BSD News Article 67379


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!asstdc.scgt.oz.au!nsw.news.telstra.net!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!news.vbc.net!news.cais.net!newsfeed.internetmci.com!solaris.cc.vt.edu!news.duke.edu!usenet
From: Charles Reese <reese@chem.duke.edu>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: ed0: device timeout (help)
Date: 29 Apr 1996 13:50:03 GMT
Organization: Duke University
Lines: 42
Message-ID: <4m2heb$6bk@news.duke.edu>
References: <4l695g$sup@river.biddeford.com> <Pine.BSF.3.91.960419105319.12453A-100000@enteract.com> <4lvkq5$cd@anorak.coverform.lan>
NNTP-Posting-Host: async135.async.duke.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 1.22 (Windows; I; 16bit)

brian@awfulhak.demon.co.uk (Brian Somers) wrote:
>Kevin Dulzo (kdulzo@enteract.com) wrote:
>
>
>: 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]
>
>[and more]
>
>: 	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
>
>If it's a cheapnet network, you're not terminated.  If you have no wire
>connected, plug a terminator directly onto the card.
>
>
>--
>Brian <brian@awfulhak.demon.co.uk>
>Don't _EVER_ lose your sense of humour....

I also had a problem like this when I first installed FreeBSD.  In my 
case it turned out to be the IRQ I was using.  It was shared with comm 2, 
(which I wasn't using) when I changed the IRQ the problem stopped.


Cheers
Charlie Reese