On boot up, use some relatively arcane GRUB magic (I'm just a user, so I have to look it up every time, okay?) to boot into some kind of safe non-graphical mode and install the GPU firmware Run a shell in the text installer and do "apt-install firmware-blah", a command which is only documented in a dusty unstyled html in a file cabinet hidden by a beware of leopard sign copyrighted 2010 Run the graphical installer in the first place so that the GPU firmware is used/installed by the installer
Did you run the text installer or the graphical installer? If you used the text installer, you might be surprised to get an unescapable gray screen on an otherwise fully working booted system! Your video out doesn't work properly because kernel modesetting doesn't work without firmware or some mumbo jumbo like that. Now that Wi-Fi works when available at install-time, let's try to install a bog standard desktop system. Can't complain about that anymore since it's fixed. If not, we can let the user decide if they are willing to compromise their principles in order to boot the system )Īs a long time non-contributing Debian/Ubuntu user (I hop between the two whenever one of them annoys me too much), I've had a lot of issues locating and using non-free firmware when required.įor the longest time (since fixed), trying to use Wi-Fi in debian-installer simply didn't work, regardless whether I used the unofficial image or dumped the firmware debs on disk. If the machine boots without them, they can be deleted upon first reboot. So in my opinion, the most common blobs should be cached by default, but not activated by default. Not including any firmware repository on the CD or on a fully installed system is just a recipe for users to get frustrated while they are trying to follow a half-outdated tutorial on one of those spammy tech support blogs. But I also know the reality of needing at least Atheros (Wifi), Intel (Ethernet), and NVIDIA firmware blobs to get my tower to boot correctly. Yes, I agree that a default Debian configuration should be clean. Maybe add an illustration of a robot terminator, to really drive the point home.
I believe there should be an official non-free repository (akin to Ubuntu's) which users can enable offline, meaning it needs to be stored on the official CD.Įnabling it should display a big scary warning about handing over partial control of your machine to greedy faceless megacorps who will throw you under the bus in a heartbeat if that makes them money.
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.
#Debian install broadcom wireless driver full#
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. My loyalty to Debian would be significantly impacted by such a change. 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. 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.
#Debian install broadcom wireless driver software#
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. 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. As a long time Debian user I'm reluctant to criticize developer ergonomics as I'm not an _active_ contributor.
0 kommentar(er)
