I’m running Tumbleweed aarch64 on Raspberry Pi-3b.
Yesterday I did “zypper dup” to update to 4.15.7-1 (was running 4.15.3-1 before, I think).
I noticed yesterday, then confirmed as I’ve rebooted several times, that the date/time are set incorrectly at boot time. Date comes up initially as something like Feb 19,2018, 09:28 EST. If I set the date/time manually, it keeps time. But time is set incorrectly at boot time.
Anyone else notice that? Any fixes? Probably a Raspberry Pi-only issue because of the way the Pi handles the RTC issue, but I thought I’d ask (and point it out for packagers).
I’m running Tumbleweed aarch64 on Raspberry Pi-3b.
Yesterday I did “zypper dup” to update to 4.15.7-1 (was running 4.15.3-1
before, I think).
I noticed yesterday, then confirmed as I’ve rebooted several times, that
the date/time are set incorrectly at boot time. Date comes up
initially as something like Feb 19,2018, 09:28 EST. If I set the
date/time manually, it keeps time. But time is set incorrectly at boot
time.
Anyone else notice that? Any fixes? Probably a Raspberry Pi-only issue
because of the way the Pi handles the RTC issue, but I thought I’d ask
(and point it out for packagers).
Hi
Yes, it seems to be DNS resolver related (as well as zypper, ping, wget
etc). If you define the ip address in the /etc/ntp.conf file and rem
out the name lines. restart the ntpd service and all should be good.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3|GNOME 3.20.2|4.4.114-42-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Thanks, Malcolm. I figured it out late last night but hadn’t gotten time to post a resolution. I just looked up some NIST server IPs and entered them into the date/time advanced section on the YAST GUI interface. But your solution would have been much faster.
