From owner-freebsd-sparc64@FreeBSD.ORG Mon Mar 22 19:00:38 2004 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 2DFF016A4D2 for ; Mon, 22 Mar 2004 19:00:38 -0800 (PST) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D92F043D54 for ; Mon, 22 Mar 2004 19:00:30 -0800 (PST) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i2N30U8o008609; Mon, 22 Mar 2004 22:00:30 -0500 (EST) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i2N30Tfk008608; Mon, 22 Mar 2004 22:00:29 -0500 (EST) Date: Mon, 22 Mar 2004 22:00:29 -0500 From: Ken Smith To: Mark Campbell Message-ID: <20040323030029.GB8044@electra.cse.Buffalo.EDU> References: <20040322032707.GA3957@carbon.redbrick.dcu.ie> <20040322034417.GB2866@electra.cse.Buffalo.EDU> <20040322051116.GA7038@carbon.redbrick.dcu.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040322051116.GA7038@carbon.redbrick.dcu.ie> User-Agent: Mutt/1.4.1i cc: Ken Smith cc: freebsd-sparc@freebsd.org Subject: Re: Openboot device path. 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, 23 Mar 2004 03:00:38 -0000 On Mon, Mar 22, 2004 at 05:11:16AM +0000, Mark Campbell wrote: > I tired this, it tried to boot off > > /pci@1f,0/pci@1,1/ide@3/disk@0 > > HOwever it simply reports, > > "No boot record found" > > I'm thinking two things > > * Openboot is trying to boot off the wrong disk; is there any way to list the > devices on the system so I can try them manually, or even better which ones > I can boot from. Mine says /pci@1f,0/pci@1,1/ide@3/disk@0,0 but I don't *think* the trailing ",0" part is significant enough to cause your problem. Other people have already mentioned how to reset defaults though and that's worth a try just in case. If it were the wrong disk I think you would see something more along the lines of this: Rebooting with command: boot disk1 Boot device: /pci@1f,0/pci@1,1/ide@3/disk@1,0 File and args: Can't read disk label. Can't open disk label package Evaluating: boot disk1 Can't open boot device Since you're getting the "No boot record found" I think it's finding the disk but not anything useful for a boot record. > * Even though I followed all the steps from sysinstall, it's possible that a > boot sector (MBR in intel world), however unlike the normal sysinstall I > wasn't prompted to install a loader after the disk partitioning table. I'm not sure why you weren't prompted for the install of the boot loader, I think it should have done that. Would you mind re-attempting the install and pay particular attention to what happens after you have finished with the partition layout? If it slips through from where you quit out of the partition layout with no mention of a boot loader at all let us know please? If it really fails to ask you about a boot record at all I should be able to figure out how to run the boot loader off the CD, but then have the boot loader boot up the kernel from the hard drive. Once it's up and running that way you should be able to manually run the sunlabel command to install the boot record. I forgot to leave a CD in a test machine before I left work today so I can't walk through that myself right now like I had planned to. :-( -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |