[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#968997: fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot



Package: fwupd
Version: 1.4.5-1
Severity: normal
X-Debbugs-Cc: debian@rocketjump.eu

Hi,

--8<------8<------8<------8<------8<------8<------8<------8<------8<----

# fwupdmgr update
• Thunderbolt Controller has the latest available firmware version
• Embedded Controller has the latest available firmware version
• Intel Management Engine has the latest available firmware version
• Prometheus has the latest available firmware version
• Prometheus IOTA Config has the latest available firmware version
• SAMSUNG MZVLB1T0HBLR-000L7 has no available firmware updates
Upgrade available for System Firmware from 0.1.66 to 0.1.68
20N2CTO1WW must remain plugged into a power source for the duration of the update to avoid damage. Continue with update? [Y|n]: Y
Downloading…             [***************************************]
Decompressing…           [***************************************]
Authenticating…          [***************************************]
Updating System Firmware…[***************************************]
Scheduling…              [***************************************]
Successfully installed firmware
• UEFI Device Firmware has no available firmware updates
• UEFI Device Firmware has no available firmware updates

An update requires a reboot to complete. Restart now? [y|N]: y

--8<------8<------8<------8<------8<------8<------8<------8<------8<----

After reboot however the firmware does not get updated, and it cleanly boots
into Debian. System firmware stays at 0.1.66. Variants I've tried:

* Disabling secure boot
* Removing fwupd-amd64-signed
* Shutdown and cold boot
* Running from single user mode (requires starting dbus and NetworkManager)

I have successfully updated the firmware of this Thinkpad T490 in the past. I've
also tried debugging it to some extent, two fwupd-*.cap files are generated in
/boot/efi/EFI/debian/fw/, however I don't quite know how they should interact
with the UEFI firmware.

If you have any further suggestions how to debug this further, let me know.

Regards,
Lee

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fwupd depends on:
ii  libc6                  2.31-3
ii  libefiboot1            37-2.1
ii  libefivar1             37-2.1
ii  libelf1                0.180-1+b1
ii  libflashrom1           1.2-5
ii  libfwupd2              1.4.5-1
ii  libfwupdplugin1        1.4.5-1
ii  libglib2.0-0           2.64.4-1
ii  libgudev-1.0-0         233-1
ii  libgusb2               0.3.4-0.2
ii  libjcat1               0.1.3-2
ii  libjson-glib-1.0-0     1.4.4-2
ii  libpolkit-gobject-1-0  0.105-29
ii  libsmbios-c2           2.4.3-1
ii  libsoup2.4-1           2.70.0-1
ii  libsqlite3-0           3.33.0-1
ii  libtss2-esys0          2.4.1-1+b1
ii  libxmlb1               0.1.15-2
ii  shared-mime-info       1.15-1

Versions of packages fwupd recommends:
ii  bolt          0.9-1
pn  fwupd-signed  <none>
ii  python3       3.8.2-3

fwupd suggests no packages.

-- no debconf information

Reply to: