I did not change any bios settings since upgrade from eoan, and firmware update worked in eoan.
But I found something interesting. In "normal life" my efi configuration looks like this: BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0001,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023,0024,0002 Boot0001* ubuntu HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi) Boot0002* Linux-Firmware-Updater HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.d.x.6.4...e.f.i... Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850) Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380) ... Note that there is an entry for fwupdx64 number 0002. After running fwupdmgr, configuration looks like this: BootNext: 0000 BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0001,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023,0024,0002,0000 Boot0000* Linux-Firmware-Updater HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.d.x.6.4...e.f.i... Boot0001* ubuntu HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi) Boot0002* Linux-Firmware-Updater HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.d.x.6.4...e.f.i... Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850) Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380) ... Note that fwupdmgr added a new entry for Linux-Firmware-Updater number 0000, and set it for BootNext. So now there are two entries for Linux- Firmware-Updater, that looks the same. After reboot, updater _did not_ run, and efi configuration returned to "normal" state. After that, I set BootNext to 0002 by hand, and rebooted. And now, firmware updater _worked_! Another piece of information: replacing shim-signed actually _did_ make a difference. I tried setting BootNext to 0002 with the previous focal shim, and it did _not_ run updater. Now it does. So maybe there is a second problem, with fwgupdmgr that sets a second entry? Or there is another problem in the shim, that it does not honour the second entry or entry number 0000 in efi configuration?... Tell me if you need more information from me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864223 Title: shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
