Dell XPS 15 9570 UEFI Issue

[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.

[Pete Howell]

I meant to say that the xen.cfg file was 0 length; not the efi file.

[awokd]

Pete Howell:

Try using efibootmgr in a live boot from a different distro.

[y...@tutanota.com]

I'm having the same issue.

I haven't been able to boot the 4.0.1 installation with UEFI on my Dell XPS 15 9570 w/  4k/NVMe/1050Ti. It doesn't look like anyone else has either. A screen briefly pops up saying Xen EFI and then it reboots. I am able to complete the installation booting from legacy boot mode but I am still unable to boot from it. I am not getting to a grub menu. "No bootable device found". Seems odd because Ubuntu/Fedora liveCDs boot fine with Dell's UEFI.

I previously installed Qubes on a USB drive for testing and was able to boot into Qubes just fine, it was just too slow. I've tried every step listed on the UEFI page as well as the Thinkpad UEFI troubleshooting page. Any suggestions on where to go from here besides selling my laptop?

For anyone else with this issue, to get through the installation: Enable Legacy Options ROMs, Disable Secure Boot, SATA ACPI mode, installation kernel parameter nouveau.modeset=0. The efibootmgr fix doesn't work in rescue mode, I think that's due to not loading the install via UEFI. efibootmgr will run fine from another liveCD booted through UEFI but it doesn't seem to help.

[y...@tutanota.com]

Update...I tried the efi=no-rs section in the UEFI troubleshooting guide again because I didn't try it from scratch and I got it to boot! The boot option shows up under UEFI but it requires Legacy Options ROMs to still be enabled in the BIOS.

Steps to install Qubes:

1. BIOS: Enable Legacy Options ROMs, Disable Secure Boot, SATA: AHCI mode

2. Boot USB drive in legacy mode - USB Storage Device.

3. Perform the steps in the UEFI troubleshooting section called "Installation freezes before getting to Anaconda / disable EFI runtime services". I used a Ubuntu liveCD to edit the xen.cfg file. When starting the installation, add kernel parameter nouveau.modeset=0.

[Pete Howell]

Can you post the link to the instructions you followed, please. I did finally give up on this and am back to Windows 10 on my Dell laptop; but, I'd like to give it another try.

I should also mention that the ISO would never boot properly from the UEFI partition on the USB stick, so I'm guessing that since the installer would only boot in legacy mode, that that may be part of the reason I get a successful Qubes install with no UEFI boot partition.

Does anyone know why the Qubes 4.0.1 image does not boot in UEFI? The partition shows up to boot from, but you just get a blank screen and no installer.

[awokd]

Pete Howell:

Believe the person you replied to was referring to
https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-getting-to-anaconda--disable-efi-runtime-services.
There are also instructions at the top of that page to edit your installer.