•   
  • 1
  • 288
  • 289
  • 290(current)
  • 291
  • 292
  • 355
  •   
  Thread Closed
v18 LibreELEC Testbuilds for x86_64 (Kodi 18.0)
(2018-08-22, 19:44)lwrcase Wrote: just updated to #0821 and it has video stuttering issues again. i tried to apply the i915_min_freq fix but it gave me a permission denied error.


Livingroom:~ # echo 756 > /sys/kernel/debug/dri/0/i915_min_freq
-sh: can't create /sys/kernel/debug/dri/0/i915_min_freq: Permission denied
 FYI; I'm also seeing the same thing on my Apollo Lake nuc6 upon upgrading to the latest 9/14/18 build (I'd been running 708b prior, but still had i915_min_freq forced to max...).

What I'm finding, is that when *not* using refresh rate switching, upon keeping an eye on the Current freq, when it drops below 200, I get visual stutter
Code:
# watch cat /sys/kernel/debug/dri/0/i915_frequency_info |grep 'Current freq'
...
Current freq: 267 MHz
Current freq: 283 MHz
Current freq: 233 MHz
Current freq: 250 MHz
Current freq: 250 MHz
Current freq: 250 MHz
Current freq: 217 MHz
Current freq: 233 MHz
Current freq: 217 MHz
Current freq: 217 MHz
Current freq: 217 MHz
Current freq: 217 MHz
Current freq: 167 MHz
Current freq: 217 MHz
Current freq: 217 MHz
Current freq: 150 MHz
Current freq: 250 MHz
...

Here's a debug log http://ix.io/1mLh when refresh rate switching is turned off, however the issue doesn't seem to occur as frequently when debug is turned on, due to what I suspect is the additional frequency boost needed to drive the debug OSD...

When I have refresh rate switching turned on, the current freq rarely exceeds 117 and the video doesn't noticeably stutter (but I rarely have refresh rate switching turned on):
Code:
# watch cat /sys/kernel/debug/dri/0/i915_frequency_info |grep 'Current freq'
...
Current freq: 117 MHz
Current freq: 117 MHz
Current freq: 117 MHz
Current freq: 100 MHz
Current freq: 100 MHz
Current freq: 100 MHz
Current freq: 100 MHz
Current freq: 100 MHz
Current freq: 100 MHz
Current freq: 100 MHz
Current freq: 117 MHz
Current freq: 100 MHz
Current freq: 117 MHz
Current freq: 100 MHz
Current freq: 117 MHz
Current freq: 117 MHz
Current freq: 117 MHz
Current freq: 100 MHz
Current freq: 100 MHz
...
 
Code:
# cat /sys/kernel/debug/dri/0/i915_frequency_info
Video Turbo Mode: yes
HW control enabled: yes
SW control enabled: no
PM IER=0x00000000 IMR=0xffffffff ISR=0x00000000 IIR=0x00000000, MASK=0x00003ffe
pm_intrmsk_mbz: 0x80000000
GT_PERF_STATUS: 0x00000000
Render p-state ratio: 0
Render p-state VID: 0
Render p-state limit: 0
RPSTAT1: 0x03000000
RPMODECTL: 0x00000d92
RPINCLIMIT: 0x00004740
RPDECLIMIT: 0x00007f80
RPNSWREQ: 100MHz
CAGF: 100MHz
RP CUR UP EI: 174 (145us)
RP CUR UP: 176 (146us)
RP PREV UP: 0 (0us)
Up threshold: 95%
RP CUR DOWN EI: 181 (150us)
RP CUR DOWN: 183 (152us)
RP PREV DOWN: 0 (0us)
Down threshold: 85%
Lowest (RPN) frequency: 100MHz
Nominal (RP1) frequency: 250MHz
Max non-overclocked (RP0) frequency: 750MHz
Max overclocked frequency: 750MHz
Current freq: 100 MHz
Actual freq: 100 MHz
Idle freq: 100 MHz
Min freq: 100 MHz
Boost freq: 750 MHz
Max freq: 750 MHz
efficient (RPe) frequency: 250 MHz
Current CD clock frequency: 288000 kHz
Max CD clock frequency: 624000 kHz
Max pixel clock frequency: 624000 kHz
I "Adjust Refreshrate is enabled" the video switches to e.g. 24 hz and therefore mainloop is only rendered 24 times a second. While when staying at 60 it needs to do it 60 times a second -> what you see is that using "Adjust Refreshrate" saves power as the GPU can be clocked lower.

But: As you see such low frequencies, you see that setting the min_freq did not work for you. That's quite clear from the log, your max is 750 - so 756 won't work for sure.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2018-09-15, 17:59)fritsch Wrote: I "Adjust Refreshrate is enabled" the video switches to e.g. 24 hz and therefore mainloop is only rendered 24 times a second. While when staying at 60 it needs to do it 60 times a second -> what you see is that using "Adjust Refreshrate" saves power as the GPU can be clocked lower.

But: As you see such low frequencies, you see that setting the min_freq did not work for you. That's quite clear from the log, your max is 750 - so 756 won't work for sure.
 Good day fritsch; as lwrcase mentioned, we don't seem to be able to set i915_min_freq with the new kernel version; attempting to do so (with any value) results in Permission denied.
Quote:[email protected]:/sys/devices/pci0000:00/0000:00:02.0/drm/card0# cat gt_min_freq_mhz 
100
[email protected]:/sys/devices/pci0000:00/0000:00:02.0/drm/card0# echo 400 > gt_min_freq_mhz 
[email protected]:/sys/devices/pci0000:00/0000:00:02.0/drm/card0# cat gt_min_freq_mhz 
400

Still works for me on 4.19-rc3 drm-tip
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
(2018-09-15, 18:29)fritsch Wrote:
Quote:[email protected]:/sys/devices/pci0000:00/0000:00:02.0/drm/card0# cat gt_min_freq_mhz 
100
[email protected]:/sys/devices/pci0000:00/0000:00:02.0/drm/card0# echo 400 > gt_min_freq_mhz 
[email protected]:/sys/devices/pci0000:00/0000:00:02.0/drm/card0# cat gt_min_freq_mhz 
400

Still works for me on 4.19-rc3 drm-tip 
  
@fritsch; Oh, thank you! That does indeed work for me.
New LibreELEC.tv Leia build #0915: Generic
(Supercedes previous build)

SHA256 Checksum: 06b03c4f78ef13f159d4d1b6895d99642aa785ed59deab2e38059e4d4ff2d033 (Generic)

# uname -a
Linux NUC 4.18.8 #1 SMP Sat Sep 15 21:11:20 BST 2018 x86_64 GNU/Linux

# lsb_release
LibreELEC (Milhouse): devel-20180915210304-#0915-g56eae68 [Build #0915]

# Kodi version
(18.0-BETA3 Git:fa47fc3). Platform: Linux x86 64-bit

Based on tip of LibreELEC.tv master (56eae68, changelog) and tip of XBMC master (fa47fc3, changelog) with the following modifications: Build Highlights:
  1. New 4.18.8 kernel (with LSPCON timeout and DP colour range fixes)

    drm/i915: set DP Main Stream Attribute for color range on DDI platforms

    commit 6209c285e7a5e68dbcdf8fd2456c6dd68433806b upstream.

    Since Haswell we have no color range indication either in the pipe or
    port registers for DP. Instead, there's a separate register for setting
    the DP Main Stream Attributes (MSA) directly. The MSA register
    definition makes no references to colorimetry, just a vague reference to
    the DP spec. The connection to the color range was lost.

    Apparently we've failed to set the proper MSA bit for limited, or CEA,
    range ever since the first DDI platforms. We've started setting other
    MSA parameters since commit dae847991a43 ("drm/i915: add
    intel_ddi_set_pipe_settings").

    Without the crucial bit of information, the DP sink has no way of
    knowing the source is actually transmitting limited range RGB, leading
    to "washed out" colors. With the colorimetry information, compliant
    sinks should be able to handle the limited range properly. Native
    (i.e. non-LSPCON) HDMI was not affected because we do pass the color
    range via AVI infoframes.

    Though not the root cause, the problem was made worse for DDI platforms
    with commit 55bc60db5988 ("drm/i915: Add "Automatic" mode for the
    "Broadcast RGB" property"), which selects limited range RGB
    automatically based on the mode, as per the DP, HDMI and CEA specs.

    After all these years, the fix boils down to flipping one bit.

    [Per testing reports, this fixes DP sinks, but not the LSPCON. My
    educated guess is that the LSPCON fails to turn the CEA range MSA into
    AVI infoframes for HDMI.]
  2. curl: update to curl-7.61.1 with latest CA cert bundle
Build Details:
  1. XBMC:
    • [ios] - use libdvdcss (PR:14411, 2 commits, 4 files changed)
  2. libnfs:
    • Implement O_EXCL for NFSv4 (9454d9f)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Updated: [env] PR:2908 (perma): linux (Generic): update to linux-4.18.7
    • Added: [env] PR:2976 (perma): curl: update to curl-7.61.1
    • Updated: [pkg] PR:14341 (perma): input: libinput: add setting to allow changing keymap layout
    • Added: [pkg] PR:14422 (perma): Use Linux Sysfs SoC interface for SystemInfo and CPUInfo
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.
New LibreELEC.tv Leia build #0916: Generic
(Supercedes previous build)

SHA256 Checksum: c2cd4978e9327cda98318403b9396d8a9f483c2203dad54e48d372569052e606 (Generic)

# uname -a
Linux NUC 4.18.8 #1 SMP Sun Sep 16 21:04:31 BST 2018 x86_64 GNU/Linux

# lsb_release
LibreELEC (Milhouse): devel-20180916210256-#0916-g56eae68 [Build #0916]

# Kodi version
(18.0-BETA3 Git:f7be5a2). Platform: Linux x86 64-bit

Based on tip of LibreELEC.tv master (56eae68, changelog) and tip of XBMC master (f7be5a2, changelog) with the following modifications: Build Highlights:
  1. [keymaps] Map key 'numpad period' to action 'channel number separator'.
Build Details:
  1. XBMC:
    • [CURL] Update to version 7.61.1 (PR:14435, 2 commits, 3 files changed)
    • [guiinfo] Fix Listitem.DBType not working for music videos. (PR:14439, 1 commit, 3 files changed)
    • [keymaps] Map key 'numpad period' to action 'channel number separator'. (PR:14441, 1 commit, 1 file changed)
    • [cleanup] yuv2rgb.neon isn't used since #9719 (PR:14440, 1 commit, 4 files changed)
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.
Hello @Milhouse,

As it is written in the readme, I have created a ticket here: https://forum.libreelec.tv/thread/13229-...004-no-ui/
Do you want to continue the conversation there or do you prefer it here?

Thank you for your work and for reading me.
@Milhouse Anything between  #0915 and #0910 that could cause Grid skin to stop updated watched status icona and cause delay in loading TV show or Movie sections? As in screen goes blank for 30 secs.
I see the same problem as above. @fritsch this is what was happening to me randomly. It appears that any overlay will cause a frequency increase and it doesn't reoccur until the frequency goes down again.

I've had 400 set for 1 week now and everything is ok. This value also fixes this for Amazon/Netflix Plugin. Glad to have found what it was.

Running a NUC7PJYH.
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Weekly Linux 4.19-rc4 build #0916x: Generic

Packages disabled/not included:

DVB Driver Addons (CrazyCat incompatible with 4.19-rc)
Known issues:

RTL8188EU, RTL8192CU/DU/EU, RTL8812AU: driver changes untested
xf86-video-nvidia: driver changes untested
r8169 (Revo 3700/Atom) network interface negotiates 10Mbps/half duplex when resuming from suspend
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.
(2018-09-16, 23:30)Nekromantik Wrote: @Milhouse Anything between  #0915 and #0910 that could cause Grid skin to stop updated watched status icona and cause delay in loading TV show or Movie sections? As in screen goes blank for 30 secs.

Your guess is as good as mine, or maybe ask the third-party skin maintainer.
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.
(2018-09-16, 23:24)sk4hrr Wrote: Hello @Milhouse,

As it is written in the readme, I have created a ticket here: https://forum.libreelec.tv/thread/13229-...004-no-ui/
Do you want to continue the conversation there or do you prefer it here?

Thank you for your work and for reading me.

I guess here for now. Can you upload your latest logfile zip (from the Samba Logfiles folder) while booted with latest #0916, and paste the download link.

If you have two GPUs installed in your system (the integrated GPU and RX550) then chances are there's the risk of some confusion.
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.
Will the pixel shader improvements with OpenGL 4.0 be implemented in LE9? I currently have a mesa override in system.d.
My XBMC / Kodi history.
XBMC for XBOX -> XBMC for Windows -> XBMC for Android -> Kodi for Android - > Kodi v16 OE (Amlogic, spare) -> Kodi v17 LE (NUC, main)
Thank you for your answer.
I do have two GPUs, the A6 and the RX550, and when the HDMI is connected to the A6, kodi starts correctly. If the HDMI is connected to the RX550, kodi does not start.

My debug logs: https://send.firefox.com/download/106e1d...AeG8NJ4l-w
  •   
  • 1
  • 288
  • 289
  • 290(current)
  • 291
  • 292
  • 355
  •   
  Thread Closed
 
Thread Rating:
  • 24 Vote(s) - 4.5 Average



Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for x86_64 (Kodi 18.0)4.524