Kodi Community Forum

Full Version: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
(2016-05-27, 23:04)Little_Kitty Wrote: [ -> ]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.

(2016-05-27, 23:04)Little_Kitty Wrote: [ -> ]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.

(2016-05-27, 23:04)Little_Kitty Wrote: [ -> ]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...

(2016-05-27, 23:04)Little_Kitty Wrote: [ -> ]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
New LibreELEC.tv Krypton build #0527: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.6.0 #1 Fri May 27 21:05:21 BST 2016 armv6l GNU/Linux

# vcgencmd version
May 20 2016 19:05:21
Copyright (c) 2012 Broadcom
version faf071dd4885c5ac1a89483d35a5326e7f69495f (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20160527210329-#0527-g454d0a5 [Build #0527]

# vcdbg log msg 2>&1 | grep DTOK
002477.140: Kernel trailer DTOK property says yes

# Kernel device tree status: Enabled

Based on tip of LibreELEC.tv master (454d0a54, changelog) and tip of XBMC master (e18bd8d8, changelog) with the following modifications:
  • Includes newclock5 patches
  • Excludes the LibreELEC linux-01-RPi_support patch in favour of sourcing these and possibly more recent patches directly from kernel branch rpi-4.6.y
  • Includes latest bcm2835-driver master (3b98f743, ahead +10)
  • Includes latest kodi-platform master (c8188d82, ahead +4)
  • Includes latest libcec master (6d68d212)
  • Includes latest libnfs master (00d9ba15, ahead +19)
  • Includes latest p8-platform master (041a8c6c, ahead +1)
  • Includes latest addons: adsp.basic (2ae604e5, +8), adsp.biquad.filters (01236bbe, +7), adsp.freesurround (34f50406, +7), asplib (da66f517), inputstream.mpd (3ac19c39, +11), inputstream.smoothstream (32275717, +2), peripheral.joystick (83371862, +30), pvr.argustv (5f48dcec, +4), pvr.demo (0fa9e1d0, +4), pvr.dvblink (a92f1264, +5), pvr.dvbviewer (3d0bea9a, +4), pvr.filmon (8743511d, +4), pvr.hdhomerun (b5ce9309, +4), pvr.hts (acd1a6ac, +5), pvr.iptvsimple (7a5a43f8, +4), pvr.mediaportal.tvserver (172a273c, +4), pvr.mythtv (e2b60252, +8), pvr.nextpvr (150698b7, +4), pvr.njoy (b5d65655, +4), pvr.pctv (feed5990, +4), pvr.stalker (4244220f, +12), pvr.vbox (c6594819, +4), pvr.vdr.vnsi (5498a8c1, +7), pvr.vuplus (ea3b33f6, +4), pvr.wmc (77af8daf, +4)
  • Exclude [env] kodi-999.10-aarch64-support.patch: Merged upstream
  • Include [env] e7cbe9cb: xf86-video-intel: Explicitely disable TearFree and TripleBuffer
  • Include [env] ed774729: Intel: Implement Passthrough-Range
  • Include [env] 98c65e6a: Kodi: Use Limited Range by default
  • Include [env] patch: xf86-video-intel: bump to 3fafabe
  • Include [env] patch: Fix SIGTERM patch after PR9748
  • Include [env] patch: Fix cmake after PR9750
  • Include [env] patch: Add extra headers needed by 3D BD MVC
  • Include [env] patch: Disable -werror as libnfs won't build 32-bit without it
  • Include [env] patch: Bump libbluray - include MVC support
  • Include [env] patch: Add experimental splash video for RPi
  • Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.*, os.* and peripheral.*
  • Include [env] patch: Enable pvr addons, disable pvr updates
  • Include [env] patch: Enable other binary addons
  • Include [env] PR:353: plymouth-lite: add bilinear interpolation patch
  • Include [env] PR:366: mysql: update to 5.7.12
  • Include [env] PR:381: splash: Select splash image based on native resolution
  • Include [env] PR:382: systemd: update to 230
  • Include [env] PR:388: xf86-video-nvidia: update to xf86-video-nvidia-361.42
  • Revert [env] 46b9b7b3: rtmpdump (Reason: use newclock5 bump)
  • Include [pkg] patch: [skin.estuary] Hide watched items on home (kodi-theme-Estuary)
  • Include [pkg] patch: drm/i915: Extend Fake HDMI live status to Valley View (linux)
  • Include [pkg] patch: drm/i915/psr: Try to program link training times correctly (HSW fix) (linux)
  • Include [pkg] patch: Revert "drm/i915: Exit cherryview_irq_handler() after one pass" (BSW fix) (linux)
  • Include [pkg] patch: CSC: Remove average logic when saving NV12 surface on IVB+ (VAAPI fix) (libva-intel-driver)
  • Include [pkg] PR:8645: [video] Add season/TV show artwork to episodes/seasons even if they have their own fanart.
  • Include [pkg] PR:8824: videodb: fix smart playlists not honoring "Show empty TV shows" setting.
  • Include [pkg] PR:8922: [guiinfo] extend ranges for listitem properties
  • Include [pkg] PR:9803: [PeripheralCecAdapter] fix playback stopping on screensaver deactivated
  • Include [pkg] PR:9847: [PVR] Feature: Make instant recording behavior configurable
Build Highlights:
  1. NOTE: DVD playback remains temporarily disabled
  2. mmal/videoplayer updates
Build Details:
  1. XBMC:
    • [PVR] add recording id to recording path (PR:9879, 1 commit, 3 files changed)
  2. newclock5:
    • New commits in this build:
      • [mmalcodec] Add back in preroll (16480c91)
      • LinuxRendererGLES: Remove unused code (c7b3c65b)
      • VideoPlayer: fix CheckEnableClockSync (4bc0ad81)
      • VideoPlayer: remove some useless code (938f74c6)
(2016-05-27, 04:28)SeVreN2013 Wrote: [ -> ]
(2016-05-27, 02:59)santope Wrote: [ -> ]I have got LibreELEC running, and downloaded the .tar, but I cannot find the "update" folder to copy it in.

1st. Enable display of hidden files and folders in LibreELEC

System > Settings > Appearance > File Lists > Show hidden files and directories

2nd. Have a USB Flash Drive with .tar file plugged into the Raspberry Pi and then go to "File Manager" to copy it into the ".update" folder

System > File Manager > storage > .update

then "Reboot" your Pi to auto start the update procedure.

(2016-05-27, 12:13)ElectricPim Wrote: [ -> ]
(2016-05-27, 02:59)santope Wrote: [ -> ]I am new to the whole RPI concept, so this is very basic question:

or through a network?

Any clue would be appreciated.
Thx,

No need to copy anything, do it by terminal, and let the RPI download it:

Code:
ssh [email protected] (or ssh [email protected]*)
cd .update
wget http://milhouse.libreelec.tv/builds/master/RPi2/***.tar
reboot

This requires a linux/osx machine, but since Microsoft finally has seen the light, you can use a Bash shell in Windows 10 (soon) to run above commands:
https://blogs.windows.com/buildingapps/2...n-windows/

Many thanks for your patience and your comprehensive replies to my newbie question.
In the end I did it through the Raspberrian GUI file manager type of thing, but I had to change the permissions, from the command line. A good Linux exercise for me !
But I will also try your suggestions, just to learn.
Another little question (this should be easy):
Can I (should I) run LibreELEC from NOOBS ?
(2016-05-28, 00:29)santope Wrote: [ -> ]Can I (should I) run LibreELEC from NOOBS ?

It's possible to do so, but unless you plan on booting multiple operating systems there is no point in using NOOBS as you'll lose a lot of storage space and have a more complicated setup.

If you need additional support it would be best to start a new thread so that this testing thread remains on topic.
(2016-05-28, 00:46)Milhouse Wrote: [ -> ]
(2016-05-28, 00:29)santope Wrote: [ -> ]Can I (should I) run LibreELEC from NOOBS ?

It's possible to do so, but unless you plan on booting multiple operating systems there is no point in using NOOBS as you'll lose a lot of storage space and have a more complicated setup.

If you need additional support it would be best to start a new thread so that this testing thread remains on topic.

Sorry, I suppose my questions pertain to LibreELEC in general, not this test version.
But I cannot test if I cannot load your test builds. And I don't find any option here to show hidden files and folders.
However, back to topic:
- I tried to play a MVC ISO file (the reason I came to this thread). It plays nicely, but only in 2D. Maybe to do with the fact that I am using a PC monitor (1080p 60Hz) and not a TV? I still expected to see an overlapping double picture or something
- Other than that, and random freezes, the only thing I noticed is the left sliding menu that keeps sliding in and out of view before you can select anything.
Thanks for the good work,
(2016-05-28, 00:13)Milhouse Wrote: [ -> ]Maybe this is a new behaviour in recent kernels...

This had me scratching my head, but this is why the default date appears to match the build date.

Since systemd 229:
Code:
* On boot-up, when PID 1 detects that the system clock is behind the
  release date of the systemd version in use, the clock is now set
  to the latter. Previously, this was already done in timesyncd, in order
  to avoid running with clocks set to the various clock epochs such as
  1902, 1938 or 1970. With this change the logic is now done in PID 1
  in addition to timesyncd during early boot-up, so that it is enforced
  before the first process is spawned by systemd. Note that the logic
  in timesyncd remains, as it is more comprehensive and ensures
  clock monotonicity by maintaining a persistent timestamp file in
  /var. Since /var is generally not available in earliest boot or the
  initrd, this part of the logic remains in timesyncd, and is not done
  by PID 1.

Since build #0522, systemd is being rebuilt during each incremental build while PR:382 (bump to systemd 230) remains unmerged upstream. Consequently the release date of systemd closely approximates to the date/time of the build in which it appears, because systemd is being rebuilt on a daily basis.

Prior to build #0522, systemd was last built during a private (unreleased) clean build on May 20, when the systemd package was built at 12:40. If you were to boot the released build #0521 which did not need to rebuild systemd, you will see the default date is "May 20 12:40:32".

When PR:382 merges upstream, systemd will be built once more and then subsequent incremental builds will no longer rebuild systemd, at which point the default date will no longer match (or approximate to) the build date.
@Little_Kitty: Given the above, if you have set the correct timezone but still have incorrect time (your date is "correct" purely by chance, something that will stop being the case in future once systemd is not built on a daily basis, and probably will be incorrect if you reboot after midnight) then I can only imagine that you do not have a functioning internet connection and will need to look at the rest of your network to determine where the fault lies.
(2016-05-27, 13:53)Shanyel Wrote: [ -> ]
(2016-05-27, 06:45)TheShoe Wrote: [ -> ]
(2016-05-27, 06:22)Milhouse Wrote: [ -> ]Is it just the time that is incorrect, and not also the date? Have you set the timezone correctly in Kodi?

oh good grief! this is a PEBCAK (Problem Exists Between Chair and Keyboard).

no i didn't. sorry for wasting your time (no pun intended). it's been a long week.

cheers and thanks for pointing out the obvious to me

I've the same issue.. timezone is set correctly to Britain (UK) in Kodi, date is lagging and time is completely off...
It started lately, didn't notice when. Tried to change a timezone to something else, restart, waited a bit for ntp update... nothing... even when back to GMT timezone. Will try to go back few realeases to find out.
Connected via LAN to router, same setup for several years now, router is synced with ntp and aligned
Any idea?


ok - so here's what solved it for me once the obvious was pointed out:

1: set country and timezone in Kodi
2: re-add pool.ntp.org in libreelec ntp settings
3: reboot and voila!

interesting although Milhouse mentioned the ntp server should not need to be set, i still had to do it to get the correct time
(2016-05-28, 04:53)TheShoe Wrote: [ -> ]interesting although Milhouse mentioned the ntp server should not need to be set, i still had to do it to get the correct time

What I actually said:

(2016-05-28, 00:13)Milhouse Wrote: [ -> ]These shouldn't be necessary unless your own network is the problem and your DHCP server is configured with an inaccurate timeserver.

The default (fallback) servers are 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org, and will be used if there is no other timeserver configured in your network.

If your network is specifying it's own timeserver via DHCP then you won't be using these default timeservers.

However if your network timeserver is inaccurate then you need to configure static timeservers (as you have done) in order to override your DHCP server.

Obviously the best option is to fix your DHCP server so that it uses an accurate timeserver, or no timeserver at all leaving your devices to use sane defaults.
i did check the router and it's configured with pool.ntp.org and the TZ is set properly. should it be 0.pool.ntp.org ?
pool.ntp.org is a cluster that dynamically resolves to multiple addresses for timeservers appropriate for your region - in effect, a load balancer, of sorts. See http://www.pool.ntp.org/en/use.html

Even if your router is configured to use pool.ntp.org, what timeserver is your LibreELEC client configured to use - is LE being configured (by DHCP) to use pool.ntp.org, or is it using your router (ie. 192.168.0.x) as the timeserver? If the latter, is the ntpd daemon working correctly in your router? Is the time on your router accurate?

In LE, try (where 192.168.0.x is your router address):
Code:
ntpd -wqd -p pool.ntp.org
ntpd -wqd -p 0.pool.ntp.org -p 1.pool.ntp.org -p 2.pool.ntp.org -p 3.pool.ntp.org
ntpd -wqd -p 192.168.0.x

and see if you get valid replies, or timeouts (ctrl-c to end each run). Each time you run ntpd for pool.ntp.org you should query a different timeserver (0.pool.ntp.org etc. will also be random).
(2016-05-28, 06:33)Milhouse Wrote: [ -> ]pool.ntp.org is a cluster that dynamically resolves to multiple addresses for timeservers appropriate for your region - in effect, a load balancer, of sorts. See http://www.pool.ntp.org/en/use.html

Even if your router is configured to use pool.ntp.org, what timeserver is your LibreELEC client configured to use - is LE being configured (by DHCP) to use pool.ntp.org, or is it using your router (ie. 192.168.0.x) as the timeserver? If the latter, is the ntpd daemon working correctly in your router? Is the time on your router accurate?

In LE, try (where 192.168.0.x is your router address):
Code:
ntpd -wqd -p pool.ntp.org
ntpd -wqd -p 0.pool.ntp.org -p 1.pool.ntp.org -p 2.pool.ntp.org -p 3.pool.ntp.org
ntpd -wqd -p 192.168.0.x

and see if you get valid replies, or timeouts (ctrl-c to end each run). Each time you run ntpd for pool.ntp.org you should query a different timeserver (0.pool.ntp.org etc. will also be random).

Tried that. I do get replies from all pool.ntp.org clusters, though the date is incorrect...
My router time is OK, checked also with windows 10 pc/laptop and time is synced correctly
I posted this a while back, but there were some other discussions going on, so I don't think it was really noticed (sorry if I missed any replies). The problem I have for quite some time now, on two different RPis, is that I need to disable and re-enable UPnP and AirPlay every time I have rebooted my device. If I don't, UPnP is not detected in my network and AirPlay won't accept incoming connections. Since it's two devices having the same issue, it's either something in my network or something with the software. Is anybody else experiencing this?
(2016-05-28, 00:29)santope Wrote: [ -> ]Many thanks for your patience and your comprehensive replies to my newbie question.
In the end I did it through the Raspberrian GUI file manager type of thing, but I had to change the permissions, from the command line. A good Linux exercise for me !

That's the spirit!

santope Wrote:But I will also try your suggestions, just to learn.
Another little question (this should be easy):
Can I (should I) run LibreELEC from NOOBS ?

Yes, I run from NOOBS, you can update openelec to libreelec.

I created a small bash script that will update LibreElec to the lastest Millhouse build. Run it on your PC/Laptop in your LAN, it uses SSH and lynx is needed (apt-get install lynx)

Code:
#!/bin/bash
# le_update.sh
DOMAIN="http://milhouse.libreelec.tv/builds/master/RPi2/"

if [ "$1" = "" ]; then
PATTERN="RPi2.arm"
else
PATTERN="#$1"
fi

URL=`lynx -dump -nolist $DOMAIN | egrep $PATTERN | tail -n 1 | awk '{print $1;}'`
URL=$DOMAIN${URL/\#/%23}
ssh [email protected] "wget -P .update ${URL} ; reboot"

You can also run it with a build number to revert to an older build.
Code:
le_update.sh 0522  // will revert to the #0522 build
(2016-05-28, 13:14)makruiten Wrote: [ -> ]I posted this a while back, but there were some other discussions going on, so I don't think it was really noticed (sorry if I missed any replies). The problem I have for quite some time now, on two different RPis, is that I need to disable and re-enable UPnP and AirPlay every time I have rebooted my device. If I don't, UPnP is not detected in my network and AirPlay won't accept incoming connections. Since it's two devices having the same issue, it's either something in my network or something with the software. Is anybody else experiencing this?

It would be useful to confirm if this is a regressions or if it has never worked.
e.g. does the LE Jarvis stable build have the same issue? If it does, then does the OE Isengard stable build have this issue?