Am 11.09.2012 18:17, schrieb mike cloaked: > On Tue, Sep 11, 2012 at 5:16 PM, mike cloaked <mike.cloaked@xxxxxxxxx> wrote: >> On Tue, Sep 11, 2012 at 11:59 AM, Thomas Bächler <thomas@xxxxxxxxxxxxx> wrote: >> >>> Your /etc/adjtime probably contains a faulty adjustment value. Delete >>> it, hwclock --systohc, then reboot. >>> >> There is a problem running the hwclock command: >> >> [root@lapmike3 etc]# hwclock --systohc >> hwclock: Cannot access the Hardware Clock via any known method. >> hwclock: Use the --debug option to see the details of our search for >> an access method. >> >> Any suggestion as to work around this? >> > I tried: > > [root@lapmike3 etc]# hwclock --debug > hwclock from util-linux 2.21.2 > hwclock: Open of /dev/rtc failed: Device or resource busy > No usable clock interface found. > hwclock: Cannot access the Hardware Clock via any known method. I guess you need to stop chrony when playing with hwclock. Maybe it is enough to just delete adjtime without that command. Forgot to tell you (but it's probably too late now) to post the first line of your /etc/adjtime, this would have told us if we are on the right track.
Attachment:
signature.asc
Description: OpenPGP digital signature
