Forgot to add that the firmware doesn’t recognise the default EFI configuration, and has to be edited to be bootable. It has to be done after every kernel and Xen update.
Copy the /boot/efi/EFI/qubes/ directory to /boot/efi/EFI/BOOT/ (the contents of /boot/efi/EFI/BOOT should be identical to /boot/efi/EFI/qubes besides what is described in steps 2 and 3):
cp -r /boot/efi/EFI/qubes/. /boot/efi/EFI/BOOT
Rename /boot/efi/EFI/BOOT/grubx64.efi to /boot/efi/EFI/BOOT/BOOTX64.efi:
change console=none to console=vga and add efi=attr=uc.
Edit EFI configuration in dom0 (Repeat after every kernel/xen upgrade):
Copy the /boot/efi/EFI/qubes/ directory to /boot/efi/EFI/BOOT/ (the contents of /boot/efi/EFI/BOOT should be identical to /boot/efi/EFI/qubes besides what is described in steps 2 and 3):
I’m currently using this laptop to install qubes. Editing the grub parameters but I don’t know how to edit the EFI configuration in dom0. Can I do this from the boot screen just before I start the qubes installation?
Are you sure my friend? I need to edit the grub parameters to even get the installation media to boot, but that’s not even the main problem that I’m having.
The main problem that I have is that after I complete the installation and then need to reboot the system, my computer just hangs
Yes, I’m sure of it, the “Edit EFI configuration in dom0 (Repeat after every kernel/xen upgrade):” fix is unrelated to your problem.
Are you able to boot in the installed Qubes OS after the installer hangs when you press on a Reboot button in the installer GUI and you power it off or reboot forcefully?
Doing a clean install now, I’ll let you know in a bit
I believe it’s after I choose reboot, the system hangs on a black screen, without even booting. I’ll let you know in a bit
I dunno why but now I’ve been getting an installation error that. The installation goes to the point where it says that it’s processing the transaction from the source, and then the installation stops, saying a bug has occurred.
Did you test the installation media before installing Qubes OS to make sure that it’s not corrupted?
You can also try to format the destination disk before installing Qubes OS on it to make sure that the old Qubes OS installation is not interfering with the new install.
I’m running a multi-boot system. I have windows 11 and debian 12. After the install fails I launch gparted live and remove the EFI system partition for qubes and the storage parition (usually the latest partitions on the disk) and then try a new install. I’m also not connected to the internet when doing the install, if that matters.
I’d rather not format my system, but I if you think it’ll help, I’ll do it
So I can get to the installation screen, and there’s an option to verify the media, it keeps saying that it’s corrupt. I’m using rufus on windows 10, and I’m running it as admin.
but I was able to use it before.
I’m using an 8 gb store n go Verbatim, usb 2.0 usb key. I have several of them. I’ll write qubes to the others and try again
If you’re using Windows to write the ISO then you can’t check if it’s corrupted or not:
Note: Using Rufus to create the installation medium means that you won’t be able to choose the “Test this media and install Qubes OS” option mentioned in the example below. Instead, choose the “Install Qubes OS” option.
Did you verify the downloaded ISO?
Maybe try to use another USB or write the ISO from the Linux OS (e.g. using a Live USB) so you’ll be sure that it was written correctly.
Edit: Ok so I formatted my harddrive and installed qubes. It says to reboot the system, and after I choose reboot, I then remove the usb key. I can reboot the system and choose to start qubes with Xen hypervisor but nothing happens. Just a black screen with a cursor flashing in the top left corner
After installation completes, I reboot the system.I have my computer setup to go straight to the boot device option. From there I choose qubes. Next I am taken to the Qubes grub menu, and the only way that I can get it to boot again is by changing “console=none” to '“console=vga” and add “efi=attr=uc” afterwards.
If I don’t do this, my system doesn’t boot to qubes. How can I make it so that I don’t have to keep doing this anytime I want to boot into qubes?
I’m on qubes 4.2.3 (R4.2)
EDIT: Ok, I made the changes you recommended. I installed qubes, rebooted to the grub menu and changed quiet rhgb to nomodeset
Here are my CPU and GPU specs:
CPU: CPU is intel ® Core™ i5-4310m CPU @ 2.7 GHz
GPU:
Mesa Intel HD Graphics 4600 (HSW GT2)/ Intel 4th Gen Core Processor Integrated Graphics controller
I tried using the nomodeset in the grub menu of the installer but I don’t see the quiet rhgb in the installer that I’m using so I removed the quiet and just added the nomodeset
How do I check the log output on the screen if it runs so quickly? I can barely see what the computer screen prints printing.
changing console=none to console=vga and adding efi=attr=uc must be edited in the grub parameters otherwise you won’t be able to boot into the OS.
Another note for anyone else that’s struggling:
I don’t know why, but my computer (this model) has a problem recognizing usb 3.0 installation media at boot time (when the computer starts). Sometimes the device would be listed in the boot devices option, and sometimes not.
The best way to work around this is to get a larger usb 2.0 usb key/drive. The computer ALWAYS recognizes these at boot time.
