rusty@hocpa.UUCP (M.W.HADDOCK) (01/09/89)
Happy New Year folks!
Unfortunately, since the beginning of the new year, fe2o3 (my ICM3216) keeps
reporting each minute (or there abouts) that the rtclock is off by 86400
seconds +/- 1. This comes to be 1-day worth of seconds. Naturally, I'm
running UToronto's BSD4.2 so I'm not sure if this is a software or hardware
bug. Maybe my clock battery is going dead as I've had fe2o3 up and running
for almost two years nearly continuous.
NSC folks: How long's that little battery s'pose to last?
Is anyone else having this problem? If you're running this BSD port check
your /usr/adm/messages file and if the same is happening to you the file
should have grown by about 1-meg in size since the new year.
Thanks for bearing with me!
-Rusty-
----
--
Rusty Haddock {uunet!likewise,att,arpa}!hocpa!rusty
AT&T Consumer Products Laboratories - Human Factors Laboratory
Holmdel, New Joyzey 07733 (201) 834-1023 rusty@hocpa.att.com
I LOVE CATS -- DEAD ONES!schultz@mmm.UUCP (John C Schultz) (01/12/89)
In article <493@hocpa.UUCP> rusty@hocpa.ATT.COM (91341-M.W.HADDOCK) writes: >Happy New Year folks! > >Unfortunately, since the beginning of the new year, fe2o3 (my ICM3216) keeps >reporting each minute (or there abouts) that the rtclock is off by 86400 >seconds +/- 1. This comes to be 1-day worth of seconds. Naturally, I'm Nope, I have not had this problem. However I am (still) using the V.2.2 National port. I don't think the battery is the problem since my board is a couple years old (Rev A PROMS) too. Of course bad batteries and/or a bug in the software is not unheard of :-). -- john c. schultz schultz@3M.Com ..!uiucuxc!mmm!schultz (612) 733-4047 3M Center, Bldg 518-1-1, St. Paul, MN 55144-1000 The opinions expressed herein are, as always, my own and not 3M's.