Installing Debian on modern hardware
It is an unfortunate fact of life that non-free firmware blobs are required to use some hardware, such as network devices (WiFi in particular), audio peripherals, and video cards. Beyond that, those blobs may even be required in order to install a Linux distribution, so an installation over the network may need to get non-free firmware directly from the installation media. That, as might be guessed, is a bit of a problem for distributions that are not willing to officially ship said firmware because of its non-free status, as a recent discussion in the Debian community shows.
Surely Dan Pal did not expect the torrent of responses he received to his
short
note
to the debian-devel mailing list about problems he encountered trying to
install Debian. He wanted to install the distribution on a laptop that was
running Windows 10, but could not use the normal network installation
mechanism because the WiFi device required non-free firmware. He tracked
down the DVD version of the distribution and installed that, but worried
that Debian is shooting itself in the foot by not prominently offering more
installation options:
"The current policy of hiding other versions of Debian is
limiting the adoption of your OS by people like me who are interested in
moving from Windows 10.
"
The front page at debian.org
currently has a prominent "Download" button that starts to retrieve a
network install ("netinst") CD image when clicked. But that image will not be terribly
useful for systems that
need non-free firmware to make the network adapter work. Worse yet, it is
"impossible to find
" a working
netinst image with non-free firmware, Sven Joachim said, though he
was overstating things a bit.
Alexis Murzeau suggested
adding a link under the big download button that would lead users to
alternate images containing non-free firmware. He also pointed
out that there are two open bugs (one from
2010 and another
from 2016) that are related, so the problem is hardly a new one.
While they are hard to find, there are unofficial images with non-free firmware for Debian, as Holger Levsen noted; he also pointed to his 2017 blog post that he uses to rediscover those images when he needs them. It is a rather strange situation; Emanuele Rocca put it this way:
This absurdly damages our users without improving the state of Free Software in any way, while Ubuntu puts the firmware back into the images and can rightly claim to be easier to install.
But Jeremy Stanley took exception to that characterization:
That is, of course, the crux of the matter. Debian has a set of ideals
about the kinds of software it distributes, enshrined in the Debian Free
Software Guidelines (DFSG); non-free licenses do not fit within those
ideals.
In addition, the Debian
Social Contract (which contains the DFSG) specifically notes that
"non-free works are not a part of Debian
".
But the problem at hand is that potential users may not even be
able to install Debian (or use it once installed) if they cannot access the
network; it is hard for some to see how that advances the cause of free
software, which is also a part of the contract.
In response to Stanley, Russ Allbery pointed out that there is a middle ground. No one had suggested removing the official images that do not have the non-free firmware, but there are some interested in making it easier to find the images needed for much of today's hardware.
The official installer does offer the option of installing non-free
firmware from a USB drive, "but
very few people use it
", Andrew M.A. Cater said.
Allbery described the
process he goes through to try to use that mechanism; it is far from
straightforward even for someone quite familiar with Debian:
One can only imagine that new users who encounter this wall are unlikely to
continue to down the Debian path. Allbery said that an installer with
non-free firmware would work much better for him, but he wasn't able to
find the specific one he needed (for the "testing" version of the distribution). Andrey Rahmatullin said that
the inability to find these images
is caused by a "failing of the Debian websites
"; there should
be an easier path to find the alternate installation images. Russell
Stuart said
that he always runs into the same problem that Allbery reported and
that, even though Stuart is a strong proponent of the separation of free
and non-free in Debian, firmware is a different beast:
After Paul Wise pointed
out that there actually are unofficial images with non-free firmware
for the testing distribution, Holger Wansing suggested
some changes (and as
a patch) for the web site to make it easier for users to find these
images when needed.
As Marc Haber said,
though, the
installation experience is likely the first impression a potential new user
will get; "we
should not be trying THIS hard to be a failure in this very important
part of the relationship our product is building with the user
".
But pointing users at the unofficial images is different from Debian
officially distributing this non-free firmware, as Steve McIntyre pointed out:
Haber feels
strongly that being purists about firmware is only leading to fewer new
users. Wise agreed
in part: "the current situation wrt hardware and software
freedom is pretty catastrophic
". He suggested making things clearer
for users and potential users, perhaps by way of an "installer launcher
app". That app would analyze the needs of the existing hardware to help
guide (and presumably educate) users in their installer choice.
While there were lots of ideas of how to make things better, this problem has existed for a long time in Debian. Marco d'Itri said that he had raised the issue back in 2004, but it likely goes much further back than that. Ansgar Burchardt said that in 2016 he had proposed creating a new section in the repository to hold the non-free firmware (separate from the rest of the non-free software), which might be a preliminary step. But consensus was not reached and that effort died on the vine. As with the open bugs, these accounts show that the distribution has been struggling with this issue for quite some time.
At this point, it is not at all clear what will happen. The discussion may just fade away, only to be picked up again down the road. The problem is real and making the situation better, at least, does not seem all that difficult, nor particularly harmful to Debian's overall goals. But that has been true all along and here we are. It would seem that there has simply not been enough "push" to make progress, but with any luck, this time around things will be different.
