Bug#945203: fwupd: Cannot update firmware
Michael Ott
Version: 1.3.3-3
Severity: important
Dear Maintainer,
My problem is the same as describe here:
https://github.com.cnpmjs.org/fwupd/fwupd/issues/1330
When I downgrade to the stable version I saw that same error.
But in version 1.3.3 I receive that one but I also cannot update
firmware:
fwupdmgr update
No upgrades for Thunderbolt Controller, current is 20.00: 20.00=same, 17.01=older
No upgrades for System Firmware, current is 0.1.33: 0.1.30=older, 0.1.29=older, 0.1.28=older, 0.1.26=older, 0.1.25=older, 0.1.33=same
Upgrade available for UEFI Device Firmware from 184.65.3590 to 184.70.3626
20KF001GGE must remain plugged into a power source for the duration of the update to avoid damage. Continue with update? [Y|n]: y
Downloading 184.70.3626 for UEFI Device Firmware...
Decompressing… [***************************************]
Authenticating… [***************************************]
Updating UEFI Device Firmware… ]
Scheduling… [***************************************]
failed to write data to efivarfs: Error writing to file descriptor: No space left on device
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (710, 'unstable'), (670, 'testing'), (660, 'experimental'), (600, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fwupd depends on:
ii libarchive13 3.4.0-1+b1
ii libc6 2.29-3
ii libefiboot1 37-2
ii libefivar1 37-2
ii libelf1 0.176-1.1
ii libfwupd2 1.3.3-3
ii libgcab-1.0-0 1.3-1
ii libglib2.0-0 2.63.1-2
ii libgnutls30 3.6.10-5
ii libgpg-error0 1.36-7
ii libgpgme11 1.13.1-1
ii libgudev-1.0-0 233-1
ii libgusb2 0.3.0-1
ii libjson-glib-1.0-0 1.4.4-2
ii libpolkit-gobject-1-0 0.116-2
ii libsmbios-c2 2.4.1-1
ii libsoup2.4-1 2.68.2-2
ii libsqlite3-0 3.30.1-1
ii libtss2-esys0 2.3.1-3
ii libxmlb1 0.1.13-1
ii shared-mime-info 1.10-1
Versions of packages fwupd recommends:
ii bolt 0.8-4
ii fwupd-amd64-signed [fwupd-signed] 1.3.3+3
ii python3 3.7.5-3
fwupd suggests no packages.
-- no debconf information
Mario.Li...@dell.com
robert
Version: 1.9.3-1
Followup-For: Bug #945203
Dear Maintainer,
A warning displayed each time I login the system (Lenovo IdeaPad 340) says
there is an update available. After ignoring it for a few weeks, I tried
updating the firmware, specifically the UEFI dbx device (217 --> 371), using
"fwupdmgr update". I received the same message:
"failed to write data to efivars: Error writing to file descriptor: No
space left on device"
After looking it up (Internet search, DBTS), I found this bug stating that
nothing can be done. I understand that there is nothing else to do if there is
not more room. Regarding the other suggested possibility (about the BIOS
locking it down), is there any option to convince the BIOS to be more "open"?
Anyway, another question is about a way to remove or to avoid the warning when
login (when the update is not possible as is our case).
The last question is to calm down my curiosity because of my poor understanding
of the life of a (software) bug. This is one of my first bug reports, and I
still don't get the criteria to change the bug status. Why the bug is open yet?
I mean, it has been dealt with. What else can be done? It is my understanding
that the information will still be available even if the bug is closed.
Thank you in advance for your time. Regards, robert
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fwupd depends on:
ii adduser 3.137
ii libarchive13 3.6.2-1
ii libc6 2.37-6
ii libcbor0.8 0.8.0-2+b1
ii libcurl3-gnutls 7.88.1-10
ii libflashrom1 1.3.0-2.1
ii libfwupd2 1.9.3-1
ii libgcab-1.0-0 1.6-1
ii libglib2.0-0 2.76.4-4
ii libgnutls30 3.7.9-2
ii libgudev-1.0-0 237-2
ii libgusb2 0.4.5-1.1
ii libjcat1 0.1.9-1
ii libjson-glib-1.0-0 1.6.6-1
ii liblzma5 5.4.1-0.2
ii libmbim-glib4 1.28.4-2
ii libmbim-proxy 1.28.4-2
ii libmm-glib0 1.20.6-2
ii libpolkit-gobject-1-0 122-4
ii libprotobuf-c1 1.4.1-1+b1
ii libqmi-glib5 1.32.4-2
ii libqmi-proxy 1.32.4-2
ii libsmbios-c2 2.4.3-1
ii libsqlite3-0 3.42.0-1
ii libsystemd0 253.5-1
ii libtss2-esys-3.0.2-0 3.2.1-3
ii libxmlb2 0.3.10-2
ii shared-mime-info 2.2-1
Versions of packages fwupd recommends:
ii bolt 0.9.5-1
ii dbus 1.14.8-2
ii fwupd-amd64-signed [fwupd-signed] 1:1.4+1
ii jq 1.6-2.1
ii python3 3.11.4-5
pn secureboot-db <none>
ii udisks2 2.10.0-4
Versions of packages fwupd suggests:
ii gir1.2-fwupd-2.0 1.9.3-1
-- Configuration Files:
/etc/fwupd/daemon.conf [Errno 2] El fitxer o directori no existeix: '/etc/fwupd/daemon.conf'
/etc/fwupd/fwupd.conf [Errno 13] S’ha denegat el permís: '/etc/fwupd/fwupd.conf'
/etc/fwupd/msr.conf [Errno 2] El fitxer o directori no existeix: '/etc/fwupd/msr.conf'
/etc/fwupd/redfish.conf [Errno 2] El fitxer o directori no existeix: '/etc/fwupd/redfish.conf'
/etc/fwupd/thunderbolt.conf [Errno 2] El fitxer o directori no existeix: '/etc/fwupd/thunderbolt.conf'
/etc/fwupd/uefi_capsule.conf [Errno 2] El fitxer o directori no existeix: '/etc/fwupd/uefi_capsule.conf'
-- no debconf information
robert
Version: 1.9.3-1
Followup-For: Bug #945203
Dear Maintainer,
I am writing to add that the firmware has been updated. I do not know how,
when, or why.
The message informing about a new possible upgrade did not show up recently.
When I realized that (it took more than a few boot cycles), I reviewed the
history which confirmed the upgrade.
This is not helpful. I mean things happening without any supervision.
Thanks anyway. Regards.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fwupd depends on:
ii adduser 3.137
ii libarchive13 3.6.2-1
ii libc6 2.37-7
ii libcbor0.8 0.8.0-2+b1
ii libcurl3-gnutls 8.2.1-1
ii libflashrom1 1.3.0-2.1
ii libfwupd2 1.9.3-1
ii libgcab-1.0-0 1.6-1
ii libglib2.0-0 2.77.1-2
ii libgnutls30 3.7.9-2
ii libgudev-1.0-0 237-2
ii libgusb2 0.4.5-1.1
ii libjcat1 0.1.9-1
ii libjson-glib-1.0-0 1.6.6-1
ii liblzma5 5.4.1-0.2
ii libmbim-glib4 1.28.4-2
ii libmbim-proxy 1.28.4-2
ii libmm-glib0 1.20.6-2
ii libpolkit-gobject-1-0 123-1
ii libprotobuf-c1 1.4.1-1+b1
ii libqmi-glib5 1.32.4-2
ii libqmi-proxy 1.32.4-2
ii libsmbios-c2 2.4.3-1
ii libsqlite3-0 3.42.0-1
ii libsystemd0 254-1
ii libtss2-esys-3.0.2-0 3.2.1-3
ii libxmlb2 0.3.10-2
ii shared-mime-info 2.2-1
Versions of packages fwupd recommends:
ii bolt 0.9.5-1
ii dbus 1.14.8-2
ii fwupd-amd64-signed [fwupd-signed] 1:1.4+1
ii jq 1.6-2.1
ii python3 3.11.4-5
pn secureboot-db <none>
ii udisks2 2.10.0-5