Bug 2230139

Hardware: RP3 with standard std Raspberry 7" touchscreen monitor that uses the display cable (not HDMI). Works with the Raspbian SD so the hardware is functional. Both are current Raspberry product, not 3rd party parts. I have a regular USB keyboard plugged in. I added the keyboard after the first failed boot. Keyboard works since GRUB responds.

I used Fedora 38 Workstation and KDE and got the same symptoms.

The image boots just fine, shows the UBOOT screen including the little boat graphic and continues into GRUB. I've tried both the kernel and uboot edit options. The uboot option doesn't work but it says so (not supported) and returns properly to the main menu so that is not really a fault at this point. GRUB also displays odd chars instead of the character graphics box lines usually seen on x86. Also a minor point.

Boot continues into the kernel load and systemd start. Systemd progresses  through kernel config, pivot root and various service starts. It is fine up to the point where graphics **should** start. The screen then slowly fades into all-white vertical strips. Unfortunately, it happens fast enough that I can't see the last lines plymouth puts up. Plymouth does not put up a splash screen like the x86 version. I see the boot progress that is "normally" hidden unless I type ESC.

I get the same result with either the Gnome based Workstation or the KDE spin so I suspect something in the switch to graphics, i.e. wayland starts?



Reproducible: Always

Steps to Reproduce:
1. Using current download .raw.xz file burn an image to the sd with arm-image-installer. Install the sd into the slot and power up
2. Let GRUB select the kernel (first menu item)
3. watch boot progress. Once the white screen appears, nothing else responds.
Actual Results:  
The screen slowly turns white (the rp version of the blue screen of death). Nothing responds to the attached USB keyboard. I haven't gotten far enough to have a live net with ssh or telnet. At this point, I unplug the power. Rinse and repeat.

Expected Results:  
It should have booted up to the new installation setup screen.

The only log file with any content is /var/log/boot.log (18K). I tried reading it with journalctl --file=boot.log but failed with "Failed to open files: Bad meessage". I'm assuming that the binary file is arch specific and I'm trying to read it from the sd card on my x86-64 workstation. I'll save the log just in case.