Pete Howell:
I had a problem with v4.0.1 hanging halfway through the install, but adding "mapbs=1
noexitboot=1" seems to have fixed the issue. Unfortunately, the system does not
boot -- it does not see a bootable device.
I tried following the UEFI troubleshooting article to no avail. Copying
/boot/efi/EFI/qubes to /boot/efi/EFI/BOOT with all the accompanying
instructions did not work. I did notice that the xen-*efi file was 0 length,
so I also followed the instructions on adding the entries (with the correct
file versions of course), but the last instruction talks about running the
efibootmgr command, which doesn't run because there is no efivars kernel module.
I personally hate UEFI, but these newer systems leave you no choice -- you
CANNOT boot from an internal drive without it. Does anyone know how to resolve
this? I have a nice and very expensive brick that I'd like to turn into a
production system.
Any help would be greatly appreciated.
Try using efibootmgr in a live boot from a different distro.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/5733ac15-21c1-77ae-1a66-0742a05d0a92%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.
