Fedora issues on raspberry pi

APTI

Well-Known Member
Joined
Dec 20, 2022
Messages
1,102
Reaction score
887
Credits
9,437
I am finding a problem with the raspberry pi and fedora. They have changed something in fedora 42 that causes massive issues. Well maybe not massive but still a problem.
I have done this on 3 RPI 4B. Each of the 3 have the same exact issue. They get a -110 error card not responding to voltage select. Now these are all working on fedora 40 and 41. The upgrades fail to work because of this issue. I went to redhat/fedora bugzilla and really no help there. It is like they don't want to acknowledge the issue and blame me.
I guess what I need to figure out is... is it actually me? or is fedora not supporting RPI any longer? I love fedora on the RPI. It is smooth and works great. Until now.

I have worked on this for a few months and can't figure out anything other than switch to PI OS. Which I would prefer not to do but may have no choice.

Any ideas out there? hopefully things I have not tried?
 


They get a -110 error card not responding to voltage

I am curious how the OS would know this? Have you tried other OS versions?
 
I am curious how the OS would know this? Have you tried other OS versions?
this happens in the boot up. But fedora 41 comes up fine. as does raspberry Pi OS. same hardware.
 
Have you tried Fedora 43?
nope. I try to stay down one. I am considering it though. The problem happens on reboot when I upgrade. or if I put a fresh install on the chip with the recommended balena etcher.
 
Oh no, not problems with fedora.
1764107258540.gif
 
I am finding a problem with the raspberry pi and fedora. They have changed something in fedora 42 that causes massive issues. Well maybe not massive but still a problem.
I have done this on 3 RPI 4B. Each of the 3 have the same exact issue. They get a -110 error card not responding to voltage select. Now these are all working on fedora 40 and 41. The upgrades fail to work because of this issue. I went to redhat/fedora bugzilla and really no help there. It is like they don't want to acknowledge the issue and blame me.
I guess what I need to figure out is... is it actually me? or is fedora not supporting RPI any longer? I love fedora on the RPI. It is smooth and works great. Until now.

I have worked on this for a few months and can't figure out anything other than switch to PI OS. Which I would prefer not to do but may have no choice.

Any ideas out there? hopefully things I have not tried?
Did you try: sudo rpi-eeprom-config --edit
BOOT_UART=1
POWER_OFF_ON_HALT=0
BOOT_ORDER=0xf461
psu_max_curent=5000
 
Did you try: sudo rpi-eeprom-config --edit
BOOT_UART=1
POWER_OFF_ON_HALT=0
BOOT_ORDER=0xf461
psu_max_curent=5000
I did a whole bunch of edits to uboot and nothing worked. this includes manual voltage setting. so something in uboot is causing the issue. I am now not the only one that is seeing it. I can confirm the issue persists in fedora 43. Even a fresh install has the issue and upgrades from fedora 42 to 43 fail due to the issue.

You changes look a bit different. Where do you do them? I am assuming that fedora has to be running, judging from the sudo command. You can't get into any OS, you can only get to uboot prompt.
 
I did a whole bunch of edits to uboot and nothing worked. this includes manual voltage setting. so something in uboot is causing the issue. I am now not the only one that is seeing it. I can confirm the issue persists in fedora 43. Even a fresh install has the issue and upgrades from fedora 42 to 43 fail due to the issue.

You changes look a bit different. Where do you do them? I am assuming that fedora has to be running, judging from the sudo command. You can't get into any OS, you can only get to uboot prompt.
Terminal . Have you tried PINN for multi boot? Are you writing image with Imager or Fedora media writer?
 
Terminal . Have you tried PINN for multi boot? Are you writing image with Imager or Fedora media writer?
fedora media writer and download the arm version of fedora. there is no multiboot. apparently it goes to uboot which fails then sends to fedora to boot up. I can't go into terminal to do anything because linux never starts, not even in CLI mode. In fact linux does not even begin to start, it fails in uboot.
 
I have used Fedora MW in the past, but my next suggestion would be to create your image using Raspberry Pi imager and select the custom image from your downloads. The Raspberry Pi has a unique boot process and I'd suggest this is worth trying if you haven't.
 

Attachments

  • Screenshot 2025-12-31 115854.png
    Screenshot 2025-12-31 115854.png
    49.1 KB · Views: 58
I have used Fedora MW in the past, but my next suggestion would be to create your image using Raspberry Pi imager and select the custom image from your downloads. The Raspberry Pi has a unique boot process and I'd suggest this is worth trying if you haven't.
tried that this morning and same issue. the problem is in uboot that comes with fedora. unless they fix it or somebody knows how to instruct me to fix it. I doubt it will work on the PI. Seems to be a problem with not just 1 pi but all of them. 3 Pi all same issue. different SD cards
 


Follow Linux.org

Members online

No members online now.

Top