Way back in the olde tymes, I was having trouble with the NIC driver in my Linux install. I posted a question about it on USENET, and got a reply from the guy who wrote the drivers. He asked for some info about the card, then updated the driver to support it.
Damn… now that’s a wholesome moment 🥹.
There used to be a lot of cards based on same or similar chips, but with small differences. That made little changes to drivers common. It’s a bit like LCD modules or audio chipset quirks. One driver with tons of little differences depending on what each manufacturer decided to do differently.
Oh hey I have the same wifi card series (little usb dongle thingy). I use the aircrack drivers when i use it. https://github.com/aircrack-ng/rtl8812au
Why aren’t these drivers installed by default yet
They’re still waiting to be mainstreamed into the kernel. The process of integrating drivers into the kernel is complicated. Coding practices of the coder that wrote the driver play a large part in that. Buggy or badly written code will not get accepted. Not all of these drivers have the code quality that is required in order to be merged with the kernel.
A lot of Linux drivers are like this - just one or two people maintaining them. They usually eventually mainline the driver rather than having a separate Git repo though.
It’s mind boggling just thinking that things like this depend on the effort of one or two guys… while on the other hand, it’s not so uncommon that a team of engineers and developers fails to deliver a working (mostly) bugfree product.
I think management is who is responsible for the shitty decisions, as always… and, in general, just holding the team back.
What’s the deal with Nebraska? Are people from there like really polite and helpful?
There’s nothing to do in Nebraska except drink and maintain Linux drivers
There’s such a lot of those heroes! I have some weird USB WiFi thing and there’s someone maintaining a driver for it!
Shoutout to screenshot tools
For all we know, he does wear a cape.
