Posts by chewitt

  • 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.

  • [RPi400] Memory leaks?

    Stop Kodi, rename /storage/.kodi to /storage/.kodi-old and start Kodi again. You'll effectively have a clean install state. Copy back sources.xml and other config bits as needed. Or just delete the DB files and they'll be recreated.

  • How to restore Kodi?

    If you are trying to do backup and restore from the same device, use the backup and restore functions in the LE settings add-on to backup the files in /storage/.kodi|.cache|.config and nothing more is needed. If you have other files i.e. media on /storage to be backed up then it's best to create your own .tar backup from the original device so that all the file/folder permissions are retained.

  • WireGuard VPN Manager

    Quote from Doemela

    LibreELEC is permanently replacing the old network engine (ConnMan) with the industry-standard NetworkManager.

    No idea how you dreamed that piece of news up, but there has never been any internal discussion about changing from industry-standard ConnMan to Network Manager and thus there is zero plan to change in this distro.

    LE13 uses iwd instead of wpa_supplicant but that change was made in May 2023 so the same change is present in LE12 too, so not exactly breaking news.

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

    I don't have the bandwidth to investigate and attempt compatibility with the random vendor u-boot versions that Radxa and others come up with so the general rule is you'll need to exorcise vendor u-boot from SPI or eMMC to allow LE to boot its own u-boot from SD card and then install the image to internal storage. I'm not aware of anything that should prevent install to NVME storage but I don't have a 5B+ board to look into. You might need to look into the state of the upstream device-tree file; in the Rockchip universe core features seem to enabled ad-hoc/per-board rather than the all-boards approach taken with other SoC platforms.

  • placing videos in one folder

    If you want the shows to appear in a Library view (under Movies or TV Shows) you need to properly structure files in folders so that scrapers categorise things correctly. If you just want to play them ad-hoc from the Videos view, then do what you like with them.

  • X96 Mini (S905L‑B) – Bricked Device, HDMI Flicker Issues, Bootloader Dump Needed

    Quote from als.zaimaj

    Given that the original ROM is no longer available, I'm trying to determine whether there is still a practical recovery path.

    It's not impossible but serious experimentation needs physical and software tools and a deeper level of technical ability than most users have or will easily learn. It's typically rather time-consuming and bit of a hard slog, so even when the user is enthusiastic to have a go; most of the staff (self included) have learned to avoid such quests.