[rescue] Fighting ALOM on a V240

Jochen Kunz jkunz at unixag-kl.fh-kl.de
Tue Aug 4 03:38:24 CDT 2009


Now I have that nice Sun Fire V240. (Dual 1 GHz, 4 GB RAM) ALOM 1.6.3
is instaled and it drives me nuts. I am trying to get NetBSD running on
that beast. (The driver for the Schizo PCI host bridge still needs
work.) So most of the time the machine is powered off, or sitting in
OBP or in the kernel debugger. ALOM constantly spills messages on the
serial console. If no OS is running SC reboots every few minutes.
(Seems to be some watchdog.) I set all auto-logout timeouts to 0 as "no
auto-logout". ("sc_clitimeout") But as the SC reboots every now and
then it doesn't help. The telnet or ssh connection to the SC is lost on
SC reboot, obviously. So I have to log into SC via telnet or ssh every
time I want to issue a ALOM command. This is even more annoying as ALOM
does not support telnet auto-login or ssh pubkey authentication.

What I now want is:
SC should not reboot if no OS is runing.
SC should not spill _any_ messages on the serial console.

I did RTFM (819-2445-11.pdf) but could not find answers to these
questions, so I have to pester you.

Thanks for your help.


Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/

More information about the rescue mailing list