Re: "Clock Skew detected error"

[TimO]

Heh, my old 486 has a similar problem.  If your machine boots with
'arbitrary' or lagging dates, then your cmos battery is probably going dead
and needs replacement.  After that is corrected and your machine always
boots with the year '1994' after setting it to 2000(as mine does); you need
to set the cmos clock to '1972' (has the same days as 2000) and add the
line:

date --set='+28 years'

to your init scripts.  This will make your 486 'usable' under Linux/GNU for
another 27 years. But, then, YMMV.  ;-)

I had just left it at '1994' but it isn't a leap year and as such will fail
after Feb 28.  Unfortunately, if you dual boot with Microsoft, there is no
way (that I know of) to obtain equivalent results.  Setting the time with
Microsoft will also reset the cmos clock and result in bogus time again. 
If you have a 'flash' bios, you may also check to see if there is an update
available which corrects the problem.

--- Tim

Sujit Vaidya wrote:
> 
> Hi Borek,
>         Thanks for your guidence. When i use the date
> and the hwclock commands the dates change. But when i
> reboot the machine it takes some arbitrary date.
> THis time it said at boot time
> System Clock: 21 Jul 07:20 EDT 1992
>           Any pointers..
> 
> THanks
> 
> SUJIT VAIDYA
> 
> --- Borek Lupomesky <[e-mail]> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Mon, 24 Jan 2000, Sujit Vaidya wrote:
> >
> > > Hi Borek,
> > >         It might be a trivial question, but i
> > would
> > > appreciate if you could guide me with regards to
> > "HOW
> > > TO SET THE REAL TIME CLOCK"
> > >         I changed the date on my machine using the
> > > date command. And the kernel compiles fine. But
> > when i
> > > boot the system it again shows
> > > system clock set to JAN **, 1994.
> >
> >    Using the date(1) command:
> >
> > date --set="Jan 25 7:24"
> >
> >    Then you should write the system clock to your
> > CMOS (backup) clock
> > using:
> >
> >    hwclock --systohc
> >