From owner-freebsd-stable@FreeBSD.ORG Fri Jan 12 17:16:31 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD1CE16A403 for ; Fri, 12 Jan 2007 17:16:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 56E7C13C441 for ; Fri, 12 Jan 2007 17:16:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l0CHGTXB007581; Fri, 12 Jan 2007 12:16:29 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Jo Rhett Date: Fri, 12 Jan 2007 12:16:24 -0500 User-Agent: KMail/1.9.4 References: <200701121025.15555.jhb@freebsd.org> <45A7AF93.1010803@svcolo.com> In-Reply-To: <45A7AF93.1010803@svcolo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701121216.25185.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Fri, 12 Jan 2007 12:16:29 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2437/Thu Jan 11 18:59:09 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-stable@freebsd.org Subject: Re: any real documentation of the boot2 prompt? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 17:16:31 -0000 On Friday 12 January 2007 10:56, Jo Rhett wrote: > John Baldwin wrote: > > A BIOS driver number is the number you pass to the BIOS to access a drive. > > Typically drive 0x0 is a floppy drive and hard drives start at 0x80. > > Usually the SCSI BIOS will list the BIOS driver number during the POST > > messages and it will look like 80, 81, etc. There is no standard way > > as it is at the BIOS' discretion. > > How do I determine this? It doesn't list them during boot. To some extent you are at the mercy of your BIOS writers, yes it sucks, and this why I like things like EFI and OpenFirmware over BIOS. > Say I boot off the CD, is there any commands I can use to determine what > the BIOS numbers are? They are da0 and da1 to freebsd. You can try using 'lsdev' in the loader from the CD. If a disk is called A: in the loader printfs it's drive 0, if it's C: it's drive 0x80, D: drive 0x81 (the drive letters may only be mentinoed in the printfs at teh start of the loader and not in lsdev, can't recall). > > To answer your question: you need to first make sure your SCSI BIOS is > > registering your second disk with the BIOS. Assuming it's mapped as > > drive 81, you can then use '1:da(1,a)'. If it shows up as drive 82, then > > use 2:da(1,a)', etc. > > How does one do so? It would have to be in your SCSI adapter's BIOS. They tend to have a BIOS setup you can enter during boot before the OS loads and you would have to poke around in there. -- John Baldwin