Re: "Clock Skew detected error"

From: Barry K. Nathan (barryn@pobox.com)
Date: Sun Jan 30 2000 - 03:13:52 EST

  • Next message: David Schleef: "Re: Everyone Classic Hardware Crash (Re: 2.3.41-4 / hda: lost interrupt)"

    [snip]
    > 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. ;-)
    [snip]

    FWIW, most PC's I've encountered don't let you set the CMOS clock back
    beyond 1980. (Once I tried to boot a Linux system with the clock set past
    2038; the date in Linux was automatically turned back exactly 100 years
    IIRC.)

    I don't have time right now to test this for Feb. 29th compliance, but I
    believe that setting the year to 1996 and having the date command add 4
    years should work, as should any other combinations involving the date
    command adding multiples of four years. Perhaps having date just add any
    arbitrary amount of time will also work, but I don't have time to test that
    either.

    -Barry K. Nathan <barryn@pobox.com>

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/



    This archive was generated by hypermail 2b29 : Sun Jan 30 2000 - 03:26:13 EST