Yes - keyboard & monitor attached. No serial console for me.
When you setup the keyboard & monitor did you change the settings in the config files?
Note - The ARM flash image is configured for serial console at default
• If using HDMI & USB Keyboard: edit theuENV.txtfile and changeSERIAL-CONSOLE=ONtoOFF
• If using the serial console: edit theconfig.txtfile and addenable_uart=1to the end
I haven’t had time to try any other combinations or configurations yet
My final update for the moment because I’ve run out of ideas of what else to try. I switched to HDMI/Keyboard and disabled serial per the instructions. I could see that the kernel started to boot, but then settled into a loop showing:
invalid bus width
error -22 whilst initialising SD Card
I reflashed the image to the SD Card, but that didn’t make any difference. It doesn’t appear that U-Boot is not very happy with my hardware for some reason.
Craig
I tried with the serial console and I got an error like above in Post 11 and Post 12.
It may be a bug so I opened report 12680.
For me HDMI/Keyboard works A-OK.
Like four IPFire logos on a mostly blank screen?
EDIT: back to Serial Console for a moment.
The text (issue) in Post 11 & Post 12 are slightly different from my text. Your has this error: Bus xhci_pci: probe failed, error -110 but I don’t see that error. Odd!
U-Boot 2021.07 (Aug 09 2021 - 09:19:51 +0000) RPi4 - IPFire.
U-Boot 2021.07 (Aug 09 2021 - 09:19:51 +0000) RPi4 - IPFire.org
DRAM: 998 MiB
RPI 4 Model B (0xa03111)
MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
Port not available.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
"Synchronous Abort" handler, esr 0x96000044
elr: 000000000009df64 lr : 000000000009e4c8 (reloc)
elr: 000000003e36ef64 lr : 000000003e36f4c8
x0 : 000000003df5e800 x1 : 6f6f625f726f665f
x2 : 7665645f6e006900 x3 : 000000003e3d27d8
x4 : 000000003df5e860 x5 : 000000000000005d
x6 : 000000003e3d27e8 x7 : 0000000000000010
x8 : fffffffffffffff0 x9 : 0000000000000008
x10: 00000000ffffffd0 x11: 000000000000000a
x12: 000000000001869f x13: 000000003df40da8
x14: 000000003df40eb0 x15: 0000000000000002
x16: 000000003e37119c x17: 0cc49240c2e78984
x18: 000000003df4cd90 x19: 0000000000000060
x20: 000000003e3d2218 x21: 0000000000000030
x22: 000000000000000b x23: 000000003e3d2218
x24: 0000000000000001 x25: 0000000000000060
x26: 000000003df56660 x27: 000000003e3c6aab
x28: 000000000000003b x29: 000000003df3fef0
Code: b2400021 f9000481 f9400c01 f8410c02 (f9000c41)
Resetting CPU ...
resetting ...
I tried with the serial console and I got an error like above in Post 11 and Post 12.
It may be a bug so I opened report 12680.
Thanks, I wasn’t sure how to open a ticket. I just went ahead and added some comments.
For me HDMI/Keyboard works A-OK.
Do you get the same above errors with HDMI/Keyboard? Or something different?Like four IPFire logos on a mostly blank screen?
Different behavior. I get past the four logos. And then it goes into a spin as I mentioned in my last comment.
Is anything plugged into USB besides a keyboard?
FYI - I found a Dell keyboard that would not allow me to boot. For fun you may want to try some other keyboard…
I have a small touchscreen that plugs in to HDMI and USB. I can try without plugging in the (USB) touchscreen. With that said, I’m really most interested in working out booting without a monitor or keyboard. This device will sit in a utility room without a monitor or keyboard connected. While I can try to get a “clean” boot with things connected, it is really only useful to do that if it helps to debug the overall issues with booting.
My IPFire RPi3B+ runs without a monitor(HDMI) and keyboard (headless!). I used the monitor(HDMI) and keyboard for Setup only and then removed both for a headless setup. I don’t need them for booting.
This is what I see for the initialization boot on the RPI4B. The first screen goes by quick:
Then a one second pause…
and then I see LOTS of screens after that.
But it sounds like you don’t get this far…
EDIT: I can boot the RPi4B without a keyboard but it must have a monitor. I’ll try other RPi devices sometime in the next week…
Maybe an HDMI Dummy Plug (Display Emulator) might help - just a guess
I’m getting error -5 while initializing mmc card with the 8gb raspberry pi 4 over and over again works fine with manjaro linux though.
I do seem to get that far, but then goes into the loop complaining about mmc that I mentioned previously.
When you are using the monitor to boot, can you also see serial console? With a dummy monitor plug, it would be necessary to be able to get to the serial console.
In the end, the ideal situation would be a fix for the underlying issues, but I’m not sure I understand how difficult that is.
I am not sure I understand why you would need the serial console…
You can access the same info via SSH:
I was able to boot the RPi4B without the Dummy Monitor plug. I noticed the config file at /boot/config.txt include a few lines containing HDMI. After digging through the RPi config documents I found a setting that seems to work.
So I added hdmi_safe=1 and it seems to boot OK with and without a HDMI monitor.
Once booted, I can access the console via SSH.
Thanks for the info. It sounds like I can get things configured while connected to a monitor and then go from there. My primary concern with not having Serial console mode is if/when something goes wrong and the network is not functional. I had an issue recently where we had a power blip and without a network, I couldn’t troubleshoot.
That happened to me also when I had a hub/switch go bad (lighting strike).
Luckily I have a computer within 5 feet of my firewall box and I could plug direct from the computer to the green port.
With some sort of console ( monitor/keyboard or serial ) you have access to your system without networking. Also it is possible to watch the boot process.
I do not want to miss this in case of serious problems.
My latest update. I took the time/effort to set up a standard external monitor and keyboard with the goal of seeing if I could get through setup. However, it still fails part way through booting. I see @gabranth99 had a similar issue with an 8G Pi 4. Mine is with 4 gig of RAM. I’m wondering if the memory on device has something to do with this?
I ordered a Raspberry Pi 4 Model B - 4 GB RAM from Adafruit. And it arrived yesterday and it worked A-OK for me. I don’t see any of the errors above.
I’d suggest trying another SDCard or re-flashing (sorry. yes, again!)
I use these SD cards:
I also use the 16 GB cards and they work fine also.
What SD cards do you use?
from different internet searches for:
raspberry pi “error -22” whilst initializing SD card
This seems like it may be an adapter issue or might be a SD card issue. Most all of the
error -NN whilst initialising SD Card
fall into a similar solution.
I will have to look around. Unfortunately, I think my smallest card is 32G. I have a couple of different manufacturers, but not smaller.
I should add that I’ve gotten the same failures with 32G cards from two manufacturers, so thinking maybe more about size than brand?
32 GB is fine. Any size should work but I wouldn’t recommend anything too small.
