SURVEY: What's your experience of LL installed in UEFI mode - good, bad or ugly?

[trinidad]

Sorry Mike if you misunderstand my reply, or I misunderstood Coastie's questions. I have not installed LL 3 on any boxes yet, but have installed 2.8 32 and/or 64 on a least a dozen, with mixed results. Some with difficulty. Some without. Only windows 8 has ever been a problem.  The only reason to use the <force> command is because windows was unable to boot through a normal EFI boot loader because of buggy firmware and was originally installed to the removable media path to avoid the failed boot loader firmware and always boot. The <allow> command is not a universal solution, but an MS fix to allow the change to be made on some OEM's but again it is itself unreliable and varies with OEM's, sometimes due to key requirements, other times due to broken OEM firmware. Sometimes when removable media is written with grub efi by <force> and even ,<allow>, so that Debian install can boot from a DVD, the underlying buggy firmware will not boot windows afterwards. To boot both windows and Debian you must change the removable media path back again, so that windows can once again boot, but of course this is no guarantee that Debian will be able to access DVD through the removable media path after that. EFI has long been supported in Debian, much longer than MS consumer software products, but the issues remain with OEM firmware. The solutions to the sloppy MS practices involving OEM firmware will take some time to appear for Debain users. I use different work arounds when I encounter buggy firmware, and operate from Debian, and not a D-based distro when I can, to make changes, which is problematic but more reliable. In any case the problem is rarely with the Debian based distro, and almost always traceable to buggy, or inoperable OEM firmware, over written in the ESP to force MS windows to load from r-media path no matter of its condition. As far as secure boot in Debian, it may be some time before a stable version appears. Most people don't like to hear that their machine, even some new ones, have broken firmware, unfortunately this is frequently the case. This of course is the whole point of U EFI, to resolve such issues, and force lazy OEM's toward a conscience. As with all things Debian, solutions will evolve from the high end (server systems) down eventually encompassing and assimilating as much of the OEM consumer market as possible. In any case EFI installation problems are not with the design of this distro, but always with buggy or broken OEM firmware, and MS sloppy practices. I have not watched the video you refer to, but if it has worked for some people, it is helpful. That's the nature of this thing. 

https://wiki.debian.org/UEFI#Force_grub-...media_path
https://wiki.debian.org/SecureBoot
https://bugs.debian.org/cgi-bin/bugrepor...bug=820036

Trinidad