From owner-freebsd-questions Wed Nov 13 07:33:03 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA23892 for questions-outgoing; Wed, 13 Nov 1996 07:33:03 -0800 (PST) Received: from croute.com (ishm2.croute.com [199.97.106.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA23821; Wed, 13 Nov 1996 07:32:41 -0800 (PST) Received: from bldg1.croute.com by croute.com (4.1/SMI-4.1) id AA00337; Wed, 13 Nov 96 09:31:53 CST Received: from COMPUROUTE/SpoolDir by bldg1.croute.com (Mercury 1.13); Wed, 13 Nov 96 9:30:58 +600 Received: from SpoolDir by COMPUROUTE (Mercury 1.13); Wed, 13 Nov 96 9:30:29 +600 From: "Larry Dolinar" Organization: CompuRoute, Inc. To: owner-questions@freebsd.org Date: Wed, 13 Nov 1996 09:30:21 +600 CDT Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Subject: Re: ed0 device timeout Cc: Just Baldrick , fadorno@mail.gte.net, questions@freebsd.org Priority: normal X-Mailer: Pegasus Mail v3.40 Message-Id: <1352AE413600@bldg1.croute.com> Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From: Fred Adorno >Nick Liu wrote: >> >> On Mon, 11 Nov 1996, Just Baldrick wrote: >> >> > We had the same problem with ed0 'Device timeout'. In our >> >I am aware of all the above. I used the softlink setup thru EZsetup. I >changed the settings to match the kernel. It has been working fine >until I went into Windows yesterday after a warm boot. Went I went back >to FreeBSD after a warm boot the timeout errors appeared again. It >seems to go away if I do a cold boot and then go into FreeBSD. I've seen the same thing with Maxtech NX-16BT's due to some Novell ODI nonsense. The particular machine in question is a dual-boot 486-66 I use for Novell and Unix backups, ergo the Novell stuff is a necessary evil. Cold boots are the answer; something about ISA bus resets, IIRC. hth, larry