LibreELEC Nightly RPI2 latest builds fail to boot.

  • Hi.

    The latest nightly builds (RPi2) from September, 04 onwards are failing to boot properly on my Rpi 3B+.

    I have already lost my installation. Wiped everything to start anew to no avail.

    There is an ongoing problem with the latest builds that are making the booting process loop right after the logo is shown.

    Is that a known issue?

    Please, let me know.

    Edited once, last by hbbs (September 7, 2023 at 5:17 PM).

  • At the moment of this writing, I'm low-level formatting my SD card. It will take a while to finish it. In the meantime, I'm gonna buy a new SD Card.

    This is strange. My RPi was working normally until I updated from the nightly build of September, 02 to today's build.

    Just one more thing. Before the low-level formatting of my SD Card. I flashed the nightly build from September, 02 and it booted normally.

    But the builds after that they all are failing to boot. Caught in a loop.

    I will be back later today with more information.


  • I believe I found what is happening.

    After trying a new SD card and even another power supply I decided to open my Raspberry Pi case to have a look.

    Putting everything back together I forgot to reconnect my USB Audio SPDIF dongle and powered on. To my surprise it successfully booted.

    When I connected my USB Audio dongle LibreElec crashed and then got stuck on a loop while trying to boot, just like before

    This is only happening with the nightly builds after September, 02.

    chewitt what changed after Sep,02 that is causing these issues?

    Please, let me know

    PS: My USB Audio SPDIF dongle is a Turtle Beach Audio Advantage Micro II.

  • My bet would be on the ALSA update

    But we need logs to be certain:

    Add "ssh" to the end of cmdline.txt (on the same line, use eg notepad++ on windows to edit that on the FAT partition), then quickly ssh in after boot, while kodi is in a crash loop and enter "systemctl stop kodi".

    Then run "pastecrash" to update the crash log info and post the URL you got - from there we can look further.

    so long,


  • Hmm, unfortunately the interesting bit, the stack backtrace, was missing in the log.

    Could check if you have more kodi_crashlog files in /storage/.kodi/temp and upload them, too (eg with "pastebinit


    According to the log there should also be a /storage/.kodi/temp/kodi_crashlog_20230907190747.log file (there might be more, but older ones will eventually get cleaned up automatically).

    so long,


  • I did some looking into this today.

    I cant see dmesg for the device (not that that would help me directly.) but good to get all the info.

    Here is the code that is being run - just after this (I believe at the time of the crash). debug logs - would be required next. Also what the log would normally say after the last "info <general>: CAESinkALSA - Unable to open device "surround71" for playback"

    xbmc/xbmc/cores/AudioEngine/Sinks/AESinkALSA.cpp at 4d639b82d1c9830eb4a010690432f75cc4d756af · xbmc/xbmc
    Kodi is an award-winning free and open source home theater/media center software and entertainment hub for digital media. With its beautiful interface and…

    There is nothing in the issues or git since 1.2.10 that looks like it "fixes this."

    Arch: armv7l

    Release: LibreELEC nightly-20230904-e2439c5

    Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --audio-backend=alsa+pulseaudio'.

    Program terminated with signal SIGSEGV, Segmentation fault.

    #0 0x76edf440 in ?? () from /usr/lib/

    Program terminated with signal SIGSEGV, Segmentation fault.

    #0 0x76f4d440 in ?? () from /usr/lib/

    2023-09-07 19:07:31.868 T:1080 info <general>: GLES: Maximum texture width: 2048

    2023-09-07 19:07:33.630 T:1080 info <general>: load keymapping

    2023-09-07 19:07:33.633 T:1080 info <general>: Loading special://xbmc/system/keymaps/appcommand.xml

    2023-09-07 19:07:33.636 T:1080 info <general>: Loading special://xbmc/system/keymaps/customcontroller.AppleRemote.xml

    2023-09-07 19:07:33.638 T:1080 info <general>: Loading special://xbmc/system/keymaps/customcontroller.Harmony.xml

    2023-09-07 19:07:33.642 T:1080 info <general>: Loading special://xbmc/system/keymaps/customcontroller.SiriRemote.xml

    2023-09-07 19:07:33.644 T:1080 info <general>: Loading special://xbmc/system/keymaps/gamepad.xml

    2023-09-07 19:07:33.648 T:1080 info <general>: Loading special://xbmc/system/keymaps/joystick.xml

    2023-09-07 19:07:33.652 T:1080 info <general>: Loading special://xbmc/system/keymaps/keyboard.xml

    2023-09-07 19:07:33.659 T:1080 info <general>: Loading special://xbmc/system/keymaps/mouse.xml

    2023-09-07 19:07:33.661 T:1080 info <general>: Loading special://xbmc/system/keymaps/remote.xml

    2023-09-07 19:07:33.666 T:1080 info <general>: Loading special://xbmc/system/keymaps/touchscreen.xml

    2023-09-07 19:07:33.673 T:1080 info <general>: GUI format 1920x1200, Display 1920x1200 @ 60.000000 Hz

    2023-09-07 19:07:33.750 T:1086 info <general>: CAESinkALSA - Unable to open device "surround71" for playback

    2023-09-07 19:07:33.752 T:1086 info <general>: CAESinkALSA - Unable to open device "surround51" for playback

    2023-09-07 19:07:33.752 T:1086 info <general>: CAESinkALSA - Unable to open device "surround71" for playback

    2023-09-07 19:07:33.753 T:1086 info <general>: CAESinkALSA - Unable to open device "surround40" for playback

    2023-09-07 19:07:33.753 T:1086 info <general>: CAESinkALSA - Unable to open device "surround51" for playback

    2023-09-07 19:07:33.754 T:1086 info <general>: CAESinkALSA - Unable to open device "surround71" for playback

    ** CRASH **

  • HiassofT

    Yes, it did solve the issue I reported yesterday.

    If you excuse me. I'd like to report another thing. This is not new. It is something that appeared late in the last development cycle.

    The reason I'm bringing this up is because I extensively tested the SPDIF out capabilities and what I'm about to report just started to happen a lot

    Here's what happened on the log that I attached below

    I played a movie with an AC3 5.1 audio track. So far. So good.

    Now is when the issue begins. I stopped the playback of said movie with an AC3 5.1 audio track and went to play another movie title, but this time with a DTS audio track.

    The sound doesn't come up. My audio receiver still shows DD Digital. It got stuck this way when I played the first movie title with an AC3 5.1 track.

    In fact. Not even the Kodi GUI sounds are being played.

    After that, I went to listen to a Web Radio (Stereo) and no sound came up.

    The only way to listen to a sound is by waiting. Sometimes this takes too much time it is better to reboot LibreELEC.

    But again eventually my audio receiver dropped the DD Digital to No Input and after that, I got sound again.

    I thought since you guys are looking into ALSA maybe I should mention this issue as well

    Feel free to contact me if anything is needed.