[OpenBIOS] Sparc64 OpenBIOS

[Nick Couchman]

So, forgive the ignorant question, but does this look to be an OpenBIOS issue or a Qemu issue?

Thanks,
Nick

>>> On 2009/11/12 at 18:39, Tarl Neustaedter <Tarl.Neustaedter at Sun.COM> wrote: 
> Nick Couchman wrote:
>> [...]
>>
>> 0 > boot cdrom 
>> [sparc64] Booting file 'cdrom' with parameters ''
>> Not a bootable ELF image
>> Not a Linux kernel image
>> Not a bootable a.out image
>> Loading FCode image...
>> Loaded 7420 bytes
>> entry point is 0x4000
>> Evaluating FCode...
>>
>> seek failed
>>
>> Can't mount root
>>
>> byte-load: exception caught!
>>  ok
>> 0 > 
>>
>> This is a Solaris 10 SPARC disc - it looks like it finds the boot code it 
> needs fine, but can't load it for some reason.  Any hints or any thing else I 
> can do to help debug the situation would be great.
>>   
> 
> What the Solaris 10 boot-blocks do (which is different in 
> OpenSolaris/Nevada, and somewhat varies between updates of Solaris 10) is:
> 
> - create /packages/ufs-file-system (or hsfs-file-system)
> - call do-boot, which it has just defined.
> 
> At the point above,  where it has failed and you are at the ok prompt, 
> you should be able to see do-boot, which includes something like:
> 
> : do-boot
>   4000 loadbase!
>   loadbase " hsfsboot" get-file if
>     ." Boot load failed" cr xit
>   then
>   reloc&go
> ;
> 
> It's pretty clear you are dying in get-file, which is also external at 
> this point, and you can debug it.
> 
> The "seek failed" message comes from an attempt to read a block that 
> isn't within the partition boundaries. Either there is something wrong 
> with the HBA driver for the cdrom, or something is going wrong chasing 
> down hsfs data pointers.




--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.