From owner-freebsd-amd64@FreeBSD.ORG  Fri Nov 12 23:04:28 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4F6EB16A4CE
	for <freebsd-amd64@freebsd.org>; Fri, 12 Nov 2004 23:04:28 +0000 (GMT)
Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 913BF43D1D
	for <freebsd-amd64@freebsd.org>; Fri, 12 Nov 2004 23:04:27 +0000 (GMT)
	(envelope-from henrik.w.lund@broadpark.no)
Received: from [10.0.0.3] (52.80-202-129.nextgentel.com [80.202.129.52])
	by mail.broadpark.no (Postfix) with ESMTP id 51FB968B5
	for <freebsd-amd64@freebsd.org>; Sat, 13 Nov 2004 00:04:26 +0100 (MET)
Message-ID: <4195417A.7010803@broadpark.no>
Date: Sat, 13 Nov 2004 00:04:26 +0100
From: Henrik W Lund <henrik.w.lund@broadpark.no>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.7.3) Gecko/20041111
X-Accept-Language: no, en-us, en
MIME-Version: 1.0
To: freebsd-amd64@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: boot0 only seeing first two drives?
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2004 23:04:28 -0000

Greetings!

I'm having a bit of a pickle with boot0, running amd64 5.3-STABLE on an 
Asus K8V mobo. My disks are set up thus:

Secondary master: 20gig Quantum Fireball ATA66 disk - one partition with 
Windows XP on it, and boot0.

VIA RAID controller, first drive: 120gig Western Digital SATA150 disk - 
one slice with FreeBSD on it and no bootloader.

The BIOS is set up to boot from the Quantum disk (as Windows refuses to 
boot unless it finds itself on disk 0x80), this brings up the boot0 boot 
manager and I can switch between FreeBSD and Windows just fine.

Now, when I throw a secondary slave into the mix, suddenly the boot0 
boot manager no longer "sees" the disk on the RAID controller (the 
FreeBSD disk, the most important one), and the CMOS setup doesn't allow 
me to bump this disk back up to 0x81.

Does the boot0 boot manager only "see" disks 0x80 and 0x81, or is this 
some kind of weirdness?

Thanks!

-- 
Henrik W Lund