Description of problem: When I did a full dnf upgrade a month or so ago the machine failed to boot, just straight to a black screen. I managed to reboot by choosing the other (bios?) version of Fedora in the motherboard boot loader (NOT the default UFEI version) When back in the system I did some detective work and discovered that if I downgraded back to the following files it worked again: shim-ia32-13-4.x86_64.rpm shim-x64-13-4.x86_64.rpm I think this file is the culprit: https://bodhi.fedoraproject.org/updates/FEDORA-2018-92b266d831 But I did an update today and the exact same thing happened, and the exact same solution worked. I think all newer versions of shim-ia32 and shim-x64 fail to work on my machine description: Desktop Computer product: All Series (All) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-2.7 dmi-2.7 smp vsyscall32 configuration: administrator_password=disabled boot=normal chassis=desktop family=ASUS MB frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled sku=All uuid=4D83D2AB-10AB-C936-9BAC-AC220B4F45BF *-core description: Motherboard product: H87I-PLUS vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 130815220502647 slot: To be filled by O.E.M. *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2003 date: 11/05/2014 size: 64KiB capacity: 8MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-sata description: SATA controller product: 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] vendor: Intel Corporation physical id: 1f.2 bus info: pci@0000:00:1f.2 logical name: scsi0 logical name: scsi1 logical name: scsi2 version: 05 width: 32 bits clock: 66MHz capabilities: sata msi pm ahci_1.0 bus_master cap_list emulated configuration: driver=ahci latency=0 resources: irq:26 ioport:f0d0(size=8) ioport:f0c0(size=4) ioport:f0b0(size=8) ioport:f0a0(size=4) ioport:f060(size=32) memory:f7c36000-f7c367ff *-disk:0 description: ATA Disk product: Samsung SSD 840 physical id: 0 bus info: scsi@0:0.0.0 logical name: /dev/sda version: CB6Q serial: S1D5NSADB86177Y size: 111GiB (120GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=5 guid=b84053b8-ad3e-44af-abac-dc983e76bb2a logicalsectorsize=512 sectorsize=512 *-volume:0 UNCLAIMED description: Windows FAT volume vendor: mkfs.fat physical id: 1 bus info: scsi@0:0.0.0,1 version: FAT16 serial: 7d49-fc3a size: 198MiB capacity: 199MiB capabilities: boot fat initialized configuration: FATs=2 filesystem=fat name=EFI System Partition *-volume:1 description: EXT4 volume vendor: Linux physical id: 2 bus info: scsi@0:0.0.0,2 logical name: /dev/sda2 logical name: /boot version: 1.0 serial: 41f44d01-fbd0-436b-8018-2debe9c26b11 size: 1GiB capabilities: journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized configuration: created=2018-05-13 17:29:15 filesystem=ext4 lastmountpoint=/boot modified=2018-08-22 15:57:30 mount.fstype=ext4 mount.options=rw,seclabel,relatime mounted=2018-08-22 15:57:30 state=mounted *-volume:2 description: EFI partition physical id: 3 bus info: scsi@0:0.0.0,3 logical name: /dev/sda3 serial: 08acd8c0-bd42-4487-8a79-dcdbcdb86dec size: 110GiB capacity: 110GiB width: 512 bits capabilities: encrypted luks initialized configuration: bits=512 cipher=aes filesystem=luks hash=sha256 mode=xts-plain64 version=1
I had a quite similar experience. With shim-x64-15-2 and UEFI Secure Boot ENABLED, an infinite boot loop occurred With shim-x64-15-2 and UEFI Secure Boot DISABLED, system boots With shim-x64-13-4 and UEFI Secure Boot ENABLED, system boot I have the grub menu enabled and the boot loop doesn't even get that far. No messages are visible (or the reboot is so fast message can't be seen). System is description: Notebook product: 80TJ (LENOVO_MT_80TJ_BU_idea_FM_Lenovo ideapad 110-15ACL) vendor: LENOVO version: Lenovo ideapad 110-15ACL serial: PF0JG1KR width: 64 bits capabilities: smbios-2.7 dmi-2.7 smp vsyscall32 configuration: administrator_password=disabled boot=normal chassis=notebook family=IDEAPAD frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled sku=LENOVO_MT_80TJ_BU_idea_FM_Lenovo ideapad 110-15ACL uuid=E3FE175B-DC9F-E611-801F-C85B768E59CC *-core description: Motherboard product: Nano 5A8 vendor: LENOVO physical id: 0 version: SDK0J40700 WIN serial: ******** slot: Chassis Location Unknown *-firmware description: BIOS vendor: Lenovo physical id: 0 version: 1QCN32WW date: 08/18/2016 size: 128KiB capacity: 8MiB capabilities: pci upgrade shadowing cdboot bootselect pc98 acpi usb biosbootspecification netboot *-cpu description: CPU product: AMD A8-7410 APU with AMD Radeon R5 Graphics vendor: Advanced Micro Devices [AMD] physical id: 27 bus info: cpu@0 version: AMD A8-7410 APU with AMD Radeon R5 Graphics slot: Socket FT3b size: 1232MHz capacity: 2200MHz width: 64 bits clock: 100MHz capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt topoext perfctr_nb bpext ptsc perfctr_llc cpb hw_pstate ssbd vmmcall bmi1 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale flushbyasid decodeassists pausefilter pfthreshold overflow_recov cpufreq configuration: cores=4 enabledcores=4 threads=4
I also had trouble after my latest upgrade, which was a few months late (I did not use Fedora for a while). At first I thought this was grub, but the system did not get far enough. I can confirm the workaround of downgrading to shim-x64-13-4 which gets my UEFI dual boot w/ Windows working again. I did not experience resets after selecting the Fedora boot entry, but the early boot hung with a garbled two lines of pixels on the screen. Power button shut down system on a short press, so something was still running. In case it matters, my /boot/efi is located on the first SSD while my Fedora installation is on a second SSD. UEFI Windows did boot normally after selecting it manually from the override boot menu with shim-x64-15-2 installed, and it still boots with shim-x64-13-4. System is description: Desktop Computer product: System Product Name (SKU) vendor: System manufacturer version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.0.0 dmi-3.0.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=Default string sku=SKU uui d=205EC8A4-7F73-E311-B5C0-305A3A47D884 *-core description: Motherboard product: Z170 PRO GAMING vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 150851456903667 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 0301 date: 08/10/2015 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-cpu description: CPU product: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz vendor: Intel Corp. physical id: 49 bus info: cpu@0 version: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz serial: To Be Filled By O.E.M. slot: LGA1151 size: 2410MHz capacity: 4200MHz width: 64 bits clock: 100MHz capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp flush_l1d cpufreq configuration: cores=4 enabledcores=4 threads=8
I also had this trouble after upgrading, specifically shim-ia32 and shim-x64 upgrading from 13-4 to 15-2 Tracked down to an out of date BIOS Motherboard ASUS B85M-G version 0904 After BIOS upgrade to version 3602 was able to use latest shim 15-2 packages. However, as BIOS upgrades aren't for everyone, this regression should be addressed ASAP.
I was told on a forum that shim-x64-15-7.x86_64 for Fedora 29 might fix it... Can someone official please make a comment?
shin-x64-15-7.x86_64 did not work for me
This issue is fixed with a fresh install of Fedora 29 for me. I don't know if I should mark it as fixed as the bug report is for Fedora 28, which is still broken, so maybe someone else could do whatever needs doing. Anyway, fantastic it is working in Fedora 29 :)
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.