Posts by mglae

Quote from matthuo

Besides, why did you say it was your fault?

I had the impression the issue only reported foor recent kernels. But it exist in kernel 4.19 too and therefore in LE 9.2.6.

This is a RPI4 kernel issue: LE10 rpi4-4gb oom errors / USB3 disk writes trigger OOM reaper on Pi 4 · Issue #3210 · raspberrypi/linux · GitHub

Edit: My fault., the issue seems only be reported for recent kernels like in LE 9.95 - not in your 9.2.6

Edit 2: Does exist in kernel 4.19/LE 9.2.6 too.

Things happen. The fix missed 9.2.6. Testing LibreELEC-settings addon · Issue #4547 · LibreELEC/LibreELEC.tv · GitHub is the only possibility to have it in 9.2

See https://wiki.libreelec.tv/configuration/startup-shutdown

There is already a 9.95.1 fix to start service addons after installation: Revert "kodi: service addon wrapper call fix" by HiassofT · Pull Request #5251 · LibreELEC/LibreELEC.tv · GitHub.

In the meantime disable and enable again the service from the addon settings.

In addition use an URL like https://gitlab.freedesktop.org/mesa/mesa/-/archive/master/mesa-<commit id>.tar.gz to get reproducible results.

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.

The error is in the nvidia detection rules. You can disable them with:

touch /storage/.config/udev.rules.d/96-nvidia.rules

Do you see the wrong dates only on empty directories?

OK. Thanks for the test marathon. BTW: what is the result of vainfo on the failing system

The error is on:

2021-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:

2021-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.

Quote from DDuck007

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.

Quote from DDuck007

A general question: Does AMD_GPU work with VDPAU-Decoder at all?

You have to configure it. Create:

KODI_GL_INTERFACE=GLX

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.

Quote from HiassofT

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