[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Yeah, 2.2.12 works and more! (was: Re: 2.2.12 does not work...)

Bart Warmerdam (bartw@xs4all.nl) wrote:

>   Ron,
>   Last time i faugth with my clock was some time ago. If your hwclock is
>   correct and date gives the wrong date try the following:
>   /etc/init.d/hwclock.sh stop
>   mv /etc/adjtime /etc/adjtime.old
>   /etc/init.d/hwclock.sh start
>   This should fix it.

Okay I did this and get:

# /etc/init.d/hwclock.sh stop
Cannot access the Hardware Clock via any known method.  Use --debug option to see the details of our search
for an access method.
CMOS clock updated to Thu Oct  3 01:39:04 PDT 2019.

So I ran:

# /etc/init.d/hwclock.sh --debug
Usage: hwclock.sh {start|stop|reload|show}
       start sets kernel clock from CMOS clock
       stop and reload set CMOS clock from kernel clock

Which doesn't tell me anything...

I shut the system down and reset it, went into ARC to check on the clock and it was like 2038 and the
incorrect day/month, but the time was correct. I changed the date, rebooted and Linux thinks the
year is 2019 now!?! Any ideas?


= Ronald Burnett Farrer =
- "mailto:rbf@magnesium.net";       -
- "http://www.magnesium.net/~rbf/"; -
! If you let Windows dominate, expect the worst: !
! "WORLD.SYS is corrupt, reboot UNIVERSE Y/n"    !
? "How could this [Y2K Bug] be a problem in a country ?
? where we have Intel and Microsoft?" -- Al Gore      ?

Reply to: