[OpenBIOS] Solaris anyone?
mark.cave-ayland at siriusit.co.uk
Mon Sep 12 12:00:27 CEST 2011
On 09/09/11 03:20, Nathan Kunkee wrote:
>>> I'll work on getting the full listing for each combination for
>>> comparison, but what I recall from last night is that each one
>>> stopped in the same place, after fcp0 or audiocs0, depending.
Yes please. In fact, I don't believe I've seen the full output of "boot
cdrom:d -v" from your Solaris copy anywhere? That would be useful to see
how far you are getting.
>> I don't know if this will work, but see if you can boot kadb ("boot
>> cdrom:d kadb -s"), and then break into Solaris when it's stuck.
>> The potential problems with this:
>> - I don't know if the cdrom has kadb on it
>> - I don't know if Solaris will respond to a <break> that early in the
>> If it does, a "$c" will show you the stack and probably tell us where
>> we're getting stuck. You may have to issue a ":c" (continue) early in
>> the boot process to get kadb to finish loading Solaris.
> kadb is available on the cdrom, however, it stops at the same place as a
> regular boot. Also, I've had no luck interrupting the boot process.
Yeah I'm guessing that this is to do with QEMU not having an equivalent
of the STOP-A/L1-A break sequence? Once you can find out which module is
causing the issue, then you can set breakpoints using the module#symbol
notation in kadb although my knowledge (and documentation I can find
anywhere on kadb) is very weak :(
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs
More information about the OpenBIOS