Posts by chewitt

    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

    • Are the two USB drives powered from the USB ports on the board or they have external PSU(s)?
    • What is 5V/?A spec of the PSU?
    • If you remove one of the drives does the remote appear reliably?
    • If you scan the bus with lsusb -tv is the remote USB dongle listed; and does the remote now work?

    If you have two drives powered from the board my hunch would be that when the board is booting and everything is in an active state the drives can pull enough power to result in the remote USB dongle not receiving enough to power on. This is probably a borderline case so it might still work occasionally. If you then remove/reconnect some time after boot the board is now in a less active and more power-stable state so the remote USB dongle reliably works.

    If the hunch is in the correct direction, perhaps using a higher rated PSU might work, e.g. the 5V/5A spec for an RPi5. Or connecting the drives to a powered USB hub, or if one of the drives has as USB 'Y' lead (to draw power from multiple USB ports) connect the non-data plug to an external USB phone charger to reduce power draw from the 4B board.

    Double-check that you are using a current nightly. The latest LE13 images are at the bottom of the page not the top; older images will probably use a repo version that no longer exists on the server.

    If that's not the issue, you need to investigate whatever local-to-your-install networking problem prevents the RPi5 from connecting to the repo (which is live/accessible). If you are using WiFi ensure "wait for network" is enabled with a long enough delay.

    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

    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.

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

    RPi3 hardware is 64-bit capable but media drivers (inherited from RPi1/2) are optimised for arm and on the advice of RPi devs we continue to ship RPi3 as an arm image. RPi4/5 run different drivers that are written and optimised for aarch64 or where the small performance difference doesn't hurt.

    If you disable auto update mode (which only auto-updates minor updates) in the GUI and then manually choose to update to LE12.2, the file downloaded and used for the update is the .tar file. If you download from the website the .img.gz file can be used.