I was able to boot up with a USB. However, to do so every time I boot, I have to go into edit Xen and add “nomodeset” at the end of “module2 /vmlinuz-6.x.x-qubes” before Qubes will run. I’m wondering if I can do something once I’m booted up to make this permanent, so I don’t have to edit Xen every time I boot
Hi stef and welcome here.
I was about to give you a different answer but maybe the docs are more appropriate?
Your question is not exactly related to Qubes OS but you had no way to know it 
The piece of software you are talking about is called “GRUB”.
The following topic adds another option to the default GRUB command in legacy mode, but you can use it as an example:
If you use UEFI, you need to use a slightly different command:
If you meant the “Qubes 4.0: EFI” way, then it’s only for old Qubes OS 4.0 version, not for newer Qubes OS versions.
For Qubes OS 4.2 and newer you need to edit the default GRUB config /etc/default/grub and regenerate the GRUB config using grub2-mkconfig -o /boot/grub2/grub.cfg command for both Legacy BIOS and UEFI.
1 Like
I wasn’t aware of this, thanks!
Then I think something don’t work as intended.
For test I’ve changed dom0_mem=1024M to 2048 and done
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
but when edited grub menu during startup there is still dom0_mem=1024
So for EFI in 4.2.4 you still need to invoke
sudo grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg
1 Like
Thanks for the help, got it fixed
How?
Maybe you already ran the sudo grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg command before on Qubes OS 4.2 or you updates Qubes OS in-place and this file wasn’t updated.
In the default Qubes OS 4.2 installation, the /boot/efi/EFI/qubes/grub.cfg file contains a link to the /boot/grub2/grub.cfg file in the /boot partition:
search --no-floppy --fs-uuid --set=dev xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
set prefix=($dev)/grub2
export $prefix
configfile $prefix/grub.cfg
Where xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is the uuid of your /boot partition.
You can restore the file manually or try to reinstall the grub2-efi-x64 package:
sudo qubes-dom0-update --action=reinstall grub2-efi-x64
1 Like
Yes.
I’ve ran it manually when tested dom0 cpu pinning. I’ve took instruction to update grub from DOC’s.
I’ll check reinstall instruction and edit this post.
PS: Ok. Just reinstalling grub2-efi.x64 in dom0 does nothing.
When renaming /boot/efi/EFI/qubes/ directory to backup and renistalling grub2 efi it creates new /boot/efi/EFI/qubes/ directory with /fonts/ and qubex64.efi inside only, which result non bootable system (yes, I’ve run grub2-mkconfig -o /boot/grub2/grub/cfg)
Trying with manual creating grub.cfg file but isn’t something should recreate it?
PS2: manually created /boot/efi/EFI/qubes/grub.cfg file works
1 Like
I don’t know how exactly does it work, but the /boot/efi/EFI/qubes/grub.cfg file should be provided by the grub2-efi-x64 package:
[user@dom0 ~]$ dnf provides /boot/efi/EFI/qubes/grub.cfg
Last metadata expiration check: XXX
grub2-efi-x64-1000:2.06-4.fc37.x86_64 : GRUB for EFI systems.
Repo : @System
Matched from:
Filename : /boot/efi/EFI/qubes/grub.cfg
1 Like
I don’t know exactly why but you have to reinstall grub2-common instead.
1 Like
For 2 weeks I’m out of Qubes