Ahh, sure! 
I didn’t expect this to be a short cut.
Let me know if there’s anything I can help the team with. In the meantime, I will continue playing with my RPi5 devices and will test them on F44 from stability standpoint.
Hi @pbrobinson ,
I’ve been testing your Fedora 44 KDE spin. Unfortunately, I’m running into a kernel panic when booting from the SD card, which is the same issue I encountered with my own installation.
If your Wi-Fi driver works on the SD card, you might want to try my install script. I’d suggest adding the serial package as well, so we can trace the kernel panic via the USB serial port during a basic prompt installation.
Along with that, I’d like to share my NVMe install script for others to try.
How to use it:
Take a running Fedora instance on an SD card, run the script (for example in /home), and answer the prompts. In about two minutes, the script sets up a fresh Fedora installation on your NVMe or USB drive. Conversely, if your system is already running on NVMe, you can use the script to create a clean SD card image with a simple prompt login.
Have fun testing it!
aarch64-fedora-nvme-install-v1.3.sh
With this script, you can find out where the ‘hitch’ is without any Window Managers (WMs) getting in the way, as it installs a purely prompt-based Fedora.
I encountered these same kernel panics in Fedora 43 because the correct drivers were missing. I’m seeing the same crash in your Fedora 44 KDE spin after a while. This usually stops happening once the kernel can correctly access and load the proper drivers. However, the Wi-Fi drivers first need to work reliably and be able to save their state to the SD card. Once that’s working and you have online access, the script can pull the original RPMs directly from the Fedora repositories for the installation.
Happy bug hunting and happy tinkering!
Best regards,
Blacky