Posts by HiassofT

  • LibreElec v11 on RPI3 won't start

    Meestor_X thanks for the new log, this looks fine now.

    The next step will be that you create a bug report on the RPi linux repo here https://github.com/raspberrypi/linux/issues

    The key point to creating a useful bug report is to provide as much as useful information as possible upfront so the devs can unterstand, reproduce, analyze and then fix the issue.

    RPi devs use a standard issue template that you have to fill out and provide the necessary info. Best have a look at it first, then take your time to collect the info and fill it out and submit it once you have all the info.

    Check through the items I listed here RE: LibreElec v11 on RPI3 won't start and include all this info in the bug report.

    I'd suggest using a meaningful title like "RPi3 boot regression with Sandisk Extreme Endurance 256GB since kernel 5.15".

    Start with mentioning boot issues with current RPiOS bullseye image and post the error message you got on screen and/or attach a picture of it.

    Also mention that you get the same issue with LibreELEC and kernel 6.1 and attach the dmesg you captured - that should be very helpful to devs.

    Run "raspinfo" on the working RPiOS legacy / Buster image to collect the info the devs usually want.

    Mention the results of rpi-update to latest 5.10 and first 5.15 kernels/firmwares, as mentioned in my list.

    Also feel free to post a link to this forum thread as a reference.

    Very likely RPi devs will then come back to you with more questions or will ask you to test some kernels with rpi-update - be patient, depending on their current workload this could take anything from a few minutes to months.

    If you want to proofread or check your bug report before you submit it on the RPi repo then just post a draft of it here in this thread and I'll have a look and comment on it.

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    The power supply is only half of the important bits, the other half is cables.

    Lots of power supplies don't maintain to provide stable 5V under load (and you might not see the dips with a multimeter, all computers nowadays can generate very short current spikes when the CPUs have lots of stuff to do and you'll see the voltage drops only with a scope - been checking that 10+ years ago on original RPi).

    Also lots of USB cables are poorly made, have thin 5V and GND strains, thus a high resistance and drop A LOT of (milli-)volts under high currents. Finding proper cables isn't easy (most of them are just crap).

    So, to summarize, if you don't want to pay the 7 bucks (or whatever they cost nowadsays) for an official RPi power supply you are going to have to endure a lot of pain and spend a lot more money on chargers/power supplies and cables until you find a working combination.

    Plus, users with power supply issues who don't understand that simple fact that a computer won't work without proper powering (would your car run properly if you filled in the wrong fuel?) have cost us developers (and RPi engineers) enormous amounts of time that we could have better spent otherwise.

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    RPis don't "always" complain about low power, only when the power is too low - which is about the worst thing you can do to an RPi as it is known to cause all sorts of problems.

    I have about two dozens of RPis here, starting from the very first RPi to RPi4 and RPI400 and none of them reports power problems when powered by the official RPi power supplies.

    I've had lots of problems though with phone chargers, USB hubs and 3rd-party power supplies in the very early days before RPi started shipping their official power supply. Since then I retired all those crappy devices and switched to official power supplies and never had any issues again.

    I suggest you do the same thing.

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    You are still having power issues

    Code
    <2>[    5.388985] hwmon hwmon0: Undervoltage detected!
<6>[    5.462544] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
<5>[    5.471394] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
<3>[   13.708922] mmc0: timeout waiting for hardware interrupt.

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    The log is complete now, however the log shows you are having power problem - and the mmc issues start right after the first undervoltage message

    Code
    [    5.395065] hwmon hwmon0: Undervoltage detected!
...
[   13.714953] mmc0: timeout waiting for hardware interrupt

    As I wrote above you need to fix the power issues first, no need to dig any further before that as the issues are very likely correlated.

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    Adding log_buf_len=4M to cmdline.txt didn't seem to have worked, the log is still cut off. Make sure everything is on the same line and if you edited the file on Windows use Notepad++ or some other editor that can cope with unix line endings - windows editor adding windows line endings usually cause havoc.

    However, I spotted a more serious issue in your first dmesg, your RPi is suffering from power problems. You need to fix this first, use the official RPi power supply, power problems are usually causing the exact same issues you are experiencing.

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    Thanks for the log, I see mmc diagnostic errors in there but unfortunately the beginning of the log is missing.

    Can you please add log_buf_len=4M to the end of cmdline.txt (everything must be on a single line, so add that just with a space separated from "quiet") and repeat that check?

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    Thanks for checking, this is already useful information!

    You are going to need to create a bug report on https://github.com/raspberrypi/linux/issues but before you do that it's best to double check, take notes of the exact steps and run an additional test with LibreELEC to collect some more info:

    Do a clean installation of LibreELEC 11.0.0 and grab a FAT formatted USB pendrive or harddisk (size doesn't matter, just that it's formatted with FAT so we can write boot logs to it).

    Boot up your RPi3 with just the LE sdcard, the USB pendrive, keyboard and monitor connected.

    When you get the "cannot mount" message run the following commands to mount your pendrive and save kernel log:

    Code
    mount /dev/sda1 /storage
dmesg > /storage/dmesg.txt
umount /storage
poweroff

    If you get some errors from these commands please post them here (or just take a picture with a camera). If everything worked you should have a file "dmesg.txt" on your pendrive. Please attach it here, then I'll have a glance through it if I can spot anything.

    Please also verify the steps you did to test with RPiOS - best do them again to double check:

    1. A clean installation of the current "Bullseye" RPiOS (2023-02-21-raspios-bullseye-armhf-lite.img.xz) doesn't boot. You should see some error messages on the screen, please take a picture of them with a camera

    2. A clean installation of the legacy "Buster" RPiOS (2023-02-21-raspios-buster-armhf-lite.img.xz) boots fine.

    3. running "sudo rpi-update 39821d33e777cde9ba1a3cc8a73cfdd62fbbd2de" "sudo reboot" works fine and "uname -a" show it's running kernel 5.10.95-v7+

    4. running "sudo rpi-update 9c6362635308cb3034d22f42daf9bfda1e3d36de" "sudo reboot" results in a non-working boot - a picture of the error messages on the screen would again help.

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    I think it would be best to start with an RPiOS buster/legacy lite image (using kernel 5.10) from here, that should boot fine

    Operating system images – Raspberry Pi
    From industries large and small, to the kitchen table tinkerer, to the classroom coder, we make computing accessible and affordable for everybody.
    www.raspberrypi.com

    Then use rpi-update to update to newer firmware/kernel versions. You can run "rpi-update GITHASH_OF_RPPI_FIRMWARE_RELEASE" to update to a specific firmware/kernel version.

    Take the githashes from here:

    Commits · raspberrypi/rpi-firmware
    Firmware files for the Raspberry Pi. Contribute to raspberrypi/rpi-firmware development by creating an account on GitHub.
    github.com

    You may want to start with rather old versions, eg the latest 5.10 version (go back several pages on the github page) which would be the 5.10.95 kernel from Feb 2 2022 with githash 39821d33e777cde9ba1a3cc8a73cfdd62fbbd2de - so run "rpi-update 39821d33e777cde9ba1a3cc8a73cfdd62fbbd2de"

    If that works, check with the next newest version which switched to kernel 5.15 on Feb 4th.

    If that works, too, go forward in time eg a month each until it stops booting, then reinstall from scratch and try with a version between the last working and the broken one. Repeat that until you narrowed it down to version X working and next one broken - that information will help RPi devs (and also us) a lot since it's usually a small set of changes which we'll have to look into (unless it was the switch from 5.10 to 5.15 - but still the info that it broke there will be helpful).

    I'm not aware of any issues with SD cards ATM, but that doesn't mean much. It could be very specific to your SD card (and Sandisk produced a variety of 256GB cards with different speed classes, so the exact model number might matter, too).

    And unfortunately searching for SD card issues in forums (or the web) is quite useless as tons of users reporting issues either had worn out or counterfeit cards, power problems, trashed filesystems because of unclean shutdowns, issues because of (too high) overclocking and whatnot - so the search turns up tons of non-issues and trying to finding actual issues in there is like finding a needle in a haystack...

    I certainly wouldn't rule out that you might have hit an actual issue that no one experienced so far (or described in enough detail so it could be investigated) - I hit an odd issue on RPi4 a few month ago - SD card wasn't properly reset on reboots under certain conditions so cold boot worked, but reboot not (that should be completely unrelated to your issue though).

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    On RPi2/3 the kernel is 32bit, the official LE11.0.0 release uses kernel 6.1 (currently it's 6.1.19 on latest nightly).

    LE10 uses kernel 5.10 (5.10.110 on latest LE10 build).

    The earliest LE11 nightly build, 20220618, uses kernel 5.15.45.

    You can look up the exact state the nightly was build from via the githash at the end of the image (eg b78941a for the 20220618-b78941a image) and feeding that into github. eg:

    LibreELEC.tv/package.mk at b78941aa4a4795fdc3c3dbcadd6216ce4a102dba · LibreELEC/LibreELEC.tv
    Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.
    github.com
    Code
      raspberrypi)
    PKG_VERSION="6b945e6f05d5cb0a299dbbb9bdd285aff330a204" # 5.15.45

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    frakkin64 no, we don't publish stats, they are rather boring anyways as they didn't change too much over the years (total RPi userbase always was in the 70-80% ballpark, only a few shifts between RPi1, 2/3, 4 over time).

    And, yes, forum posts are only about issues, the users without problems are mainly silent - except for some rare "thank you"s here and there.

    OFC there's still a significant amount of RPi2/3 users on LE9 (because of HEVC) and the absolute number of RPi2/3 installations is still very large.

    And we also see still lots of other devices on older LE versions, most likely because they still "work just fine" - so no need to upgrade.

    Chip crisis prevented lots of users from upgrading to RPi4, this might change in the next half year when RPi4 production (hopefully) ramps up and shops can stock them again. So I expect to see RPi2 (which is already down to about 5%) and RPi3 installations to decline in numbers and RPi4 to increase.

    so long,

    Hias

  • LibreElec v11 on RPI3 won't start

    Quote from frakkin64

    I don't know what the installs look like with LE11, but the impression from the release notes is that most RPi3 users may not be upgrading due to the loss of HEVC accelerated decoding.

    The number of RPi2/3 users on LE10 and LE11 is actually quite high, during the last year the overall userbase distribution has been quite stable at roughly 40% RPi4, 30% RPi2/3, 20% Generic/x86, 10% everything else.

    LE11 is quite new which means we have roughly 5 times as many LE10 users as LE11 users, but still this means quite a lot of LE11 RPi2/3 installations.

    I'd also recommend testing with RPiOS and current "rpi-update" kernel, this will be the same as current LE11 nightly build and if there's an actual issue with the mmc driver (which is not caused by wearing out SD card, overclock, undervoltage etc) then RPi engineers would be the ones who could analyze and fix the issue - so posting on RPi forums would be best.

    Personally I've never had such an issue on RPi2/3 (mainly using Sandisk Extreme and Extreme Pro 32GB SD cards here).

    so long,

    Hias