It might be another 32/64 bit image difference.
On my player based on the 64bit image:
Code:
pi@Orpheus:~ $ timedatectl
Local time: Fri 2022-06-24 15:06:35 BST
Universal time: Fri 2022-06-24 14:06:35 UTC
RTC time: n/a
Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
While on my 32 bit player:
Code:
pi@Prometheus:~ $ timedatectl status
Local time: Wed 2022-06-22 07:50:21 BST
Universal time: Wed 2022-06-22 06:50:21 UTC
RTC time: n/a
Time zone: Europe/London (BST, +0100)
System clock synchronized: no
NTP service: n/a
RTC in local TZ: no
Notice the NTP service is not available.
Then, using the set-ntp command which should turn on or off the NTP, on 64 gives:
Code:
pi@Orpheus:~ $ timedatectl set-ntp 0
==== AUTHENTICATING FOR org.freedesktop.timedate1.set-ntp ===
Authentication is required to control whether network time synchronization shall be enabled.
Authenticating as: ,,, (pi)
Password:
I quit out rather than giving my password because I didn't want to turn it off.
Same command on 32:
Code:
pi@Prometheus:~ $ timedatectl set-ntp 0
Failed to set ntp: NTP not supported
And in case that's just something that happens when turning off an already off service:
Code:
pi@Prometheus:~ $ timedatectl set-ntp 1
Failed to set ntp: NTP not supported
Could it be the NTP packages are missing from the 32 bit image?
