On 04.06.2024 18:19, Jonas Kvinge wrote:
On Tue, 2024-06-04 at 15:01 +0200, Freek de Kruijf wrote:
If you disable chronyd.service and enable systemd-timesyncd.service the system will soon have the time of the last shutdown and when the network is up it will synchronize with a time server.
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.
Debian after reboot shows:
Then find out how Debian does it and then we can look whether the same method is also available in openSUSE.
kernel boot: 2024-06-04T14:41:54.222699+00:00 WFD002000001 kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083] 2024-06-04T14:41:54.232954+00:00 WFD002000001 kernel: [ 0.000000] Linux version 6.1.0-rpi6-rpi-v8 (debian-kernel@lists.debian.org) (gcc- 12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.1.58-1+rpt2 (2023-10-27)
date: Tue Jun 4 14:44:10 UTC 2024
uptime: 14:44:32 up 1 min, 2 users, load average: 3.85, 1.25, 0.44
openSUSE after reboot shows (same hardware as Debian), still May 16.
kernel boot: May 16 10:01:21 edge.vendanor.com kernel: Booting Linux on physical CPU 0x0000000000 [0x410fd083] May 16 10:01:21 edge.vendanor.com kernel: Linux version 6.9.1-1-default (geeko@buildhost) (gcc (SUSE Linux) 13.2.1 20240509 [revision b7a2697733d19a093cbdd0e200ffce069a4bc812], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.42.0.20240130-3) #1 SMP PREEMPT_DYNAMIC Fri May
date: Tue Jun 4 02:54:53 PM UTC 2024
uptime: 14:54:55 up 19 days 4:53, 2 users, load average: 4,86, 1,16, 0,38
Jonas