In addition use an URL like https://gitlab.freedesktop.org/mesa/mesa/-/archive/master/mesa-<commit id>.tar.gz to get reproducible results.
Posts by mglae
-
-
bjohv052 Please try the test version of LibreELEC-settings: Testing LibreELEC-settings addon · Issue #4547 · LibreELEC/LibreELEC.tv · GitHub
-
So VAAPI is available but the EGL interop test in Kodi fail. Unfortunately I have no idea what is the conclusion is.
-
-
-
OK. Thanks for the test marathon. BTW: what is the result of vainfo on the failing system
The error is on:
Code2021-03-28 18:26:37.280 T:1070 DEBUG <general>: Vaapi2 EGL interop test results: general no, deepColor no
"general" and "deepColor" should be "yes".
There seem to be no bug report yet on Mesa GitLab.
-
Unfortunately your debug log starts after the interesting part:
Code2021-03-28 13:18:24.577 T:1048 INFO <general>: VDPAU::CreateContext - creating decoder context[...] 2021-03-28 13:18:56.979 T:1048 INFO <general>: Enabled debug logging due to GUI setting. Level 2.
radeon.cik_support=0 amdgpu.cik_support=1 brings back the VAAPI and simply works.
Which LE version did you use before yesterday?
There was both a Mesa and a kernel update yesterday. With the amdgpu driver still working and having used a recent LE version you can start to revert the kernel update first.
A general question: Does AMD_GPU work with VDPAU-Decoder at all?
You have to configure it. Create:
and restart kodi.
-
Complete debug log via pastekodi please.
A Polaris12 GPU using the amdgpu driver is working with the nightly. As a test you can enable the amdgou driver on your Kabini GPU with radeon.cik_support=0 amdgpu.cik_support=1 kernel parameters (CIK = Sea Islands GPUs)
For the records: Southern Islands (SI) GPUs can be enabled with radeon.si_support=0 amdgpu.si_support=1 and both parameter pairs can be combined.
-
FYI: that doesn't work too well if display is set to 4k (which is default after plain install without changing settings)
There is a post 19.0 PR fixing the default whitelist that may help (there is more fixed than the title suggest): Resolution: Try double refreshrate and pulldown also when no whitelist is set by fritsch · Pull Request #19382 · xbmc/xbmc · GitHub
-
Setting export KODI_GL_INTERFACE=GLX allows using VDPAU on AMD, but there is no reason to do this today.
Start a clean build (erase the build directory) if you did an incremental build before.
-
You are right, kodi should use "MemAvaiable:" (when available on kernel >= 3.2).
-
There is a pending stuttering fix for kodi on X11: WinSystemXLGL: Properly return msecs for GetVblankTiming by fritsch · Pull Request #19448 · xbmc/xbmc · GitHub
-
You can see the raw kernel values with cat /proc/meminfo
-
Temporary use kodi + vnsi on a working platform.
-
-
- Make a backup via LibreELEC-Settings and save it outside of the HTPC.
- Replace the KERNEL and SYSTEM files with the new ones from Ubuntu or Windows.
- Boot LE with fingers crossed.
PS: there is neither LE 18 nor LE 19
-
CvH You find a equivalent journalctl URL in post 1
-
No real idea. You can try to replace "quiet" with "debug" in syslinux.cfg.