Date: Fri, 28 Feb 1997 10:29:18 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Ted Cohn <ted@wildeye.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: ed0 device timeout! Message-ID: <Pine.BSI.3.94.970228102545.11866B-100000@localhost> In-Reply-To: <v02130500af3ba44fb3bb@[206.99.115.112]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Feb 1997, Ted Cohn wrote: > I've read numerous archived postings regarding this, but the solutions > do not correct my problem with the board. I've installed version 2.1.6 > and have built a small kernel with only specific devices enabled. The > board's IRQ is 10 and port is 0x300. Of course this board works > perfectly running Win95. > > It worked briefly at one point, but froze in mid-ftp transfer. The > connection via 10Base-T appears fine. My Powerbook duo runs fine with > the cable. I've tried different cables without luck too. Could the > device driver itself be buggy? It is more likely that your Ethernet card is busted. It may be marginally OK, so win95 won't complain, but FreeBSD is the greatest hardware tester around and will ferret out flaky hardware. Plus, NE2000 are cheap on purpose, they aren't the highest quality hardware in the universe. Try replacing it and see if that helps. And just for kicks, esp. if this is a Plug & Pray box, make sure nothing else is using IRQ 10. I know for a fact that the ed0 driver is very good. I ran an NE2000 pretty hard in this box (was a P90) for several months without a single burp. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.970228102545.11866B-100000>