[SunHELP] Q: U1 170E TOD/NVRAM replacement (Was: HELP! Ultra 1 170E 3D hangs...)

Fuerst, Robert C. (Chris) sunhelp at sunhelp.org
Wed Nov 29 06:07:11 CST 2000


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C059FC.E7995430
Content-Type: text/plain

First of all I just wanted to say that Gary is my old "big toe" at college.
Gave me my first intro to UNIX - "Don't mess with the software".
I think I ended up with a C average.  Oh well, a few beers at the local pub
and all was well.  Hope things are doing good besides your 170E Gary.

The best NVRAM faq follows.  Has links to NVRAM chips for $20.
Your not getting ANY errors in your massages files?
Have you changed the cooling fan yet and given the MB a good air wash?

http://www.squirrel.com/sun-nvram-hostid.faq.html
The clock on my Sun has stopped working. When I turn off the machine it
loses track of the time and/or complains about invalid TOD when I turn it
on. How do I get my clock to keep time when the system is off? (Replace
chip) 
http://www.linuxos.net/docs/solaris/common_err.html
WARNING: TOD clock not initialized-- CHECK AND RESET THE DATE!
========================================================-===== This message
indicates that the Time Of Day (TOD) clock reads zero, so its time is the
beginning of the UNIX epoch: midnight 31 December 1969. On a brand-new
system, the manufacturer might have neglected to initialize the system
clock. On older systems it is more likely that the rechargeable battery has
run out and requires replacement. First replace the battery according to the
manufacturer's instructions. Then become superuser and use the date(1)
command to set the time and date. On SPARC systems the clock is powered by
the same battery as the NVRAM, so a dead battery also causes loss of the
machine's Ethernet address and host ID, which are more serious problems for
networked systems. 



> -----Original Message-----
> From:	grafe at omega.ie.pitt.edu [SMTP:grafe at omega.ie.pitt.edu]
> Sent:	Tuesday, November 28, 2000 10:54 PM
> To:	sunhelp at sunhelp.org
> Subject:	[SunHELP] Q: U1 170E TOD/NVRAM replacement (Was: HELP! Ultra
> 1 170E 3D hangs...)
> 
> We have an Ultra 1 170E (SunOS 5.7 Generic_106541-12)
> that started to act-up about a month ago
> (e.g., random "hangs" and kernel panics).
> Both POST and SunVTS pass with "no errors".
> 
> After pulling & reseating memory since the last hang,
> we noted that the TOD was not being maintained
> while the system was powered down.
> 
> First off, can a failing TOD/NVRAM randomly "hang"
> or panic the system without other test indications ?
> 
> Second: Can anyone recommend sources for TOD/NVRAM
> modules (525-1430 ?) for our Ultra 1 170E ?
> 
> Thanks.
> --
> Gary
> gerst4+ at pitt.edu
> 

------_=_NextPart_001_01C059FC.E7995430
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2651.67">
<TITLE>RE: [SunHELP] Q: U1 170E TOD/NVRAM replacement (Was: HELP! Ultra =
1 170E 3D hangs...)</TITLE>
</HEAD>
<BODY>

<P><FONT FACE=3D"Times New Roman">First of all I just wanted to say =
that Gary is my old "big toe" at college.</FONT>
<BR><FONT FACE=3D"Times New Roman">Gave me my first intro to UNIX - =
"Don't mess with the software".</FONT>
<BR><FONT FACE=3D"Times New Roman">I think I ended up with a C =
average.  Oh well, a few beers at the local pub</FONT>
<BR><FONT FACE=3D"Times New Roman">and all was well.  Hope things =
are doing good besides your 170E Gary.</FONT>
</P>

<P><FONT FACE=3D"Times New Roman">The best NVRAM faq follows.  Has =
links to NVRAM chips for $20.</FONT>
<BR><FONT FACE=3D"Times New Roman">Your not getting ANY errors in your =
massages files?<BR>
Have you changed the cooling fan yet and given the MB a good air =
wash?</FONT>
</P>

<P><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.squirrel.com/sun-nvram-hostid.faq.html" =
TARGET=3D"_blank">http://www.squirrel.com/sun-nvram-hostid.faq.html</A><=
/FONT></U>
<BR><FONT FACE=3D"Times New Roman">The clock on my Sun has stopped =
working. When I turn off the machine it loses track of the time and/or =
complains about invalid TOD when I turn it on. How do I get my clock to =
keep time when the system is off?<I> (Replace chip)</I> </FONT></P>

<P><U><FONT COLOR=3D"#0000FF" FACE=3D"Times New Roman"><A =
HREF=3D"http://www.linuxos.net/docs/solaris/common_err.html" =
TARGET=3D"_blank">http://www.linuxos.net/docs/solaris/common_err.html</A=
></FONT></U>
<BR><B><FONT COLOR=3D"#0000FF" FACE=3D"Times New Roman">WARNING: TOD =
clock not initialized-- CHECK AND RESET THE DATE!</FONT></B><FONT =
FACE=3D"Times New Roman"> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D-=3D=3D=3D=3D=3D This message indicates that =
the Time Of Day (TOD) clock reads zero, so its time is the beginning of =
the UNIX epoch: midnight 31 December 1969. On a brand-new system, the =
manufacturer might have neglected to initialize the system clock. On =
older systems it is more likely that the rechargeable battery has run =
out and requires replacement. First replace the battery according to =
the manufacturer's instructions. Then become superuser and use the =
date(1) command to set the time and date. On SPARC systems the clock is =
powered by the same battery as the NVRAM, so a dead battery also causes =
loss of the machine's Ethernet address and host ID, which are more =
serious problems for networked systems. </FONT></P>
<BR>
<BR>

<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:  </FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">grafe at omega.ie.pitt.edu =
[SMTP:grafe at omega.ie.pitt.edu]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent:  </FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Tuesday, November 28, 2000 10:54 PM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To:    </FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">sunhelp at sunhelp.org</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject:       </FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">[SunHELP] Q: U1 170E TOD/NVRAM =
replacement (Was: HELP! Ultra 1 170E 3D hangs...)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We have an Ultra 1 170E (SunOS 5.7 =
Generic_106541-12)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">that started to act-up about a month =
ago</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">(e.g., random "hangs" and =
kernel panics).</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Both POST and SunVTS pass with =
"no errors".</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">After pulling & reseating memory =
since the last hang,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">we noted that the TOD was not being =
maintained</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">while the system was powered =
down.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">First off, can a failing TOD/NVRAM =
randomly "hang"</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">or panic the system without other =
test indications ?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Second: Can anyone recommend sources =
for TOD/NVRAM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">modules (525-1430 ?) for our Ultra 1 =
170E ?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">--</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Gary</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">gerst4+ at pitt.edu</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C059FC.E7995430--



More information about the SunHELP mailing list