Artyom Tarasenko wrote:
Looks like the last stage of the kernel loader wasn't able to determine the CPU model? Or at least didn't like it. Maybe the OpenSolaris version you are booting doesn't support the specified (or default) cpu model?
krtld: error during initial load/link phase
krtld could neither locate nor resolve symbols for: /platform/sun4u/kernel/sparcv9/unix in the boot archive. Please verify that this file matches what is found in the boot archive. You may need to boot using the Solaris failsafe to fix this. panic - kernel: Unable to boot EXIT 0 >
r733 actually gets further than this now. It seems to die whilst trying to load files from the file system/map virtual memory.
And... Solaris 2.5.1 on sparc32 also looks pretty similar with r733:
Jumping to entry point 00004000 for type 00000005... null path krtld: error during initial load/link phase Unhandled Exception 0x00000007 PC = 0x0010724c NPC = 0x00107250 Stopping execution
Unmodified Solaris 2.6 doesn't get this far, I guess due to the 80 chars limitation. Will check the patched version later.
Hmmmm this looks more promising. If you compile with DEBUG_CIF enabled in libopenbios/client.c and try again then you can see all the calls into OpenBIOS, and hence the device nodes and properties that are being accessed. This will probably tell you why you are getting the null path error. It's interesting to note that type 0x5 is an a.out as opposed to an ELF binary.
But all in all it looks like the problem is buried in OpenBIOS, since qemu is definitely good enough to boot 2.5.1 under sparc32.
Probably. All we need now is the debug information so that we can fix it :)
ATB,
Mark.