Proper config of fwupd in PVE 9

[EllerholdAG]

Hello lovely proxmox people,

I wanted to test if fwupd could update any of my devices in my server.

After installation in PVE 9, it couldnt find the ESP!

In the PVE documentation https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_firmware_persistent it says to add `EspLocation=/boot/efi` to the `/etc/fwupd/daemon.conf`. This doesnt work either. (The doc is outdated in more ways: you have to add [fwupd] before EspLocation= too and this file gets automatically copied to /etc/fwupd/fwupd.conf).

Looking at https://github.com/fwupd/fwupd/wiki/PluginFlag:esp-not-found, it seems like this workaround was disabled by the fwupd package.

Is there any chance we could get fwupd working again in PVE 9?

In PVE8 this seem to work - even without EspLocation= ! There are 5 .conf files in /etc/fwupd instead of 0 in PVE9. Did something massive change in fwupd for trixie?!

 

[metcon]

I have the same problem.

I have a three node Proxmox cluster of Dell Optiplex mini PC's. Dell announced a BIOS firmware update and on version 8 I used fwupdmgr. That is not working anymore with version 9.

I think the only solution for now is to flash a USB drive with the BIOS firmware update, stick it in each node and install the firmware that way.

 

[pep.]

There's a bug tracking ticket but no documented progress: https://bugzilla.proxmox.com/show_bug.cgi?id=6654

 

[pludikovsky]

Found this thread because I've had the same issue, but it seems I managed to fix it:

1. Install (if not already done) `udisks2`
2. Run /usr/bin/fwupdtool esp-list --verbose. This should start the udisks services through the socket.
3. fwupmgr get-updates etc. shouldn't complain anymore

I based it on this part of the fwupd Wiki:

To debug, you can use sudo /usr/bin/fwupdtool esp-list --verbose and most commonly you'll see a warning about GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UDisks2 was not provided by any .service files - in this case you can install UDisks and restart your computer.

 

[pep.]

Found this thread because I've had the same issue, but it seems I managed to fix it:

1. Install (if not already done) `udisks2`
2. Run /usr/bin/fwupdtool esp-list --verbose. This should start the udisks services through the socket.
3. fwupmgr get-updates etc. shouldn't complain anymore

I based it on this part of the fwupd Wiki:

I can't find the post right now, but AFAIK udisks2 is "deprecated" on Proxmox's part because it pulls in a lot of dependencies and has apparently caused issues in the past.

 

[pludikovsky]

@pep. It's stated in the Firmware Updates article:

Proxmox VE ships its own version of the fwupd package to enable Secure Boot Support with the Proxmox signing key. This package consciously dropped the dependency recommendation for the udisks2 package, due to observed issues with its use on hypervisors.

But since the Upstream support for the EspLocation option was removed I guess the fallback is udisks2 again I guess.