-
Yes I’ve read the install notes
- I also read this issues page: New installation from usb fails to boot · Issue #6447 · QubesOS/qubes-issues · GitHub
- Ryzen 3700X
- Radeon RX 5700xt
- ROG STRIX B450-F
- 16gb of RAM
- 512gb NVME
- Qubes 4.0.4
What I’ve attempted
- Computer had Windows 10 installed on it.
- Downloaded the .iso file from the website, checked the SHA-256.
- Used Rufus to create the installer
- Used MBR for Rufus to create the installer
- Yes I used DD image mode
- Turned off the computer, replaced with the new NVME drive with Pop!OS installed previously, performed a quick format to “clean” the drive.
- Booted into BIOS and put the drive in the correct boot order
- Made sure IOMMU was on
- Made sure TPM was on
- Made sure SVM was on
- Booted the computer and popped open the installer to “Install Qubes”
- I’m met with “Warning: dracut-initqueue timeout - starting timeout scripts”
- Turned off the computer, used a second laptop to use Balena Etcher to create the installer.
- Booted the computer and popped open the installer to “Install Qubes”
- I’m met with “Warning: dracut-initqueue timeout - starting timeout scripts”
- Installed Pop!OS on the new NVME drive.
- Downloaded a new .iso whilst on linux
- Checked the 256 of the file
- Mounted the .iso
- Used sudo dd if=/home/user/Documents/Qubes-R4.0.4-x86_64.iso of=/dev/sda status=progress bs=1048576 && sync
- Installer is created
- Downloaded a new .iso whilst on linux
- Turned off the computer, put USB back into the computer.
- Booted the computer and popped open the installer to “Install Qubes”
- I’m met with “Warning: dracut-initqueue timeout - starting timeout scripts”
- Use a completely different USB stick that hasn’t been used for this before
- Repeat the process
- Met with same error.
I decided to VM the OS in Boxes (yes I know not to use it due to a different hyper-visor thing). It boots past the errors and gets to the install screen before stating VM hardware doesn’t have the proper software (obviously). I just used to it make sure the .iso was not corrupted as a double check.
Currently using Pop!OS as a holdout until I can figure what is going on.
Any help is appreciated.