DRM Prime and D2P and Sat TV

    with the following settings I try to watch SAT TV (Germany)

    Code
    - Allow using DRM Prime decoder
- Allow HW acceleration with DRM Prime
- Prime Decoder Method: Direct to Plane

    and I'm failing, seeing a spinning wheel.

    When Prime Decoder Method set to EGL it is working

    Questions:

    wrong settings on my end ?

    Info:

    Monitor is an PC Monitor (Philips 278B1, 4K without HDR)

    while I'm reading the gits (LE, XBMC) I'm aware of the last changes regarding rendering, etc.

    I'm thinking about opening a bug report at XBMC ...

    Log:

    https://paste.libreelec.tv/guideless-amir.log

    in the log I find

    Code
    2026-05-30 14:03:32.945 T:858   warning <general>: bool KODI::WINDOWING::GBM::CDRMUtils::FindVideoAndGuiPlane(uint32_t, uint64_t, uint64_t, uint64_t): Rendering will be done through EGL. Can not find a Video Plane [3840x2160] format:YU12, modifier:LINEAR together with a Gui Plane [1920x1080] format:AR24, modifier:INTEL_Y_TILED.

    Under System Display is set to 3840x2160p with Refresh Rate: 60 and that Resolution is whitelisted too ...

    ===

    other question

    while running with the above settings, esp. "Allow HW acceleration ..." and D2P: EGL

    I see after hitting the o-key => Tab "Player": "Video decoder: ff-h264-drm_prime (sw)"

    I guess "sw" means software ?

    I need some clarification here: Why SW while HW acceleration is on (or allowed) ?

    well, "allowed" means "might be on" not necessarly means "is on" ...

    Intel hardware should be using EGL/VAAPI rendering. We probably need to do some appliance.xml fiddling to hide other options.

    Code
    2026-05-30 14:02:18.372 T:858     debug <general>: [WHITELIST] whitelisted modes:
                                                   3840x2160 @ 60.000000 Hz
                                                   1920x1080 @ 60.000000 Hz

    NB: ^ this is bad configuration when you have all the normal rates available from the TV

    well, some moons ago I had configured my LE according to the above wiki side.

    All was working up to nightly from around 2026-05-18 (since then I need to reconfigure it).

    usually Adjust Refresh setting to "On Start/Stop" was set with the suggested Mode Whitelist

    now Adjust Refresh and 3840x2160@50 causes trouble here:

    movies from SAT-TV (1280@720@50) are displayed as the following:

    the screen is quartered and the TV movie is running only in the upper left quarter with an complete picture

    (o-key tells 3840x2160@50).

    All other quarters are just black.

    before 2026-05-18 the monitor just switched to 50 Hz and it was fullscreen.

    happens only with SAT-TV, not with local movies (independent their resolution)

    P.S.

    hoped it would be fixed with kodi: bump to 6532ed36

    Edited once, last by joe65 (June 2, 2026 at 3:45 AM).

    • Remove i915.force_probe=!a7a0 xe.force_probe=a7a0 from kernel boot params
    • Add video=HDMI-A-1:1920x1080M@60D to kernel boot params
    • Configure Kodi to run the GUI at 1080@60
    • Configure EGL/VAAPI (not D2P, not DRMPRIME)
    • Configure the whitelist for 3840@60/59.94/50/29.97/25/24/23.976 and 1080@60/59.94/50/24/23.976
    • Configure adjust refresh (start/stop)
    • Configure allow rate doubling

    Then play some media and pastebin another debug log.

    The TV panel is 4K native resolution so the TV has a ton of advanced scaling capabilties. Kodi can also upscale, but they are not as advanced as the TV's ones. So run the GUI at 1080p, allow Kodi to upscale SD media to 1080p, but allow the TV to handle upscaling of 1080p to 4K as it will do a better job.

    Quote from chewitt

    but allow the TV to handle upscaling of 1080p to 4K

    Sat-TV isn't upscaled to 4K (only to 1920x1080) !

    Code
    2026-06-02 15:56:24.199 T:900     debug <general>: bool KODI::WINDOWING::GBM::CDRMUtils::FindCrtc(): Original crtc id: 149, mode: 1920x1080 @ 60 Hz

    I guess it's nailed caused by the boot parameter (removed)

    it's an PC-Monitor

    to get sat-tv upscaled to 4K I need to remove the boot parameter AND

    either "adjust refresh rate on start/stop" set to off OR remove whilelist 3840@50

    otherwise I have a quartered display where o-key tells 3840@50 ! (see attachment !)

    I get the same effect when I set GUI to 50 Hz, although the monitor could do 3840x2160@50

    ===

    I took a look in elder guisettings.xml (backuped ~2 weeks ago, when I had trouble to update caused by undersized /flash):

    adjust refresh and whitelist 3840@50 were both set:

    id="videoscreen.whitelist">0384002160060.00000pstd,0384002160059.94006pstd,0384002160050.00000pstd,0192001080060.00000pstd,0192001080059.94006pstd</setting>
    and

    id="videoplayer.adjustrefreshrate" default="true">2</setting>

    the combination was running !

    the display switched to 3840@50 - I'm slidly unsure here: 50 or 60, but I tend to 50 -

    and in general I had fullscreen

    this is gone since ~2 weeks

    the last known good was - unsure - : nightly-20260518-fb65a7c

    ===

    Question:

    does refresh rate take care on what is whitelisted or does it already realize which monitor resolution is offered and take that ?

    ===

    now playing around with refresh rate and whitelist I got the impression that sometimes LE doesn't realize what is set or the order what is set first has an impact

    Quote from joe65

    Sat-TV isn't upscaled to 4K (only to 1920x1080) !

    Yup, Kodi upscales to 1080p and the TV upscales 1080p to the native 4K panel resolution. The TV will show that it has a 1080p signal but there are always physically 4K pixels in the screen, no?

    Quote from joe65

    how can I find that out ?

    If the panel advertises 4K modes it has 4K (or more) pixels. If you send it a 1080p signal the internal processor upscales 1080p to the native 4K panel resolution. It does that better than Kodi (and with zero load on the HTPC). Or you have a magic screen that somehow changes its pixel count when you send it a 1080p signal /shrug

    well, I wasn't satisfied with what was said here.

    I didn't know that you're on XBMC too.

    I'm not after "winning new friends" and thought to post the link to the bug report here too, but was otherwise involved.

    I'm after getting a fix for an - IMO - regression.

    Clearly displayed in the photo in comment #10: in an quarter of an 4K monitor it says this quarter *is* 4K ...

    well, I was slightly aware of the possibility "getting new friends" (but I referenced this discussion in the bug report, too, keeping it not under the radar somehow)

    I hope to shift this, if you realize that I'm trying to get -IMO- bugs/regressions fixed [and as long until they are], not for me only then the community (before they getting aware of them, when nightly becomes release) .

    Okay ?

    P.S.

    don't shift reports here to "erledigt" until the user is telling so or isn't convinced it's "erledigt".

    P.P.S.

    I'm following the git's (do not understand all, though) and I'm aware that something has changed since 18.05.2026 and the change might not be finished yet.

    My obvious change was that I could do something before that date, but couldn't do afterwards => regression.

    anyway, it's now there where the main developer is acting ...

    Edited 2 times, last by joe65 (June 6, 2026 at 7:18 PM).

    Kodi Piers (22) now contains some major changes to how Kodi handles GUI/video output on Linux. Most changes are addressing functional and feature gaps in GLES/GL rendering support. However they also cleanup older VAAPI code and fix bugs. I guarantee there are also more bugs to be found and hopefully fixed.

    In short: Kodi has changed. Users with configurations that previously relied on fallbacks/quirks/bugs may find their configuration needs to be adjusted as the dependent fallbacks/quirks/bugs have changed or no longer exist.

    Using D2P (as you were) is wrong for an Intel GPU device, it should use EGL. It's unclear if you were also trying to use DRMPRIME paths but that would also be wrong. Your old config was dependent on a load of fallbacks and quirks. Kodi settings needs tweaking to force EGL output and hide the wrong settings when using VAAPI .. it's on a to-do list.

    If you configure Kodi for 4K desktop with only 4K whitelist entries Kodi will upscale everything to 4K. If you configure Kodi for 1080p desktop and provide 4K and 1080p whitelist entries Kodi will scale anything under 1080p to 1080p and will render 4K at the native media resolution; this is generally considered "best practice" as Kodi is not modifying the original media (1080p and up) and most TV's are better at scaling 1080p to 4K than Kodi. Running a 1080p desktop normally means the GUI looks sharper and the HTPC device uses less CPU/IO resources resulting in smoother navigation.

    In summary: something in the Alpha state development release you are using has changed. You have been advised of a different and better configuration to use. You have confirmed that different and better configuration works. However you are unhappy at having a different configuration.

    "You can please some of the people some of the time, not all the people all the time"

    /shrug

    Quote from chewitt

    ...

    Using D2P (as you were) is wrong for an Intel GPU device, it should use EGL. It's unclear if you were also trying to use DRMPRIME paths but that would also be wrong.

    I've seen reardonia has tested it on Intel (N100 or so => somewhere under his patch sets/changes) so I tried it to.

    You told this is wrong, so I changed it.

    Quote from chewitt

    ...

    Running a 1080p desktop normally means the GUI looks sharper and the HTPC device uses less CPU/IO resources resulting in smoother navigation.

    that's my main attempt too (lower resources/temp (!)) and fullfill what manufactur recommands (3840@2160@60)

    Quote from chewitt

    ...

    You have confirmed that different and better configuration works. However you are unhappy at having a different configuration.

    This *is* not (complete) the case (see comment #12)

    again: just take a look at the photos (comment #10, #12 => "Video Resolution"

    #12: manufactur recommendation hurt.

    it was working before. I mean the 3840@2160@50, what -btw- the monitor offers by design...

    (temp.) vanished ...

    Quote from chewitt

    "You can please some of the people some of the time, not all the people all the time"

    /shrug

    this works on both ends of us !

    This sentence initial goes:

    "You can fool all people some of the time, and some of the people all the time, but you cannot fool all the people all the time."
    (Abraham Lincoln)

    where I translate "fool" to german "belügen" oder härter "verarschen".

    *NOT* my Intension !!!

    P.S.

    we should just wait what reardonia will tell ...

    - yes I've read from him something like: GUI only 1080, but up to now I can't believe he is fine with "a monitor can't anymore run a resolution it is design for" -

    Edited once, last by joe65 (June 7, 2026 at 12:34 PM).