Steve's blog

There can be issues with shipping installer images including UEFI. But they're mainly due to crappy UEFI implementations that vendors have shipped. It's fairly well-known that Apple have shipped some really shoddy firmware over the years, and to allow people to install Debian on older Apple x86 machines we've now added the workaround of a non-UEFI 32-bit installer image too. But Apple aren't the only folks shipping systems with horrendously buggy UEFI, and a lot of Linux folks have had to deal with this over the last few years.

I've been talking to a number of other UEFI developers lately, and we've agreed to start a cross-distro resource to help here - a list of known-broken UEFI implementations so that we can share our experiences. The place for this in in the OSDev wiki at http://wiki.osdev.org/Broken_UEFI_implementations. We're going to be adding new information here as we find it. If you've got a particular UEFI horror story on your own broken system, then please either add details there or let me know and I'll try to do it for you.

00:40 :: # :: /debian/efi :: 3 comments

Comments

Re: Tracking broken UEFI implementations
Holzhaus wrote on Fri, 07 Aug 2015 03:22

My HP ProBook 6465b ignores boot entries that I set via efibootmgr or bcdedit and always boots this file: EFI/Microsoft/Boot/bootmgfw.efi

I wrote some more details here: http://homepage.ruhr-uni-bochum.de/Jan.Holthuis/misc/uefi-madness/

Your Comment