Actionable Item: Integrate fwupd (pulled from repo due to lack of integration points) in various tools and software in Solus. The should likely be:
- Mentioned In
- D5809: Update python-docker-py to 3.7.1
R3918:094d33259e0a: Initial inclusion of fwupdate
D2379: Initial inclusion of fwupdate
R3917:0ad3c93b648a: Initial inclusion of libsmbios
D1503: Initial inclusion of fwupd
D1502: Initial inclusion of fwupdate
D1501: Initial inclusion of libsmbios
- Mentioned Here
- D5647: Initial commit of fwupd
T61: look of solus-sc seems broken on unstable (gtk 3.20)
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 :)
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 Version: 0.2.4.2 VersionLowest: 0.2.4.2 Created: 2018-01-23
What am I missing?
I just read that Lenovo has joined the LVFS (https://phoronix.com/scan.php?page=news_item&px=Lenovo-LVFS-Support). 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 !
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.
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".
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.
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 \ https://staging.fwupd.org/lvfs/upload_hwinfo
}solus@user ~ $
FYI the upload is failing
cat /etc/machine-id` \ -F file=@/tmp/id-ctrl \ https://staging.fwupd.org/lvfs/upload_hwinfo <!DOCTYPE html> <!-- Copyright (C) 2018 Richard Hughes <firstname.lastname@example.org> Licensed under the GNU General Public License Version 2 --> <html lang="en"> <head> <title>LVFS: Temporarily Unavailable</title> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0-beta.2/css/bootstrap.min.css" integrity="sha384-PsH8R72JQ3SOdhVi3uxftmaW6Vc51MKb0q5P2rRUpPvrszuE4W1povHYgTpBfshb" crossorigin="anonymous"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> </head> <body> <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. </div> </div> </div> </body> </html>
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.