Article View: comp.sys.nsc.32k
Article #1535Clock on ICM-3216
From: M.W.HADDOCK
Date: Sun, 08 Jan 1989 16:59
Date: Sun, 08 Jan 1989 16:59
24 lines
1377 bytes
1377 bytes
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!
Technical Details
Message-ID:
<493@hocpa.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!ames!ucsd!rutgers!att!whuts!homxb!hocpa!rustyShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!ames!ucsd!rutgers!att!whuts!homxb!hocpa!rusty From: rusty@hocpa.UUCP (M.W.HADDOCK) Newsgroups: comp.sys.nsc.32k Subject: Clock on ICM-3216 Keywords: ICM3216 clock chip BSD Message-ID: <493@hocpa.UUCP> Date: 8 Jan 89 16:59:01 GMT Reply-To: rusty@hocpa.ATT.COM (91341-M.W.HADDOCK) Organization: AT&T Consumer Products Laboratories Lines: 24