Hello,
I am new to Volumio, I am trying to install it on a RPI3. I have downloaded and installed version 2.513. First boot via Ethernet cable, configuring Wifi, and since that time, I use only the Wifi.
The audio part works fine, I use an external USB DAC (Objective DAC). I can listen to music, no problem. My music is on an NAS, as flac files.
I have an issue with time synchronisation. The RPI3 keeps using the date/time of the first boot, i.e 20 Dec 2018, and does not update.
This is my first question: during the configuration phase, it was apparently able to grab time synchronisation from the cable connection, I did not do anything special for this. But, after reboot on Wifi, it seems to go back to this date, which I do not understand. From my pov, it should:
- be able to get accurate date time though wifi (see below, this does not work yet)
- go back to 1970, first “Unix date”.
How can the “20 Dec 2108” survive to a reboot? Is it stored/cached somewhere?
EDIT: I noticed there is a file named fake-hwclock.data in /etc which obviously acts as a cache, so that’s why the date does not go back to 1970 on reboot. This is the anser to the question above…
I am trying to have ntp client running to solve this issue.
ntp and timesyncd are running:
volumio@volumio:~$ ps -edf | grep timesyncd
systemd+ 337 1 0 03:28 ? 00:00:00 /lib/systemd/systemd-timesyncd
volumio 1265 1082 0 03:55 pts/0 00:00:00 grep timesyncd
volumio@volumio:~$ ps -edf | grep ntp
ntp 714 1 0 03:28 ? 00:00:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 100:104
volumio 1267 1082 0 03:55 pts/0 00:00:00 grep ntp
I am synchronized on a ntp server, after stopping and restarting the service, and uncommenting the last line of /etc/systemd/timesyncd.conf
Servers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
volumio@volumio:~$ systemctl stop systemd-timesyncd.service
volumio@volumio:~$ systemctl start systemd-timesyncd.service
volumio@volumio:~$ sudo systemctl status systemd-timesyncd.service
â—Ź systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: active (running) since Thu 2018-12-20 03:59:17 CET; 3s ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 1313 (systemd-timesyn)
Status: "Using Time Server 149.202.220.144:123 (0.debian.pool.ntp.org)."
CGroup: /system.slice/systemd-timesyncd.service
└─1313 /lib/systemd/systemd-timesyncd
Dec 20 03:59:17 volumio systemd[1]: Started Network Time Synchronization.
Dec 20 03:59:17 volumio systemd-timesyncd[1313]: Using NTP server 149.202.220.144:123 (0.debian.pool.ntp.org).
But I’m still stuck on the same date:
Thu Dec 20 04:01:26 CET 2018
Timedatectl show that the ntp synchronisation is active, but still the wrong date…
volumio@volumio:~$ sudo timedatectl
[sudo] password for volumio:
Local time: Thu 2018-12-20 04:16:03 CET
Universal time: Thu 2018-12-20 03:16:03 UTC
RTC time: n/a
Time zone: Europe/Paris (CET, +0100)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: no
Last DST change: DST ended at
Sun 2018-10-28 02:59:59 CEST
Sun 2018-10-28 02:00:00 CET
Next DST change: DST begins (the clock jumps one hour forward) at
Sun 2019-03-31 01:59:59 CET
Sun 2019-03-31 03:00:00 CEST
What is wrong? Thanks for your help.