Op maandag 11 december 2017 13:42:59 CET schreef BWC Illmensee GmbH - Ralph Gauer:
My latest test with this service on a Rasberry Pi 3B, with tha latest aarch64 image, shows that it is not working. After a reboot the journal always starts with date/times Oct 26 14:29:36 and only after NTP becomes active, which is after the network is active, the date/time becomes the current time.
For now fake-hwclock does a better job.
On a Rpi2 and a Rpi1 the systemctl-timesyncd *does* its work. I activated it after reading this discussion. It changes the time from the kernel build-time to its saved time even before the fake-hwclock comes to work (I had both active at first). The root file system is mounted with "/dev/mmcblk0p2 / ext4 acl,user_xattr,noatime,commit=120 1 1". Perhaps you have some other options active that interfere with saving the time in the inode attributes?
Not that I am aware off. I only did some basic installation stuff. Did enable systemd-timesyncd.service, even started it, but after a reboot the date/time only changes after NTP becomes active. /etc/fstab looks like follows: /dev/disk/by-id/mmc-SD08G_0x7c498e75-part2 / ext4 noatime,nobarrier 1 1 /dev/disk/by-id/mmc-SD08G_0x7c498e75-part1 /boot/efi vfat defaults 0 0 /dev/disk/by-id/mmc-SD08G_0x7c498e75-part3 swap swap defaults 0 0 Command mount shows for / /dev/mmcblk0p2 on / type ext4 (rw,noatime,nobarrier,data=ordered) -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org