I intended to save my command history to disk so that I could post step-by-step exactly what to do. But I must have been in a dispvm at the time, because now I can't find that history. So the following is from memory and not precise.
I tried every trick I could find related to Qubes UEFI installation, and thinkpad troubleshooting. What finally worked does not appear to be documented in any of the Qubes documentation. Qubes uses Fedora's installer, Anaconda, and the following approach is documented on Fedora's wiki.
1. Follow Qubes install guide up to the `dd` command. Don't write to usb with `dd`.
2. Instead, use Fedora's `livecd-iso-to-disk` tool. You'll need the `livecd-tools` package. See https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB#Command_line_method:_Using_the_livecd-iso-to-disk_tool_.28Fedora_only.2C_non-graphical.2C_both_non-destructive_and_destructive_methods_available.29
I don't recall for certain exactly what I passed to `livecd-iso-to-disk`. Try this:
sudo livecd-iso-to-disk --efi --format Qubes-R3.2-x86_64.iso /dev/xvdi
The media as written will not quite boot, yet. Qubes EFI boot is configured to find a label "Qubes-R3.2-x86_64", but the media written by the livecd tool is labelled "BOOT" (and the filesystem does not support the longer label, so the --label option would not help).
3. Mount the usb media (/dev/xvdi in the example above)
4. Edit xen.cfg. If I recall correctly, `<mount>/EFI/BOOT/xen.cfg`.
In this file, replace every occurrence of `LABEL=Qubes-R3.2-x86_64` with `LABEL=BOOT`
You should now have install media that work on UEFI firmware!
After install, I recommend upgrading kernel version for recent hardware. I.e. with
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel kernel-qubes-vm
Thanks a lot Dave C and Stephan Marwendel. By following both of your instructions I got the installation working on my Lenovo ThinkPad Yoga 460!
Hi, I have one question (I am pretty new).
By doing dosfslabel /dev/sdb1 BOOT Im getting the following message:
There are differences between boot section and its backup.
This is mostly harmless. Differences: (offset:original/backup)
Not automatically fixing this.
Can I just ignore this message ? Or what can I do to fix it ?