[Milhouse]

New LibreELEC.tv Leia build #0729: RPi / RPi2
(Supercedes previous build)

Code:

# uname -a
Linux rpi512 4.12.4 #1 Sat Jul 29 21:53:43 BST 2017 armv6l GNU/Linux

# vcgencmd version
Jul 28 2017 20:20:00
Copyright (c) 2012 Broadcom
version 6716e816fd1614c326071d86188976b5fbf9c22b (clean) (release)

# lsb_release
LibreELEC (Milhouse): devel-20170729213910-#0729-g3897072 [Build #0729]

# Kodi version
(18.0-ALPHA1 Git:53da7c7). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (38970726, changelog) and tip of XBMC master (53da7c75, 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.12.y
  
• Includes latest bcm2835-driver master (23047785)
  
• Includes latest kodi-platform master (36fb4937)
  
• Includes latest libcec master (8adc786b, ahead +26)
  
• Includes latest libnfs master (df94ae93, ahead +56)
  
• Includes latest p8-platform master (a822e196)
  
• Includes latest addons: inputstream.adaptive (e298e958, +8), inputstream.rtmp (39d7979a), peripheral.joystick (1815c0fb, +1), pvr.argustv (4e8c838b), pvr.demo (f67dff13), pvr.dvblink (640629ca), pvr.dvbviewer (9faf2413), pvr.filmon (1c9d2ebe), pvr.hdhomerun (48868e44), pvr.hts (878757a9, +3), pvr.iptvsimple (8ccf85cc), pvr.mediaportal.tvserver (d7a9acdb, +1), pvr.mythtv (4704f721, +5), pvr.nextpvr (03a3b714), pvr.njoy (79e8e653), pvr.octonet (a77cf111), pvr.pctv (00b76689), pvr.stalker (9e28f125), pvr.vbox (44f3d04e, +9), pvr.vdr.vnsi (9268f008, +1), pvr.vuplus (55e4f5f9), pvr.wmc (1d655540)
  
• Include [env] compare: kodi updates
  
• Include [env] patch: pvr addons: disable broken addons
  
• Include [env] patch: inputstream.rtmp: disable outdated addons that no longer build
  
• Include [env] patch: rev hack for kodi
  
• Include [env] patch: tvheadend42: fixup ffmpeg patch
  
• Include [env] patch: Bump included addon versions to prevent online updates
  
• Include [env] patch: Add experimental splash video for RPi
  
• Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
  
• Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, other)
  
• Include [env] PR:1726: [WIP] lirc: update to 0.10.0
  
• Include [env] PR:1773: init: make break after behaviour really break after
  
• Include [env] PR:1776: Don't cause system to hang on halt/reboot when net-booting
  
• Include [env] PR:1791: nss/nspr: include in main image [rfc]
  
• Include [env] PR:1798: linux: update to linux-4.12.4
  
• Include [env] PR:1824: samba: make SMB3_11 the default protocol, don't force in kodi
  
• Include [env] PR:1835: add support for optional kernel modules in image and from addons
  
• Include [pkg] patch: skin.estuary: reduce system info font size (kodi)
  
• Include [pkg] PR:12110: smbclient: cleanup smbclient configuration
  
• Include [pkg] PR:12311: FIX: ensure real filename from videodb in playlists
  

Build Highlights:

1. New 4.12.4 kernel
   

Build Details:

1. LibreELEC.tv:
   • avahi: cleanup (PR:1844, 1 commit, 2 files changed)
     
2. XBMC:
   • [PVR] Obtain live stream URL from client addon before starting playba (PR:12587, 1 commit, 4 files changed)
     
   • [xbmc] Addon settings fixes (PR:12536, 1 commit, 2 files changed)
     
   • [imdb] fix crash on empty videoInfoTag (PR:12373, 1 commit, 2 files changed)
     
   • Fix missing include when building for X11 without VAAPI and VDPAU (PR:12576, 1 commit, 1 file changed)
     
   • Some fixes for issues raised by cppcheck (PR:12544, 14 commits, 97 files changed)
     
3. pvr.vbox:
   • Change the build instructions to apply to the latest Kodi master (PR:198, 1 commit, 1 file changed)
     
   • Fix Kodi link in the README (PR:199, 1 commit, 1 file changed)
     
   • Implement PVR addon API changes to make the addon build again (PR:200, 3 commits, 3 files changed)
     
   • Minor README updates (PR:201, 4 commits, 2 files changed)
     
4. Additional commits/pull requests/changes not yet merged upstream:
   • Added: [env] PR:1798: linux: update to linux-4.12.4
     

[Pienoet]

Is it possible tp play HEVC 1080p on a raspberry pi2 with this builds?

I overclocked my pi2 but it plays about couple of minutes and the my pi2 locked up.

It might be overheating. If you could kindly provide a little more information on your overclock settings, what case or heat sink you are using and the bit rate of the HEVC film you were trying to watch. Then I am sure some of the more experienced members of this forum would be able to assist you.

Thank you for response.

I´m trying to play a 8 bit hevc file with these overclock settings

Code:

gpu_mem_1024=256
arm_freq=1075
core_freq=530
sdram_freq=600
sdram_schmoo=0x02000020
dtoverlay=sdhost,overclock_50=100
gpu_freq=510
over_voltage_sdram=6
over_voltage=8
force_turbo=1

And i´m using this case

[Milhouse]

I´m trying to play a 8 bit hevc file with these overclock settings

Code:

gpu_mem_1024=256
arm_freq=1075
core_freq=530
sdram_freq=600
sdram_schmoo=0x02000020
dtoverlay=sdhost,overclock_50=100
gpu_freq=510
over_voltage_sdram=6
over_voltage=8
force_turbo=1

Have you confirmed your overclock is 100% stable? Judging from the crashes, it probably isn't.

I also don't think you need core_freq AND gpu_freq - gpu_freq will configure the core_freq.

You can use "bcmstat.sh xgpd1" (built-in to these builds, and needs a wide ssh console window!) to monitor temperature, core frequencies and cpu load in real time. This will also confirm what ARM/Core/H264/SDRAM frequencies are being successfully configured from config.txt.

If your temperature is not excessive - the RPi2 CPU will begin to throttle at 80C and cap the ARM frequency at 85C - then it's unlikely to be a temperature issue. Rather, you simply didn't win in the silicon lottery and need to wind back your overclock.

Note that bcmstat.sh will report under-voltage, frequency cap and throttle events in the U, F and T columns. A lower-case value (eg. "u") indicates an event has occurred one or more times in the past since the system booted, while an uppercase value (eg. "U") means the event is ongoing (ie. happening right now). A blank value in the U/F/T columns indicates no event has so far occurred since the system booted.

[Pienoet]

I´m trying to play a 8 bit hevc file with these overclock settings

Code:

gpu_mem_1024=256
arm_freq=1075
core_freq=530
sdram_freq=600
sdram_schmoo=0x02000020
dtoverlay=sdhost,overclock_50=100
gpu_freq=510
over_voltage_sdram=6
over_voltage=8
force_turbo=1

Have you confirmed your overclock is 100% stable? Judging from the crashes, it probably isn't.

I also don't think you need core_freq AND gpu_freq - gpu_freq will configure the core_freq.

You can use "bcmstat.sh xgpd1" (built-in to these builds, and needs a wide ssh console window!) to monitor temperature, core frequencies and cpu load in real time. This will also confirm what ARM/Core/H264/SDRAM frequencies are being successfully configured from config.txt.

If your temperature is not excessive - the RPi2 CPU will begin to throttle at 80C and cap the ARM frequency at 85C - then it's unlikely to be a temperature issue. Rather, you simply didn't win in the silicon lottery and need to wind back your overclock.

Note that bcmstat.sh will report under-voltage, frequency cap and throttle events in the U, F and T columns. A lower-case value (eg. "u") indicates an event has occurred one or more times in the past since the system booted, while an uppercase value (eg. "U") means the event is ongoing (ie. happening right now). A blank value in the U/F/T columns indicates no event has so far occurred since the system booted.

Thank you for this great info.

I will remove core_freq and gpu_freq form my settings.
I allready reduce the arm_freq to from 1100 to 1075 and set the sdram_freq to 600 and it´s much better now.

The temperature is good it wasn't getting higher then 66 celsius while playing a 8-bit HEVC file.

I will try bcmstat to monitor the core frequencies and cpu load etc.

Thanks again for info!

[polo_joe]

Does overclocking sdcard not work anymore? I get some errors in dmesg.

[ 1.712859] mmc0: read transfer error - HSTS 20
[ 1.712868] mmc0: reducing overclock due to errors
[ 1.712878] mmc0: req failed (CMD17): -110, retrying...
[ 1.712919] mmc0: overclocking to 83333333Hz
[ 1.714277] mmc0: read transfer error - HSTS 20
[ 1.714283] mmc0: reducing overclock due to errors
[ 1.714291] mmc0: req failed (CMD17): -110, retrying...
[ 1.714318] mmc0: overclocking to 71428571Hz
[ 1.719725] mmc0: read transfer error - HSTS 20
[ 1.719730] mmc0: reducing overclock due to errors
[ 1.719738] mmc0: req failed (CMD17): -110, retrying...
[ 1.719766] mmc0: overclocking to 62500000Hz

http://sprunge.us/AHcJ

[popcornmix]

Is it possible tp play HEVC 1080p on a raspberry pi2 with this builds?

I overclocked my pi2 but it plays about couple of minutes and the my pi2 locked up.

I would say you really need a pi3 to play 1080p HEVC.
The arm has double width NEON compared to Pi2, as well as being clocked faster.
It does make a noticeable difference.

[Pienoet]

Is it possible tp play HEVC 1080p on a raspberry pi2 with this builds?

I overclocked my pi2 but it plays about couple of minutes and the my pi2 locked up.

I would say you really need a pi3 to play 1080p HEVC.
The arm has double width NEON compared to Pi2, as well as being clocked faster.
It does make a noticeable difference.

Thank you popcornmix i will buy a pi3 then.

Does a pi3 need to overclock to play HEVC 1080p and 720p netflix?

[popcornmix]

Does a pi3 need to overclock to play HEVC 1080p and 720p netflix?

Netflix doesn't provide HEVC. It uses an external software decoder (H.264). Pi3 can play 720p without overclock. 1080p is too much for that decoder.

I've had no trouble with 1080p 8-bit HEVC on a Pi3 with no overclock.
Overclocking can help with 10-bit content.
It can help with high bitrate stuff (although I've only found test files that require this - normal encodes aren't generally high enough bitrate to cause an issue).

[popcornmix]

Does overclocking sdcard not work anymore? I get some errors in dmesg.

I've still overclocking (dtoverlay=sdtweak,overclock_50=83) without problems or errors in dmesg log.
I don't believe anything has changed here.

[polo_joe]

Does overclocking sdcard not work anymore? I get some errors in dmesg.

I've still overclocking (dtoverlay=sdtweak,overclock_50=83) without problems or errors in dmesg log.
I don't believe anything has changed here.

Is something wrong with my config.txt?
http://sprunge.us/XhSJ

Edit: After power cycle all back to normal.

[J_E_F_F]

I've still overclocking (dtoverlay=sdtweak,overclock_50=83) without problems or errors in dmesg log.
I don't believe anything has changed here.

Is there a preferred method, for this? I use dtparam=sd_overclock=83 on my RPi3 should that be changed to the dtoverlay method you posted?

[4ch3los]

Hey Friends,
am i the only person having trouble with the onboard Bluetooth chip of the rpi3?

After turning it on in the libreelec settings, it says: "No Bluetooth adapter found."

[popcornmix]

Is there a preferred method, for this? I use dtparam=sd_overclock=83 on my RPi3 should that be changed to the dtoverlay method you posted?

I believe sdtweak is the recommended way of specifying it.
Otherwise you may stop wifi from working.

[Sholander]

Thank you for this great info.

I will remove core_freq and gpu_freq form my settings.

I don't think that is what @Milhouse meant when he wrote:

"I also don't think you need core_freq AND gpu_freq - gpu_freq will configure the core_freq."

I think that you should keep "gpu_freq" and remove only "core_freq".

[Pienoet]

Does a pi3 need to overclock to play HEVC 1080p and 720p netflix?

Netflix doesn't provide HEVC. It uses an external software decoder (H.264). Pi3 can play 720p without overclock. 1080p is too much for that decoder.

I've had no trouble with 1080p 8-bit HEVC on a Pi3 with no overclock.
Overclocking can help with 10-bit content.
It can help with high bitrate stuff (although I've only found test files that require this - normal encodes aren't generally high enough bitrate to cause an issue).

Thanks!