On Mon, Mar 20, 2000 at 12:59:10AM +0100, Ruediger Oertel wrote:
> On Sun, 19 Mar 2000 [EMAIL PROTECTED] wrote:
>
> > Hi,
> >
> > I've a problem with the real-time clock. It detects digital unix epoch 1952,
> > but sets
> > my clock to year 2052 (even if SRM says 2000)!
> > Any idea ?
> yes, it seems to be something like a y2k-bug ...
>
> it's got to be close to these
[...]
> from linux-2.2.14/drivers/char/rtc.c:
> [...]
> static unsigned long epoch = 1900; /* year corresponding to 0x00 */
> [...]
> if (year > 10 && year < 44) {
> epoch = 1980;
> guess = "ARC console";
> } else if (year < 96) {
> epoch = 1952;
> guess = "Digital UNIX";
> }
I think this may be a pure userspace problem... *If* you use the rtc driver
and hwclock, all will be fine. hwclock mis-detects in not-up-to-date versions
the epoche when accessing the RTC chip on older machines via inb()/outb().
This should be fixed in the most recent versions.
MfG, JBG
PS: Please send your /proc/rtc output to Andries <[EMAIL PROTECTED]>!
He is the hwclock maintainer.
--
Fehler eingestehen, Gr��e zeigen: Nehmt die Rechtschreibreform zur�ck!!!
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
PGP signature
