From owner-freebsd-sparc64@FreeBSD.ORG Tue Dec 2 15:17:16 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BA5216A4CE for ; Tue, 2 Dec 2003 15:17:16 -0800 (PST) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F3BF43FCB for ; Tue, 2 Dec 2003 15:17:14 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.12.10/8.12.9) with ESMTP id hB2NHDYR028300 for ; Tue, 2 Dec 2003 18:17:13 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: Date: Tue, 2 Dec 2003 18:17:12 -0500 To: sparc64@FreeBSD.ORG From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Booting from alternate disk in sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2003 23:17:16 -0000 Well, I started to write up one observation, and in the process found out that the situation was a bit different than what I thought. I now have two drives in my Ultra-10, and wanted to boot off the second drive. I got to the open-firmware prompt. Typing "boot disk0" boots up off the first disk, with the messages: - - - - [start] Rebooting with command: boot disk0 Boot device: /pci@1f,0/pci@1,1/ide@3/disk@0,0 File and args: >> FreeBSD/sparc64 boot block Boot path: /pci@1f,0/pci@1,1/ide@3/disk@0,0:a Boot loader: /boot/loader Console: OpenFirmware console FreeBSD/sparc64 bootstrap loader, Revision 1.0 [etc] - - - - [end] So I tried typing 'boot disk1' at the open-firmware prompt. It starts up about the same, except that it has 'disk@1,0' where the above has 'disk@0,0', and then it hangs before printing out the message 'Console: OpenFirmware console'. Well, I always thought it was completely dead there, and I would drop back to the openfirmware prompt and try again. But while it does stop there for a minute and 15 seconds, apparently it will continue on and boot OK if I'm just patient enough to wait for it. What I *was* going to say in this message, was that I had an alternate trick for getting to the second disk. I'd type 'boot disk0', and then hit the space key to fall into the boot loader. I would type "show currdev", and it displayed: /pci@1f,0/pci@1,1/ide@3/disk@0,0:a so I would type in: unload set currdev=/pci@1f,0/pci@1,1/ide@3/disk@1,1:a load boot/kernel/kernel boot (ie, just changing disk@0,0 to disk@1,1). And with that, it does boot up off the second disk. Of course, now I imagine that 'disk@1,1' isn't all that different than 'disk@1,0'. So I don't know why there's such a long pause there when I try "boot disk1", but it does seem to work... Do others have multi-boot setups on their sparc64 machines? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu