•   
  • 1
  • 177
  • 178
  • 179(current)
  • 180
  • 181
  • 304
  •   
v18 -  LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)
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: 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
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2017-07-29, 22:37)Double L Wrote:
(2017-07-29, 20:27)Pienoet Wrote: 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
rpi3 | LE9 Leia | Milhouse Testbuilds
2x odroid C2 | LE8.xx Krypton | LE9 Leia | Raybuntu's Community Build.
odroid XU4 | ubuntu-16.04.2-minimal-odroid-xu4
odroid XU4Q | ubuntu-16.04.0-minimal-odroid-xu4 | TVheadendserver
Reply
(2017-07-30, 00:20)Pienoet Wrote: 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.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2017-07-30, 00:59)Milhouse Wrote:
(2017-07-30, 00:20)Pienoet Wrote: 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!
rpi3 | LE9 Leia | Milhouse Testbuilds
2x odroid C2 | LE8.xx Krypton | LE9 Leia | Raybuntu's Community Build.
odroid XU4 | ubuntu-16.04.2-minimal-odroid-xu4
odroid XU4Q | ubuntu-16.04.0-minimal-odroid-xu4 | TVheadendserver
Reply
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
Reply
(2017-07-29, 20:27)Pienoet Wrote: 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.
Reply
(2017-07-30, 11:27)popcornmix Wrote:
(2017-07-29, 20:27)Pienoet Wrote: 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?
rpi3 | LE9 Leia | Milhouse Testbuilds
2x odroid C2 | LE8.xx Krypton | LE9 Leia | Raybuntu's Community Build.
odroid XU4 | ubuntu-16.04.2-minimal-odroid-xu4
odroid XU4Q | ubuntu-16.04.0-minimal-odroid-xu4 | TVheadendserver
Reply
(2017-07-30, 11:40)Pienoet Wrote: 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).
Reply
(2017-07-30, 09:42)polo_joe Wrote: 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.
Reply
(2017-07-30, 13:54)popcornmix Wrote:
(2017-07-30, 09:42)polo_joe Wrote: 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.
Reply
(2017-07-30, 13:54)popcornmix Wrote: 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?
Reply
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."
Reply
(2017-07-30, 16:00)J_E_F_F Wrote: 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.
Reply
(2017-07-30, 01:22)Pienoet Wrote: 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".
Reply
(2017-07-30, 13:52)popcornmix Wrote:
(2017-07-30, 11:40)Pienoet Wrote: 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!
rpi3 | LE9 Leia | Milhouse Testbuilds
2x odroid C2 | LE8.xx Krypton | LE9 Leia | Raybuntu's Community Build.
odroid XU4 | ubuntu-16.04.2-minimal-odroid-xu4
odroid XU4Q | ubuntu-16.04.0-minimal-odroid-xu4 | TVheadendserver
Reply
  •   
  • 1
  • 177
  • 178
  • 179(current)
  • 180
  • 181
  • 304
  •   
 
Thread Rating:
  • 12 Vote(s) - 4.67 Average



Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)4.6712