From owner-freebsd-current Wed Feb 16 12: 7:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id F155737B551 for ; Wed, 16 Feb 2000 12:07:26 -0800 (PST) (envelope-from jas@flyingfox.com) Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by builder.freebsd.org (Postfix) with ESMTP id 98350132D9 for ; Wed, 16 Feb 2000 12:06:47 -0800 (PST) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id LAA13282 for freebsd-current@freebsd.org; Wed, 16 Feb 2000 11:54:57 -0800 (PST) Date: Wed, 16 Feb 2000 11:54:57 -0800 (PST) From: Jim Shankland Message-Id: <200002161954.LAA13282@biggusdiskus.flyingfox.com> To: freebsd-current@freebsd.org Subject: sysinstall of 20000214 snap hangs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried installing the 2/14 4.0 snap onto a Cyrix MediaGX-based box, and the sysinstall hung at the "probing devices" phase. Because the 3.4 sysinstall works just fine on this box, and because the last thing I see on the debug screen (ttyv1) is DEBUG: Found a disk device named ad0 I'm inclined to cast a suspicious eye toward Soren's new IDE driver :-). I realize the information I've provided so far is unlikely to be sufficient to diagnose, much less remedy, the problem; but I'm not not sure what to do next. I'm happy to work with anyone who'd like to take a closer look at this. Jim Shankland Decision Data/NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message