Hey! Your response is super appreciated as I really wanna figure this out. So I purchased. A new keyboard and I tried this - “rhgb quiet usbcore.a/uthorized_default=0 qubes.skip_autostart” And it did not work as I’m still stuck in the infinite loading thing. THANKSSS!!
Also, I deleted Plymouth and quiet, pressed enter then typed my password, then it says “Starting Plymouth-quit-wait.service - Hold until boot process finishes up…”
Then there are 4 lines of code that say “audit: type=???” (I don’t wanna say the specific number in case it reveals anything - I don’t know tech that well.)
Nothing has happened for the past 10 minutes or so. Just sitting at the same screen.
Ok, this basically tells us that you installed it on an external USB drive.
This is what’s happening:
- GRUB loads
- The Xen Hypervisor loads
- The Linux kernel loads
- The Initial Ramdisk loads, which contains USBGuard
(to protect dom0 from USB attacks during boot and while the machine is running)
- You then type in your correct password to decrypt the root partition
- USBGuard freaks out because GRUB told the initramfs to deny any and all USB access to dom0 (
usbcore.authorized_default=0), and stops theswitchrootfrom happening
(For completeness, switchroot is essentially the initramfs saying “right, everything looks good, all modules are loaded, all hardware is initialised, root partition, you take it from here…”)
@qubesishard, you will likely get a lot of people here advising you against booting Qubes OS from an external drive for this very reason 
I will say this:
You’re more than welcome to do it, but remember that by doing so, you will miss out on key features of Qubes OS, and get an inferior experience.
By booting from an external drive attached via USB, in order for your machine to actually boot successfully, your USB controller that the drive is attached to must stay in dom0. Whilst you will be able to attach block devices (partitions) to other qubes, you will not be able to attach USB devices (webcams, keyboards, game controllers, printers, etc.) to other qubes.
If you try and attach the USB controller that the boot drive is plugged into, Qubes OS will freeze/implode, and you’ll most likely need to power cycle your machine (i.e. cut the power and turn it back on again).
So, if you remove usbcore.authorized_default=0 from the GRUB parameters, yes, your installation should boot, but:
- You will not be able to take full advantage of USB passthrough
- Your dom0 might not be able to be fully trusted, since you could potentially contaminate it with a USB device
Either way, let us know how you go 
1 Like
- Ok you convinced me, I don’t wanna boot from. A external usb, how can I fix this and not boot from one?
- I tried to reboot, deleting what you told me to, and I didn’t get stuck on the infinite progress bar, but instead my screen is now just black and says “dracut-cmdline[428]: Warning: USB in dom0 is not restricted. Consider rd.qubes.hide_all_usb or usbcore_authorized_default=0.”
- THANK YOU SO MUCH! I LOVE YOU!
Do you see any other messages before “Starting Plymouth-quit-wait.service - Hold until boot process finishes up…”?
Is it the same as here?
What GPUs do you have in your machine (integrated and/or dedicated)?
Do you have multiple displays? To what GPU are they connected?
You can try to connect your display to another GPU if you have more than one.
Or you can try to reinstall Qubes OS with kernel-latest, there is a separate Qubes OS installer GRUB menu option for this.
Thanks for the reply apparatus! I only have 1 GPU, with 2 Displays both connected to my GPU. I will try to reinstall Qubes in the kernel now. Thank you brother!!! Love you
1 Like
How do I access kernel latest?
I don’t see that option Mr. Apparatus, only 3 options are “Qubes, with Xen hypervisor”
“Advanced options for Qubes (with Xen hypervisor” and “UEFI Firmware Settings”. When I click on “Advanced options for Qubes (with Xen hypervisor)” it then takes me to “Xen hypervisor, version 4.17.4”. Then it takes me to “Qubes, with Xen 4.17.4 and Linux 6.6.36-1.qubes.fc37.x86_64
It’s a Qubes OS installer boot options. You need to reinstall the Qubes OS.
I don’t know how I can. I literally can’t go back to windows anymore.
You don’t have the USB disk with Qubes OS installer that you used to install Qubes OS?
I do still have the USB Thumb drive - yes.
Then boot from it and reinstall the Qubes OS from there.
Ok genius apparatus, your great wisdom is much appreciated. I pressed the install from kernel option, some things popped up, that had the green OK, now my screen is just black but my computer is still on. Should I power cycle?
1 Like
So you can’t reach the installer home screen:
When you boot with kernel-latest, but you can reach it if you boot with default Qubes OS installer boot option?
I’m not sure why Qubes OS installer is not working for you with kernel-latest.
What CPU and GPU do you have?
No, my screen is now black and I’m gonna power cycle it. And I was able to reach that screen when I just did the test media and install option - yes. I have a 14900KF with a 4070 TI SUPER
ALSO! This may be important idk - I just tried to do the install and check media option (default one) and it failed at 004.8%. It says “[FAILED] Failed to start checkisomd5@dev-sda.service - Media check on /dev/sda.”
“dracut - initqueue[1686]: Job for checkisomd5@dev-sda.service failed because the control process exited with error code.”
“dracut - initqueue[1686]: See “systemct1 status checkisomd5@dev-sda.service” and “journalct1 - xeu checkisomd5@dev-sda.service” for details”
“dracut: FATAL: CD Check failed!”
“dracut: Refusing to continue”
“reboot: System halted”
The nouveau driver for your GPU is only supported starting with kernel 6.7:
- Nov, 2023: AD10x and GSP support merged in Linux 6.7.
NV194 (AD104) GeForce RTX (4070, 4070 Ti)
The default installer boot option (test media and install) is using kernel 6.6 so it’s not using nouveau.
But I don’t know why kernel-latest 6.10 is not working for you.
You can try to boot in your installed Qubes OS with nomodeset kernel command line option. Add it in the GRUB menu in the same way you did for qubes.skip_autostart.
That’s expected if you’ve created your installation media from Windows:
Note: Using Rufus to create the installation medium means that you won’t be able to choose the “Test this media and install Qubes OS” option mentioned in the example below. Instead, choose the “Install Qubes OS” option.
2 Likes
So what your saying is, I still remove “ usbcore.authorized_default=0”, but this time I put in “ nomodeset”
Your patience with me is appreciated so much more than you know and I truly mean it. I apologize im not that good with computers!