Just wondering why my attempt to move a working headless Fedora 34 build from a 2 GB rpi4 to a 4 GB rpi4 fails even to boot. In fact, it never even puts out the steady red LED. I copied the micro SD card (from the 2 GB pi) directly over USB and wrote the build to another SD card using dd using a set of commands that has always been reliable in the past.
Any thoughts, please?
On Sat, Jan 8, 2022 at 8:09 PM David W. Legg dwlegg@gmail.com wrote:
Just wondering why my attempt to move a working headless Fedora 34 build from a 2 GB rpi4 to a 4 GB rpi4 fails even to boot. In fact, it never even puts out the steady red LED. I copied the micro SD card (from the 2 GB pi) directly over USB and wrote the build to another SD card using dd using a set of commands that has always been reliable in the past.
Any thoughts, please?
Why not just physically move the SD card from one to the other?
It's ultimately hard to know why without including the commands you used as what you describe is a fairly high level overview.
Could you provide more details....
This will make it easier to help you.
Il giorno 8 gen 2022, alle ore 21:14, Peter Robinson pbrobinson@gmail.com ha scritto:
On Sat, Jan 8, 2022 at 8:09 PM David W. Legg dwlegg@gmail.com wrote:
Just wondering why my attempt to move a working headless Fedora 34 build from a 2 GB rpi4 to a 4 GB rpi4 fails even to boot. In fact, it never even puts out the steady red LED. I copied the micro SD card (from the 2 GB pi) directly over USB and wrote the build to another SD card using dd using a set of commands that has always been reliable in the past.
Any thoughts, please?
Why not just physically move the SD card from one to the other?
It's ultimately hard to know why without including the commands you used as what you describe is a fairly high level overview. _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
I've physically swapped Fedora ARM SD cards between RPi3 and RPi4 devices in my Pi cluster without any problems.
Are you certain your RPi4 4GB device has sufficient power? I've seen Pi devices with different USB peripherals not boot reliably if I don't have a good 5V 3A power supply connected to it.
I've sent the rpi4 back as faulty ,:( Thanks for your help, all. :D
On Sun, 9 Jan 2022, 17:12 John Walicki, johnwalicki@gmail.com wrote:
I've physically swapped Fedora ARM SD cards between RPi3 and RPi4 devices in my Pi cluster without any problems.
Are you certain your RPi4 4GB device has sufficient power? I've seen Pi devices with different USB peripherals not boot reliably if I don't have a good 5V 3A power supply connected to it. _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
So, this is the continuation of the above saga.
With a brand *new* rpi4, I made two different 32GB SD cards of different makes from both:
Fedora-Minimal-34-1.2.aarch64.raw.xz
and
Fedora-Minimal-35-1.2.aarch64.raw.xz
I did not fiddle with partition sizes or anything like that, but I did connect an HDMI monitor and keyboard/mouse USB dongle. No network. 5V from a known good PSU. I simply cut the cards with:-
# xzcat Fedora-Minimal-35-1.2.aarch64.raw.xz | sudo dd status=progress bs=4M of=/dev/sdf and similar for the F34 file. With both boots, after many minutes, I got this repeatedly in the journal:
fedora kernel: mmc0: invalid bus width fedora kernel: mmc0: error -22 whilst initialising SD card
Nothing very definite appeared when I googled for some of the key words.
So, I have here two systems that both boot from an SD card, but then get confused about the SD card they have just booted from. Weird :(
Any insights appreciated, as usual. Thanks. :D
So, here is my (temporary) solution, as reported in Bugzilla bug https://bugzilla.redhat.com/show_bug.cgi?id=2011423
So my 4GB rpi4 refused to boot with the symptoms described about, i.e. mmc0 errors.
I also found that Fedora-Minimal-34-1.2.aarch64.raw.xz and Fedora-Minimal-35-1.2.aarch64.raw.xz also failed to boot. So, I downloaded the latest PIOS image, cut an SD card, and (hey presto) it booted (so no problems with my pi, psu or other hardware).
However, there is a hint in the Fedora aarch64 wiki that one needs to remove /boot/dtb to get Fedora to boot (and also in the Bugzilla bug itself)). The only problem was that my Fedoras 34 and 35 both fell over without ever creating /boot :( So, here is what I did from my root history on my x86_64 Fedora desktop box:-
1002 # Put an SD card in USB card writer/reader. 1003 arm-image-installer --image=Fedora-Minimal-35-1.2.aarch64.raw.xz --target=rpi4 --media=/dev/sdX # Your X will vary. Use journalctl -f
1005 mkdir /mnt/usb 1006 mount /dev/sdX2 /mnt/usb/
1007 # You have remove the dtb soft link and the directory it point to:- 1008 rm /mnt/usb/dtb 1009 rm /mnt/usb/dtb-5.14.10-300.fc35.aarch64/ 1010 rm -rf /mnt/usb/dtb-5.14.10-300.fc35.aarch64/
1012 umount /mnt/usb 1017 gparted /dev/sdX& # Usegparted to enlarge /dev/sdf3 partition so that the whole image is < 10MB. 1018 parted /dev/sdX
1019 # Take a copy of the SD Card image and check that all partitions are actually there:- 1020 dd if=/dev/sdX of=Fedora-Minimal-35-1.2.aarch64-rm_dtb-size-10000MB.img status=progress bs=1M count=10000 1021 1023 fdisk -l Fedora-Minimal-35-1.2.aarch64-rm_dtb-size-10000MB.img 1024 # Put card into rpi4 and boot.
This works for F34 and F35 on my 4GB rpi4. I never had to do all this previously, but maybe these instructions will help some-one :)
Meanwhile, the Fedora wiki needs to be updated, and/or the Fedora .xz file images need to be fixed by some-one with the superpowers.
:D
On Thu, Jan 13, 2022 at 11:12 AM David W. Legg dwlegg@gmail.com wrote:
So, here is my (temporary) solution, as reported in Bugzilla bug https://bugzilla.redhat.com/show_bug.cgi?id=2011423
So my 4GB rpi4 refused to boot with the symptoms described about, i.e. mmc0 errors.
I also found that Fedora-Minimal-34-1.2.aarch64.raw.xz and Fedora-Minimal-35-1.2.aarch64.raw.xz also failed to boot. So, I downloaded the latest PIOS image, cut an SD card, and (hey presto) it booted (so no problems with my pi, psu or other hardware).
However, there is a hint in the Fedora aarch64 wiki that one needs to remove /boot/dtb to get Fedora to boot (and also in the Bugzilla bug itself)). The only problem was that my Fedoras 34 and 35 both fell over without ever creating /boot :( So, here is what I did from my root history on my x86_64 Fedora desktop box:-
The 'dtb' symlink is located on the second partition of the image.
1002 # Put an SD card in USB card writer/reader. 1003 arm-image-installer --image=Fedora-Minimal-35-1.2.aarch64.raw.xz --target=rpi4 --media=/dev/sdX # Your X will vary. Use journalctl -f
1005 mkdir /mnt/usb 1006 mount /dev/sdX2 /mnt/usb/
1007 # You have remove the dtb soft link and the directory it point to:- 1008 rm /mnt/usb/dtb 1009 rm /mnt/usb/dtb-5.14.10-300.fc35.aarch64/ 1010 rm -rf /mnt/usb/dtb-5.14.10-300.fc35.aarch64/
You do not need to delete the kernel dtb directory (dtb-5.14.10-300.fc35.aarch64), just the 'dtb' symlink.
1012 umount /mnt/usb 1017 gparted /dev/sdX& # Usegparted to enlarge /dev/sdf3 partition so that the whole image is < 10MB. 1018 parted /dev/sdX
1019 # Take a copy of the SD Card image and check that all partitions are actually there:- 1020 dd if=/dev/sdX of=Fedora-Minimal-35-1.2.aarch64-rm_dtb-size-10000MB.img status=progress bs=1M count=10000 1021 1023 fdisk -l Fedora-Minimal-35-1.2.aarch64-rm_dtb-size-10000MB.img 1024 # Put card into rpi4 and boot.
This works for F34 and F35 on my 4GB rpi4. I never had to do all this previously, but maybe these instructions will help some-one :)
There seems to be some difference in Pi's, we tested the Fedora 34 and 35 images on various Raspberry Pi 4's - 2GB, 4GB and 8GB. The only board which required the firmware provided dtb was the Raspberry Pi 400. From the bug, someone else hit it with the Raspberry Pi 4 8GB, but I was unable to reproduce. We compared the eeprom bootloader versions, and both were running the same version (c2f8c388 - Apr 29 2021).
Have you tried a different mSD card?
Paul
Meanwhile, the Fedora wiki needs to be updated, and/or the Fedora .xz file
images need to be fixed by some-one with the superpowers.
:D _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Once upon a time, Paul Whalen pwhalen@redhat.com said:
There seems to be some difference in Pi's, we tested the Fedora 34 and 35 images on various Raspberry Pi 4's - 2GB, 4GB and 8GB. The only board which required the firmware provided dtb was the Raspberry Pi 400. From the bug, someone else hit it with the Raspberry Pi 4 8GB, but I was unable to reproduce. We compared the eeprom bootloader versions, and both were running the same version (c2f8c388 - Apr 29 2021).
Have you tried a different mSD card?
Hmm, I picked up a Pi4 4G recently, and was also unable to boot Fedora from the SD card (had to use a USB adapter instead). Same error as in this thread, tried multiple cards (including a card from a Pi3), no different.
Yes, Paul, I tried 2 different makes of card and four different cards, 3 different power supplies, and 2 different ways of writing the cards.
On 13/01/2022 20:59, Paul Whalen wrote:
Have you tried a different mSD card?
I suspect that, with the shortage of chips from China, we are dredging the bottom of the barrel and are buying some Raspberry Pis with anomalous, early or unusual hardware or firmware behaviour. :(
On 13/01/2022 21:07, Chris Adams wrote:
Hmm, I picked up a Pi4 4G recently, and was also unable to boot Fedora from the SD card (had to use a USB adapter instead). Same error as in this thread, tried multiple cards (including a card from a Pi3), no different.
-
Chris Adams -
David Legg -
David W. Legg
-
John Walicki -
Nathan Giovannini -
Paul Whalen -
Peter Robinson