#fwupdmgr 2.1.3 hat meine Logitech Maus "soft gebrickt".
Das Update ist fehlgeschlagen - Maus tot.
fwupdmgr Downgrade auf 2.0.20 hat Wunder gewirkt.
Alles wieder gut.
Das war knapp!

#opensuse #slowroll

#nørdpost på engelsk

I'm running Kubuntu with Plasma 6 and the associated graphical software/application installation and update manager Discover. It is a pretty neat piece of software, spanning the general application manager (apt), flatpaks, snaps and firmware through fwupdmgr.
However when fwupdmgr doesn't play along it becomes a bit annoying. It keeps finding an update for the Lenovo USB-C dock (which I am pretty happy with), but fwupdmgr is not my friend in this case, so I can't actually perform the update.
But every time I use Discover for updating, I need to unselect the dock firmware manually, because I can't make Discover ignore it...
If somebody knows of a way to make Discover ignore a specific update I'd love to hear about it 😆.

🧵 1/2

#KDE #Discover #fwupdmgr #kubuntu #Lenovo

fwupdmgr ist einfach großartig! 👌

Egal ob Dock-Firmware, EFI oder sonst etwas - FW-Aktualisierungen waren nie einfacher.

#linux #fwupdmgr #firmware #efi #update

Edit: seems to be resolved now

Anyone else getting fwupdmgr checksum errors right now?

$ fwupdmgr refresh --force
Updating lvfs
Downloading… [************************************** ]
Failed to update metadata for lvfs: checksum failure: failed to verify data, expected ffbee0c4af245985093489884ef435767f1fd919

#fwupdmgr #lvfs #fwupd

There is a kernel regression (https://bugzilla.redhat.com/show_bug.cgi?id=2346831) that prevents the creation of zero-size EFI variables and breaks #fwupdmgr on some bleeding-edge #Linux distributions.

If you are getting a "failed to write-firmware: could not set DP_BUF" error message while trying to update your PC/laptop/server firmware, or upgrading through e.g. GNOME Software silently fails, you can:

- Boot an older kernel (6.13.2 works for me)

- Use a fixed fwupd version (commit 1c94c4f)

- Do nothing and wait

A #virtualization update: the idling load average of 1 *wasn't* the fault of #Proxmox, but a perpetually firing IRQ (or something in that area, according to "top") making the system think it had more to do than it actually did.

See if you can spot the point on the graph where I used this really useful blog post (https://static.xtremeownage.com/blog/2024/proxmox---random-error-fixes/) to help me prep before a #firmware update under Proxmox, and then rebooted to resolve the firmware issue ... :-D #fwupd #fwupdmgr #EFI #UEFI #Linux #hardware

fwupdmgr: /usr/libexec/fwupd/efi/fwupdx64.efi and /usr/libexec/fwupd/efi/fwupdx64.efi.signed cannot be found

#Ubuntu #BIOS #EFI #UEFI #fwupdmgr

https://andreas.scherbaum.la/blog/archives/1137-fwupdmgr-usrlibexecfwupdefifwupdx64.efi-and-usrlibexecfwupdefifwupdx64.efi.signed-cannot-be-found.html