[Milhouse]

i have the timeservers setup via the libreELEC settings
0.pool.ntp.org
1.pool.ntp.org.

These shouldn't be necessary unless your own network is the problem and your DHCP server is configured with an inaccurate timeserver.

When i turn on the PI it shows the wrong time.

Wrong *time*, or wrong *date*?

Having the wrong *time* would suggest you have an incorrect timezone.

A date of January 1970 means you have no timeserver at all, or no internet connection. (edit: systemd will now set an approximate date - see post #681)

A wrong *date* means the timeserver being used is not accurate, or not available.

It shows the time that the image was updated? like i put the latest from 26 may it shows 26 may.

Just a guess - perhaps the kernel uses the date the kernel is built in the absence of any other time source?

I see the following with tonight's #0527 build on an RPi3:

Code:

rpi22:~/.cache # journalctl
-- Logs begin at Fri 2016-05-27 21:07:10 BST, end at Fri 2016-05-27 22:38:14 BST. --
May 27 21:07:10 LibreELEC systemd-journald[200]: Runtime journal (/run/log/journal/) is 512.0K, max 2.0M, 1.5M free.
May 27 21:07:10 LibreELEC kernel: Booting Linux on physical CPU 0x0
May 27 21:07:10 LibreELEC kernel: Linux version 4.6.0 ([email protected]) (gcc version 5.3.0 (GCC) ) #1 SMP Fri May 27 21:05:19 BST 2016
May 27 21:07:10 LibreELEC kernel: CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
May 27 21:07:10 LibreELEC kernel: CPU: div instructions available: patching division code
May 27 21:07:10 LibreELEC kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
May 27 21:07:10 LibreELEC kernel: Machine model: Raspberry Pi 3 Model B Rev 1.2
...
May 27 21:07:18 rpi22 avahi-daemon[478]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.18.
May 27 21:07:18 rpi22 avahi-daemon[478]: New relevant interface eth0.IPv4 for mDNS.
May 27 21:07:18 rpi22 avahi-daemon[478]: Registering new address record for 192.168.0.18 on eth0.IPv4.
May 27 21:07:18 rpi22 connmand[434]: Setting domainname to local
May 27 21:07:18 rpi22 connmand[434]: eth0 {add} address 192.168.0.18/24 label eth0 family 2
May 27 21:07:18 rpi22 connmand[434]: ntp: time slew +1345.690052 s
May 27 21:29:44 rpi22 systemd[1]: Time has been changed
May 27 21:29:44 rpi22 connmand[434]: eth0 {add} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>
May 27 21:29:44 rpi22 connmand[434]: eth0 {add} route 192.168.0.1 gw 0.0.0.0 scope 253 <LINK>
May 27 21:29:44 rpi22 connmand[434]: eth0 {add} route 0.0.0.0 gw 192.168.0.1 scope 0 <UNIVERSE>

The exact same time - May 27 21:07:10 - is also the initial date/time when booting the #0572 build on an RPi1:

Code:

rpi512:~/.cache # journalctl
-- Logs begin at Fri 2016-05-27 21:07:10 BST, end at Fri 2016-05-27 23:47:09 BST. --
May 27 21:07:10 LibreELEC systemd-journald[182]: Runtime journal (/run/log/journal/) is 512.0K, max 2.0M, 1.5M free.
May 27 21:07:10 LibreELEC kernel: Booting Linux on physical CPU 0x0
May 27 21:07:10 LibreELEC kernel: Linux version 4.6.0 ([email protected]) (gcc version 5.3.0 (GCC) ) #1 Fri May 27 21:05:21 BST 2016
May 27 21:07:10 LibreELEC kernel: CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
May 27 21:07:11 LibreELEC kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
May 27 21:07:11 LibreELEC kernel: Machine model: Raspberry Pi Model B Rev 2
...
May 27 21:07:24 rpi512 connmand[277]: Setting domainname to local
May 27 21:07:24 rpi512 connmand[277]: eth0 {add} address 192.168.0.8/24 label eth0 family 2
May 27 21:07:24 rpi512 connmand[277]: ntp: time slew +1206.453992 s
May 27 21:27:30 rpi512 systemd[1]: Time has been changed
May 27 21:27:30 rpi512 connmand[277]: eth0 {add} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>
May 27 21:27:30 rpi512 connmand[277]: eth0 {add} route 192.168.0.1 gw 0.0.0.0 scope 253 <LINK>
May 27 21:27:30 rpi512 connmand[277]: eth0 {add} route 0.0.0.0 gw 192.168.0.1 scope 0 <UNIVERSE>

Not entirely sure how or where it gets the date/time from, but for it to be the exact same on two different devices booted at two different times is likely to be more than just a coincidence.

Booting #0526 build on 27 May @ 23:53 on RPi3:

Code:

rpi22:~/.cache # journalctl
-- Logs begin at Thu 2016-05-26 21:08:43 BST, end at Fri 2016-05-27 23:53:11 BST. --
May 26 21:08:43 LibreELEC systemd-journald[207]: Runtime journal (/run/log/journal/) is 512.0K, max 2.0M, 1.5M free.
May 26 21:08:43 LibreELEC kernel: Booting Linux on physical CPU 0x0
May 26 21:08:43 LibreELEC kernel: Linux version 4.6.0 ([email protected]) (gcc version 5.3.0 (GCC) ) #1 SMP Thu May 26 21:06:51 BST 2016
May 26 21:08:43 LibreELEC kernel: CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
May 26 21:08:43 LibreELEC kernel: CPU: div instructions available: patching division code
May 26 21:08:43 LibreELEC kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
May 26 21:08:43 LibreELEC kernel: Machine model: Raspberry Pi 3 Model B Rev 1.2

Maybe this is a new behaviour in recent kernels...

is it correct NTPdate isnt installed?

connmand handles ntp.

What is the output from:

Code:

cat /storage/.cache/timezone
connmanctl clock | pastebinit
connmanctl services | pastebinit
connmanctl services $(connmanctl services | awk '/^\*/ {print $NF}') | pastebinit
journalctl -a | pastebinit