Rocket Lake (RKL) discussion
#61
After reading a bit more, seems both use Intel XE GPUs so they should be somewhat similar, but maybe the difference is significant enough that the media-driver needs specific changes.
Who knows...
Reply
#62
(2021-05-31, 10:05)a1rwulf Wrote: 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.
Which configure options did you use for mediadriver?
Similar ones to LibreELEC or did you disable some full-feature options by not using -DENABLE_NONFREE_KERNELS=ON -DBUILD_KERNELS=ON?
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Reply
#63
(2021-04-20, 08:08)deadite66 Wrote: but it does work via mpv --hwdec=vaapi
Same here, mpv works
Quote:Using hardware decoding (vaapi-copy).
AO: [alsa] 48000Hz stereo 2ch s16
VO: [gpu] 1920x1080 nv12
and mpv also uses VA_EXPORT_SURFACE_SEPARATE_LAYERS
https://github.com/mpv-player/mpv/blob/m...api.c#L240
like Kodi does:
https://github.com/xbmc/xbmc/blob/master...L.cpp#L453

But instead of relying on only one plane as Kodi does:
https://github.com/xbmc/xbmc/blob/master...L.cpp#L486

mpv can handle up to four planes:
https://github.com/mpv-player/mpv/blob/m..._gl.c#L156

If I miscompared the code of Kodi and mpv, sorry, but I have no idea what this
all means, nor do I have any idea about the details of video decoding. I just would
like to have a working system using a current rocketlake cpu Wink
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Reply
#64
to add to that running intel_gpu_top shows if the gpu decoding is being used, Video and VideoEnhance should be more than 0%
mpv --hwdec=vaapi-copy may be necessary rather than just hwdec=vaapi.
Intel Core i5-11500, ASRock B560M-ITX/ac, 240GB SSD + 4TB  Western Digital Blue, Arch Linux, mythtv 31+fixes + TBS 6205 QUAD FREEVIEW DVB-T2
Reply
#65
Some more details, but no fix. The code which creates 2 planes is in media-driver:
https://github.com/intel/media-driver/bl....cpp#L7055

I verified it by changing https://github.com/intel/media-driver/bl....cpp#L7048
to "if (!mediaCtx->m_auxTableMgr)": the logline in Kodi "DRM-exported layer has 2 planes - only 1 supported"
disappeared, the image stayed green however.

The aux plane stuff (I have no idea what I am talking about, just reading code Wink ) was added with
https://github.com/intel/media-driver/co...0c8246ad52

This commit mentions "GEN12_MC_CCS" which apparently means a new feature of the gen12 iGPU:

https://www.phoronix.com/scan.php?page=n...-Mesa-19.3

https://git.kernel.org/pub/scm/linux/ker...5af15525b4
"drm/i915/tgl: Gen-12 render decompression"

https://gitlab.freedesktop.org/mesa/mesa...uests/2302
"Add MCS_CCS (MCS_LCE) compression support for Gen12"

This new hardware feature seems to be the reason why the bug only occurs on 11th gen i5/i7/i9.

How to force the graphic stack to return just one plane to Kodi is a question I could not find an
answer for but we should look into this gen12-specific stuff.
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Reply
#66
(2021-06-17, 10:44)a1rwulf Wrote: Yeah in that case I think it makes sense that you open an issue on the media-driver github and ask about
the state of rocketlake support.
Done: https://github.com/intel/media-driver/issues/1210
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Reply
#67
Following the discussion on my media-driver issue I found this when enabling more logs in Kodi:
Quote:DEBUG <general>: CDRMUtils::DrmFbGetFromBo - using modifier: 0x100000000000002
This drm modifier translates to I915_FORMAT_MOD_Y_TILED:
https://git.kernel.org/pub/scm/linux/ker...rcc.h#n469

As I have no idea and absolutely no experience in coding this video stuff I would like to ask if it is possible
that Kodi can disable this modifier? It seems that in the past Kodi did already modify the drm modifiers:
https://github.com/xbmc/xbmc/commit/88d4...dce811L433
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Reply
#68
seemed like we had a flurry of activity on the intel/media-driver issue then it dried up, the tech talk went over my head.

so is it an intel issue or kodi, anyone get the gist of it?
Intel Core i5-11500, ASRock B560M-ITX/ac, 240GB SSD + 4TB  Western Digital Blue, Arch Linux, mythtv 31+fixes + TBS 6205 QUAD FREEVIEW DVB-T2
Reply
#69
I tried to force DRM_FORMAT_MOD_LINEAR in the hope that only one plane per layer will be created, but failed.

@FernetMenta @fritsch: can you help?
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Reply
#70
Not using kodi on intel anymore since several years. The DRM import won't solve your problem though - the shaders behind it, have a similar expectation. I don't see the reason intel should do a "special case" for this machine - rendering it incompatible to all standard software ... and needing workarounds everywhere.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#71
(2021-06-27, 19:41)fritsch Wrote: I don't see the reason intel should do a "special case" for this machine - rendering it incompatible to all standard software
Most likely because their implementation is wrong: https://github.com/intel/media-driver/is...-866529700
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Reply
#72
Thanks for triggering the discussion on media-driver @bkuhls let's see how far we get.
After reading all the comments it still looks like they should fix their side or change the docs
as they clearly state that each layer will contain exactly one plane.
Reply
#73
(2021-06-30, 07:17)a1rwulf Wrote: they should fix their side
maybe they did, using this tree
https://github.com/intel/media-driver/tr...dc819a3241
all HD content previously showing only greenish flicker now works!

I did not further analyse which commit fixed the problem but it looks like this one did:
https://github.com/intel/media-driver/co...dc819a3241
Kodi 19.5-Matrix/OpenGLES/gbm (+ PR19558 ) - Linux kernel 5.14.21 x86_64 - ffmpeg 4.4-git (+ patch )
Mesa 22.3.7 with iris driver - VA-API version 1.16.0 + Intel iHD driver version 22.6.3 - libdrm 2.4.116 - libcec 6.0.2
Intel i9-11900T - ASRock Z590 Extreme - BIOS version 2.20
Reply
#74
nice, all the demo's work now, enabling prefer vaapi render method works too.

using intel_gpu_top VideoEnhance stays on 0% now. hmm.

thanks for pushing this along bkuhls.
Intel Core i5-11500, ASRock B560M-ITX/ac, 240GB SSD + 4TB  Western Digital Blue, Arch Linux, mythtv 31+fixes + TBS 6205 QUAD FREEVIEW DVB-T2
Reply
#75
given their response its working on kodi atm due to them disabling "E2E Compression" for the moment.
sounds like a temporary reprieve and some point it will be re-enabled and either kodi adds the additonal plane for CCS or it stays broken on kodi.

so if kodi doesn't add this new plane can we just lock the current intel media driver or patch to disable E2E Compression in newer versions.
Intel Core i5-11500, ASRock B560M-ITX/ac, 240GB SSD + 4TB  Western Digital Blue, Arch Linux, mythtv 31+fixes + TBS 6205 QUAD FREEVIEW DVB-T2
Reply

Logout Mark Read Team Forum Stats Members Help
Rocket Lake (RKL) discussion0