Update firmware fails

[red11]

1. It started yesterday when I booted up Blufin 42 Stable I got Software notification:
   
   

I assume this is some false positive, because I don’t know if Software is obligated to install some firmware level software in “immutable” distro.

QUESTION: Does Software really takes care of installing firmware or is this false positive?

2. If I open up Firmware app I get this:
   
   
   
   clicking on Upgrade button and software gets downloaded and then reports error:
   
   

It looks like bug: Updating EM120R GL fails "no firehose port provided for filename" · Issue #8598 · fwupd/fwupd · GitHub

QUESTION: Is this really a bug?

3. If inside Firmware app I click on Lenovo System Firmware I get the following:
   
   

Looks like there are three versions available from my currently installed firmware. If I click on e.g top Upgrade button it downloads the software and it displays info that update requires reboot with reboot confirmation and after reboot nothing happens. I expected new firmware to be installed, but nothing. Then back to step 1.

QUESTION: Is this upgrading firmware somehow broken or am I missing something?

---

4. General question: Am I just being unlucky with this firmware updates or do you experience the same level of “challenges”?

[inffy]

fwupd is the part that handles those under the hood.

So yes firmware can be updated on immutable distros just like in any other.

Then it depends on your OEM how they handle those, most of them don’t provide firmwares through LVFS. Lenovo, framework atleast do and some HP models.

[tunix]

I bought my first Thinkpad this week and you just shared the same experience I had. Unfortunetely Device Firmware app is a mess and has bad UX. The CLI on the other hand takes care of upgrading firmwares just fine. You can do so via fwupdmgr upgrade and it’ll update all devices. (just keep saying no to reboot requests until all firmware are gone through)

[inffy]

Yep, I handle all of them through terminal with fwupdmgr

[red11]

I get the same error using fwupdmgr upgrade from terminal:

[shishimaru]

I guess it’s worth to ask Lenovo how to properly update that sometimes they provide with something to flash through BIOS

[red11]

In first post I have posted link to original bug report and it is exactly the same chip.

My laptop is working just fine, I don’t have an urge to update firmware. I expect bug will be fixed some day and after Blufin update I will have an option to upgrade.

I was just currious if some forum member have the similar issue, because we are all using the same software (Blufin) and maybe expecting some general software issue. But in this case issue is probably way more specific and closer to real hardware then in most other cases.

The PC world is difficult to manage, because hardware components are way more dispersed in PC world than in e.g. mobile world. Despite I am having standardised product (Lenovo Thinkpad L14), but because of using niche system (Blufin with only few thousands daily users), chances two uses having same hardware are slim. Like Eskimo swimming inside Brasilian rain forest brook.

I don’t know if I want to bother with asking Lenovo, because (link in my first post) it looks like a known bug.

[red11]

Today I have ujust update and I see 42.20250720.2 was installed with:

  fwupd 2.0.7-100.ublue -> 2.0.12-100.ublue
  fwupd-plugin-flashrom 2.0.7-100.ublue -> 2.0.12-100.ublue
  fwupd-plugin-modem-manager 2.0.7-100.ublue -> 2.0.12-100.ublue
  fwupd-plugin-uefi-capsule-data 2.0.7-100.ublue -> 2.0.12-100.ublue

This is great, because from bug report I see this issue was fixed in fwupd 2.0.9 and now Blufin upgrades fwupd from 2.0.7 to 2.0.12.

Then I have rebooted and executed: fwupdmgr upgrade and update successfully finished, prompted to reboot and during BIOS start firmware upgrade appeared and successfully completed.

Problem solved.