Posts by chewitt

  • [RPi3B+] RTSP Stream Not Playable

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. Generate a log URL (do not post/upload logs to the forum)

    use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

  • [x86-64] Kodi stopped working for me....

    The initial file played (Cosmos s01e11) seems to evaluate/read from NFS storage okay but Kodi then ends up repeatedly attempting to setup the audio output sink and never succeeding with content like this ^

    The connected HDMI device is a monitor that only supports 1920x1080@60? - Does it have speakers? - It's rather unusual to see no ELD data (from EDID on the HDMI connection) returning info on speaker placement options:

    Code
    2025-03-31 21:26:34.536 T:1162    debug <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=0" may be unconnected (no ELD data)
2025-03-31 21:26:34.537 T:1162    debug <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=1" may be unconnected (no ELD data)
2025-03-31 21:26:34.538 T:1162    debug <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=2" may be unconnected (no ELD data)
2025-03-31 21:26:34.538 T:1162    debug <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=3" may be unconnected (no ELD data)
2025-03-31 21:26:34.556 T:1162     info <general>: CAESinkALSA - No playback configurations available for device "surround21:CARD=HID,DEV=0"

    The problem smells like bad/missing EDID data on the HDMI connection so I'd suggest experimenting with different HDMI ports on both ends, different HDMI cables, etc. - You can also update to an LE13 nightly but I rather doubt this is a software issue.

  • [RPi4] SonyE65 Bluetooth Crashes LE

    If something crashes the question is what/where?

    If Kodi crashes (and then restarts itself) we need to see the Kodi crash log. It's useful if debug is enabled beforehand, but the main point is the crashlog will show what Kodi was doing when it crashed.

    If it crashes at a lower level there will be some kind of info or kernel splat in the systemd journal, and we need to see that no a Kodi debug log.

  • Is Intel N150 Twin Lake not supported yet?

    Generic uses a different install flow to ARM SoC boards like Raspberry Pi where you write the image direct to boot media. Generic expects to boot from an install USB which installs LE to a formatted (as anything) spare storage device; normally an internal drive but can also be another USB stick. You've written the installer to the target device, but the installer cannot install to itself when its the active boot device (and there are correctly no other devices to install-to found). The workaround is to interrupt boot at the syslinux stage and type 'run' instead of booting into the installer; the 'run' (from USB) mode should expand the storage partition to 100% size and then boot into Kodi. You end up at the same destination but having taken a different route.

  • [x86-64] Kodi crashing when doing certain tasks (LE 12.0.2)

    Kodi saves settings on shutdown and if you trigger a hard crash before exit that doesn't happen. So not saving settings is normal and expected in that scenario. The crash would be more interesting .. but the log you've shared looks like the log on startup (after the crash) rather than the actual crash log, and debug is not enabled, so there are no obvious clues to the failure. In future use the native paste function so can click a URL instead of having to download and open log files.

    The only things that do stand out are:

    a) The huge number of add-ons installed and these are often the source of instabilities and random issues. I'd suggest stopping Kodi, renaming /storage/.kodi to /storage/.kodi-old and then restarting with a clean instance and then progressively migrating a more minimal config back. Stick with the default Estuary skin to eliminate the demands of super-heavy skins.

    b) The pirate IPTV feed with 15,000+ channels (no legal feed has that many) which results in a huge amount of additional processing when attempting to use DVB and EPG functions. Kodi works great with hundreds of channels, it doesn't work so great with that kind of feed size. That's a self-inflicted problem though .. and I lost interest in looking further.

  • [RPi5] TrueHD or any Dolby via eARC Stopped Working

    Quote from yamcenutzer

    BTW, why did you single out that one warning line about waiting for a buffer? What does that tell you?

    Da Flex has an obsession with buffering and frequently flags it for no discernable reason /shrug

    I'm not seeing anything in the log. The relevant streams are being selected and Kodi outputs RAW to the HDMI device. Make sure the HDMI port's involved (on TV and AVR) support eARC, as sometimes it's only implemented on one of them.

  • [x86-64] Audio Passthrough Not Working on LE 12 Nightly

    It should work, but not all HDMI ports are eARC compatible, not all cables support HDMI 2.0+ modes, and NUC firmware continues to be a lottery so ensure the system BIOS and particularly any LSPCON chip firmware is at latest versions. If an LSPCON chip is used the output may need to be set to DP not HDMI as the LSPCON chip converts DP to HDMI for output (which is cheaper than wiring up the native HDMI outputs). If none of the above .. /shrug

  • Update from LE 8 to LE 12

    Da Flex it's not a different architecture.

    rolapinou Basically correct. I would clean install then add sources.xml and check the SMB access is working fine. Then I would stop Kodi and move the SQL database config to advancedsettings.xml and restart Kodi to start the DB migration. I doubt there's much else that can or should be reused from the older install, perhaps some addon settings from userdata.

    Note that current Kodi requires MySQL/MariaDB v5.7 or newer so check the version on the Synology first. I'd also SSH in to tail the kodi.log file to check for errors during the DB migration as it will need to step through quite a few versions and will take time.

  • [RPi4] Argon One Case Shutdown

    Once you install an addon (ID) from a third-party repo it will only update from that repo even if other repos have the same addon ID and a newer version available. I forget the logic for manual installs from zip but I suspect Kodi will not auto-update the ID from an online repo if you install from zip. Kodi has some very specific logic around repo updates due to general problems seen with piracy oriented third party add-on repos that have the habit of publishing addons and modified dependencies that reuse the same ID(s) with the version articifically bumped to 'force' the modified version to be used instead of the correctly numbered versions available in the official Kodi repo.

  • [x86-64] Switching Display Modes does not work for Zoom

    Different issue that we fixed: https://github.com/LibreELEC/LibreELEC.tv/issues/9884 and different zoom issue still being resolved on RPi4/5: https://github.com/raspberrypi/linux/pull/6741

    Re-reading the issue report (not on a phone) and I'd guess either the there's no function to do what you want for Zoom? - I don't see anything similar on https://kodi.wiki/view/List_of_built-in_functions or it's not working and needs to be reported upstream to Kodi developers via https://github.com/xbmc/xbmc/issues

  • New ASUS NUC 14 Essentials doesn't see wired Ethernet NIC

    I've done some further build experiments with patches. In short, the second patch smp flagged does not apply to Linux 6.12.y as the function being patched doesn't exist, and the more I look into surrounding code for the change that adds it, the more I see that r8169 has seen a large amount of change in Linux 6.13.y and 6.14.y and I don't think it's worthwhile trying to add ever-more patches to see if the NIC works.

    As LE13 currently plans to use Linux 6.12.y this means the release version of LE13 will not support the chip so you will either need to keep using the development build I previously shared until LE14 ships sometime in 2026 or you will need to learn how to self-build an LE image with a newer kernel. The development image will continue to work, but once LE13 ships we'll bump the LE add-on repo version to match the release version and from that point there will be no updated to the repo, and a some point we'll cleanup/delete the old development repos.

  • Is Intel N150 Twin Lake not supported yet?

    Intel continuously breeds new something-lake chipsets and most folks lost track of what's supported or not some time ago. If it appears not to work with LE12 which uses Linux 6.6.x, test the latest LE13 nightly as that's using Linux 6.12.x. If it's so darn new that even Linux 6.12.x doesn't support it, then you'll need to self-build an image with Linux 6.14.x and cross fingers.

  • Irrelevant Kodi Omega (on Ubuntu) post

    We don't allow "warnings" from a random forum user to dictate release strategy. If you have an issue; report it to Kodi devs and then work with them to get it resolved. Then the issue is not an issue, and the fix can go into some future LE update. That's how it works. If you don't report it, there is no issue, or the only person with the issue is you..