On Sat, Aug 26, 2017 at 12:16 PM, Björn 'besser82' Esser <besser82@xxxxxxxxxxxxxxxxx> wrote: > Am 26.08.2017 um 18:57 schrieb Lars Seipel: >> >> On Fri, Aug 25, 2017 at 08:24:59PM +0000, Fedora Branched Report wrote: >>> >>> Package: shim-signed-13-0.2 >>> Old package: shim-signed-0.8-10 >>> Summary: First-stage UEFI bootloader >>> RPMs: shim-aa64 shim-ia32 shim-x64 >>> Added RPMs: shim-aa64 shim-ia32 shim-x64 >>> Dropped RPMs: shim >>> Size: 2238688 bytes >>> Size change: 1219336 bytes >>> Changelog: >>> * Thu Mar 23 2017 Petr Šabata <contyk@xxxxxxxxxx> - 0.8-9 >>> - Re-enable dist tag for module builds >>> >>> * Tue Aug 22 2017 Peter Jones <pjones@xxxxxxxxxx> - 13-0.1 >>> - Initial (partially unsigned) build for multi-arch support on >>> x64/ia32. >>> >>> * Thu Aug 24 2017 Peter Jones <pjones@xxxxxxxxxx> - 13-0.2} >>> - Obsolete old shim builds. >> >> The package no longer ships /boot/efi/EFI/fedora/shim.efi which is what >> people's boot entries refer to. It's shimx64.efi now. This causes >> failure to boot on EFI systems. >> >> Which component, if any, is tasked with adjusting EFI boot entries in >> such a case? Anyway, it doesn't happen, so some kind of warning (at >> least to -devel and -test) would seem appropriate, ideally prior to the >> new package reaching the mirrors. > > > I suspect this has sth. to do with the changes for '32 bit UEFI Support' > [1]… > > Usually a new 'Fedora' boot entry is autogenerated after (maybe needed) > unlocking the boot device entries in UEFI / BIOS, removing the old boot > entry for Fedora and booting from the HDD, which contains the UEFI boot > partition. > > In sadly this impact *is not properlydocumented* in the corresponding > system-wide change [2]. :/ /boot/efi/EFI/Boot should contain bootx64.efi which should also be identical (other than filename) to shimx64.efi, and fallback.efi Sounds like the package scripts don't update NVRAM boot entries, and then also fallback.efi isn't including the proper path with new shim filename. Just a guess. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
