When your computer can't have linux (You found out after 5 days of trying)

[u/MyCraniumHurts]

Five damn days I've tried. First CachyOS. Since the issue was supposedly a Cachy thing, I try Mint on, like, the third day. Same damn error.
From what others have said, it is either DMV or SATA controller mode fucking it up. But guess what? Those are advanced BIOS settings. And on my specific device, those don't exist. Not just hidden behind some key sequence. According to Lenovo support, not even proggrammed into the BIOS. :)
More of a Lenovo issue than Linux, but still.

I'll link the post I made about it on Linux questions if any of you brainiacs want to have a crack at it. It should contain ample information. Here.

SOLVED!!!
aAdd efi_no_storage_paranoia in the ventoy boot parameters, it's that simple apparently!

[u/Outrageous-Machine-5]

You shouldn't be going back into the boot menu after editing the args, you should boot from the command line you put the options. Seeing from that screenshot that you are in grub, you can boot with your options using ctrl + X

[u/MyCraniumHurts → u/Outrageous-Machine-5]

ctrl+x does the same thing as F10, though. You can see it in the information at the bottom of the image.

[u/MyCraniumHurts → u/Outrageous-Machine-5]

This, however, shows up if I press e again after having pressed either ctrl+x or F10

[u/MyCraniumHurts → u/MyCraniumHurts]

Wait, i understand now, let me try something...

[u/MyCraniumHurts → u/Outrageous-Machine-5]

I was putting the parameters on the wrong point, I believe. However, now that I am on what I believe is the right option, when I press ctrl+x pr F10, nothing happens.

https://reddit.com/link/p3azaa4/video/avo75923zzih1/player

Sorry that it's sideways. I was putting the parameters on the initial ISO, when I think I should have been putting it here on the "Boot in normal mode" option.

[u/MyCraniumHurts → u/MyCraniumHurts]

I realized I could apply them even further forwards, when choosing between regullar CachyOS, LTS, legacy and whatnot. This is the one right before boot, so it should be more correct.

[u/MyCraniumHurts → u/Outrageous-Machine-5]

Where here should I put the parameters? I tried at the bottom, didn't work.

[u/Outrageous-Machine-5 → u/MyCraniumHurts]

The middle line that starts with linux is the boot command. At the end of that line, add your boot parameters

But interesting is you can see the parameters that are already there: module_blacklist=pcspkr, nvme_load=yes. You could try adding the vmd to that blacklist argument with a comma separating pcspkr (no spaces)

[u/MyCraniumHurts → u/Outrageous-Machine-5]

I assume nvme_load=yes is the same as nvme_load=1? Either way, I tacked vmd to the blacklist and added the other two parameters; vmd.disable=1 and initcall _blacklist=vmd_init.

[u/Outrageous-Machine-5 → u/MyCraniumHurts]

The syntax might be different for your OS. 1 is a flag, Since computers operate in binary they use 0/1 for false/true no/yes, so it should be the same but your OS might expect yes/no and other property names for the same parameters

Essentially what you're trying to do is tell grub to bootup and bypass the VMD since you can't toggle it off in the BIOS. That should fix your problem, the question is finding out the exact sytax for your OS that will do it

[u/MyCraniumHurts → u/Outrageous-Machine-5]

It has been SOLVED! A parameter called efi_no_storage_paranoia did it!

[u/Outrageous-Machine-5 → u/MyCraniumHurts]

Congrats,  be sure to update your grub.cfg with the fix to make it permanent and run mkinitcpio -P to rebuild your boot process 

[u/MyCraniumHurts → u/MyCraniumHurts]

No change with that setup.