Path: utzoo!attcan!uunet!cs.utexas.edu!rice!sun-spots-request
From: davy@itstd.sri.com
Newsgroups: comp.sys.sun
Subject: Anybody seen this?
Keywords: Miscellaneous
Message-ID: <9551@brazos.Rice.edu>
Date: 29 Jun 90 22:43:55 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 29
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 246, message 11

Hardware/Software: Sun 3/80, diskless, SunOS 4.1, generic kernel

Boot the machine, it prints "Warning: TOD clock not initialized...".  So,
I run the "date" command to initialize it.  This usually fixes this on
most machines.  Boot the machine again, and it still complains about the
TOD clock not being initialized.

Call Sun service; maybe there's a bad NVRAM chip or bad battery or
something.

Swap the CPU board keeping the old NVRAM and ID PROM.
No change.
Swap the NVRAM chip.
No change.
Swap the ID PROM.
No change.

We never did see a battery like the ones the 3/50's used to have...  how
do they store the TOD clock anyway?

So, I've got two 3/80s that think it's 1986 every time they boot.  And if
I try to set the date ahead four years, SunOS 4.1 hangs to the point you
have to power-cycle the machine to reboot it.  (Something in the streams
driver, I think.)

Anybody got any solutions?

Dave Curry
SRI International