Background
Hello, after a pretty horrid experience attempting to install CachyOS (Failed to run pacstrap will haunt me in my dreams), I have decided to try and install QubesOS onto my currently bricked PC. Before this it was running Windows 11 and I could arguably go back, but I’d rather try this first.
I said before I thought it was too complicated to try and use QubesOS for gaming, but it should be an interesting learning experience none the less.
Install Set-up
My set-up is a corsair DIY build kit, similar to this one from their site:
-
CPU: Intel i9-14900k
-
GPU: Nvidia RTX 4080
-
RAM: 32GB DDR5 5600MHz
-
USB with QubesOS 4.3 ISO flashed with BalenaEtcher
-
Wired connection to router
-
ISO drive plugged into motherboard
-
Monitor plugged into GPU (Did not detect from motherboard)
Installation Attempts
First Attempt: Normal Run
Tried install normally, turned off secure boot and attempted to install with option “Test this media and install QubesOS”. Installation failed.
Errors
- Firmware Bug: CPU APIC ID mismatch
- ACPI BIOS Error (bug):
- I had this issue when installing another OS, possible related to issues with MSI motherboards not conforming to UEFI specifications which fails in GRUB boot loader
- From the look of the code line, it looks like QubesOS might use the systemd work around, but I cannot confirm this
- tmpfs: Unsupported parameter ‘huge’
- 2 nouveau errors
- These are issues already mentioned with the documentation, issue is with Nvidia card with known work arounds
Second Attempt: BIOS edits
Tried to install after changing the BIOS mode, of which I have the option of UEFI which I used in previous attempt, and CSM which from what I read should be ‘legacy mode’. Installation failed.
Errors
- Same as above
- I had hoped the BIOS mode change would fix the ACPI error, but it did not
Third Attempt: Working on it
This is the part where the guide suggests handling nouveau errors.
From the documents:
These errors may also occur due to an incompatible Nvidia graphics card. If you have one, follow the following instructions:
- Disable secure/fast boot and use legacy mode
- Enter GRUB, move the selection to the first choice, and then press the Tab key.
- Now, you are in edit mode. Move the text cursor with your arrow key and after
kernel=line, add:
nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:offIf the above code doesn’t fix the problem, replace it with:
noexitboot=1 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau --- intitrd.img
The documents also direct you to a community guide.
Errors
I haven’t attempted it yet and am looking for feedback.
- I’m assuming all of this is done from the live version running from the USB and not installed yet on my drive
- From the documentation, it says to use the
Tabkey, I’m assuming this is outdated and is now theekey, unless there is something I’m missing - After hitting the
ekey, I do not see anykernel=line, I’m assuming place these above the lastmodule2line. - From the community guide, in the EFI section, is this while GRUB is up, or after attempting install than using a TTY? Somewhat confusing usage of dom0 to me as I am not officially in QubesOS, just the image
Notes and Thoughts
So far hasn’t been anything too unexpected, but I do want to say how much I love the quality documentation of QubesOS. They really do a good job of solving issues and keeping the information easy to find, even if I’m not always smart enough to use it ![]()
Any and all help appreciated, otherwise I might have to tuck tail and return to Windows. Also considering the issues with other OS installs, I performed hardware checks on RAM and my drive to make sure there were no issues.