Posts by chewitt

  • [x86-64] No MPEG2 hw acceleration with AMD GPU

    Quote from smp

    I don't see how this is relevant to this particular case.

    It's relevant because explicit configuration of things is a general design objective for the buildsystem. Whether that was/wasn't an option in the past is irrelevant because what's possible today takes prescedence.

    I plan to leave the PR open for a while for people to show up with comments on the state of MPEG2 decoding.

  • LibreELEC, DNS and connman

    ConnMan owns resolv.conf and it exists in /run which is not persistent over reboots. You can configure things using the settings add-on which has a dbus-agent that speaks to connmanctl, or by using connmanctl from the CLI, or by cloning /etc/connman/main.conf to /storage/.config/connman_main.conf and editing defaults there (reboot to effect changes).

  • LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588

    Clear SPI and boot LE from SD card. Establish that you can see the NVME drive, i.e. the kernel modules and device-tree stuff is there to support that function. Format the NVME drive with a single EXT4 partition 100% sized with a unique disklabel. (re)Mount /flash as writeable and reconfigure /flash/extlinux/extlinux.conf so disk=label=STORAGE points to the NVME disklabel instead. It will boot from SD card, but Kodi effectively runs form NVME so you see the benefit of faster I/O access.

  • 2.5 GBit/s Ethernet adapter for LibreELEC?

    Quote from jbinkley60

    I wonder if we can get the LibreElec team to add support for the RTL8157 chipset ?

    The r8152 kernel driver shows signs of RTL8157 support so have a look at the system log for missing firmware messages. If that's all that's needed (or perhaps adding new USB id's) then it's trivial to add support.

    NB: on the flip-side if it needs a downstream/vendor driver we'll politely refuse; it needs to be supported upstream.

  • After switching from HDMI 2.0 TV to HDMI 2.1 no HDR anymore ;(

    Having "Adjust display HDR mode" disabled results in HDR media being tonemapped to SDR whereas enabled implies the hardware is HDR capable (but while the TV might be, the kernel DRM layer says otherwise) so Kodi doesn't tonemap and you see the normal washed out colours when HDR media is used with an SDR colourspace.

    K22 is a big improvement on the previous HDR experience in Kodi but a lot of the underlying logic and config options are still based on K21 capabilities so there's some cleanup/reworking needed. Hopefully by the time K23 ships that's been done; along with more of the kernel level support for colourspace/bit-depth being implemented and matured.

  • After switching from HDMI 2.0 TV to HDMI 2.1 no HDR anymore ;(

    Code
    info <general>: [display-info] make: 'Sony' model: 'SONY TV  *00'
info <general>: [display-info] supports hdr static metadata type1: true
info <general>: [display-info] supported eotf:
info <general>: [display-info]   traditional sdr: true
info <general>: [display-info]   traditional hdr: false
info <general>: [display-info]   pq:              true
info <general>: [display-info]   hlg:             true

    This ^ shows the Sony TV advertises HDR

    Code
    info <general>: [display-info] make: 'Samsung Electric Company' model: 'S95F'
info <general>: [display-info] supports hdr static metadata type1: true
info <general>: [display-info] supported eotf:
info <general>: [display-info]   traditional sdr: true
info <general>: [display-info]   traditional hdr: false  <= this is an old standard nobody uses
info <general>: [display-info]   pq:              true   <= this is HDR/HDR10 as we know it
info <general>: [display-info]   hlg:             true

    This ^ shows the Samsung TV also advertises HDR

    Code
    2026-06-16 08:45:50.124 T:765     debug <general>: [WHITELIST] whitelisted modes:
                                                   4096x2160 @ 24.000000 Hz
                                                   4096x2160 @ 23.976000 Hz
                                                   ...

    This output in both logs ^ shows you aren't following whitelist recommendations in https://wiki.libreelec.tv/configuration/4k-hdr although that's just an optimum config observation and not the cure for anything.

    Code
    debug <general>: LinuxRendererGLES::Configure: HDR passthrough: off

    This ^ appears in both logs.

    Kodi should be configured for "Adjust display refresh rate" (start/stop) with "Adjust display HDR mode" (enabled) and "Allow using DRMPRIME decoder" (disabled) and "PRIME Render Method" (EGL).

    Swordsmith is [email protected] but this res/rate combination doesn't exist on the DRM connector so the whitelist logic chooses [email protected] instead ^ and Kodi downscales the content (downscaling frames is easier than reducing the refresh rate). The NY demo file is [email protected] which matches an available 4K mode.

    I'm not aware of anything in the kernel/DRM layer that would block HDR metadata from being used. IMHO it's more likely that Kodi settings need changing (did "Adjust dusplay HDR mode" exist in LE12?) or it's something more basic like not having deep colour modes (or whatever Samsung calls them) enabled on the HDMI port that you're connected to on the TV.