[Bug 1222676] New: EFI Firmware Updates downloaded, but not installed
https://bugzilla.suse.com/show_bug.cgi?id=1222676 Bug ID: 1222676 Summary: EFI Firmware Updates downloaded, but not installed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: gp@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- This has been going on for some months where regardless of whether I use fwupdtool or GNOME Software available firmware updates are shown, downloaded, and a reboot offered, alas when I reboot these updates are not installed. After running whatever update tool, updates are present under /boot/efi/EFI/opensuse/fw. After reboot they are gone - but apparently not installed (and indeed there is nothing unusual during the power on and boot sequence, like I believe I saw in the past when firmware updates were applied): % ls -l /boot/efi/EFI/opensuse/fw -rwxr-xr-x 1 root root 1243680 Apr 1 16:09 fwupd-279599d4-78c7-4c99-84ea-4a7c8d2b10e1.cap -rwxr-xr-x 1 root root 9431077 Apr 1 16:09 fwupd-4e78ce68-5389-4a95-bf10-e3568c30caf8.cap -rwxr-xr-x 1 root root 28843840 Apr 1 16:09 fwupd-a0fd4aef-f691-4c90-a089-7dd4f4481db0.cap % ls -l /boot/efi/EFI/opensuse/ total 4,5M -rwxr-xr-x 1 root root 847k Apr 1 03:39 MokManager.efi -rwxr-xr-x 1 root root 58 Apr 1 03:39 boot.csv drwxr-xr-x 2 root root 4,1k Apr 1 16:09 fw -rwxr-xr-x 1 root root 64k Feb 25 2023 fwupdx64.efi -rwxr-xr-x 1 root root 203 Apr 1 03:39 grub.cfg -rwxr-xr-x 1 root root 2,1M Apr 1 03:39 grub.efi -rwxr-xr-x 1 root root 541k Apr 1 03:39 grubx64.efi -rwxr-xr-x 1 root root 935k Apr 1 03:39 shim.efi Asking naively: is /boot/efi/EFI/opensuse/fw the right directory for these updates to be put in? It looks is if they are not "found", yet "something" removes them upon startup? Hardware is a ThinkPad X1 Yoga Gen 8. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222676 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |jlee@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222676 Joey Lee <jlee@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jlee@suse.com |dennis.tseng@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222676 https://bugzilla.suse.com/show_bug.cgi?id=1222676#c1 --- Comment #1 from Tseng <dennis.tseng@suse.com> --- Could you manually install those .cap files ? For example: $fwupdmgr get-updates $fwupdmgr install fwupd-279599d4-78c7-4c99-84ea-4a7c8d2b10e1.cap $reboot
Asking naively: is /boot/efi/EFI/opensuse/fw the right directory for these updates to be put in? It looks is if they are not "found", yet "something" removes them upon startup?
In my environment with fwupd-1.8.6: step-1) fwupdmgr refresh Successfully downloaded new metadata: 2 local devices supported. $ls /var/lib/fwupd/metadata/lvfs metadata.xml.xz metadata.xml.xz.jcat step-2) fwupdmgr update download .cap files now ... Before reboot, let's check cap files in fw directory: $ls /boot/efi/EFI/opensuse/fw xxxxxx.cap xxx.cap Also let's check devices to be updated: $fwupdmgr get-updates No updates available ............ Devices with the latest available firmware updates: . System Firmware . xxxxxxxxx $sudo reboot Updating your firmware Do not power down you system. step-3) Double check final result after system reboot, $fwupdmgr get-updates Devices that have been updated successfully /boot/efi/EFI/opensuse$ ls fw xxxxx.cap still there. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com