From owner-freebsd-questions Mon May 26 12:41:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07091 for questions-outgoing; Mon, 26 May 1997 12:41:16 -0700 (PDT) Received: from radford.i-plus.net (root@Radford.i-Plus.net [206.99.237.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA07085 for ; Mon, 26 May 1997 12:41:12 -0700 (PDT) Received: from abyss (pitlord@Abyss.i-Plus.net [206.99.237.44]) by radford.i-plus.net (8.8.5/8.8.5) with SMTP id PAA01807; Mon, 26 May 1997 15:38:23 -0400 (EDT) Message-Id: <199705261938.PAA01807@radford.i-plus.net> X-Mailer: Microsoft Outlook Express 4.71.0544.0 From: "Troy Settle" To: , "P. van Leeuwen" Subject: Re: ed0 timeout Date: Mon, 26 May 1997 15:40:50 -0400 X-Priority: 3 X-MSMail-Priority: Normal MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0544.0 Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: P. van Leeuwen >Hi > >I'm having strange problems with my pc. >First, I noticed the following error, it being repeated a zillion times :) > >/kernel : ed0 : device timeout > >Sometimes it seems to be fatal, as I would lose my network connection, but >other times ( like now ) my connection is fine, but the error is there. I have changed >the network adapter three times and this morning a put in a new motherboard, and still >no change. My hardware is as follows : > >133Mhz Pentium >Asus P/I -P55TVP4/133 >IDE controller + 1.6G drive >D-link De220 network adapter (in non PNP mode) > >The error started when I upgraded to 2.2-stable from 2.2.1-RELEASE. The make world >also failed twice. The error is probably hardware related, because both >NT and DOS give me network errors. But can it be the adapter? (All three?) > >Any suggestions? > I've had this come up a few times, and after much fussing, it turned out to be bad network media. I had to replace a segment of coax that had been damaged when crushed by a desk. Other times, it was either a terminator or a T that had gone bad. If you are indeed using coax as your network media, make sure that one end is grounded (only one end). Second, make sure that each piece of wire is long enough (I would say at least 6 feet). Third, check to see if there's any T 's that are gone bad (doens't take much). Finally, make sure that your terminators are in good shape. Remember also, that you can only have 2 terminators on any one network. If you are using TP wiring, make sure that all the connections are good, and that you have at least cat3 wire for 10baseT, and cat5 for 100baseT. One bad connection can cause major problems on such a network. In both cases, a test kit is indespensible. -- Troy Settle Network Administrator, iPlus Internet Services http://www.i-Plus.net