I’d just like to say a few things:
- Legacy most does not mean USB mode. Legacy mode means that the BIOS will look for instructions on the first 512 bytes of the boot disk for “what to do next”
- The Qubes OS ISO should be able to boot in Legacy and UEFI mode.
- There’s no hardware or firmware-related reason why Legacy mode should work over UEFI. People just prefer one over the other because of “personal preference” (I didn’t know how else to describe “I don’t trust Microsoft to boot my computer and be honest about it!” )
- These are the modules that failed to load, and I assure you that they’re not what’s causing this error:
It depends on the BIOS. There was a time when hardware manufacturers just wanted the BIOS to be as little as possible and only initialise everything and hand it over to the OS (it was cheaper that way). No fancy graphics, no sounds, no mouse cursor, not even a text editor, just a menu. These are the BIOSes that won’t give you any grief, because they’re straightforward. Coreboot is based on this model.
But nowadays, I mean, just look at how complex your BIOS screen is. Animations, full 256-bit colour, a mouse cursor, drop-down menus, images everywhere. That all has to fit on a SOIC chip…
It’s marketed for a specific purpose (gaming). And sometimes that purpose is determined by company marketing, and less by functionality and versatility.
I mean, look at how much digging you had to do to find IOMMU and AMD-V. Ten years ago they would be front and centre. Also, you’re lucky that they actually had options in the BIOS to begin with. Software/Firmware designers in recent years have taken a more “No, don’t bother making a menu option for that, The stupid user won’t know what it is, and will break their machine. Just leave it automatically off” approach to their menu options.
sigh, but this is the way the world is going…
In fairness, it is a very nice motherboard.
Nicely done. It got most of it right
Don’t do that. You don’t need to.
Your systemd reached the Basic System target, which means the initramfs is satisfied that your machine is sufficiently configured to hand over to a hard disk to continue the boot process.
You’re getting a timeout because the initramfs is shouting to the
/LiveOS/squashfs.img on the Qubes ISO “Where the heck are you!!! You’re supposed to be on stage!!!”, but it can’t seem to find it.
Your udev took an unusually long time to load, which suggests that your block devices might be placed where the installer expects them to be.
Just a hunch…
They’re all here if you want to try them one by one, but honestly you shouldn’t have to…