Although LVFS supports updating firmware using #fwupd on a huge number of devices right now, where should our main focus be for 2025?

If there's something specific you're thinking about, please reply with a link to the vendor product page. Thanks!

Server machines
7.2%
Consumer mainboards for desktops
34.2%
Laptops (specifically, additional OEMs)
34.2%
Removable hardware (mice, keyboards, SSDs, etc)
24.3%
Poll ended at .
@hughsie Lenovo IdeaPad Gaming laptops.
@9to5linux @hughsie +1 for Lenovo Legion devices.
@weipah @9to5linux I've asked my Lenovo friend. At the end of the day it's a commercial decision for any OEM.
@hughsie @weipah @9to5linux yeah, thanks, but it’s very sad that in 2024 we still have to install Windows to update the BIOS/UEFI firmware… I’m not saying that they should offer Linux support, but at least make the firmware update independent of the installed OS, like in the old days when we put the new firmware on floppy disks.
@hughsie I'm surprised, there is no support for @tuxedocomputers laptops.
@mkyral
Apparently they have a test account but not uploaded any firmware yet https://fwupd.org/lvfs/vendors/#tuxedo
LVFS: Vendor Status

@krake @mkyral I asked them in 2020 and 2022. At this point, I have given up on them for getting LVFS support and upstreaming drivers to Linux right. Even if they do both things eventually, they certainly don't go back so many years, that my laptop will be covered.

Both criteria will be essential for my next buying decision.

https://twitter.com/Cr0ydon/status/1241783130874355713

@[email protected] (@Cr0ydon) on X

It would be awesome if Tuxedo would upload their firmware to LVFS. Any specific reasons to not do this, @TUXEDOComputers?

X (formerly Twitter)

@croydon @mkyral
Interesting, thanks!

I just saw that they made an update available for my 6 year old laptop, so they do seem to care for quite some time after sale.

If it is mostly a resource problem we might still get there 😀

@hughsie While I do have a motherboard that's fairly new (it was released almost two years ago), I'm sure there's a bunch of laptops that need better firmware support.

@hughsie I voted laptops but want to give my reasoning:

- Servers: I don't really care about them personally. Plus servers are the kind of thing with a team managing them.

- Removable devices: Definitely helpful but not as critical as PC BIOS, IMO.

- Desktop w/ consumer MOBO: Important to get bios updates for security. But people building PCs know how to update BIOS, and you can w/o an OS.

- Laptops: Again important to get bios updates, and there's no external mechanism for it either!

@hughsie

(1) open source firmware and enabling that

(2) making it easier for others to sync and run an LVFS mirror

Thanks!

@purpleidea for #2 -- it's actually a thing now! My local server in my office mirrors the LVFS and resigns all the firmware with it's own local key. What we're missing is two things:
* A way of deploying it in a container -- e.g. a docker-compose.yml file
* Some documentation of the feature, e.g. see screenshot.
@hughsie I remember looking into this some time back. It was sort of possible with pulp, but it ended up being really complicated. Are there better docs now? When it looks more like the Fedora mirrors system and the core system could get firmware from other mirrors that would be the best.
@hughsie @purpleidea does it mirror, or just cache?
@vathpela @purpleidea mirror if you use https://lvfs.readthedocs.io/en/latest/offline.html but if you set up the webapp it's completely fallback instance.
Offline Firmware — LVFS documentation

@hughsie @vathpela Why isn't this just an rsync?
@purpleidea @vathpela it could be, but IIUC there's no rsync available on the ECS instances we're using. So far all the agencies and companies wanted to use a pulp manifest instead.

@hughsie @vathpela Managing and distributing firmware is so viciously important, that it's crucial to make it easier for others to clone the data and history.

Why? This lessens the risk that a bad actor might push a blob, and then push a subsequent copy thus hiding their tracks. By using standard protocols, it's less likely that this will go unnoticed, since others can snapshot and diff more easily.

This is important for your own reputation and for that of the excellent LVFS =D

@hughsie I voted laptop but could have picked server as well. What I thought was a good criteria is number of machines shipped over the longest time with available updates, so fleet laptops may have the most effect for resources spent, at least ones people want to run Linux on. Servers already have good support for firmware management from Linux, the benefit would be in replacing proprietary tools with standard ones.
@hughsie Primarily mobos/laptops. However, it'd be nice if monitors could be updated. I have a pair of LG 4k 32" at home and Dell P and U series at work that require quite a lot of juggling to even update the vendor recommended way (janky GUI update utilities that looks like they've been hallucinated by some LLM).
@hughsie Asus #Vivobook series, specially the affordable ones.

I personally voted for desktop Mainboards but I also think that the three most voted for options are kinda all important, recently I installed the WD SN770 SSD on my Linux laptop, I found out it had an update, It wasn't on LVFS and to update it manually in the terminal was so hard I ended up booting Windows off a USB stick just to update my SSD.

LVFS is such a great concept and it makes me really sad that vendors aren't contributing to it more.

@hughsie From my own perspective, server is the less interesting option. Using the lights-out/BMC functionality you can already orchestrate firmware upgrades on a fleet of machines. fwupd support would be nice, but it's already something that can be automated without needing to wait on the vendor to adopt new firmware packaging and distribution channels.

Laptop is probably the most critical, as laptop BIOSes tend to often also lack support for doing a firmware upgrade (whereas desktop systems tend to have that built-in nowadays). You typically have to boot into Windows. With the recent Framework AMD launch for example, folks needed to get on BIOS 3.03 for things to work properly. Though @frameworkcomputer lets you do the firmware upgrade from a USB stick, the fact that it was available through fwupd was even nicer. But I have a Lenovo IdeaPad for example on which this is a real chore.

After that it's a toss-up between external peripherals and desktop for me. Though I did appreciate the ability to update the Logitech unifying receiver when some vulnerability came out a few years ago. That was great.

@hughsie We needs support for Lenovo Yoga laptops
@hughsie Myself I'd love to be able to update my consumer MB, but having done very large scale web operations in the past: servers would be killer
@hughsie devices with complex upgrades or Windows-only upgrades. e.g. some SSDs

@hughsie how about home user / gamer mainboards from #Gigabyte, #Asus, #Msi, #ASRock and other friends?

Also #hp #prodesk / #elitedesk would be nice. In their case UEFI can be updated over the internet from UEFI itself (no USB stick needed).

@hughsie personally #msi motherboards and #acer Laptops would be nice, but I think my next laptop won't be Acer again, due to their insyde bios just not working
@hughsie Great that you run a small survey about this! Just keep in mind that mastodon users are not representative.
@hughsie Having better support for servers would be fantastic, even though it only benefits a tiny fraction of the fwupd users (updating firmware on servers can be a major pain, but that's mainly the vendor's fault)
@hughsie gaming hardware might also be interesting, not from a security pov, but from convinence. Updating headsets or controllers currently can be quiet hard or even impossible.