From owner-freebsd-bugs Thu Mar 23 19:40:59 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from smtp6.teleport.com (smtp6.teleport.com [192.108.254.45]) by hub.freebsd.org (Postfix) with SMTP id 98AE437BC28 for ; Thu, 23 Mar 2000 19:40:55 -0800 (PST) (envelope-from phred@teleport.com) Received: (qmail 2916 invoked from network); 24 Mar 2000 03:40:49 -0000 Received: from user2.teleport.com (qmailr@192.108.254.12) by smtp6.teleport.com with SMTP; 24 Mar 2000 03:40:49 -0000 Received: (qmail 9971 invoked by uid 414); 24 Mar 2000 03:40:45 -0000 Date: 24 Mar 2000 03:40:45 -0000 Message-ID: <20000324034045.9970.qmail@user2.teleport.com> From: phred@teleport.com To: freebsd-bugs@freebsd.org Subject: re kern/17565 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Further to my bug report last night: a friend pointed out jkh's announcement of the fixed-up 4.0-RELEASE which I was not aware of. Given that I was downloading it last night (i.e., after the patched code was put on the ftp servers), there are two possibilities: either an actual bug (which seems unlikely, given the ubiquity of PCI-IDE), or something odd about my mobo, an ASUS ME-99B Socket 370 type for the Celerons. And that may be the case, since I tried installing OpenBSD 2.6 last night as a cross-check and came up with the same result: no disk access during the installation. Perhaps it's just a flaw on my particular board, or perhaps it's a BIOS or firmware issue, or perhaps there is some generic interface issue (which in all fairness I couldn't call a "bug"). I'll check some more things, one of which is to get 3.4 on a CD-ROM (Powell's Tech Bookstore is about six blocks away from me here in downtown Portland, Oregon :) and report back what I find. thx, phred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message