3

I have a problem which I can not solve.

I have a Raspberry Pi 4B with 4GB RAM. This worked until this morning without problems with a USB 3.0 stick from Transcend and with 64-bit Bullseye PiOS (desktop).

I then formatted the stick and reinstalled the PiOS with RPI-Imager on macOS 14.0. Since then, the Raspberry Pi no longer boots into the desktop.

Here's what happened:

  1. Rainbow splash screen
  2. mmc1: Controller never released inhibit bit(s) at the top left of the screen.
  3. Resizing root filesystem...
  4. Generate SSH key is displayed
  5. Fix PARTUUID is displayed for only a fraction of a second (I had to film my screen to read it)
  6. Restart in 5 seconds...
  7. The screen goes black and we start again from 1

Sometimes you can see the Raspberry Pi image for the desktop version which is displayed at normal system startup, for a second or so.

I then took another Raspberry Pi 4B with 2GB RAM for testing. This one shows the same problem all of a sudden (and never before).

What I have tried so far:

  1. Installed a fresh USB-Stick with the RPI-Imager -> same problem
  2. Deleted partitions from all USB-Sticks/SD-Cards, created MS exFAT partition and installed them with the RPI imager -> same problem
  3. Using the RPI imager, updated the bootloaders on both Raspberry Pi's. Both USB boot/SD card boot and SD card boot only. The process seems to work properly, but there is no green screen at the end, but the green LED is flashing constantly
  4. SD card installed with PiOS -> same problem
  5. 3(!) other power supplies (5V/3A, 5V/2,5A, 5V/4A) tested -> same problem
  6. Created USB-Sticks / SD-Cards on a Windows 11 computer -> same problem
  7. USB-Sticks / SD-Cards installed with Win32DiskImager (64-Bit Bullseye PiOS AND 32-Bit Bullseye PiOS) -> same problem

I'm sorry to say that I'm at a loss. Does anyone have an idea? Thanks a lot.

Improve this question
9
  • I'm confused - so you have 2 Pi4's and they both get stuck in boot loops - is that the right? Have you downloaded the latest Bullseye dated May 3rd 2023? Have you previously used Bullseye on these Pi4's? Commented Oct 3, 2023 at 17:58
  • Have you copy and pasted the following? raspberrypi.stackexchange.com/questions/143274/… Commented Oct 3, 2023 at 18:24
  • Does it work if you use a SD Card? Erasing/reformatting is just a waste of time because the installer overwrites the media. Commented Oct 3, 2023 at 21:52
  • So you never can complete the "First boot sequence". 1. Check the LED blink pattern and compare it to support.pishop.ca/article/… 2. Check the MD5 sum of the image you create the boot media from (It has been reported that corrupt downloads can cause erratic behavior) Commented Oct 4, 2023 at 9:06
  • 1
    @MatsK Thanks for the link. I receive 3 short blinks which is a "Generic failure to boot". I cleaned the USB-Sticks and SD-Cards with Diskpart from Windows and created an exFAT pertionin prior installing a fresh Bulleye Image. Commented Oct 4, 2023 at 10:50

2 Answers 2

Reset to default
2

My PI's are again working as expected. Long story short, I deleted the pre-configuration within the RPi-Imager and everything worked fine with an SD-Card after activating the config option hdmi_force_hotplug=1.

I replaced the pre-configuration and everything worked fine with the SD-Card again.

After this success, I installed the image to my earlier mentioned USB-Stick (with hdmi_force_hotplug=1). The first thing I saw was the message mmc1: Controller never released inhibit bit(s) on the screen. After 5 seconds or so, the initial boot process started. After finishing this process, my RPi performed a restart, did "something" and rebooted again. After the last boot, the RPi booted into the PiOS Desktop.

What I've learned is that the message

mmc1: Controller never released inhibit bit(s)

seems to be irrelevant and is only seen during USB-Boot.

Furthermore it's new for me that the actual Bullseye Image reboots twice after initial setup. All later startups do not reboot and are quicker.

And last but not leased during USB-Boot it seems that there is no activity to see on the green LED while loading the Desktop. While using an SD-Card you can see constant LED flickering until the Desktop has loaded.

Improve this answer
1
  • In my case, I just flashed a USB with Raspberry Pi imager saying no to custom settings. The Pi loaded fine with it. Then I shut it down, place the original USB drive in that had been causing problems (it was created with custom settings) and it booted fine. Commented Aug 23, 2024 at 17:22
0

enter image description herePhoto of boot screen

Confirmed. The error on Pi3B+

mmc1 controller never released inhibit bits

disappeared like magic after I installed another power supply. (Old originalPi 2.5A to New Plusivo or OriginalPi 3A) Please can someone confirm that this is a solution for the Pi4 (be careful not to get dirt on the power plug in the Pi)

Improve this answer
2
  • 1
    Your answer would be much more useful if you stated what Pi you have, what specification did your first PSU have and what specification PSU you changed to. Please edit and update your answer with the additional information (not in the comments). Thanks. Commented Apr 27 at 20:29
  • No error PI3B+ after a day after replacing the power supply... I think about how many times the home assistant restarted before it succeeded, especially when it was colder (typical electrolytic capacitor problem) Commented Apr 28 at 10:48

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.