Posts by atoulmin

    well, sounds like I need to get 24hz, or rather 23.98hz working. anyone have any ideas on that? I’m not sure what is going on with my video pipeline. I tried copying the edid, but that didn’t help. I’m not totally sure what the Prime DRM decoding does, but it doesn’t seem to affect my problem on or off.

    I did manage to get HD audio working (with playback at 60hz).

    Looking at your log, it looks like you have your Kodi gui set to 3840x2160.

    This should be 1080p as you don’t want Kodi scaling anything. When you select a 4K video it will switch to 4K and the right colourspace.

    So change your resolution in the menu to 1920x1080 50/60

    Then make sure match video frame rate on start and stop is on. It then should switch to 4K 24 BT2020 for playing movies. See how that goes.

    What version of LibreELEC are you using? The nightly generic? Make sure you don’t use the generic legacy.

    Also do you have match frame rate turned on? I have a nuc11 and it works fine. There is no 4k60HDR support at the moment.

    So I didn’t realise it had to be on the same line, adding the force_probe at the end will now boot LibreELEC into Kodi. Hooray.

    However when I attempt to play a video I get sound, but the picture will Goto switch but will revert to Kodi menu. The movie will continue to play with sound but no video.

    Log file attached

    Can you please run lspci -s 03:00.0 -n and check that 56a1 is the device ID of your card that needs to be used by the force probe.

    Otherwise - If it is the MEI error.

    I believe we will need to update the kernel configuration.

    Based on this:- ihttps://http://gitlab.freedesktop.org/drm/intel/-/issues/7732

    Looks like we need to update the kernel

    Code
    LibreELEC (community): nightly-20230102-2cfb343 (Generic.x86_64)
    LibreELEC:~ # lspci -s 03:00.0 -n
    03:00.0 0300: 8086:56a1 (rev 08)
    LibreELEC:~ # 

    So I tried adding that as suggested and rebooted, still no luck. Same issue


    This might help. Looks like it’s recognised.


    Here is the log.

    Hi,

    I’m not sure if I should report here or GitHub. However the latest nightly builds will not boot past the “just enough OS” logo if I use my Intel ARC750. If I remove that card and use the AMD 6400 it works fine. I can still SSH into the machine while it’s at the logo.

    I’m assuming Mesa support isn’t quite there yet?

    The screen does not switch to HDR when it first loads the stream. So the procedure I mentioned is the only way for me to force HDR, otherwise it will keep playing in SDR. So when I do switch from a playing video to the home screen it will recognize the HDR and switch the display.

    This may fix the problem?

    CWinSystemGbm: add colourspace connector property by lrusak · Pull Request #21845 · xbmc/xbmc
    This allows setting the Colorspace connector drm propery. This allows specifying the output colorspace and allows tv's to trigger into a specific colorspace…
    github.com