I’m getting the boot loop everytime I don’t use a keyboard and display. I configured ipfire fine via HMI and wanted to use it mobile without display and keyboard. No display, no keyboard → boot loop. Display and keyboard connected - boots fine. Weired and not useable!
Good to know. Should be mentioned in the wiki.
did it work?
Yes it worked. No boot loop anymore. So I updated the rasp pi4 article.
1 Like
@arne_f - Is there anything else I can try to test out? I didn’t see any associated updates in the most recent test version, but I may have missed it. In the end, I could always swap my two Pi 4’s and probably get up and running. I had been holding off doing that in order to allow for testing more combinations, but I don’t know what else I can try? Anything else I can do to help?
Craig
One more interesting data point. I found out that Ubuntu is using u-boot as well. I grabbed the 20.04 (desktop) image, flashed it to an SD card and tried to boot it up. I’m seeing exactly the same error code loop there as I’m seeing with IPFire. I will update the IPFire ticket with this new information and I will go ahead and open a bug report in u-boot as well.
1 Like
This is strange because i use ubuntu 20.04 on an 8GB RPi4 to built the IPFire image.
Maybee there are also different 8GB hardware revisions.
I honestly don’t know at this point. While I’m fairly technical, u-boot is way lower level than I generally deal with and I don’t really know how else to help.
Hi, i’m new to Ipfire and Raspberry and i’m facing the same problem
invalid bus width
error -22 whilst initialising SD Card
And really don’t know what to do, i’ve tried flashing it many times using different pieces of software and still getting the same error
i have the new board rev 1.4
which models do you have?
I have Rev 1.2 as 2GB and 4GB version.
Rev 1.4 has an important hardware change. The VIA VL805 has no firmware EEPROM anymore so the bootloader must initalize it before it try to use it.
I have tried to update u-boot to 2021.10 rc5 which now crash on all my RPi 4 boards.
https://people.ipfire.org/~arne_f/highly-experimental/u-boot-2021.10-rc5/
so is no solution.
Is it worth me downloading and trying on my Pi or is it completely busted?
I did try to post to their mailing list about this issue, but my post has so far not cleared moderation. It is unclear to me how to interact with the u-boot team to even log this issue.
Craig
Hello,
maybe that’s a helpful hint.
https://forums.raspberrypi.com/viewtopic.php?t=319125
https://archlinuxarm.org/forum/viewtopic.php?f=67&t=15422
According to this threads i have modified the files boot.cmd and boot.scr and ipfire boots up until setup with a revision 1.4 board.
- booti ${kernel_addr_r} ${ramdisk_addr} ${fdt_addr_r};
+ booti ${kernel_addr_r} ${ramdisk_addr} ${fdt_addr};
- booti ${kernel_addr_r} - ${fdt_addr_r};
+ booti ${kernel_addr_r} - ${fdt_addr};
But after that it doesn’t go any further.
The keyboard does not work or the system hangs.
Regards
Michael
This seems like a very positive bit of insight!
Considering the popularity of RPi 4 boards, should a note be put on the wiki, to the effect that “newly purchased boards are currenly not working” ?
there is already a note:
True - but newbies might not be aware of whether rev 1.4 is old, new or somewhere in between nor might vendors be aware of what rev they are selling, because there appears to be no relevant markings.
IPFire Project won’t endear itself to prospective users if many buy a new device, only to find that it might not be supported any time soon.
It isn’t ALL “newly purchased boards”. My RPi4B 4GB RAM model is brand new and just purchased last month. And it works A-OK.
Feel free to update the IPFire Wiki as you see fit. It is open to the IPFire community for reading and writing.
Probably dependent on the stock that a supplier has so newly purchased may still be an old hardware version if the stock is not so new.
Unfortunately if Raspberry don’t put a hardware version number on the board then it is just a guessing game.