[RPi4] [LE 9.2.6] Stuck at boot

  • Hello,

    Since few days, my Libreelec refuse to start. It often gets stuck on bootscreen "LibreElec (official) : 9.2.6".
    Sometimes, it goes as far as "reached target system time synchronized", but stop here...

    I'm on Raspberry Pi 4 (4GB), and problem is the same if I try to install clean version of Libreelec on a new SD card...

    Can anyone could help me please ?

  • This is unusual, and I suggest to provide a link to a complete kodi.log.

    To rule out a hardware defect, you can also try a different OS, like Raspbian.

    Flexin' vinyl, jammin' break beats. 8)

  • Is this an installation with added/changed settings in the config.txt file. Try starting up with the default config.txt file.

    Also, try a fresh install anyway with the default English language setting (I know, you French, hehe...), but it could be a language setting problem.

  • Thanks for your help :)

    I already tried to start from fresh install on brand new SD card, but problem is same : ok for first boot, but if I shutdown my system, it doesn't start : stuck at "Librelec 9.2.6 (official)"... :(

    My config.txt is the same as original :

  • I believe that I am having the same problem. It's a brand new RPi4 2GB model and a fresh Libreelec 9.2.6 install. Occassionally, it seems to boot up fine. But most of the time it appears to hang at the step saying "Reached target System Time Synchronized." It isn't actually hung, because I can still SSH in to it and get a command prompt or access the files.

    I've attached a kodi_logs.zip with 4 different kodi.log files. 1 from a successful boot and 3 from failed ones.

    Also, when it is "hung", if I connect and issue a reboot command, it shows 3 services running a stop job. One is kodi and that one usually completes. The other 2 are: Argon One Fan and Button Service and Broadcom sdio firmware update for BCM43430A1. Those alternate for a while. Then the Argon One service stop completes and it goes through stopping more services. Then after the Stopped Login Service, It starts showing the "A stop job is running for Broadcom sdio firmware..." again. Eventually that seems to complete or timeout and it proceeds to "Reached target Reboot." It doesn't actually reboot at that point. And if I power off the system and power it back on, the "hang" just repeats.

  • I have exactly the same problem. I'm using a Raspberry Pi 4B (4GB) with an e-marked USB-C 18W power supply and a wired Internet connection.

  • I would try to boot from an USB Flash key (or USB/SATA adapter) instead of SD card.

    Make sure you have a fresh bootloader / VL805 firmware installed, you may also need to tune up the bootloader options.

    Read carefully here (including all links published there): Raspberry Pi 4 libreelec not booting

  • I installed Kodi 18.7 on Raspberry Pi OS and it is working very well. It seems to be a problem with LibreELEC, not Kodi?

  • Hello,

    I installed LibreElec 9.2.6 and RecalBox 7.1.1 in dual boot on my SD card, with PINN (similar to NOOBS, but more OS possible). Everything seems to be working fine, my problem with LibreElec has not reappeared for a week...

    Maybe a simple LibreElec install with PINN can resolve issue ?

  • Maybe similar problem here, but only occasionally. Most of the time, it works flawless, but sometimes I get this:

    [Time] Timed out waiting for device /dev/serial1

    [Depend] failed for Broadcom sdio firmware update for BCM43430A1

    [Failed] Failed to start Load Kernel Modules.

    See 'systemctl status systemd-modules-load.service' for details.

    Mounting Kernel Configuration File System...

    Starting Apply Kernel Variables...

    [OK] Mounted Kernel Configuration File System.

    [OK] Started to create list of required static device nodes for the current kernel.

    [Failed] Failed to start Apply Kernel Variables.

    See 'systemctl status systemd-modules-load.service' for details.

    [***] (3 of 4) A start job is running for wait for Kernel Time Synchronized .

    Startup works for weeks, then this is happening several times in a row. Trying again later works again. Any ideas? Maybe a thermal issue?