Posts by heitbaum

  • [RPi3B+] Mounting pCloud Drive

    In LE12 we moved the libraries to lib.private to keep them from colliding and cluttering the LD_LIBRARY_PATH.


    nuc12:~ # find .kodi/addons/ | grep libfuse.so
    .kodi/addons/virtual.system-tools/lib.private/libfuse.so
    .kodi/addons/virtual.system-tools/lib.private/libfuse.so.2
    .kodi/addons/virtual.system-tools/lib.private/libfuse.so.2.9.9
    .kodi/addons/virtual.network-tools/lib.private/libfuse.so
    .kodi/addons/virtual.network-tools/lib.private/libfuse.so.2
    .kodi/addons/virtual.network-tools/lib.private/libfuse.so.2.9.9

    the rpath has been updated on the binaries

    nuc12:~ # ldd .kodi/addons/virtual.system-tools/bin/mtpfs
    linux-vdso.so.1 (0x00007f34ba525000)
    libfuse.so.2 => /storage/.kodi/addons/virtual.system-tools/bin/../lib.private/libfuse.so.2 (0x00007f34ba4e1000)
    libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f34ba2ec000)
    libusb-1.0.so.0 => /usr/lib/libusb-1.0.so.0 (0x00007f34ba2d7000)
    libc.so.6 => /usr/lib/libc.so.6 (0x00007f34ba119000)
    libudev.so.1 => /usr/lib/libudev.so.1 (0x00007f34ba0ca000)
    /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f34ba527000)

    The code that does this is: https://github.com/LibreELEC/Libr…package.mk#L194

  • Jellyfin Addon from LibreELEC repository

    Addons PR updated to the latest - previous Jellyfin downloads have been removed from the Jellyfin download server.

    jellyfin: update to 10.10.1 and addon (2) by heitbaum · Pull Request #9501 · LibreELEC/LibreELEC.tv
    release notes: https://github.com/jellyfin/jellyfin/releases/tag/v10.10.0 https://github.com/jellyfin/jellyfin/releases/tag/v10.10.1
    github.com
    jellyfin: update to 10.10.1 and addon (5) by heitbaum · Pull Request #9502 · LibreELEC/LibreELEC.tv
    release notes: https://github.com/jellyfin/jellyfin/releases/tag/v10.10.0 https://github.com/jellyfin/jellyfin/releases/tag/v10.10.1 Backport of jellyfin:…
    github.com

  • [RPi5] Network Disappeared

    Not a bug as such, but simply they are not yet supported. Looking at the open tickets and the above seems to be getting to the bottom of the wireless issues reported, this is a good another “now known” item.

    The list probably looks like the below now: (noting that these are shortcomings in drivers, kernels, supplicants, ….) The “But it should work” philosophy whilst idealistic is not true even in commercial / non iwd / non LE landscapes. Wireless will probably always have its challenges given standards and compatibility across the many elements that make it up - but every known reproducible issue should improves our support and hopefully the Linux wireless ecosystem system.

    Known issues

    • wireless networks with FT enabled may not work
    • wireless networks with WPA3 may not work
    • wireless networks where the signal strength is low may not authenticate
    • The wl bcm_sta driver (at this stage) will be dropped from LE13 - (lack of patches to make it compatible with linux 6.12)

      For these 4 known issues - there does seem to be movement upstream in “fixing“ / “adding support for”

  • [x86-64] LE 12.0.1 on Intel Meteor Lake

    Yes. Maybe. No.
    Answer will depend.


    In my case - I run nightly+ on my daily system (Generic ADL) , but am developing everyday as you would see. The operating system is starting to take shape for the LE13 release, in that the big changes - compilers, libraries, kernels are pretty much done. So no major changes at the operating system level that would impact are expected. We will be updating to the next Mesa soon.

    As a developer, I run RC software packages, so that we try and address issues with “new packages” before they are released - thus I try to be on the front foot so that the commits are soak tested first. The team in both Kodi and LE do the same.


    There are kodi changes happening (api) that will mandate changes/updates to addons, and this will continue through to the release of Kodi Piers. These may cause you to have to update - if you use these.

    You will need to decide what’s best for you, but if you stay on a version “eg the early sept one” and don’t have fixed the issue you are trying to address, then when the LE13 does come out, the issue may still not be fixed in the release version. In the case of using “new hardware”, I would stay using recent nightlies, to make sure that they work with your system. Older hardware is usually more stable in the linux kernels/graphics software.


    based on Chewitts answers - I would fix your system so that it can play all, as if there is another issue that comes, it might not get fixed. If there is a further problem that is not whitelist. So GUI in 1920x1080 and whitelist max 3840x2160.

  • [x86-64] LE 12.0.1 on Intel Meteor Lake

    I can see a few things.

    You are using the xe driver - good (as the kernel log indicates that 4908 is not supported properly by the i915 driver.)

    The Kodi gui is 4096x2160 - suggest setting this back to HD

    I believe from the logs that the GUI is working - please confirm

    I believe from the logs the “bootsplash” is working - please confirm

    From the playback logs, you can see that koi probably picks the wrong resolution for playback of the HD stream. Use the whitelist, get it to use a HD resolution.

    The stream you are playing is broken - see ffmpeg logs.

    Please test a known working file. E.g. 2D BBB - http://bbb3d.renderfarming.net/download.html

    I am compiling a nightly image for you to test (current master + the 6.12-rc4 linux) download from https://heitbaum.libreelec.tv - will be there shortly.