Re: Steps to take after updating the Boot ROM?

[Adrian Christiansen <adrian.christiansen%gmail.com@localhost>]

Ah!, yes ofcourse! I checked all the diag envs again, and sure enought
diag-switch? was set to true. The output further down will say why I
didn't spot that before.

I did set auto-boot? to false before running printenv. Which stops it
from booting over the network.

Type b (boot), c (continue), or n (new command mode)
> n
Type help for more information
ok printenv
Parameter Name        Value                          Default Value

selftest-#megs        1                              1
output-device         screen                         screen
input-device          keyboard                       keyboard
sbus-probe-list       0123                           0123
keyboard-click?       false                          false
keymap
ttyb-rts-dtr-off      false                          false
ttyb-ignore-cd        true                           true
ttya-rts-dtr-off      false                          false
ttya-ignore-cd        true                           true
ttyb-mode             9600,8,n,1,-                   9600,8,n,1,-
ttya-mode             9600,8,n,1,-                   9600,8,n,1,-
fcode-debug?          false                          false
diag-file
diag-device           net                            net
boot-file             netbsd
boot-device           disk3:a                        disk
auto-boot?            false                          true
watchdog-reboot?      false                          false
local-mac-address?    false                          false
creen-#columns       80                             80
screen-#rows          34                             34
scsi-initiator-id     7                              7
use-nvramrc?          false                          false
nvramrc
sunmon-compat?        true                           true
security-mode         none                           none
security-password
security-#badlogins   341704883                      <no default>
oem-logo                                             <no default>
oem-logo?             false                          false
oem-banner                                           <no default>
oem-banner?           false                          false
hardware-revision     .G.¼.T.:...á.¨

Then it prints a special character that locks the terminal, so I don't
know what comes next.

Now I wonder how I can set the hardware-revision to something that
doesn't lock my terminal.

I have replaced the battery of the NVRAM so it should be fine. It was
flat when I got it, and it remembers that disk0:0 is the boot device
(which is odd, since id 3 is default).

2015-09-27 17:38 GMT+02:00 Georg Brein <georg.brein%unibas.ch@localhost>:
> Can you send us a copy of the OpenBoot power-up messages and the output
> of the OpenBoot command "printenv"? Maybe the "diag-switch?"
> variable is set (which would explain why the IPX is booting
> from the diagnostic boot device which is by default the network)?
> "diag-switch?" is automatically set by OpenBoot on detecting a faulty
> NVRAM checksum which may point to a failing NVRAM battery.
>
> Regards, Georg Brein
>
>
> Am 27.09.2015 um 17:22 schrieb Adrian Christiansen:
>
>> Hi guys!
>>
>> So quite a while ago I updated the Boot ROM in my SPARCstation IPX,
>> since it caused issues with the secondary boot loader (I still have
>> that broken ROM and I'm willing to test patches).
>>
>> Anyway, the IPX keep auto booting of the network, and
>> hardware-revision prints garbage. Are there a few things I've should
>> have done when replacing the ROM?, the NVRAM doesn't seem entirely
>> correct.
>>
>> Cheers!,
>> Adrian.
>