From owner-freebsd-current Wed Feb 16 17:41: 9 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 073DD37B595 for ; Wed, 16 Feb 2000 17:41:07 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id 4D410132D9 for ; Wed, 16 Feb 2000 17:40:25 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02710; Wed, 16 Feb 2000 17:52:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002170152.RAA02710@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jim Shankland Cc: freebsd-current@freebsd.org Subject: Re: sysinstall of 20000214 snap hangs In-reply-to: Your message of "Wed, 16 Feb 2000 11:54:57 PST." <200002161954.LAA13282@biggusdiskus.flyingfox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 17:52:27 -0800 From: Mike Smith 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 :-). 8) At that point, it's actually more or less finished with the IDE drive, actually, so it's probably not that. > 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. Debugging these is often actually really painful, because it's hard to tell where exactly you're hung up. You might try hitting a key on the main sysinstall screen (don't laugh), as well as checking for peripherals that are wedged in an active state (eg. CDROM if it's not already listed as found). Then you might also try disabling any devices in the kernel config that aren't actually present in your system (eg. second IDE channel, random ethernet interfaces especially). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message