#fwupdmgr — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fwupdmgr, aggregated by home.social.
-
#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
-
#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
-
@tootbrute
Yeah... that's really cool.
To be honest, updating works on every distro manually with #fwupdmgr
But on Fedora, the updates are made automatically by the systems Updatemanager. (i.e. Discover on KDE) -
@tootbrute
Yeah... that's really cool.
To be honest, updating works on every distro manually with #fwupdmgr
But on Fedora, the updates are made automatically by the systems Updatemanager. (i.e. Discover on KDE) -
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 -
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 -
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 -
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 -
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
-
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
-
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
-
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
-
-
-
-
