Posts by popcornmix

  • [RPi4] No Audio on LE 11 and LE 12

    It's not a LibreELEC issue because the bootloader diagnostic shows "EDID=none". That is a hardware issue.

    It is either:

    the hdmi display.

    the hdmi cable (or adaptor if using one for full size to micro-hdmi)

    the hdmi socket on pi


    All tests should be done with no sdcard and using bootloader diagnostic display:

    Try with other socket on pi. If hdmi1 also reports EDID=none then it's not the pi socket

    Try connecting to another hdmi display. If you still get EDID=none then it's not the display but the cable.

    If another display works then your display is not correctly reporting an edid.

    If there's another hdmi socket, then try that. Otherwise report issue to you display manufacturer.

  • Buying a RPI5

    Quote from Elicity

    Can I change the eeprom option from LE itself or do i need to boot into rpi-os or raspbian ?

    You can ssh in and run:

    Code
    rpi-eeprom-config -e
    Quote

    Like buying a car that intentionally leaks gas, just for those that want to pull a trailer. Seems like a design flaw workaround to me.

    The issue is there exist HATs (not ones designed by RPi...) that can be damaged if 5V is provided (which comes straight from USB power connector) but 3V3 is not (which comes from PMIC which ideally would be powered off on shutdown).

    So, yes it is a workaround, but not for a design flaw that the Pi created.

  • Buying a RPI5

    2GB is enough for LibreELEC.

    You only need more if you want to run additional services (e.g. using docker).

    There is no fix for what you linked. It is by design. By default power is available for HATs after a shutdown.

    If you are not using a HAT that requires that you set POWER_OFF_ON_HALT=1 and get the lower power consumption.

  • Hulu channel freezes after approximately 30 seconds on KODI 21.2.0

    Quote from johnny77

    **************I pruned the file but it was still too big so I compressed it. It is actually kodi.log.gz not kodi.log*****************************kodi.log

    -J

    Don't enable the component specific debug unless asked for it - it just makes the log so large it's very hard to read.

    But, the real answer is if you have an issue with a specific addon, then check out the addon's thread.

    https://forum.kodi.tv/showthread.php?tid=364953

    where it does sound like there is a known issue "All live channels freeze after just a few seconds".

  • [RPi4] AV1 Capabilities

    Quote from elim_garak

    I've been looking into a case and will probably go with the Argon One which is both a massive heatsink and includes a configurable fan. I'll have to endure the fan for AV1 playback. Hopefully it won't be too annoying.
    OTOH maybe the smarter alternative would be just to invest in a rpi5 instead of burning 25£ on an additional case.

    But when booting to LE isn't the bootloader firmware tied to the LE version? I'm not sure how to update it since that is the latest version shown to me.

    I've had success with completely passive heatsink cases like the flirc one (which has a kodi branded variant).

    There should be no tie between LE and bootloader. Latest bootloader will typically be fine for any images (even old ones).

  • [RPi4] AV1 Capabilities

    Yes, the jumping is likely because video decode cannot keep up.

    What you find is audio plays at correct speed, but video is playing slower, so a/v sink drifts apart.

    Once a/v sync reaches a set threshold, kodi will seek (jump) to restart with audio back in sync (but it will obviously drift again).


    Your bootloader version does pre-date automatic NUMA settings and SDRAM_BANKLOW will be ignored.

    However looks like you are on a Pi4, so SDRAM_BANKLOW=3 was the default so it may not be critical, but it may be worth updating that to be sure.

    Setting numa=fake=1 should get you back to pre-numa performance (which I'd expect to be a little lower, but may be worth a test).

    Quote

    LE 12 nightly-20250116-37e4458 - dav1d 1.4.1, Kodi 21 --> played fine on slow scenes, some "lag/drops" on fast paced scenes
    LE 13 nightly-20250205-562de9e - dav1d 1.5.1, Kodi 22, NUMA --> playback keeps jumping every 4 seconds

    It might be best to try and find a file that plays well on one of the systems but not the other (something where you can check a/v sync is accurate throughout). If the answer is "struggles on both", then it might just be slightly different thresholds in kodi makes one appear better (but really you can't easily judge which is better when both fail to keep up).

    Note: Pi5 benefits significantly more from NUMA than Pi4 (and it's much faster to start with).

  • [RPi5] Continious crash on LE13 nightly

    Unfortunately the crash backtrace has no info. A debug build may be needed.

    I'm not quite understanding what you wrote.

    When does the crash occur? After it's been running happily for some time? (how long?)

    Does the crash occur when you are doing a specific operation? (e.g. starting playback of a file? Navigating through menus? While system is idle?)

    Finding the first nightly build with the problem is one way of narrowing things down.

    Also, if you rename ~/.kodi and restart (so back to default settings) does it still crash?

  • [Rpi 5] New Raspberry Touch Display 2

    I believe the Touch Display 2 is natively portrait, and kodi doesn't support rotation through DRM so this is not going to work well even if you get the touchscreen working (presumably there are kernel commits missing).

    Running RPiOS desktop, and using kodi21 from apt would support rotation I believe (but it's a less efficient render path).