Login at Kodi Home

**wsnipex** · 2021-05-31, 07:34

(2021-05-30, 14:17)graysky Wrote:
(2021-05-30, 14:15)deadite66 Wrote: i just cloned https://aur.archlinux.org/kodi-git.git then ran makepkg -s

Right, but just like the official PKGBUILD, this will build all three targets, gbm, wayland, and x11. I am asking which one fails for you.

Code:
... echo "building kodi-wayland" cmake "${_args[@]}" -DCORE_PLATFORM_NAME=wayland ../"$_gitname" make echo "building kodi-gbm" cmake "${_args[@]}" -DCORE_PLATFORM_NAME=gbm ../"$_gitname" make # build x11 version last that will make it fallback in the launcher script echo "building kodi-x11" cmake "${_args[@]}" -DCORE_PLATFORM_NAME=x11 ../"$_gitname" make

out of interest: why are you building 3 times, when you can have X11, Wayland, GBM in a single binary? The overhead in the binary is minimal, compared to building 3 times

**deadite66** · 2021-05-31, 08:29

Posted our findings on the kodi github issue, thanks for your help graysky.

**a1rwulf** · 2021-05-31, 08:48

I think the problem is:

cpp:
CVaapi2Texture::Map", "DRM-exported layer has %d planes - only 1 supported

However on my 11th gen system, I don't see this issue.
If I'm not mistaken you have libva 1.11 while I have libva 1.12, might be an idea to update that as well.

**deadite66** · 2021-05-31, 09:28

kodi.log with libva 1.12
https://paste.kodi.tv/zahulakuta.kodi

still get a black screen.

**a1rwulf** · 2021-05-31, 09:56

I'll download the sample and try on my setup

**a1rwulf** · 2021-05-31, 10:05

Works fine for me.
I have following in my log: driver in use: Intel iHD driver for Intel® Gen Graphics - 21.2.0 (3312e66b).
I'm only guessing around, but maybe you can compile the same commit and verify.

graysky · (This post was last modified: 2021-05-31, 13:22 by graysky.)

(2021-05-31, 07:34)wsnipex Wrote:
(2021-05-30, 14:17)graysky Wrote:
(2021-05-30, 14:15)deadite66 Wrote: i just cloned https://aur.archlinux.org/kodi-git.git then ran makepkg -s

Right, but just like the official PKGBUILD, this will build all three targets, gbm, wayland, and x11. I am asking which one fails for you.

Code:
... echo "building kodi-wayland" cmake "${_args[@]}" -DCORE_PLATFORM_NAME=wayland ../"$_gitname" make echo "building kodi-gbm" cmake "${_args[@]}" -DCORE_PLATFORM_NAME=gbm ../"$_gitname" make # build x11 version last that will make it fallback in the launcher script echo "building kodi-x11" cmake "${_args[@]}" -DCORE_PLATFORM_NAME=x11 ../"$_gitname" make

out of interest: why are you building 3 times, when you can have X11, Wayland, GBM in a single binary? The overhead in the binary is minimal, compared to building 3 times

Following the official Arch Linux PKGBUILD which does this. I think it is to maintain a minimal set of depends since each one is its own package.

**deadite66** · (This post was last modified: 2021-05-31, 13:21 by deadite66.)

tried installing intel-media-driver-21.2.1 and intel-gmmlib-21.1.3 from Community-Staging with a black screen still.

have a feeling this is going to be a slow burn issue until more people have rocket lake and trying to run kodi on linux and run into problems.

graysky · (This post was last modified: 2021-05-31, 13:43 by graysky.)

(2021-05-31, 09:28)deadite66 Wrote: kodi.log with libva 1.12
https://paste.kodi.tv/zahulakuta.kodi

still get a black screen.

@deadite66 - Which package did you update to get VA-API version 1.12.0?

**deadite66** · 2021-05-31, 13:45

libva-git from aur

**a1rwulf** · 2021-05-31, 15:04

(2021-05-31, 13:21)deadite66 Wrote: tried installing intel-media-driver-21.2.1 and intel-gmmlib-21.1.3 from Community-Staging with a black screen still.

have a feeling this is going to be a slow burn issue until more people have rocket lake and trying to run kodi on linux and run into problems.

Yeah I'm not sure tbh.
I'm on a slightly older kernel, not sure if there has been a "regression" or new feature which requires changes on our side.
The thing is that the Intel media-driver and the kernel have had a few issues here and there on the new hardware (maybe still have issues) and to me it seems
stuff is still a bit experimental.

**deadite66** · 2021-06-06, 11:55

Tried playing various test files to try and find a pattern, still none the wiser.
all files played with "prefer VAAPI render method" turned off, else black screen on all files.

Working:
BigBuckBunny_2000h264.mp4 https://paste.kodi.tv/uloyojejox
BigBuckBunny_2000hevc.mp4 https://paste.kodi.tv/dosolezipa
bird90.mkv https://paste.kodi.tv/qumicafoqe
FPS_test_1080p23.976_L4.1.mkv https://paste.kodi.tv/usekugerog
jellyfish-40-mbps-hd-h264.mkv https://paste.kodi.tv/bineqevaja
jellyfish-40-mbps-hd-hevc.mkv https://paste.kodi.tv/gibolaqepu

Not (black screen) Working:
jellyfish-40-mbps-hd-hevc-10bit.mkv https://paste.kodi.tv/uvewosaxet
lg-uhd-paris-www.demolandia.net_.mkv https://paste.kodi.tv/fizoyusare

**a1rwulf** · 2021-06-08, 21:11

thanks for testing and reporing @deadite66.
Currently I'm quite busy with life, in order to get any further I'll need to add code for more verbose logging of the vaapi surfaces.
Will you be able to build such code yourself and test?
I'll probably manage to do so, somewhen next week or the week after.

**deadite66** · 2021-06-08, 21:25

i can make attempt at compiling and test it.

bkuhls · 2021-06-08, 21:34

(2021-06-08, 21:11)a1rwulf Wrote: Will you be able to build such code yourself and test?

If you tell me what to do I can help as well, CPU is a i9-11900t.
Here playback of PVR channels encoded in h264 shows only black screen, SD channels work.