From owner-freebsd-questions  Wed Mar 17 20:33:51 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from inet.chip-web.com (c1003518-a.plstn1.sfba.home.com [24.1.82.47])
	by hub.freebsd.org (Postfix) with SMTP id CD0A614C29
	for <freebsd-questions@FreeBSD.ORG>; Wed, 17 Mar 1999 20:33:49 -0800 (PST)
	(envelope-from ludwigp@bigfoot.com)
Received: (qmail 250 invoked from network); 18 Mar 1999 04:33:30 -0000
Received: from speedy.chip-web.com (HELO speedy) (172.16.1.1)
  by inet.chip-web.com with SMTP; 18 Mar 1999 04:33:30 -0000
Message-Id: <4.1.19990317203143.00cdbe50@mail-r>
X-Sender: ludwigp2@mail-r
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 17 Mar 1999 20:33:28 -0800
To: Chris <chrismar@readington.com>, freebsd-questions@FreeBSD.ORG
From: Ludwig Pummer <ludwigp@bigfoot.com>
Subject: Re: ed0 timeout
In-Reply-To: <Pine.BSF.4.10.9903172220050.7030-100000@walnut.readington.
 com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 07:37 PM 3/17/99 , Chris wrote:
>Hey, I just installed FreeBSD 3.1-RELEASE from the CDs, went perfectly,
>but I can't seem to get it on the network.
...
>ed0: device timeout
>
>I realize that this is probably covered in archives, but this not working
>at the moment. :)

Or the manpage...

toy# man 4 ed
ED(4)        FreeBSD Kernel Interfaces Manual (i386 Architecture)        ED(4)

NAME
     ed - high performance ethernet device driver
...
DIAGNOSTICS
...
     ed%d: device timeout  Indicates that an expected transmitter interrupt
     didn't occur. Usually caused by an interrupt conflict with another card
     on the ISA bus.

IIRC, bad cabling can also cause device timeout errors.

--Ludwig Pummer ( ludwigp@bigfoot.com ) ICQ UIN: 692441


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message