From owner-freebsd-questions  Mon Nov 11 11:39:25 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA05494
          for questions-outgoing; Mon, 11 Nov 1996 11:39:25 -0800 (PST)
Received: from value.net (root@value.net [204.188.125.4])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA05477
          for <questions@FreeBSD.ORG>; Mon, 11 Nov 1996 11:39:23 -0800 (PST)
Received: from value.net (nickliu@value.net [204.188.125.4]) by value.net (8.8.2/8.7.3) with SMTP id LAA12385; Mon, 11 Nov 1996 11:39:08 -0800 (PST)
Date: Mon, 11 Nov 1996 11:39:07 -0800 (PST)
From: Nick Liu <nickliu@value.net>
To: Just Baldrick <baldrick@rmsq.com>
cc: fadorno@mail.gte.net, questions@FreeBSD.ORG
Subject: Re: ed0 device timeout
In-Reply-To: <199611111633.JAA00912@rmsq.com>
Message-ID: <Pine.BSI.3.95.961111113410.12021A-100000@value.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



 On Mon, 11 Nov 1996, Just Baldrick wrote:

> Hi,
> 
> We had the same problem with ed0 'Device timeout'.  In our
> case it was because the ethernet card was set to a
> different IRQ than the FreeBSD IRQ.
> Also, it could be due to an IRQ conflict, eg a SoundBlaster
> trying to use the same interrupt.
> 
> 
> Hope this helps.
> 
> 

Another thing you could try is to take out the on board address specified
in your kernel config file and then recompile the kernel.

Good luck.