'awokd' via qubes-users:
For what it's worth, yesterday I updated dom0 on a previously working
Qubes 4.0.1 installation, rebooted, and ran into this exact problem. I
have absolutely no idea if it's related.
Also, re: grub, from my experience it appears to me that it only uses
grub.efi if you have more than one OS installed, such as R4.0.1 and
R4.1, otherwise xen.efi is used which does not have any boot menu or
command line capabilities. I imagine you could change this from rescue
media using some kind of UEFI boot config utility, or perhaps by running
grub-install? With rescue media, you also can modify boot parameters in
In my case, changing xen.cfg back to 4.14 kernel seems to solve the
issue, but I know I had a 4.19 kernel working on this same machine
before. I haven't tried legacy boot at all.
Anyway, point is that it may not be strictly due to UEFI, per se. For
me, 4.14 worked fine under UEFI, and then the 4.19 update caused the
same symptoms you're seeing, which is just like any other
update-gone-wrong, UEFI or not. Also, I don't even know if it was the
kernel update that caused it. It could have been caused by a dracut
update, Xen, or anything else, I assume.
It's on a currently non-production system so I'm probably not going to
troubleshoot it. Most likely I'll wait around for the next kernel update
and see if that fixes it, or wait around for 4.0.2 and reinstall and see
if that fixes it.
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!