-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package & Integrate fwupd (T2532) #292
Comments
Beatrice T. Meyers (#DataDrake), 2017-02-17 21:52:16 UTC Please format according to the following: |
Marc Van Giel (#marcvg), 2017-02-20 09:49:36 UTC More information about vendor support here: https://en.wikipedia.org/wiki/Fwupd |
Beatrice T. Meyers (#DataDrake), 2017-02-23 18:42:33 UTC This is going to have to wait until |
Nathan Caldwell (#saintdev), 2017-02-26 00:09:02 UTC
It's kind of hidden in the End Users page of the fwupd site. |
Ikey Doherty (#ikey), 2017-04-12 23:17:54 UTC
|
Michael Tintiuc (#michaeltintiuc), 2017-06-29 12:47:33 UTC Happy to see that this is going to be implemented at some point, looking forward to that. |
Philipp (#der_eismann), 2017-10-09 08:58:37 UTC #ikey, anything new after 6 months? |
Pierre-Yves (#kyrios123), 2017-10-09 09:11:27 UTC
See here : clearlinux/clr-boot-manager#77 |
Marc Van Giel (#marcvg), 2017-10-10 13:34:50 UTC Note: fwupd-1.0.0 released. https://blogs.gnome.org/hughsie/2017/10/09/fwupd-hits-1-0-0/ |
Joey Riches (#joebonrichie), 2017-11-30 17:44:25 UTC Saving ikey some time for when he gets to this, also interested in playing around with supported firmware myself. |
Martin (#baimafeima), 2017-12-06 14:19:15 UTC 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 |
Marc Van Giel (#marcvg), 2017-12-06 14:39:05 UTC Device/hardware detection is part of fwupd.
I would assume that it only detects supported devices. |
Willi Mutschler (#wmutschl), 2018-01-23 20:39:44 UTC 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):
However, the only thing it finds is:
What am I missing? |
unknown user (#unknown), 2018-08-06 16:34:18 UTC 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? |
Pierre-Yves (#kyrios123), 2018-08-06 17:13:32 UTC 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 ! |
Joshua Strobl (#JoshStrobl), 2018-08-06 17:33:35 UTC
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:
|
unknown user (#unknown), 2018-08-06 18:06:15 UTC 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". |
Joshua Strobl (#JoshStrobl), 2018-08-06 18:13:02 UTC 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. |
Joshua Strobl (#JoshStrobl), 2018-08-06 18:13:45 UTC Adding Upstream Issue since it relies on changes in |
Zvober (#crom5), 2018-08-21 05:39:42 UTC 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:
|
onkara (#iamonkara), 2018-11-19 21:05:27 UTC FYI the upload is failing
|
onkara (#iamonkara), 2018-11-19 21:08:24 UTC Any updates on |
Philipp (#der_eismann), 2019-03-08 23:28:27 UTC 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 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. |
Nathan Caldwell (#saintdev), 2019-03-09 02:04:32 UTC
That's what ikey meant by |
Philipp (#der_eismann), 2019-03-09 11:41:39 UTC 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 |
Alec Scott (#alecbcs), 2019-05-07 18:39:32 UTC It looks like the Clear Linux team is no longer interested in integrating this into |
tuxayo (#tuxayo), 2019-08-12 14:43:18 UTC
Indeed :(
Can someone else confirm if that's a viable solution for Solus? |
Moriel (#moriel5), 2019-09-16 07:13:11 UTC Apparently |
Silke (#silke), 2020-10-17 13:12:43 UTC I have a working
#kyrios123, #JoshStrobl: is this sufficient integration to get fwupd back in the repo? |
Jacob (#Jacalz), 2020-11-20 11:21:38 UTC It is going to be very exciting to hopefully see those patches landing #silke. I think I remember seeing a differential revision opened here for integrating it, but I can't seem to find it any more. Am I remembering incorrectly or is it just very hard to find? |
Silke (#silke), 2020-11-20 11:32:04 UTC #Jacalz I haven't posted a differential, as I'm waiting on a go-ahead from #JoshStrobl. It is on his to-do list afaik, so we'll just have to be patient :) |
Jacob (#Jacalz), 2020-11-20 12:30:10 UTC #silke Thank you. Looks like I am remembering incorrectly then. Looking forward to seeing one posted :) |
Georgy (#DrSheppard), 2021-02-02 00:18:37 UTC Update on this task clearlinux/clr-boot-manager#77 |
Troy Harvey (#Harvey), 2021-02-02 00:41:02 UTC There is no update there, nothing changed. Last post was from 31 Jan 2020 an basically reaffirmed their position from 8 May 2019 which had already been linked too. We don't need updates that tell us that nothing has changed. |
Georgy (#DrSheppard), 2021-02-02 01:03:46 UTC
Ooops) I was wrong with the year. It's not joke |
Claude Durocher (#clauded), 2022-01-19 02:00:19 UTC Just wandering if any progress can be made here. I personally installed the snap version and was able to update my bios with fwupdmgr. The snap version is not perfect as it displays errors about missing libraries so a native package would be a plus, even without clr-boot-manager integration. |
Joey Riches (#joebonrichie), 2022-08-16 14:01:02 UTC Let's get all the packaging stuff landed (at least with the patches on phab) then we can figure out how to integrate it into the upgrade process. Consider the packaging progress part up for grabs. |
Moriel (#moriel5), 2022-08-17 14:42:16 UTC
I could not agree more. If things are not ready or are undecided, then they do not yet need t be deployed, but at least the foundations should be prepared on Phabricator and then figure out how to work on top of them. |
Silke (#silke), 2022-08-21 14:24:00 UTC I submitted an initial set of patches for the packaging and integration of |
Claude Durocher (#clauded), 2022-08-22 13:33:02 UTC I did a quick check and I think those buildeps must be added: |
Silke (#silke), 2022-08-24 15:56:46 UTC
Both of those are present:
I don't see |
Claude Durocher (#clauded), 2022-08-24 17:49:10 UTC I cloned this repo: https://dev.getsol.us/source/fwupd.git and this is what I get on first compile test:
|
Silke (#silke), 2022-08-24 17:57:25 UTC
It looks like you haven't applied D13506, also don't forget to build the dependencies first! |
Claude Durocher (#clauded), 2022-08-26 21:39:23 UTC Good to know :)
|
Silke (#silke), 2022-08-28 09:52:00 UTC
Strange, AFAIK Solus doesn't disable unprivileged user namespaces. Can you execute |
Claude Durocher (#clauded), 2022-08-29 01:25:55 UTC "unshare -U true" returns nothing. Compile after returns the same error. |
Hey (#Teroh), 2022-10-12 22:43:25 UTC Anything i can do to help with this issue? |
This checkbox:
I'd remove it as we'll eventually deprecate SC if favor of specific DE's store frontends. Or at least rephrase it to reflect that. |
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.See KDE Discover #318 and GNOME Software #319.clr-boot-manager
fwupd support, pending issue here. PR here.The text was updated successfully, but these errors were encountered: