4 Jun
2024
4 Jun
'24
15:42
On Tue, 04 Jun 2024 17:19:26 +0200
Jonas Kvinge
chronyd is running on the Raspberry Pi Os installations too, without timesync systemd service, and there it's not an issue. And I don't see how a systemd service can solve this since it will be started after the kernel starts booting, but I've tested switching to timesync on openSUSE like you said, it does not solve any issue with the time.
If you want to understand how Raspberry Pi OS does something, would you not do better asking on a Raspberry Pi list or forum? IIUC correctly systemd is active in the initrd so could potentially do things before the system is active. For the avoidance of doubt, I know nothing about your particular issue or how to solve it.