Debian Votes To Add Non-Free Firmware to Official Install Media

The Debian logo
(Image credit: Debian Foundation)

Update 06:18 PT 10/6/2022:

The initial version of this story incorrectly described that Debian were including non-free software. The article has been updated to correct the information. 

Latest Videos FromTom's Hardware
Ian Evenden
Freelance News Writer

Ian Evenden is a UK-based news writer for Tom’s Hardware US. He’ll write about anything, but stories about Raspberry Pi and DIY robots seem to find their way to him.

  • atomicWAR
    To get wifi (and others) working a deal with the Devil is made...but it is still a deal with the Devil! Sad times...
    Reply
  • RichardtST
    As complexity goes up, compatibility goes down. That said however, I don't see a problem with including propriety drivers. In general, hardware vendors supply drivers for free anyway. If you've already paid for the hardware, why shouldn't you use the driver that comes with it? I see the issue here not as the use of a proprietary driver, but that the driver has to exist at all. Why isn't the hardware built to be compatible with existing drivers in the first place? That is the problem.
    Reply
  • That's a good thing. The issues with drivers were a nightmare in Linux. The performance was worse than Win10, less options to choose from, no documentation, etc. Whenever I installed a Linux distro I wanted the OS to work. I didn't want to spend hours of searching the internet, asking at forums, to make the WiFi or ethernet work.
    The problem is not the proprietary drivers, the problem is no driver at all.
    Reply
  • odgalvin
    This article and its title are misleading. The change is that nonfree firmware, which isn't part of the Debian system, is now being included in the installation media to enable certain drivers to work - the drivers themselves aren't effected. All drivers (like any other software) included in Debian is free/open, same as always.
    Reply
  • palladin9479
    Debian's "no non-FOSS software" stance has caused it way more pain then needed and why I stayed firmly within the CentOS/ RHEL space for my home linux needs. Alowing firmware / non-FOSS drivers is over a decade too late but at least it happened. Not all devices store firmware on the device PROM chips and instead rely on the drivers to load the firmware into system memory, that is where the huge disconnect is at.
    Reply