From owner-freebsd-questions Thu Jul 10 17:09:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA05858 for questions-outgoing; Thu, 10 Jul 1997 17:09:50 -0700 (PDT) Received: from mackay01.cqit.qld.edu.au (root@cqit.qld.edu.au [203.22.80.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA05852 for ; Thu, 10 Jul 1997 17:09:43 -0700 (PDT) Received: from carbon.chalmers.com.au (ppp0.cqit.qld.edu.au [203.22.80.5]) by mackay01.cqit.qld.edu.au (8.7.3/8.6.9) with ESMTP id KAA07367; Fri, 11 Jul 1997 10:05:33 +1000 (EST) Message-ID: <33C578CE.AAF36777@chalmers.com.au> Date: Fri, 11 Jul 1997 10:05:35 +1000 From: Robert Chalmers Reply-To: robert@chalmers.com.au Organization: chalmers.com.au X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: Brandon Gillespie CC: Guy Helmer , freebsd-questions@FreeBSD.ORG Subject: Re: BUG in -current ed0 driver? (Re: Help! ed0 no longer works after 'make world' upgrade to -CURRENT) X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brandon Gillespie wrote: > On Thu, 10 Jul 1997, Guy Helmer wrote: > > 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 Yup, tried a few of these tests myself. device timeout. ed0 or ed1. I've tried both ed0 and ed1. Tried them on a few cards, I have the 3.0 SNAPSHOT-5/22/1997 Sometimes it works, sometimes it dont' ? > > > > > > 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. > > Actually, after a few more tests I can safely say that the following > behaviour occurs EVERY time: > > 1) Hard Boot system with 3.0 kernel, ed0: device timeout > 2) Hard Boot system with 2.2.2 kernel, ed0 works (but of course, the > > OS doesn't load because of version incompatabilities) > 3) *soft* boot (just reset) into 3.0 kernel, ed0 WORKS?? > > Because of this behaviour, I'm assuming the 2.2.2 kernel is doing > something (initializing in some way?) which the 3.0 kernel isn't, and > which is sticking around with the soft boot... -- http://www.chalmers.com.au Books-New & Secondhand Support Whirled Peas. Agents for CIBTC. Associate of Amazon.com, and Partner Program with iBS. Books about China, books from China. Sheng huo jiu shi dou zheng Business Links in Dalian, and Beijing. Building the China Trade