> Are you trying that with rtcsync or rtcdrift? I am trying with rtcsync. This works on my smaller processor. rtcdrift does not work on either processors. No rtc drift file is created, nor is the rtc being corrected. I am also getting this error message
Could not enable RTC interrupt : Invalid argument All of this is pretty much a mystery to me. Writing the clock with hwclock also works on the main processor, but not with chronyd. On Juli 17 2024, at 9:49 am, Miroslav Lichvar <mlich...@redhat.com> wrote: > On Tue, Jul 16, 2024 at 03:42:05PM +0200, Jan Claußen wrote: > > So I found online that an rtcfile directive is needed for the rtcdata > > command to work. I am still getting the above error message now. Makes me > > wonder if RTC syncing ever worked with the rtcsync directive present. There > > was never really a log about chrony syncing to the RTC. I have now tried to > > manually set the RTC to a wrong value and have waited more than 11 minutes. > > The RTC is still not getting set. > > Are you trying that with rtcsync or rtcdrift? > With rtcsync there are no log messages from chronyd. It's the kernel's > job to sync the RTC. With rtcdrift you will need to add also > rtcautotrim to the config or periodically call chronyc trimrtc. > > https://chrony-project.org/faq.html#_what_is_the_real_time_clock_rtc > -- > Miroslav Lichvar > > > -- > To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org > with "unsubscribe" in the subject. > For help email chrony-users-requ...@chrony.tuxfamily.org > with "help" in the subject. > Trouble? Email listmas...@chrony.tuxfamily.org. >
