From owner-freebsd-small Wed May 17 22:25:48 2000 Delivered-To: freebsd-small@freebsd.org Received: from lepton.subatomix.com (okc-224-168.mmcable.com [24.94.224.168]) by hub.freebsd.org (Postfix) with ESMTP id AD7C537BD55 for ; Wed, 17 May 2000 22:25:42 -0700 (PDT) (envelope-from jss@lepton.subatomix.com) Received: from localhost (jss@localhost) by lepton.subatomix.com (8.9.3/8.9.3) with ESMTP id AAA03243; Thu, 18 May 2000 00:29:24 -0500 (CDT) (envelope-from jss@lepton.subatomix.com) Date: Thu, 18 May 2000 00:29:24 -0500 (CDT) From: "Jeffrey S. Sharp" To: Warner Losh Cc: freebsd-small Subject: Re: (Probably a) dumb question In-Reply-To: <200005180137.TAA90658@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 May 2000, Warner Losh wrote: > In message "Jeffrey S. Sharp" writes: > : selection mode. So the basic problem is that the kernel isn't choosing > : fla0s1a as the root device. > > Old bootblocks? No, I don't think so. I originally used the prep.fla.sh script from 3.4-RELEASE to prepare the DOC a few months ago. I haven't touched the MBR since then, but I replaced boot1 and boot2 with the 4.0-RELEASE versions by hand (disklabel). When I boot from the DOC, boot2 sees the DOC as BIOS drive 0, reads boot.conf, and tries 0:ad(0,a)/kernel.kgz after a few seconds. The kernel uncompresses, does its little dance, and eventually tries to mount the wrong root device. Things I haven't done yet are: * Try putting boot1 and boot2 on it again * Try using a non-kgzipped kernel =============================== Jeffrey S. Sharp (XorAxAx) jss@subatomix.com -----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS/IT/MU d-@ s-:+ a21 C++(++++) UBL+(+++$)> P L+(+++$)> E+> W++ N+(++) o? K? w++$> !O M(-) !V PS+ PE Y PGP- t+ 5 X+ R(+) tv+ b+ DI++(+++) G++ e> h--- r+++ y+++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message