al@grebyn.com (Albert L. Donaldson) (12/22/88)
I've just purchased a used Sun 3/50M, and I'm unable to get the system to re-boot without forgetting the current date. The clock (i.e., hh:mm) seems to be pretty close, but the date loses anywhere from 25 days to a month. I've replaced the battery on the CPU board (twice), and even swapped out the CPU board last night (for an unrelated problem). As I remember, I'm got ROM rev 2.6 on the current CPU board. The kernel was built from the standard standalone prototype (SDST50?), with a change to the entry for zs0 to allow it to handle dial-in and dial-out on the serial port. Otherwise, nothing special. Is this a known problem with a known solution, or should I keep running down to Radio Shack til I find a battery that works? :-) Al Donaldson al@grebyn.com ..!uunet!vrdxhq!escom!al
smb@research.att.com (01/04/89)
Sounds like the time-of-day clock bug; check if that patch has been installed.
bet@bent.mc.duke.edu (Bennett Todd) (01/05/89)
I had this exact problem; it went away when I applied the Sun clock patch (a fix for a bug in the clock driver that shows up on leap years). The official fix from Sun is available from the Sun-spots archives as sun-spots/tod-patch. [[ Archive server users should use the request "send sun-spots tod-patch". --wnl ]] -Bennett