Well, doing as you did, I used the same tool as you did. However…
I still get nothing but a black screen right after the boot sequence completes. On the serial console I get a login prompt, on the HDMI monitor after GDM service start., nothing on the HDMI monitor, in fact my monitor reports NO SIGNAL after about 30 seconds. The serial console shows a bit more services starting and the following, with a login prompt is:
[ OK ] Finished systemd-user-sess…ervice - Permit User Sessions.
Starting gdm.service - GNOME Display Manager…
Starting plymouth-quit-wai… until boot process finishes up…
[ OK ] Started rpc-statd-notify.s…m - Notify NFS peers of a restart.
[ OK ] Started gdm.service - GNOME Display Manager.
This is on the same hardware setup, that I can use Pi OS 11 ARM64, Manjaro ARM64, Ubuntu ARM64, SparkyLinux ARM64, and Kali ARM64, without issue. If it was a hardware issue, surely at least some of these other distributions would fail in like manner in some way.
To be sure, I have also tried multiple different SD cards, multiple Pi4B devices, etc., Still can’t get Fedora 37 ARM64 image as noted above to display any UI on the HDMI monitor. I see the same boot sequence you do, the same start up sequence you do, but I never get the HDMI monitor display result you do.
Is there any thing I can tweak or change in the config.txt file to force the HDMI configuration to a ‘safe’ mode, or set the Fedora image to a safe mode type of state? At this point open to suggestions, but have come full circle. In my case, Fedora ARM64 Does not work on Raspberry Pi 4, when other OSes work fine.