Solaris

As I may or may not have stated in the initial post, I did suspect that at first. I ran the command bootmode bootscript="setenv device-output ttya" to try and at the very least reroute output. But even with the output being the monitor, I should be able to see the POST while consoled in and I can't.

This may help....

Sun V445 hangs before {0} ok prompt

and this one:

ALOM - Console -

BE CAREFUL reading this. There's a number of us discussing what's right and what's wrong.

I guess the console baud rate could be set way different to the SC baud rate thereby you're terminal not reading console output properly or even see garbage output.

Being 2300 hrs in the UK right now I'm going to have to leave you discussing with the many experts on this forum. Be assured that you're in the right place to get help.

hcksd8

I read through those forums, and found a few things I haven't tried yet. (correcting time in ALOM, and booting without harddrives) will post an update when I've tried them.

I recommend that you take a look at the settings (eg, console redirection, serial comms, etc) but don't be tempted to start changing things en masse.

As you said, both machines were working, you worked on the hardware, and now both have the same problem. Logic says that it's something you've done. This hardware has interlocks to protect the hardware (eg, it knows if a fan isn't running) so leaving one tiny cable unplugged could do something like this.

Are the processors properly seated and locked down? Stuff like that.

All too often an IT fault is responded to by reinstalling the O/S, reinstalling the app that errored, completely restoring a filesystem, and other too drastic responses like that turning the one original problem into a multitude of problems that then take ages to fix. My advice is don't be tempted but retrace your steps.

on v125, if you replace CPU fan(s) with 2wire (instead of 3wire), you get a bunch of warnings in Solaris log file, but it works.

Console settings are set to 9600 8-N-1

I figure if I can see the SC console settings are correct, right?

Also interesting to note, I received a new chassis, and am able to get the OBP but still not getting any visuals on the monitor. I was receiving similar issues to the old chassis until I changed the keyswitch to diagnostics and it came up perfectly. I may try on the old chassis to see if it works out.

---------- Post updated at 12:49 PM ---------- Previous update was at 09:28 AM ----------

Okay.... I have resolved the issue. I feel really dumb about it, the reason I'm posting is in case someone else down the line has a similar issue....


Apparently V240 CPU slots have a little silver lever next to them. You have to pull the lever up, place the CPU in, and lower the lever flush with the motherboard.

I feel very dumb, but this has been an excellent learning experience, and I thank all who participated.

That's a good result. Thanks for letting us know.

It all comes with experience mate so don't feel dumb about it.

If any of us had been there we would have seen that straight away but thousands of miles makes it difficult.

Exactly like you said, logic implied that it had to be something you did since two machine were involved.

I'll mark this as solved.