Bug 98269 - Fresh 6.1 installation fails to boot
Summary: Fresh 6.1 installation fails to boot
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: sparc64 (show other bugs)
Version: 6.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: Mark Linimon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-01 08:10 UTC by Jarkko Santala
Modified: 2007-06-12 04:43 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jarkko Santala 2006-06-01 08:10:17 UTC
I tried to install 6.1 sparc64 into a spanking unused Sun Blade 100 with
15GB IDE driver and 128MB RAM plus 2x256MB additional RAM. Installation
went smoothly, but after reset it fails to boot with the following message:

Sun Blade 100 (UltraSPARC-IIe), No Keyboard
OpenBoot 4.0, 640 MB memory installed, Serial #12345678.
Ethernet address xx:xx:xx:xx:xx:xx, Host ID: 12345678.



Boot device: disk:b  File and args:

How-To-Repeat: Install a fresh copy of 6.1 into a Sun Blade 100 or perhaps some other IDE Sun.
Comment 1 jtanis 2006-06-01 09:05:45 UTC
Assuming a Blade 100 operates near to the same as most previous
Sparcs/UltraSparcs, the system defaults to booting off of the device
last booted off of. Try hitting stop-a and doing a "boot disk," or
whatever your version of PROM requires to boot off the first disk.
This looks to me to have absolutely nothing to do with freebsd, its
not even loading the freebsd bootloader from what I've seen. If
installation was successful most likely you are attempting to boot off
the wrong device (or at least, not the device the bootloader was
installed on). Also, if its really typing x's for your ethernet
address, you may need to get a new nvram as it's battery may be dead
-- I'm not sure whether the Blade 100 uses NVRAM or if its one of the
newer systems with an SEEPROM and therefore doesn't need a battery. Is
there a keyboard connected? If there is, I think freebsd may be the
least of your problems.

-- 
James Tanis
jtanis@pycoder.org
http://pycoder.org
Comment 2 Jarkko Santala 2006-06-01 09:37:28 UTC
On Thu, 1 Jun 2006, James Tanis wrote:

> Assuming a Blade 100 operates near to the same as most previous
> Sparcs/UltraSparcs, the system defaults to booting off of the device
> last booted off of. Try hitting stop-a and doing a "boot disk," or
> whatever your version of PROM requires to boot off the first disk.

Good tip, this indeed was the problem. After "boot disk" the system boots 
fine. Thank you very much. Any chance of this bit of valuable information 
making its way to 
http://www.freebsd.org/releases/6.1R/installation-sparc64.html so that I'd 
be the last to submit a PR about such a silly thing? ;)

In any case at least after this google will probably come up with more 
that 3 hits for "File /boot/loader not found".

> This looks to me to have absolutely nothing to do with freebsd, its
> not even loading the freebsd bootloader from what I've seen. If
> installation was successful most likely you are attempting to boot off
> the wrong device (or at least, not the device the bootloader was
> installed on). Also, if its really typing x's for your ethernet
> address, you may need to get a new nvram as it's battery may be dead
> -- I'm not sure whether the Blade 100 uses NVRAM or if its one of the
> newer systems with an SEEPROM and therefore doesn't need a battery. Is
> there a keyboard connected? If there is, I think freebsd may be the
> least of your problems.

I changed that stuff by hand, no worries.

Thanks,

 	-jake

Jarkko Santala <jake@iki.fi>    http://www.iki.fi/jake/
System Administrator            http://www.portalify.com
Unixtarhuri                     +358 40 720 4512
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2007-05-26 06:59:08 UTC
State Changed
From-To: open->feedback

So, can this PR be closed now? 


Comment 4 Mark Linimon freebsd_committer freebsd_triage 2007-05-26 06:59:08 UTC
Responsible Changed
From-To: freebsd-sparc64->linimon
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2007-06-12 04:42:54 UTC
State Changed
From-To: feedback->closed

Feedback timeout (2 weeks).