For future readers considering it:
For its security to be functional QubesOS relies on hardware a lot. It is not a normal linux distribution that just works: check device compatibility first.
It is also likely to be a device issue. Or, more specifically, memory issue due to device issue. Check troubleshooting after installation and ask for help. Do not just search the internet.
Sad but true. Good stuff is on the forum (and chats).
You are installing type-1 hypervisor with fedora 37, fedora 40, debian 12, and whonix by default, some of it over tor. It cannot not be slow.
Qubes is a huge storage, memory and effort hog. It doesn’t have nested virtualization, gpu domain, and seamless gpu passthrough by default among many other things. This is a challenge, not a distro hop. Do not use it without fitting intent, being crazy, or having someone to help you. User discretion advised.
As long as we don’t have gpu domain, display shouldn’t be that hard to troubleshoot since it is managed by dom0: conventional display troubleshooting steps can work.
Once sys-gpu released, display secrets are hidden in sys-gpu. Checking forum is a good first step. Most help on the forum comes as commands. If you mean literal --help, it is not enough to troubleshoot a display without background knowledge. If you want to have docs baked into qubes, please bump this issue, I strongly agree that it must be at least an installable package in dom0, so users can read it even if something doesn’t work.
Justified.