Andreas_Hallmann wrote:

> Well, but don't expect to much of that selftest.
> Its only a semideciding process.
> If it detects a problem, well you got it.
> But if it doesn't, you can't tell they are good.

thanks,

i set the selftest-#megs to 96
and test said all ok.

this was after i pulled and rotated all the RAM sims.

is now doing a build.

wish me luck.

chs,
P.







>
>
> Have you tried to pull and re-insert all rams?
> This often helps. Also permutating the order they are inserted might really help.
>
> There was a bunch of educational promo ss4 / ss5 sold by sun, with poor ram.
> (Sorry Sun, I have to say that, even so it was the only mistake in 15 years.)
> Timing is tight with this rams.
>
> So the above often helped.
>
> cheers Andreas
>
> On Sat, Jun 17, 2006 at 02:26:25AM -0500, Johan A. van Zanten wrote:
> >
> > "Paul (NCC/CS)" <pts@bom.gov.au> wrote:
> > >
> > > Hi,
> > > can someone tell me a command to test the ram in my ss5?
> > > I think there is something at the OpenBOOT prompt,
> > > but what? Or do you just disable fastboot, ie no command exists.
> >
> >
> >  Check out the "selftest-#megs" variable in OpenBOOT. You may want to set
> >  it to the number of MB of RAM in the machine. For example, 64 MB:
> >
> > setenv selftest-#megs 64
> >
> >
> >  And the next time the machine is reset or powered on (or boots, i think)
> > it will test that much RAM.
> >
> >  -johan
>
> --
> NetBSD: If you happen to have any problem with your uptime.

--

____________________________________________

Paul
Australian Bureau Of Meteorology
____________________________________________