From owner-freebsd-bugs  Sat Jul 29 15:58:05 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id PAA03114
          for bugs-outgoing; Sat, 29 Jul 1995 15:58:05 -0700
Received: from Root.COM ([198.145.90.1])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id PAA03100
          for <freebsd-bugs@freebsd.org>; Sat, 29 Jul 1995 15:58:03 -0700
Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id PAA13309; Sat, 29 Jul 1995 15:57:24 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id PAA00596; Sat, 29 Jul 1995 15:58:47 -0700
Message-Id: <199507292258.PAA00596@corbin.Root.COM>
To: n6156@vistec.com (Marcus John)
cc: freebsd-bugs@freebsd.org
Subject: Re: Init problems with WD 8003E 
In-reply-to: Your message of "Sat, 29 Jul 95 23:18:00 +0700."
             <m0scJH7-0001J2C@vistec.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sat, 29 Jul 1995 15:58:47 -0700
Sender: bugs-owner@freebsd.org
Precedence: bulk

>I often get "ed0 device timeout"-errors directly after booting up my 2.0
>or 2.0.5 release. My machine is eqipped with a WD 8003 compatible :-).
>
>The kernel configuration is definitely OK! Because the init-code for the 
>WD card works 50% of the time.
>
>Surprisingly after I load a Packet-driver in DOS mode the problem
>disappears. Unfortuately I have no source for this rather old driver.

   It sounds like a configuration problem, but it is difficult to tell. Have
you tried assigning the card to a different irq or shared memory address to
see if it affects the problem? Could be having a conflict with another card at
the same I/O address?

-DG