https://github.com/fwupd/fwupd
A system daemon to allow session software to update firmware - GitHub - fwupd/fwupd: A system daemon to allow session software to update firmware
It updated a Thinkpad dock with no issues while on Windows, I had to find specific drivers and sketchy update utilities. Awesome!
I used it at work recently to update my work-provided HP Thunderbolt dock, and it resolved an issue where the external monitors would fail to activate after resuming from standby. I never got an update notification when I was using my Windows laptop so I was oblivious to it; it was only thanks to connecting it to my Linux laptop and fwupd, that I found out there was an update, which subsequently resolved the issue.
I love it when stuff like this happens and Linux saves the day. =) (and I get to show off to my Windows heathens colleagues.)
FYI fwupd also works on windows
There's an MSI in the releases https://github.com/fwupd/fwupd/releases
I thought I read somewhere that windows update would eventually pull from lvfs but I can't find a source for that
Either it doesn't support my mobo, or my mobo doesn't support firmware updates from inside the OS. I had to update my mobo manually yesterday. At least I now get a clean boot without any irq handler warnings.
Looks like they have no idea how to get their software working using Nix. The following blurb is absurd to most GUIX or Nix users:
NOTE: In most cases, end users should never compile fwupd from scratch; it's a complicated project with dozens of dependencies (and as many configuration options) and there's just too many things that can go wrong.
Users should just have fwupd installed and updated by their distro, managed and tested by the package maintainer. The distribution will have also done some testing with how fwupd interacts with other software on your system, for instance using GNOME Software.
I'm not sure I see the problem here? It does say most cases and I'd definitely consider Nix/GUIX users to be in the minority for this (on top of users who would even compile software themselves in the first place).
Also from what I experienced during my (not so long) time with NixOS, usually things in Nixpkgs were contributed there by community members who ported applications over to be compatible with Nix. Sure, it's a nice extra thing when the application developer does so out the gate, but given how special Nix and GUIX's environment is, the onus has never really been on the app dev.
I’m not pointing to a problem per se. I’m just saying that this dev dismissed the act of building this from scratch as impossible when it is not actually impossible. Honestly, I’m just trying to spread the word about Nix and GUIX because they make things that were previously considered impossible (like this) possible.
I see, that's plenty fair enough, although I don't think they meant it quite so literally (but rather as a method of lightening their support requests - I don't have any fwupd capable hardware AFAIK however I get the feeling fwupd is pretty popular).
I find it really cool what Nix/Guix are doing and I give major props to their communities for what they've pulled off, for what its worth.
Interestingly enough, someone actually did release two nix derivations for this software!
Oh that's awesome! Although I can't say I'm surprised, the last I heard Nixpkgs had more packages than the AUR, which is certainly no small feat.