ioctl(RTC_SET_TIME) to /dev/rtc0 to set the time failed

[ghost]

I tried to install on sbc s905x with the ubuntu version of armbian os 22 but got hit by a problem in the hwclock as below logs

11 Oct 11:35:52 ntpdate[13682]: step time server 202.65.114.202 offset -0.002831 sec hwclock: ioctl(RTC_SET_TIME) to /dev/rtc0 to set the time failed: Invalid argument 2024-10-11T11:35:53.002Z matori Failed to exec command: /bin/sh -c /usr/sbin/hwclock -w hwclock: ioctl(RTC_SET_TIME) to /dev/rtc0 to set the time failed: Invalid argument: exit status 1 2024-10-11T11:35:53.002Z [A] matori: UpdateNtpDate failed (15.726925459s) 2024-10-11T11:35:53.003Z [Job] [Prepare the System Environment] execute failed <nil>

Is there a parameter or config to bypass the hwclock setting? , because my sbc when checking the clock using timedatectl is in accordance with the existing time

[eball]

@MATORINET unfortunately, we didn't have to do any tests on sbc. Did you succeed in installing k3s on sbc before?

[ghost]

@eball for manual installation Kubernetes Using K3s successfully used smoothly, Previously I used Docker for Casa OS in my sbc is also smooth . for this issue in my sbc kernel which has not found a driver for the requirements use of hwclock during Terminus installation, if there is an option parameter for skipping hwclock i can try to manual installation Terminus . I hope there is more complete documentation of the detailed parameters at the time of installation

[eball]

@MATORINET Our Terminus needs the time to be accurate to make sure that every single feature is working fine. Probably you can make a fake hwclock to passthrough it.

[ghost]

@eball I've tried using fake-hwclock but at the time of installation it is still constrained in hwclock -w , For RTC in sbc using virtual RTC, can only see the result of ntp, to write using hwclock -w so far has not found a solution