From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 15 18:52:49 2004 Return-Path: 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 9CABD16A4CE for ; Mon, 15 Nov 2004 18:52:49 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7120A43D31 for ; Mon, 15 Nov 2004 18:52:49 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 18591 invoked from network); 15 Nov 2004 18:52:49 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 18:52:46 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFIqElf075648; Mon, 15 Nov 2004 13:52:36 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 15 Nov 2004 12:54:39 -0500 User-Agent: KMail/1.6.2 References: <4195417A.7010803@broadpark.no> In-Reply-To: <4195417A.7010803@broadpark.no> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151254.39712.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 18:52:49 -0000 On Friday 12 November 2004 06:04 pm, Henrik W Lund wrote: > 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? It only sees whatever drives the BIOS lists. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org