Page MenuHomeSolus

Integrate fwupd
Open, LowPublic


Actionable Item: Integrate fwupd (pulled from repo due to lack of integration points) in various tools and software in Solus. The should likely be:

  • Software Center - Firmware installation and updating. Relevant upstream repo here however no upstream issue, not necessary.
  • Maybe sol
  • Track and land upstream clr-boot-manager fwupd support, pending issue here.
marcvg created this task.Feb 10 2017, 2:22 PM
marcvg updated the task description. (Show Details)Feb 20 2017, 9:46 AM
marcvg updated the task description. (Show Details)

More information about vendor support here:

DataDrake triaged this task as Normal priority.

This is going to have to wait until appstream-glib gets updated.

I could not find a complete list of vendors that use this technology, but Dell is one of them.

It's kind of hidden in the End Users page of the fwupd site.

siru added a subscriber: siru.Apr 8 2017, 11:45 AM
ikey changed the status of subtask T2675: Update appstream-glib to 0.6.11 from Open to In Progress.Apr 12 2017, 11:11 PM
ikey added a subscriber: ikey.

fwupd is going to need managing by clr-boot-manager. Please note that it is NOT PERMITTED for any Solus package to contain /boot files anymore. I'm planning for clr-boot-manager to manage fwupd though, so I'd like to see this in the repo, with that exception :)

taaem added a subscriber: taaem.May 8 2017, 9:29 PM

Happy to see that this is going to be implemented at some point, looking forward to that.

sd added a subscriber: sd.Jul 2 2017, 2:52 AM
jalden added a subscriber: jalden.Jul 3 2017, 10:05 AM
DataDrake reassigned this task from DataDrake to ikey.Jul 9 2017, 5:37 PM

@ikey, anything new after 6 months?

alecbcs added a subscriber: alecbcs.
joebonrichie added a subscriber: joebonrichie.

Saving ikey some time for when he gets to this, also interested in playing around with supported firmware myself.

joebonrichie renamed this task from fwupd 0.8.0 to fwupd.Nov 30 2017, 5:44 PM

I suppose before updating firmware there must be a way to find out what firmware it is that I have on my computer. Is such a probing function integrated with fwupd or would a tool like MEAnalyzer be necessary? See:

marcvg added a comment.Dec 6 2017, 2:39 PM

Device/hardware detection is part of fwupd.

fwupdmgr get-devices

Displays all devices detected by fwupd.

I would assume that it only detects supported devices.

wmutschl added a subscriber: wmutschl.EditedJan 23 2018, 8:39 PM

Hi, I have a Dell XPS 13 and used fwupdmgr in Ubuntu to update my firmware. Now I am using Solus and tried to install fwupd with snap, i.e. as root user (or with sudo):

snap install uefi-fw-tools
snap connect uefi-fw-tools:fwupdmgr uefi-fw-tools:fwupd
uefi-fw-tools.fwupdmgr refresh
uefi-fw-tools.fwupdmgr get-devices

However, the only thing it finds is:

XPS 13 9360
Guid:                 5ff..................
DeviceID:             UEFI-5ff........
Provider:             UEFI
Flags:                internal|allow-offline|require-ac|supported
Created:              2018-01-23

What am I missing?

I just read that Lenovo has joined the LVFS ( Now I can easily update the firmware of my ThinkPad. Will fwupd be available anytime soon?

It's not because a company joins the LVFS that magically you'll be able to update the firmware of your computer... It doesn't mean that all the models of this manufacturer will be supported and this is especially true for older models !!!

This is anyway in the Solus to-do list, probably not a high priority item though and anyway it is pending upstream. If you want to discuss this further, there are the forums and the social medias... this is the bug tracker !

JoshStrobl added a subscriber: JoshStrobl.EditedAug 6 2018, 5:31 PM

If you want to discuss this further, there are the forums and the social medias... this is the bug tracker !

This is a development tracker and @Vistaus's comment is relevant to the task, since the LVFS support enables them to ship updated firmware via fwupd. You are correct however regarding the fact it may not support their device, but the tone could've been different.

From Hughes' post:

That said, we’ll only be supporting UEFI hardware produced fairly recently, so there’s no point looking for updates on your beloved T61. I also can’t comment on what other Lenovo branded hardware is going to be supported in the future as I myself don’t know.

Vistaus added a comment.EditedAug 6 2018, 5:54 PM

Thanks @JoshStrobl ! I'm pretty sure that my device will be supported as this ThinkPad model was officially released globally in February 2018 as part of their (new) 2018 line-up (though I bought it last month), so it would be weird if Lenovo wouldn't support their 2018 line-up through this new firmware update method as 2018 is the current year, so the 2018 line-up should be covered by "fairly recently".

JoshStrobl reopened this task as Open.Aug 6 2018, 6:13 PM

I'm going to re-open this task and move it to Software (for "enabling fwupd") since we technically landed it (thus fulfilling the package request + inclusion), however pulled it from the repo when @joebonrichie landed it, since we have no integration points at this moment in time, in addition to pending upstream items.

JoshStrobl lowered the priority of this task from Normal to Low.
JoshStrobl moved this task from Backlog to Improvement on the Software board.
JoshStrobl added a project: Upstream Issue.

Adding Upstream Issue since it relies on changes in clr-boot-manager.

JoshStrobl renamed this task from fwupd to Integrate fwupd.Aug 6 2018, 6:17 PM
JoshStrobl updated the task description. (Show Details)
K4rlos added a subscriber: K4rlos.Aug 7 2018, 12:00 PM
crom5 added a subscriber: crom5.Aug 21 2018, 5:39 AM

Yesterday, 20.08.2018 I noticed an interesting info: "The Next Challenge For Fwupd / LVFS Is Supporting NVMe SSD Firmware Updates". Shortly said, Richard Hughes at Red Hat is hoping for Linux users with NVMe drives to send him the id-ctrl identification data on their drives - this data will be useful so he knows what drives/models are most popular but also for how the firmware revision string is advertised across drives and vendors:

I followed the instructions. Can you please confirm that all went ok:

solus@user ~ $ sudo nvme id-ctrl --raw-binary /dev/nvme0 > /tmp/id-ctrl
solus@user ~ $ curl -F type=nvme \

-F "machine_id="`cat /etc/machine-id` \
-F file=@/tmp/id-ctrl \


"success": true

}solus@user ~ $

FYI the upload is failing

cat /etc/machine-id` \
-F file=@/tmp/id-ctrl \
<!DOCTYPE html>
<!-- Copyright (C) 2018 Richard Hughes <>
     Licensed under the GNU General Public License Version 2 -->
<html lang="en">
    <title>LVFS: Temporarily Unavailable</title>
    <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
    <link rel="stylesheet" href="" integrity="sha384-PsH8R72JQ3SOdhVi3uxftmaW6Vc51MKb0q5P2rRUpPvrszuE4W1povHYgTpBfshb" crossorigin="anonymous">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <div class="container mt-3">
      <div class="container mt-3">
        <div class="alert alert-warning" role="alert">
          The LVFS is temporarily unavailable and should be back soon.

Any updates on fwupd its badly needed for folks like me who have purchase laptops like X1 Carbon 6th gen and have battery drain issues during sleep

JoshStrobl removed ikey as the assignee of this task.Feb 9 2019, 8:25 PM
Jacalz added a subscriber: Jacalz.Feb 9 2019, 8:28 PM
nursoda added a subscriber: nursoda.Mar 6 2019, 8:54 AM
der_eismann added a comment.EditedMar 8 2019, 11:09 PM

I wanted to give it another try because I also really need this and I noticed that Clear Linux already has a package for it, which means that clr-boot-manager must be compatible.
TL;DR: I just updated the ME firmware of my T480s successfully.

The package still needs some polish (as I have basically no knowledge of DBus, polkit & stuff like that), but it's working fine. The only problem I see is that we don't mount the EFI partition which means the user has to do it himself when he wants to update BIOS/firmware. Any ideas on that? Maybe someone can help me with that, see D5647.

The only problem I see is that we don't mount the EFI partition which means the user has to do it himself when he wants to update BIOS/firmware.

That's what ikey meant by fwupd needs managing by clr-boot-manager.

Ah, you're probably right. However I wouldn't consider this a blocker because there are lots of updates that don't require the EFI partition and it's possible to make it run without clr-boot-manager integration. Also it doesn't seem like there is much development on that front.

pappfer added a subscriber: pappfer.Apr 2 2019, 7:05 AM
Jacek added a subscriber: Jacek.Apr 15 2019, 8:34 AM

It looks like the Clear Linux team is no longer interested in integrating this into clr-boot-manager. If all that needed, is to mount the /boot partition before running fwupd, maybe we could consider integrating this with eopkg for the time being, and then sol later on.