davy@itstd.sri.com (06/30/90)
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
ellery@trantor.harris-atd.com (Ellery Chan) (07/06/90)
In article <9551@brazos.Rice.edu> you write: |> 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. <various futile workarounds attempted> |> |> Anybody got any solutions? |> |> Dave Curry |> SRI International Under Known Problems in the Special Notes on SunOS Release 4.1: "Sun-3/80 Users Must Reset the Date After Powering Up: Every time a Sun-3/80 running SunOS release 4.1 is shut off and then powered up again, the date must be reset..." You didn't mention powering down, but could this be the root of your problem? Ellery Chan | ARPA : ellery@trantor.harris-atd.com Harris Corp., MS 3A-1912 | USENET: ...!uunet!x102a!trantor!ellery PO Box 37, Melbourne, FL 32902 | AT&T : (407) 729-3364