This was also essential to get the system ID set correctly:
There are a few good docs from Sun directly that are also pretty useful for navigating OpenBoot like this one:
Hope that helps! I’m trying to get Solaris 2.6 or 2.7 running on mine with OpenWindows GUI on a BlueSCSI v2.
Benjamin Krein
Sent from my iPhone
On Oct 10, 2024, at 5:53 PM, Gregg Levine via vcf-midatlantic <vcf-midatlantic@lists.vcfed.org> wrote:
Hello!Thanks Ethan, excellent advice as usual. Remind me next show, and I'lltry to arrange something special.-----Gregg C Levine gregg.drwho8@gmail.com"This signature was present when the impossible happened 23 years ago, twice."On Thu, Oct 10, 2024 at 5:49 PM Ethan O'Toole <telmnstr@757.org> wrote:
The NVRAM is probably a Dallas module that might go bad? There are ways to
get replacement (Glitch) and reprogram in some stuff to make it go. You
might be able to program it while it's on and just not power cycle it as
well to get it going.
Also, my Sun-foo is super rusty but there is a way to turn off extended
diagnostics in the openboot thing so that it skips a lot of the checks and
boots faster.
- Ethan
On Thu, 10 Oct 2024, Gregg Levine via vcf-midatlantic wrote:
Hello!
I own of those rigs. Now the problem: Can anyone on the list tell me
why a system would find itself stuck probing the keyboard, when it
runs headless? And how to get things started again.
It follows that the unit who was last running, call it seven years
ago, and when I first started it up again, the thing complained about
the NVRAM and the next problem was a complaint of it being the system
calls itself unknown.
-----
Gregg C Levine gregg.drwho8@gmail.com
"This signature was present when the impossible happened 23 years ago, twice."