Public bug reported: On Lenovo ThinkPad Carbon gen 7, the default EFI boot list 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) ... After fwupdmgr downloads new firmware and tries to prepare the updater, the list looks like this before reboot: 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 there are two entries for the firmware updater, "standard" 2 and a new one: 0, with BootNext pointing to the newly created entry 0. Upon reboot, firmware updater _does not run_, update files stay in /boot/efi/EFI/ubuntu/fw, and boot order table returns to "default" state. After that, if I set BootNext to 2 by hand and reboot, fwupdx64 runs and updates are successfully installed. It looks like fwupdmgr fails to recognize existing boot entry for fwupdx64 and creates a new one, and such configuration apparently confuses the BIOS. Mario Limonciello from the shim team(?) expressed thoughts about it here: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1864223/comments/33 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fwupd 1.3.9-4 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 6 15:07:40 2020 InstallationDate: Installed on 2020-01-02 (155 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: 2020-02-28T20:48:58.742643 mtime.conffile..etc.fwupd.remotes.d.lvfs.conf: 2020-02-28T20:48:58.770639 ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882357 Title: ThinkPad Carbon g7: fwupd creates duplitate entries for Linux- Firmware-Updater To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1882357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
