From owner-freebsd-questions Thu Jul 10 09:08:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09122 for questions-outgoing; Thu, 10 Jul 1997 09:08:51 -0700 (PDT) Received: from cs.iastate.edu (cs.iastate.edu [129.186.3.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09112 for ; Thu, 10 Jul 1997 09:08:45 -0700 (PDT) Received: from longshot.cs.iastate.edu (longshot.cs.iastate.edu [129.186.3.94]) by cs.iastate.edu (8.8.5/8.7.1) with ESMTP id LAA04688; Thu, 10 Jul 1997 11:08:28 -0500 (CDT) Received: from localhost (ghelmer@localhost) by longshot.cs.iastate.edu (8.8.5/8.7.1) with SMTP id LAA16340; Thu, 10 Jul 1997 11:08:27 -0500 (CDT) X-Authentication-Warning: longshot.cs.iastate.edu: ghelmer owned process doing -bs Date: Thu, 10 Jul 1997 11:08:26 -0500 (CDT) From: Guy Helmer To: Brandon Gillespie cc: freebsd-questions@FreeBSD.ORG Subject: Re: Help! ed0 no longer works after 'make world' upgrade to -CURRENT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Jul 1997, Brandon Gillespie wrote: > On Thu, 10 Jul 1997, Brandon Gillespie wrote: > > I just upgraded from 2.2.2-RELEASE to 3.0-CURRENT with a make world, then > > a recompile of my kernel. However, my ed0 is no longer working! It has > > the exact same port/irq settings as my kernel did with 2.2.2, and it > > probes in the boot sequence. But when it tries to initialize the network > > all I get is: > > > > ed0: device timeout > > It appears to be working.. all I did: > > first boot: didn't work > boot -c, set irq/port (even though its to the same thing): didn't work > recompile kernel (same config), reboot: didn't work > reboot with old 2.2.2 kernel: didn't boot, dunno if it would have worked > reboot back to 3.0: works?? FWIW, I've been running 3.0-current for over a month now on my 386/40, and the WD8003E quit working yesterday while the system was in operation (I was running a cvsup at the time). Ever since it quit working, I get "ed0: device timeout" when the system runs the networking configuration at boot time, and I've booted numerous times; the card didn't seem to work under Win95, either. None of my (10-year old) WD8003EBT cards would even allow the system to go through POST (bus speed problems?), so I'm waiting for a cheap NE2000 clone to arrive. > Did I scare the new kernel into submission, did it see an implied threat > that I'd use 2.2.2 if it didn't get its act in shape? Why did it suddenly > work? I would have thought that Windows95 would have scared the old card into submission, so maybe it really is dead :-) Guy Helmer, Computer Science Graduate Student - ghelmer@cs.iastate.edu Iowa State University http://www.cs.iastate.edu/~ghelmer