<html><head></head><body><div dir="auto">Hi Todd,<br><br>Are you using a serial console or the Creator framebuffer with a Sun keyboard? Whichever, I would be inclined to try it the other way around.<br><br>If you had been using a serial console via an intermediate device such as a reverse-TELNET concentrator or external port-multiplexer, try a direct connection instead, *some* of those middleware-serial boxes can trigger all kinds of trouble.<br><br>I have also seen cases before where eg: a well-worn Sun keyboard socket with a loose connection to the cable can cause these kinds of hard-hangs. It might also be worth trying with the Creator removed.<br><br>I would also detach any Ethernet cable from the on-board Ethernet socket, whilst installing Solaris: the unpatched Solaris HME NIC hardware/driver often doesn't successfully negotiate duplex mode with some network switches, which can result in a veritable tsunami storm of interrupts that may result in a hang.<br><br>Finally, which PROM revision does the console display when the system is powered on?<br><br>Regards,<br>Mike</div><br><br><div class="gmail_quote"><div dir="auto">On 4 April 2024 15:59:41 BST, Todd Vernon via rescue <rescue@sunhelp.org> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">Agree that NetBSD is ignoring something that Solaris is not. I feel like the last message in the boot before it hangs is a clue,</div><div dir="ltr">"using default device instance dataâ€</div><div dir="ltr"><br></div><div dir="ltr">Im not exactly sure what that means so I reset the IDProm and reprogrammed it using 80 as the machine type but no luck. Im not even completely sure that “default device instance data†is what is stored in there but some google searches seem to be tied to that. </div><div dir="ltr"><br></div><div dir="ltr">NetBSD boot seems completely normal with no warnings or messages I would not expect. </div><div dir="ltr"><br></div><div dir="ltr">I’ve moved all the sims around and removed different sets and like clockwork it always hangs at the same place so im pretty sure its not a memory issue.</div><div dir="ltr"><br></div><div dir="ltr">Im down to just the CDROM drive or just the Zulu to take everything else off the SCSI bus. It’s a head scratcher.</div><div dir="ltr"><br></div><div dir="ltr">Thanks for the reply!</div><div dir="ltr"><br></div><div dir="ltr">-t</div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">
<br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="font-size:medium;margin-top:0px"><div style="margin-top:0px;font-weight:bold"><div style="margin-top:0px"><div style="margin-top:0px"><div style="margin-top:0px"><font style="font-size:14px">Todd Vernon</font></div><div style="font-weight:normal;margin-top:0px"><font style="font-size:13px">Entrepreneur | Investor</font></div><div style="font-weight:400;font-size:13px;margin-top:0px;color:rgb(80,0,80)">Email: <a href="mailto:todd@toddvernon.com" target="_blank">todd@toddvernon.com</a></div><div style="font-weight:400;font-size:13px;margin-top:0px;color:rgb(80,0,80)">LinkedIn: <a href="https://www.linkedin.com/in/toddvernon/" target="_blank">toddvernon</a></div></div></div></div></div></div></div></div><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Apr 3, 2024 at 11:03:25 PM, vom513 via rescue <<a href="mailto:rescue@sunhelp.org">rescue@sunhelp.org</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" type="cite">
<div>
<div>
Apologies for asking the likely obvious - have you booted this machine with diag-switch and let it run through the tests ?<br><br>Since you have tried real CDs as well as ZuluSCSI virtual, it sounds like perhaps something that Solaris is “touching†that NetBSD is not ?<br><br>Have you actually tried to follow all the way through and install/run NetBSD ?<br><br>I guess a hail mary would be to start removing hardware and components one by one and try a Solaris boot after each step.<br><br>Sorry for the obvious things, just wanted to reply with what I would try. <br><br>Please do let us know if you make progress or figure out the root cause.<br>_______________________________________________<br>rescue list - <a href="http://sunhelp.org/mailman/listinfo/rescue_sunhelp.org">http://sunhelp.org/mailman/listinfo/rescue_sunhelp.org</a><br>
</div>
</div>
</blockquote>
</div></blockquote></div></body></html>