Qubes install says my AMD ASRock B550 setup does not support virtualization (but it does) and have tripled checked all virt options (all turned on)

stumpi · September 6, 2022, 12:38am

First, the error does not seem to match any of the solutions in the UEFI troubleshooting doc, but from this post I suspect one of the option may help?

Anyway, I have a ASRock B550 Phantom Gaming 4 mobo and I made sure to turn on virtualization (SVM Mode) and SR-IOV Support (Single Root IO Virtualization Support) and was able to get to the install but got an error message that my sys did not support virtualization? Just for giggles I tried booting up with the drive from my previous computer that had qubes installed, it booted fine but I couldnt start any of the appvms because it says that virtualization is not supported? I then hunted around in the settings a bit more and found that IOMMU was not enabled so I enabled that. Now when i try to install I am getting a dracut-initqueue error and it slows down significantly and even when i do get the option to control+D or exist to shell its frozen and I cant get to either. Also when i try to boot from my previous computer’s drive it boots, and I can unlock the LVM drive encryption but then when i try to put the password for logging in it freezes.

So since I cant seem to get to a shell or even ctrl+d I am not sure how to look at any errors/logs and since my situation doesnt seem to be like the ones in the trouble shooting section I am not sure which one(s) to try.

Help

stumpi · September 7, 2022, 6:23pm

ok, no progress yet on my part (still crossing fingers that some kind/experienced soul might have an idea?).

I did want to ask, since it seems like I could install with IOMMU disabled, would it make sense to try installing anew with IOMMU off, then enable IOMMU, then start digging around? I was kinda thinking no since when using my old computers ssd with qubes already installed it would freeze when I tried to login, but then again the qubes installation on that drive was for a completely different computer?

Or maybe another way (like booting with a live other-distro) to check and see if virtualization is set correctly?

Thoughts? Please

stumpi · September 8, 2022, 3:13pm

Ok, so I made a live version of fedora 32, booted my new AMD machine up with it and typed lscpu. That gave me the following:

Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   43 bits physical, 48 bits virtual
CPU(s):                          12
On-line CPU(s) list:             0-11
Thread(s) per core:              2
Core(s) per socket:              6
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       AuthenticAMD
CPU family:                      23
Model:                           113
Model name:                      AMD Ryzen 5 3600 6-Core Processor
Stepping:                        0
Frequency boost:                 enabled
CPU MHz:                         2239.907
CPU max MHz:                     3600.0000
CPU min MHz:                     2200.0000
BogoMIPS:                        7186.60
Virtualization:                  AMD-V
L1d cache:                       192 KiB
L1i cache:                       192 KiB
L2 cache:                        3 MiB
L3 cache:                        32 MiB
NUMA node0 CPU(s):               0-11
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full AMD retpoline, IBPB conditional, STIBP conditional, RSB filling
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid ap
                                 erfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt t
                                 ce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate sme ssbd mba sev ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsa
                                 veopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefi
                                 lter pfthreshold avic v_vmsave_vmload vgif umip rdpid overflow_recov succor smca

So the “Virtualization” line indicates AMD-V, I dont know if that also means its turned on or jsut available but regardless it seems to be an option. So with that in mind, I am even more stumped?! Is it Xen that is not seeing it? I didnt think Xen would be part of the setup/installation but the installation says I dont have virtualization.

Please help!!!

stumpi · September 12, 2022, 1:02pm

Is there some other information I should be posting? I honestly am not sure how to go about figuring this out.

stumpi · September 15, 2022, 7:30pm

So when i try to boot with IOMMU enabled I end up with a “Warning: dracut-initqueue timeout - starting timeout scripts” error. So i tried another USB drive (using rufus and the dd option) but still get this error. When i try to boot up with the drive, it gives me a very verbose boot up, then the error, then the option to Ctrl+D or press enter for maintenance but with the caveat that it freezes so I cant actually press ctrl+d or enter.

If I dont have IOMMU enabled then i get get through to the installation gui where it then tells me I dont have virtualization.

Am not sure if this is not interesting issue for people or a “dumb post” or if all who have looked genuinely dont know but I’m not sure what else to do, I posted about possibly using an unstable weekly iso but I have no idea where the ISOs are kept (or if one is expected to compile it ones self which is beyond me).

alzer89 · September 20, 2022, 12:45pm

@stumpi, it sounds like you have a very restrictive BIOS that is withholding CPU functionality. This is the unfortunate reality when it comes to “gaming” PCs, and trying to use them for purposes other than gaming.

Can you be a little more specific about what happens when you get that dracut-initqueue error?

That basically means that the initial ramdisk has set everything up ready to hand everything over to a blcok device (usually a hard drive, but in this case, the ISO), but it can’t seem to find it, or it can’t find it in a suitable-enough state to “switch root”.

stumpi · September 20, 2022, 2:45pm

For whats its worth, I tried with the latest qubes iso and with IOMMU I still had the exact same issue, got a bunch of dracut-initque timeout errors and ended up with the sys freezing when I am given the option to ctrl+d or Enter

renehoj · September 20, 2022, 3:15pm

This weekend I installed Qubes on a ASUS B450-F with a Ryzen 5 2600x, I’m using the same configuration you are using, and it works for me.

In the advanced menu is enabled
CPU Config/SVM Mode
PCI Subsytem/SR-IOV
NBIO Common/NB Config/IOMMU

stumpi · September 20, 2022, 3:24pm

@alzer89 Thank you. so very much, at this point (almost) any kind of response is really appreciated.

Regarding the gaming BIOS I was not aware that gaming setups were generally more restrictive, I based my purchase on this post as they were able to get it running (I have reached out to the poster, they have been inactive for quite awhile it seems). I was thinking since the posters post was almost a year ago that at worst I should be able to do like they did (turn on IOMMU and other virt settings) and get something going and maybe whatever was causing issues for them would now be resolved. I was sadly quite wrong.

Ok, regarding the dracut-initqueue error. I wanted to get to a shell and try to cp the error log but as the system freezes by the time i get to that option I havent been able to get to a shell to cp the log. If you have some thoughts on how I might get a shell i’d gladly poke around and post wh

stumpi · September 20, 2022, 3:59pm

Thanks for the response. I checked them before but checked again, and they are all enabled. took photos just to make sure i have the options you are talking about:

renehoj · September 20, 2022, 4:01pm

Yes, it’s the same settings I use.

I did also enable CMS/Legacy mode and disable secure boot.

stumpi · September 20, 2022, 4:07pm

ok so I tried to take photos while booting the install usb/iso. I also tried ocr’ing the output so it might be easier to read/parse (though keep in mind its ocr so unlikely to be perfect). Any other ideas would of course really really be appreciated!

First I got:

9.055346] dracut-pre-udevt6231: modprobe: FATAL: Module crams not found in
directory /lib/modules/5.18.16-1.fc32.qubes.x86_64
9.1947093 dracut-pre-udevt6741: modprobe: FATAL: Module floppy not found in
OR
] Started Show Plymouth Boot Screen.
Ok
1 Started Forward Password Requests to Plymouth Directory Watch.
Ok
1 Reached target Local Encrypted Volunes.
OR
1 Reached target Paths.
1 A start job is running for udev Wait for Complete Device Initialization (50s / min 25)

Then tried to ESC into a shell, no shell but that seemed to cancel the init and gave me:

9.0553461 dracut-pre-udevt623]: modprobe: FATAL: Module crams not found in
directory /11b/modules/5.18.16-1.fc32.qubes.x86_64
3.1547091 dracut-pre-udevt6741: modprobe: FATAL: Module floppy not found in
OK
1 Started Show Plymouth Boot Screen.
OK
"Started Forward Passuord hequests to Plynouth Directory Watch.
OK
I Reached target Local Encrupted Volunes.
OK
1 Reached target Paths.
OK
] Finished udev Walt for Complete Device Initialization.
Starting Device-Mapper Multipath Device Controller.
OK
I Started Device-Mapper Multipath Device Controller.
OK
1 Reached target Local Pile Systens (Pre).
OK
1 Reached target Local File Systems.
Starting Open-ISCSI..
Starting Create Volatile Files and Directories...
OK I Started Open-ISCSI.
Starting dracut initqueue hook...
OK
I Finished Create Volatile Files and Directories.
OK
]Reached target System Initialization.
OK
] Reached target Basic System.
225.818741) dracut-initqueuel18661: Warning: dracut-initqueue timeout - starting tImeout scripts
226.4863721 dracut-initqueue(1866]: Warning: dracut-initqueue timeout
- starting timeout scripts
226.974146] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
227.5394871 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
228.1889491 dracut-initqueuel1866]: Warning: dracut-initqueue timeout
- starting timeout scripts
228.6798431 dracut-initqueue(1066]: Warning: dracut-initqueue timeout - starting timeout scripts
229.248925] dracut-initqueue[18661: Warning: dracut-initqueue timeout - starting timeout scripts
229.815559] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
230.3842211 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting timeout scripts
238.955226] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
•starting timeout scripts
231.5250391 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
232.0908781 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
232.6588181 dracut-initqueue[1866]: Warning: dracut-initqueue timeout - starting timeout scripts
233.2247271 dracut-initqueuet1866]: Warning: dracut-initqueue timeout - starting timeout scripts
233.7961341 dracut-initqueueL1866]: Warning: dracut-initqueue timeout - starting timeout scripts
234.3633771 dracut-initqueueL1866]: Warning: dracut-initqueue timeout - starting timeout scripts
234.931182] dracut-initqueuel18661: Warning: dracut-initqueue timeout
- starting timeout scripts
235.5011881 dracut-initqueuel1866]: Warning: dracut-initqueue timeout
- starting timeout scripts
236.0697801 dracut-initqueuel18661: Warning: dracut-initqueue timeout - starting timeout scripts
236.6396861 dracut-initqueueL1066]: Warning: dracut-initqueue timeout - starting timeout scripts
237.208781] dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
237.7779701 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
238.3486891 dracut-initqueue[1066]: Warning: dracut-initqueue timeout - starting timeout scripts
238.916356] dracut-initqueue[1066]: Warning: dracut-initqueue timeout - starting timeout scripts
239.486253] dracut-initqueue[1066]: Warning: dracut-initqueue timeout - starting timeout scripts
248.0544561 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
240.6209481 dracut-initqueue[1866]: Warning: dracut-initqueue timeout - starting
timeout scripts
241.1885241 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting
timeout scripts
241.7522531 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
242.3213721 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
242.8906871 dracut-initqueuel1066] : Warning: dracut-initqueue timeout - starting timeout scripts
243.4558771 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
244.0269811 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
244.595697] dracut-initqueuel1866]: Warning: dracut-initqueue timeout - starting timeout scripts
245.167236] dracut-initqueuel1B66]: Warning: dracut-initqueue timeout - starting timeout scripts
245.7374481 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
246.306319] dracut-initqueue1066]: Warning: dracut-initqueue timeout
246.6744361 dracut-initqueue[1866]: Warning: dracut-initqueue timeout
- starting timeout scripts
- starting timeout scripts
247.4435921 dracut-InitqueueL1866]: Warning: dracut-Initqueue timeout - starting timeout scripts
248.0122441 dracut-initqueuel18661: Warning: dracut-initqueue timeout - starting timeout scripts
24B.5816781 dracut-initqueuel1B66]: Warning: dracut-Initqueue timeout - starting timeout scripts
249.1503611 dracut-initqueue[1866]: Warning: dracut-initqueue timeout - starting timeout scripts
249.7182741 dracut-initqueue[1866]: Warning: dracut-initqueue timeout - starting timeout scripts
250.288355] dracut-initqueuel18661: Warning: dracut-initqueue timeout - starting timeout scripts
250.8591361 dracut-initqueueL1866]: Warning: dracut-initqueue timeout - starting timeout scripts
251.4254621 dracut-initqueuel1866]: Warning: dracut-initqueue timeout - starting timeout scripts
251.9952221 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
252.564309] dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
253.1305891 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
253.7000631 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
254.2691381 dracut-initqueuel18661: Warning: dracut-initqueue timeout - starting timeout scripts
254.8354441 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
255.4825391 dracut-Initqueuel10661: Warning: dracut-initqueue timeout - starting timeout scripts

And went on like that ended up with:

259.9569571 dracut-initqueuet10661: Warning: dracut-initqueue timeout
- starting timeout scripts
260.5234031 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
261.092266] dracut-initqueuet1066]: Warning: dracut-initqueue timeout
• starting timeout scripts
261.6594171 dracut-initqueue[10661: Warning: dracut-initqueue timeout
- starting timeout scripts
262.229081] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting timeout scripts
262.7975051 dracut-initqueue(1966]: Warning: dracut-initqueue timeout
- starting timeout scripts
263.3662651 dracut-Initqueuel18661: Warning: dracut-initqueue timeout - starting timeout scripts
263.9368181 dracut-initqueuet18661: Warning: dracut-initqueue timeout
starting timeout scripts
264.5065131 dracut-initqueuel10661: Warning: dracut-initqueue timeout
starting timeout scripts
265.075205] dracut-initqueuet1066]: Warning: dracut-initqueue timeout - starting timeout scripts
265.645492] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
266.211372] dracut-initqueuel1866]: Warning: dracut-initqueue timeout - starting timeout scripts
266.782846] dracut-initqueuel1866]: Warning: dracut-initqueue timeout - starting timeout scripts
267.350507] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
267.918070] dracut-initqueuel1866]: Warning: dracut-initqueue timeout - starting timeout scripts
268.488092] dracut-initqueuet1066]: Warning: dracut-initqueue timeout - starting timeout scripts
269.055976] dracut-initqueue[1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
269.6249871 dracut-initqueuel1866]: Warning: dracut-initqueue timeout - starting timeout scripts
270.1949921 dracut-initqueue(10661: Warning: dracut-initqueue timeout - starting timeout scripts
270.7644211 dracut-initqueuet1066]: Warning: dracut-initqueue timeout - starting timeout scripts
271.3331331 dracut-initqueuel1866]: Warning: dracut-initqueue timeout
starting timeout scripts
271.902768] dracut-initqueuel1866]: Warning: dracut-initqueue timeout
- starting timeout scripts
272.4716981 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
273.038294] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
273.608700] dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
274.169456] dracut-initqueuel10661: Warning: dracut-initqueue timeout
- starting timeout scripts
274.739207] dracut-initqueuel1866]: Warning: dracut-initqueue timeout
starting timeout scripts
275.3062731 dracut-initqueue[1866]: Warning: dracut-Initqueue timeout
starting timeout scripts
275.875908] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
276.4479521 dracut-initqueuel1B66]: Warning: dracut-initqueue timeout - starting timeout scripts
277.0172461 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
277.5863511 dracut-initqueueL1066]: Warning: dracut-initqueue timeout - starting timeout scripts
278.1572851 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
278.726846] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
279.298036] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting timeout scripts
279.8635211 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting timeout scripts
288.429026] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
• starting timeout scripts
280.9963991 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting timeout scripts
281.565840] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting timeout scripts
282.132834] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting
timeout scripts
282.703180] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
283.269500] dracut-initqueue1066]: Warning: dracut-initqueue timeout
starting
timeout scripts
283.8370591 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting
timeout scripts
284.403358] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting
timeout scripts
284.971425] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
starting
timeout scripts
285.5389321 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
286.1888481 dracut-initqueuel1866]: Warning: dracut-initqueue timeout
starting timeout scripts
286.679446] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
287.2470951 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
287.8134541 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
- starting timeout scripts
288.3796581 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
288.950359] dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
289.519496] dracut-initqueuel10661: Warning: dracut-initqueue timeout
- starting timeout scripts
290.0891371 dracut-initqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
290.657200] dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
291.223223] dracut-imitqueuel1066]: Warning: dracut-initqueue timeout - starting timeout scripts
291.792481] dracut-initqueuel10661: Warning: dracut-initqueue timeout - starting timeout scripts
292.3593151 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
292.9269531 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
293.4948721 dracut-initqueuel1066]: Warning: dracut-initqueue timeout
- starting timeout scripts
293,494209] dracut-initqueuel1066]: Warning: Could not boot.
- starting timeout scripts
Starting Dracut Emergency Shell..
Warning: /dev/root does not exist
I Generating
"run/ initranf's/rdsosreport.txt"
I Entering emergency mode. Exit the shell to continue.
I Type
"Journalct]" to view system logs.
I You might want to save
after mounting them and attach it to a bug report.
"/run initranfs/rdsosreport.txt" to a USB stick or /boot
Press Enter for maintenance
| (or press Control-D to continue):

But is frozen here so I can’t press c+d or enter

Here are direct photos of the boot up:

renehoj · September 20, 2022, 4:26pm

If Enter gives a shell you can try if and use journalctl to see if you can get any extra information

stumpi · September 20, 2022, 4:42pm

Unfortunately it freezes at the end so neither Enter nor Ctrl+D give me anything.

by the way, secure boot is off on my sys but I am not sure about CMS (CSM?) legac mode, is this what you were referring to?

renehoj · September 20, 2022, 4:46pm

Yes, CSM is the compatibility support module it’s the same as legacy mode, it switches UEFI mode on and off.

stumpi · September 20, 2022, 6:22pm

Well, a tiny bit of progress.

I believe I was stupidly booting UEFI at the boot menu, I guess “USB” is “legacy”.

So now, after selecting install or check media install i get the pretty Qubes screen with the little progress line across the bottom (which moves really slow) and then

… the same “entering emergency mode” and frozen sys with seemingly no ability to control+D or enter maintenance

So I havent gotten the Qubes loading screen (or whatever its called) before, at least not with IOMMU enabled. Not sure this is significant?

This was with the most recent ISO, would it be better to go back to the stable 4.1.1 installation ISO instead?

renehoj · September 20, 2022, 7:02pm

I don’t think it matters which ISO you use, but it’s hard to say without seeing the system log.

You can try removing all extension cards and hard drives, booting only using internal graphics. If you keep getting the same error, my guess would be that the motherboard is supported by qubes.

enmus · September 20, 2022, 10:30pm

I think @51lieal too could help here, as usual

alzer89 · September 20, 2022, 11:27pm

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:

https://docs.kernel.org/filesystems/cramfs.html

https://www.kernel.org/doc/html/latest/admin-guide/blockdev/floppy.html

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…

https://ftp.qubes-os.org/iso/

They’re all here if you want to try them one by one, but honestly you shouldn’t have to…

augsch · September 20, 2022, 11:41pm

I’m curious about how you created your installation media using Rufus. Did you change the “partition scheme” option that you can choose between “MBR”(BIOS or UEFI CSM) and “GPT”(UEFI none CSM). It’s usually easier to install and use to select GPT.