From owner-freebsd-hackers@FreeBSD.ORG  Mon Jun 27 22:48:47 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: hackers@freebsd.org
Delivered-To: freebsd-hackers@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4CD0C16A42B
	for <hackers@freebsd.org>; Mon, 27 Jun 2005 22:48:47 +0000 (GMT)
	(envelope-from mwm-dated-1120776563.40f9da@mired.org)
Received: from delight.idiom.com (delight.idiom.com [216.240.32.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8F4B643D70
	for <hackers@freebsd.org>; Mon, 27 Jun 2005 22:48:45 +0000 (GMT)
	(envelope-from mwm-dated-1120776563.40f9da@mired.org)
Received: from idiom.com (idiom.com [216.240.32.1])
	by delight.idiom.com (Postfix) with ESMTP id 99C201F8E84
	for <hackers@freebsd.org>; Mon, 27 Jun 2005 15:48:44 -0700 (PDT)
Received: from mired.org (mwm@idiom [216.240.32.1])
	by idiom.com (8.12.11/8.12.11) with SMTP id j5RMmgwA030139
	for <hackers@freebsd.org>; Mon, 27 Jun 2005 15:48:44 -0700 (PDT)
	(envelope-from mwm-dated-1120776563.40f9da@mired.org)
Received: (qmail 85448 invoked by uid 1001); 27 Jun 2005 22:49:23 -0000
Received: by bhuda.mired.org (tmda-sendmail, from uid 1001);
	Mon, 27 Jun 2005 18:49:23 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17088.33395.356858.72172@bhuda.mired.org>
Date: Mon, 27 Jun 2005 18:49:23 -0400
To: hackers@freebsd.org
X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Primary-Address: mwm@mired.org
X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;
	h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\
From: Mike Meyer <mwm@mired.org>
X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew)
X-Mailman-Approved-At: Tue, 28 Jun 2005 13:08:03 +0000
Cc: 
Subject: /boot/loader bug?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2005 22:48:47 -0000

As reported here (I hope - the moderator got the message) and in
-questions, I have a motherboard that installs just fine, but gets a
"Can't work out which disk we are booting fromm" message when the
installed os boots.

Hacking boot/i386/loader/main.c to wire the proper values into
new_currdev fixed the problem. At this point, I'm considering filing a
bug report - but I'm not sure where the bug is.

Is this a /boot/loader bug, and it should have known what was going
on? Is this a BIOS bug, in that it reported the wrong thing to
/boot/loader? Is it a bug in one of the earlier boot stages?

Anyone got any opinions on this? Any suggestions for things to look at
to determine what component is actually buggy?

	Thanks,
	<mike
-- 
Mike Meyer <mwm@mired.org>		http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.