"set auto_action boot" Won't. Bad NVRAM?

From: Dabe Murphy <dabe_at_parabon.com>
Date: Mon, 19 Feb 2001 19:58:03 -0500 (EST)

I have an AlphaServer1200 which, when I feed it NVRAM commands, doesn't
seem to accept them[*].

Most noticably, I can't seem to make the machine auto boot. If I do:

>>> set auto_action boot
>>> init

it happily resets itself, probes its devices and drops me back to the
">>>" prompt. Typing "show" at that point tells me that "auto_action"
is still set to "HALT". GRRR!!!

It's the same for "bootdef_dev", "boot_file", and "boot_osflags".

* - One notable exception (and this may have been a fluke) was when I
changed the value of "console" from "serial" to "graphics". That kind of
pisses me off, on account of it takes creedence away from my guess that
the NVRAM is faulty (unless maybe the default "console" setting is derived
at boot-time, depending on the presence/absense of a keyboard?)

I've R'd all The F'ing M's I could find (and searched the archives, FAQs,
web, etc.) but everything just says "set auto_action boot". Period.

Does anybody know if there's any kind of, like, jumper that disables
writes to NVRAM? or am I not setting enough variables? or something, geez,
*ANYTHING* else I can try?

Alas, kicking the box hasn't had quite the effect I'd hoped... :-}

Replies to me; I'll summarize as usual. TIA!

                                                Dabe
Received on Tue Feb 20 2001 - 00:57:18 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT