13 ms·
Debian and firmware
- cube00 5y agoAs bad as it is in the short term the only way we'll see long term change is to keep the friction on. It's this friction that forces the change of habit to support manufacturers who open their firmware. If it's seamless then there's no incentive to seek out the open option next time you buy. In my personal case nVidia stopped supporting my graphics card and eventually their binary blob stopped working with the newer Linux kernels so I had to chuck it away. Now I've learnt the hard way that I'll never by nVidia again (or if I do I'll make sure it's open first). At the time nVidia was getting a lot of good press supporting Linux and I didn't realise that meant closed source blobs that would eventually stop working.
- mastax 5y agoAMD and Intel GPUs also have closed source firmware.
- cube00 5y agoAs long as the code running on the Linux side is open and the closed source firmware stays on their chip that's fine by me. At least then you have a fighting chance to change the open source side up to date to allow the card to keep working. I know it's not pure freedom but I'm picking my battles these days and if I can keep something working by bridging the gap between an evolving kernel and static closed firmware then that's good enough for me.
- anthk 5y agoI have an Intel NUC based iGPU and it works with Linux-Libre + MESA. OpenGL and Vulkan. Ok, just libre games/engines, but they with all the FX'.
- majormajor 5y ago> As bad as it is in the short term the only way we'll see long term change is to keep the friction on. It's this friction that forces the change of habit to support manufacturers who open their firmware. If it's seamless then there's no incentive to seek out the open option next time you buy. My experience is the same as the author's: there's more today that needs non-free support to use Linux on the desktop than there was in the past. So the friction isn't doing its job. So why bother if the friction is just pushing users to distros which bundle the blobs more directly, instead of pushing manufacturers at all?
- hypothesis 5y ago> My experience is the same as the author's: there's more today that needs non-free support to use Linux on the desktop than there was in the past. Is that a function of Linux Desktop simply being more capable nowadays? Also, there is a world of difference between not publishing signed closed-source firmware for a driver that does not exist vs having an open source driver with published firmware.
- majormajor 5y agoI wouldn't say the Linux Desktop has gotten any more capable since Compiz, so no. (Nor have most desktops - depending on how much you value things like iMessage integration in modern Macs.) Before that, since... Phoenix/Firebird/Firefox and the decline of IE-only sites? Office file format compatibility? It's more the examples provided in the original article: cpu firmware blobs, network firmware blobs, same as always, just even more.
- usrn 5y agoThat's a good point. I think the author might be forgetting using ndis wrapper to run Windows drivers (so that's non-free software on the same machine as your OS) for unsupported network cards. We've come farther and have new, different problems now. The situation then looked bleak much like the situation now.
- mjg59 5y agoThat's still where we are for a lot of modern Broadcom wifi, which was also the biggest issue in the ndiswrapper days.
- mjg59 5y ago> Is that a function of Linux Desktop simply being more capable nowadays? I don't think so - it's more a function of hardware becoming more complicated, and vendors choosing to put a lot of the logic in firmware rather than putting it in ROM because there's a much lower chance of them getting it right first time now than there was in the past.
- qbasic_forever 5y agoWhat incentive do manufacturers have to release open firmware? Let's get serious, it's been 20+ years and desktop Linux usage isn't moving the needle or getting any of their attention. IMHO it would be far better to put effort into change at a different level, like perhaps a broader push with right to repair legislation that expands it to include releasing firmware in addition to schematics, spare parts, etc. Change is going to have to come from a different source, you're just abusing users today for no benefit.
- usrn 5y agoEveryone in the embedded space goes to kernel.org for WiFi stuff (firmware, regulatory info etc) regardless of which OS they're using. Being put at the top of the Wiki because you're "easy to work with" would be a massive advertisement.
- jabl 5y agoBy all means, the "free software community" should promote HW with free firmware, and giving the top spot on the kernel.org pages sounds like a good approach. And yeah, I spent a lot of time looking at wifi drivers when getting a wifi router. ath9k was the gold standard here with no blobs, and as a result was the favored platform for the wifi bufferbloat work. Unfortunately the follow-up ath10k needs a blob. But I don't think punishing potential users who just want to get their laptop to work is particularly effective free software advocacy. Most likely the user has no clue what wifi chip their laptop has.
- NovemberWhiskey 5y ago>the only way we'll see long term change is to keep the friction on ... but there are two possible long term changes, right? In one of them, the friction incrementally pushes manufacturers not to have proprietary firmware and the number of machines supported by the Debian official install improves. In the other one, the friction incrementally discourages users from installing Debian, and they either give up on Linux or adopt a distribution that isn't quite so user-hostile.
- b5n 5y agoDepends on how you define 'user-hostile'. There's already a link to the non-free image on the current installation page, and I wouldn't consider respecting your freedoms as hostile.
- NovemberWhiskey 5y agoSo if Debian were some megacorp, someone would already be complaining about the "dark pattern" that puts the link to the directory (n.b. not the actual images) for non-free images down the bottom of that page in small print inside a box labeled like a warning, and calls them "unofficial". As opposed to making it clear that this is the one you need if you're doing something outrageous like ... using a laptop or something.
- thrown12 5y ago>As bad as it is in the short term the only way we'll see long term change is to keep the friction on. It's this friction that forces the change of habit to support manufacturers who open their firmware. If it's seamless then there's no incentive to seek out the open option next time you buy. The only friction you're causing is to Debian users. My current laptop is Arch after 5 laptops that ran Debian. My Debian desktop is barely functional with the friendliest AMD GPU to Linux I could find. By my next update cycle I will be Debian free for the first time in 20 years. Debian needs less friction if it wants to keep me as a user.
- dralley 5y agoI doubt that has anything to do with "friction", Debian's release cycle just isn't compatible with wanting to run new hardware. Drivers are distributed via the kernel, Debian uses old kernels and can't afford to do the same kind of hardware enablement backports that Red Hat, SUSE and Canonical can do, so being stuck with the old kernel means poor support for brand new hardware.
- thrown12 5y agoNot sure why you're talking about new hardware. The graphics card is now 4 years olds.
- Barrin92 5y ago>it's this friction that forces the change of habit to support manufacturers who open their firmware. You can only force anyone to do anything if you have power. If you don't have power you're just a weird guy screaming from a soapbox and people are going to ignore you. No offense but do you think nvidia cares about your boycott? There's no shortage of graphics card buyers. I assume the non-free version of Debian sees significant amounts of downloads, maybe at this point more than the free version, so the situation is obviously quite awful or this post would not exist.
- pabs3 5y agoOne way that vendors have released libre firmware is when someone already working on the proprietary firmware convinced their bosses that libre firmware is a good idea. This happened with two of the open WiFi firmware projects.
- mastax 5y agoAlmost every hardware device has one or more CPUs on it. As Foone joked, "USB is a standard to let you connect 8051 microcontrollers to PCs." Given the choice between burned-in firmware and externally-loaded firmware, the latter seems clearly superior from an openness perspective. The firmware binary and the loading mechanism opens up the opportunity for reverse engineering, modification, and replacement open firmware. We currently have a strange situation where the devices that are easy to use are the most open and the most locked down ones, and the middle-ground is punished by policy. If that policy were successful at promoting open firmware I think that would be acceptable, but I don't think I even need to argue that is not the case.
- diffeomorphism 5y ago> if that policy were successful at promoting. Not disagreeing that policies should be made with success in mind. But by the same reasoning "vegan" should include the top 5 most popular meat dishes as exceptions. This would easily make it more popular, more accessible and probably much more successful at reducing meat usage over all. The issue is that the definition of "success" might be entirely unacceptable. Just like "entirely free but...." might be unacceptable.
- MrJohz 5y agoIn all fairness, flexitarianism is a thing, and I know a lot of people who would never want to go fully vegetarian or vegan, but who want to reduce their meat intake significantly, generally for environmental reasons. The change in messaging from "a single animal death is murder and unacceptable" to "any reduction is good, the more the better" is probably significantly not effective in this context at actually reducing overall meat consumption (although I unfortunately don't have any evidence for that hunch).
- trashburger 5y agoIf you consider the fact that veganism/vegetarianism is very unhealthy without taking the nutrients you're missing as supplements (which could be argued as being "reverse engineered meat"), then I would suggest that yes, until we reverse engineer the "meat" we should include it in the "diet" (along Free software).
- dleslie 5y agoWhat to do? Fund the development of, and provide to top tier support for open hardware and open firmware. Computers aren't just software, after all; Debian drawing the line at software probably needs to end.
- 3np 5y agoMy 5c: Debian is a free base distro. For users who want an all-batteries-included image including non-free firmware, there are derivatives like Mint and Ubuntu. If someone wants to step up and maintain [Debian+non-free-firmware] releases, this will probably be greatly appreciated but it should not come at the expense of maintaining the rest of Debian and stretching their already thin resources. One thing that could start paving a path forward would be to make contributing to Debian more approachable... Not saying they should get on GH/GL or anything, but there's huge room for improvement in their existing tools and docs.
- genghizkhan 5y agoDebian already maintains these images and has non-free firmware packages. They're just not enabled on the main installation disc by default. You can get non-free Debian images, they're just harder to get to. Edit: Here we go. They're "unoffical" images for sure, but they seem to be maintained similarly to the official ones. https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/ https://cdimage.debian.org/cdimage/unofficial/non-free/cd-in...
- 3np 5y agoYes, the OP is mentioning those as well. I don't think they, or the non-free repos, are under scope for LTS for example, though?
- b5n 5y agoAs a long time Debian user I'm reluctant to criticize developer ergonomics as I'm not an _active_ contributor. That being said, _as a user_, I've not had any issue locating and using non-free firmware when required, and I would be disappointed to see the project change course by including non-free components in an offical manner. Removing the slight inconvenience (literally clicking a link _on the installation page_ and downloading the firmware included image) further dilutes the project's free software position and will encourage users to install software that does not respect their freedoms. If users never brush up against the inconvenience they'll be much less likely to seek out hardware alternatives or even educate themselves on the topic at all, this is damaging to the community as a whole. I know I'm in the minority, and expect my opinion to be weighted accordingly, but principle is a key factor I use when choosing anything - including software. My loyalty to Debian would be significantly impacted by such a change. Is Debian missing projected growth KPI's or shedding users? Is this a key hurdle to onboarding new contributors? I'm aware there may be other considerations that those actively participating in the community or leadership may be aware of that I am not, and I might be ignorant to the full value of the proposition. Debian is amazing and I have the upmost respect for everyone involved over the decades, but a move in a direction that weakens its position on non-free components would most likely drive me to using Guix exclusively.
- devdao 5y agoPrinciples matter!
- throwaway48375 5y agoThey are the only reason I use Debian at all.
- Gigachad 5y agoThis could be seen as a benefit and a downside. It’s basically suggesting that you find other distros nicer to use but chose to use the less nice one due to principals. Most users will pick the nicer to use one.
- Brian_K_White 5y agoDo not agree. Let the countless others do that. Can anyone say with a straight face that there is anything wrong with Debian's vision or principles merely existing somewhere in the world? Ok, so they exist somewhere in the world, in Debian. And it predates you. Debian didn't come along and fuck up your life. There is no basis for any kind of "take it back" idea to "fix" Debian. If you don't subscribe to those principles, great news! The entire rest of the world agrees with you! Go use Ubuntu or Mint or really anything. If your argument is that Debian is an important base for countless users of other distros, and so it's inconsiderate or irresponsible or something not to serve all those indirect users better (according to your personal definition of "better"), well then why ARE so many other distros choosing Debian's shoulders to stand on if it's so unhelpful? All those other distros are perfectly free to provide their own base the "right" way. You in fact are free yourself to launch a new better os to replace Debian. Go ahead. No one is stopping you. Show those backwards clods how it's done by practical people with their heads screwed on straight.
- tedunangst 5y ago
- binkHN 5y agoOpenBSD is in a similar boat and continues to fight the good fight. The developers continue to reach out to the hardware manufacturers to get permission to include firmware in OpenBSD without an NDA. Sometimes they're successful, but, more often than not, they're not. I think if more of the open source community stood steadfast in this regard, more progress could be made here. The saddest part of all this, perhaps, is we're all purchasing hardware that is, basically, useless without the firmware as it's not included with the hardware we purchased.
- jmclnx 5y agoYes, but one you need these blobs for wireless, you will may to use a wired connection or download them to a flash drive and copy them over. What OpenBSD seems better, but in many cases, you may need a wired connection for on First Install. Upgrading, no issues but I like to be plugged in anyway just in case wireless drops.
- tedunangst 5y agoOpenBSD kinda does what's proposed here. The firmware packages aren't included in the distribution per se, but they're auto downloaded. It's pretty transparent for users.
- josephcsible 5y agoI'm usually on the FSF's side about everything, but this is one place where I disagree with them and agree with this article. A free OS with free firmware is definitely better than a free OS with proprietary firmware, but both of those are way better than a proprietary OS with proprietary firmware. By making the middle ground difficult, a lot of users have to choose between ideological purity and working hardware, and almost all of them will choose the latter in a big net loss for freedom. (E.g., "What do you mean this Linux thing doesn't support my network card unless I jump through all these hoops? I'll stick with Windows, where it just works out of the box.")
- bruce511 5y ago100% this. A decade ago I needed to replace some internal Linux file servers. I was keen to try ZFS, and so I tried BSD. Naturally on new hardware. Turns out BSD didn't support the on-board ether net. Tried a bunch of network cards from the cupboard, no support their either. Opportunity lost. Switched to Windows server (and was blown away by how polished that was, but that's another story.) I get the advantages of free software, I really do, but this sort of neglect of usefulness in the name of ideological purity does not win converts. On the other hand who cares? Free Software does not need to grow, it fulfils a purpose for those who want to be ideological pure, and I accept that is a valuable thing. Chasing converts at the cost of purity may just end up being no-man's-land. Perhaps what the author is looking for I'd a debian derivitive, not debian itself?
- pabs3 5y agoDebian itself provides the blobs for years, the post is mostly about making those CDs with blobs the default user experience for Debian itself, not for derivatives, some of which provide blobs by default.
- jabl 5y ago> On the other hand who cares? Free Software does not need to grow Sure, there's no VC breathing down the neck of Debian, but arguably the purpose of free software is to provide software freedom for users. If people aren't able to use that free software, it's a bit pointless. Further, a (small) fraction of users grow into developers creating more free software. To the extent non-free firmware allows more people to use free software, I don't think it's clear at all that a puritan approach to firmware is a net win for software freedom.
- pabs3 5y agoHere is a page of open firmware that is known about: https://wiki.debian.org/Firmware/Open https://wiki.debian.org/Firmware/Open As you can see, it is very minimal.
- tomc1985 5y agoThere will always be calls to compromise on principles to maximize some metric or another. There are legions of business wannabes and people who think they know best, and they will sweetly offer up their opinions to tempt you towards what they think is best. I hope Debian ignores them.
- apatheticonion 5y agoAs a Windows/MacOS user who has moved full time to linux, I ended up on Debian Testing as my daily (going to try Fedora soon). I still live back in the days when Fedora would give you a pop up to install non-free drivers ("additional software" or something like that). I have been using Debian as my daily driver for almost 6 months now and Linux in general for years - I still have no idea how the video drivers work. I have no idea how to install them, which ones mean what, what's free, non-free, optimal, professional - I have no idea how any of it works and it's a source of frustration for me. What is mesa? Why do people tell me not to install the video drivers from the Radeon website. When I download and install the drivers from the Radeon website there are lots of errors but it still seems to work - did I install them wrong? How to I update them? When I install the `apt install firmware-amd-graphics` I get loads of warning, but it works so I ignore them. What is going on and why isn't it as simple as Window's where I run an executable and a setup wizard does the rest?
- diffeomorphism 5y ago> still have no idea how the video drivers work. Why would you want to? This is not something I want to actually have to care about. And also I absolutely don't have to. > What is going on and why isn't it as simple as Window's where I run an executable and a setup wizard does the rest? Do you mean the included drivers? Or the OEM ones? Or the Nvidia ones? Current or beta? Also, it is even simpler than that on distros that support nonfree stuff, e.g. on ubuntu it is just click here for which nvidia stuff you want and done. As opposed to navigate websites, versions and wizards in windows.
- johnny22 5y agomesa is the thing that handles opengl and vulkan for most cards that aren't nvidia. Generally you don't have to touch video drivers at all in linux except for arm stuff and nvidia. (that's not always the case,but mostly) Just keep your kernel up to date. That's the main problem with debian and wanting to say play games or have newer hardware.
- Cu3PO42 5y agoThe driver situation for modern AMD GPUs is pretty good. There is an open-source `amdgpu` driver in the mainline Linux kernel maintained by AMD themselves. If you use a somewhat recent kernel, that'll be there. You need `mesa` in userspace which provides the OpenGL interface, etc. to your applications. This is why there's no need to install anything from the Radeon website -- you already have a driver. As for the `firmware-amd-graphics` package, it provides proprietary firmware for your GPU. That could be as insignificant as microcode updates or an important part of the interface that the driver expects. It's probably a good idea to install (and maybe try and fix the warnings.)
- Maursault 5y agoI hesitate to post, but I respect Debian. Firmware has gotten so large, all distributions and OS communities would benefit from focusing on it as a project to provide free firmware. I don't know how large the firmware developer community is. Firmware space has gotten so large, an entire OS could fit in there. What if there were a miniDebian, or miniFreeBSD, that was a virtuous but smaller reflection of the OS, not unlike iOS and macOS? I'm not sure if crypto or key signing by hw makers, under the excuse of security, makes this impossible, but I'd really like to have more options with the firmware on my machines. Like, why can't I run VMWare ESXi from firmware? It should fit in there. If if is technically possible, it should be allowed; we pay for the hardware, it belongs to us. Why is this even a thing? Who are the bad guys here? Why are they screwing with us?
- mschuster91 5y agoThe amount of people capable of doing firmware work is extremely low, and the amount of documentation available that's needed to write firmware for highly embedded systems is even lower - not to mention that the stuff that is implemented in this kind of firmware is extremely complex and if anything RF is involved it gets even hairier because of compliance to standards and legal regulations. Last thing an open source dev wants is complaints from users that their home got raided by the FCC for operating a noisy transmitter that interrupts service for someone else. There isn't even enough manpower to get the Raspberry Pi, the world's most used embedded system for tinkerers, a fully blob-free experience - it's madness to expect that for systems like GPUs that are orders of magnitude more complex than that.
- outsomnia 5y agoThe canonical firmware is the BIOS, I was pleasantly surprised when Fedora updated the BIOS on my Dell XPS device by itself recently... historically that has been somewhere between a nuisance (Reboot and then UEFI network update), a struggle (dig out the image from an EXE on a flash drive), or impossible (some windows-only app that doesn't work via a VM). And whatever the annoyance level, when done manually it was usually done months or years after the BIOS release. Other firmware the cpu microcode is handled via packaging. There has been a lot of work packaging peripheral firmware for things like mice... it's not like it is going to go away. This is also distributed in packaging in Fedora now. It's not ideal that these are proprietary blobs but some accommodation is needed I think.
- pabs3 5y agoThat firmware update was made possible by the fwupd software project (containing various firmware updaters) and the LVFS project, a service for hardware vendors to upload their proprietary firmware updates for mice, the BIOS/UEFI and other devices to. https://fwupd.org/ https://fwupd.org/ While it is great, it doesn't solve the problem that this post is talking about; when devices have no pre-installed firmware and expect you to upload (proprietary) firmware on every boot. This is usually things like WiFi chips, GPUs, Ethernet etc.
- outsomnia 5y ago> it doesn't solve the problem that this post is talking about; when devices have no pre-installed firmware and expect you to upload (proprietary) firmware on every boot. This is usually things like WiFi chips, GPUs, Ethernet etc. Same as Fedora, Debian seems to package linux-firmware? https://packages.debian.org/sid/firmware-misc-nonfree https://packages.debian.org/sid/firmware-misc-nonfree
- pabs3 5y agoRight, and linux-firmware contains mostly proprietary firmware. There is a small amount of libre firmware in it but that doesn't get built from source. The post is about directing users to an installer ISO that installs the proprietary firmware by default.
- molticrystal 5y ago>Due to these reasons, more and more devices in a typical computer now need firmware to be uploaded at runtime for them to function correctly. This has grown: > Going back 10 years or so, most computers only needed firmware uploads to make WiFi hardware work. You can actually go back to almost 30 years with dialup modems, most notably the winmodem/softmodem popularizing this concept in the pc market. If there is anything to blame on this path of binary blobs, I'd fault them.
- CogitoCogito 5y agoInstalling the non-free firmware on Debian is as easy or easier than similar installation on all other operating systems. So this is really a complaint about something that is almost as easy as it gets needing to be just slightly easier. It’s making a mountain out of a molehill. That said, who cares if some users want it? Debian doesn’t aim to serve all users’ needs. Those who want non-free firmware bundled with the operating system can get that with one of the many Linux-based (or non Linux-based) operating systems out there. Debian just isn’t for those users. That’s fine.
- comex 5y agoIs the situation really that different from how it used to be? At least for me personally, if I compare to around 2008 or so when I had Debian installed as the primary OS on a desktop PC and as a toy on my Mac laptop: > Modern laptops normally don't come with wired ethernet now. Both then and now, on my laptop, I use Ethernet occasionally but rarely, only when I specifically need its speed or reliability advantages. The rest of the time I use Wi-Fi, which did and does require non-free firmware. Ethernet moved from a built-in port to a dongle, but my actual usage patterns have barely changed. That said, there used to be some Wi-Fi chips that didn't require non-free firmware (just not the ones I had), whereas now there are none. For desktops, on the other hand, it was and is worth hooking up Ethernet, making the point largely moot. (I think I used Wi-Fi on my desktop at the time, but I wished I didn't have to. Now I don't.) > There won't be any usable graphics on the laptop's screen. Even at the time, I saw hardware-accelerated graphics as essential, both for windowing (Compiz) and for gaming. So I used the 'nvidia' non-free driver on the PC… just as I do now. (I don't remember what the Mac had.) Incidentally, for those who don't prioritize graphics performance over freedom, free drivers are better than they used to be. Unfortunately, they require non-free firmware – and I know this post is about firmware. But still… that seems like a win of some sort.
- guilhas 5y agoThe installation asks you yes/no if you want to install non-free firmware
- p0d 5y agoTbh I don't care about free, non-free firmware. This was not my install issue.
- guilhas 5y agoThere is a similar model notes in the wiki InstallingDebianOn HP Envy 14 Beats Edition 2020ep https://wiki.debian.org/InstallingDebianOn/HP/Envy%2014%20Beats%20Edition%202020ep https://wiki.debian.org/InstallingDebianOn/HP/Envy%2014%20Be... > The installer isn't able to detect the Wifi or LAN network cards. To do a net install from the LAN card you need to drop to a shell and do modprobe atl1c echo "1969 1083" > /sys/bus/pci/drivers/atl1c/new_id
- shmerl 5y agoIt is annoying for sure, that for something like AMD GPU you have to go out of the way to get a "non official" Debian installer that includes amdgpu firmware, otherwise installer won't be able to work. For the most part this annoyance affects the installation step. After your system is in some semi-working state where you at least can install packages or have access to network, you can add any firmware you want already.
- teddyh 5y agoThe problem of non-free firmware has been solved, already. If you need it, you simply download the image which contains it: https://fiendish.github.io/The-Debian-Gotham-Needs/ https://fiendish.github.io/The-Debian-Gotham-Needs/
- p0d 5y agoI am a 20yr linux user. I got a new HP laptop recently and decided to try Debian. To my surprise Debian didn't recognise my network adapter and would not let me continue the installation. I wrongly assumed the installer would install, let me fix the adapter. I read around and used an installer which apparently had proprietary drivers. Same issue, couldn't install. At this stage I returned to Ubuntu.
- pabs3 5y agoLWN discussion about this post: https://lwn.net/Articles/891767/ https://lwn.net/Articles/891767/
- wheelerof4te 5y agoDebian is the only Linux distro with a sane release cycle left. Every other Linux distribution feels like alpha or beta software.
- Neuroncrm 5y ago
- the_biot 5y agoIt's a shame that there's barely even a conversation about fixing the problem of the ever growing pile of proprietary firmware blobs; more and more often people seem to just accept the situation. There isn't AFAIK an organisation or project dedicated to producing free firmware to replace the blobs. The most you see is the occasional project for making firmware for a single chip. Debian's page lists these: https://wiki.debian.org/Firmware/Open https://wiki.debian.org/Firmware/Open It's a depressingly short list. I guess the problem is in part that there's no money to fund anyone for doing such (very hard) work, and no incentive for companies to pay for it.
- marcosdumay 5y agoIt's not really growing. They just used to come inside the device, and now they are changing into the distro. That's an improvement, just not as big one as it could be.
- m0llusk 5y agoNon free firmware is a huge ongoing problem for me. I am posting this from a laptop that has some major failings because of the lack of updated firmware. Slightly apart from the main issue here I would suggest that there is an opportunity for communication with some of the parties that matter most. Producing media that shows how much happier customers are with products that have freely available firmware with updates might convince some manufacturers to change their ways. If it were clear that power users would direct purchasing for whole organizations based in part on availability of firmware then there would be a clear profit motive for doing that. At this time makers see providing firmware as an expense and a risk that only diminishes their position.
- hedora 5y agoMore importantly, going to debian.org/shop should provide a list of best-of-current-generation hardware devices that work flawlessly without setting the kernel taint bit, covering a dozen hardware niches: - router - NAS - thin and light laptop - cheap laptop - beast of a CPU laptop - gaming laptop - ml laptop - low wattage compact desktop / htpc - workstation - gaming desktop - tablets, watches, phones, etc. - handheld portable gaming system (e.g. rk2020, steam deck, odin pro) To get on the list, manufacturers would have to commit to making a Linux SKU that does not change (modulo hardware bugfixes) for 3-5 years. PC Engines alrady does this for routers; Pine does it for cheap laptops; AMD GPU gaming desktops are also an easy target. They'd also need to donate a few dev / continuous integration machines to the project (or operate them themselves). Each night, these machines would automatically confirm that all hardware devices are working right in top of trunk and all contemporary supported releases. There could be revenue sharing, or not. Don't care.
- yyyk 5y agoMy subjective impression is that Debian has been losing ground, especially against Arch. I don't think firmware is the main issue - the complex packaging method and the contradictory nature of Debian 'testing' are the main issues. Yet this change will help, so I'm in favour.
- guilhas 5y agoWhy should Debian/Linux and users reward hardware that goes out of their way to make everyone's life worse for profit? Maybe hardware companies should make an effort to contribute and make their hardware work better on Linux When I buy a laptop I make sure it is Linux/Debian/Arch... compatible Extra I go on eBay and get a cheap compatible open source driver WiFi card, like QCNFA335 to replace the original