Fighting ALOM on a V240

[Jochen Kunz]

Hi.

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.
--


tsch|_,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
_______________________________________________
rescue list - http://www.sunhelp.org/mailman/listinfo/rescue

[Pete-37]

I found an old 42t thats in great shape other then it doesn't work. Just
says 212 on the front display and nothing else happens. Looks like a
memory system error of some sort. I'd really like to get it working again.

When I first tried turning it on it went past the 212 display and seemed
to be going through it's normal diagnostics. It would always seem to
stop at some number though. Most of the time it was 212. Never got
anything on the monitor but, I think the 13w3 adapter I had wasn't wired
right for this.  After a few more boot tries it just went to 212 as soon
as powered on and stayed there. I opened it up and there was a simm
hanging half out of the socket. Reinserted it but, still 212. Played
with taking ram out and moving it around and no change. I imagine it
probably took out the motherboard.

Unless anyone has an idea what else it might be I suppose I need to
replace the motherboard. Anyone have a motherboard they can part with. ?
I suppose I would be interested in a whole 42t if taking the time to
pull it out is a hassle. I'm in California but, shipping a motherboard
from anywhere in the world probably isn't out of the question. Shipping
a system from outside the US probably would be. Any help appreciated.

Total off subject but, I also need to find  MPE on dat for a HP3000/957.
_______________________________________________
rescue list - http://www.sunhelp.org/mailman/listinfo/rescue

[Sridhar Ayengar]

leaknoil wrote:

> I found an old 42t thats in great shape other then it doesn't work. Just
> says 212 on the front display and nothing else happens. Looks like a
> memory system error of some sort. I'd really like to get it working again.
>
> When I first tried turning it on it went past the 212 display and seemed
> to be going through it's normal diagnostics. It would always seem to
> stop at some number though. Most of the time it was 212. Never got
> anything on the monitor but, I think the 13w3 adapter I had wasn't wired
> right for this.  After a few more boot tries it just went to 212 as soon
> as powered on and stayed there. I opened it up and there was a simm
> hanging half out of the socket. Reinserted it but, still 212. Played
> with taking ram out and moving it around and no change. I imagine it
> probably took out the motherboard.
>
> Unless anyone has an idea what else it might be I suppose I need to
> replace the motherboard. Anyone have a motherboard they can part with. ?
> I suppose I would be interested in a whole 42t if taking the time to
> pull it out is a hassle. I'm in California but, shipping a motherboard
> from anywhere in the world probably isn't out of the question. Shipping
> a system from outside the US probably would be. Any help appreciated.

Are you sure the memory is good?  Usually this is caused by the first
stick going bad, and the machine can't continue onto any additional
sticks.  It wouldn't surprise me if, when the RAM got unseated, the
memory got zapped.

This memory shouldn't be too hard to find.  Certainly easier to find
than a motherboard.

Peace...  Sridhar
_______________________________________________
rescue list - http://www.sunhelp.org/mailman/listinfo/rescue

[Pete-37]

There are two banks of four and each bank had different sized ram in it.
I tried taking out the first four, the second four, swaping the banks,
and then each bank individually again swapped. Still right to 212. Same
thing it does if no ram is installed.  Right to 212.  The lose simm was
in what I supposed could be the first simm socket. It may have taken out
the slot and so, as you say, it can't continue.

Sridhar Ayengar wrote:

>
> Are you sure the memory is good?  Usually this is caused by the first
> stick going bad, and the machine can't continue onto any additional
> sticks.  It wouldn't surprise me if, when the RAM got unseated, the
> memory got zapped.
>
> This memory shouldn't be too hard to find.  Certainly easier to find
> than a motherboard.
>
> Peace...  Sridhar

_______________________________________________
rescue list - http://www.sunhelp.org/mailman/listinfo/rescue