"Kernel regressions" was a little bit too generalizing in this meme. Technically drivers that became part of the kernel can also regress, as recently seen by users of Corsair Void wireless headsets (an unpatched 6.13 kernel is panicing once the headset adapter is plugged in).
Linus likes to break driver interfaces every other Tuesday though. Meaning you can get stuck on an old kernel version, depending on your hardware. This happens pretty regularly for ARM based boards for example.
I’m going to piggyback off your comment to take a moment to complain about System76 computers, which I own and enjoy. That being said I wanted to run Fedora instead of PopOS.
It’s super frustrating to me that many of my old computers could automatically do firmware updates using fwupd, but to update System76 laptops I have to install from a copr repo their system firmware update service.
The funny thing is they do appear to support fwupd, I assume they just aren’t maintaining it.
A Linux laptop for Linux people, but they’ve managed to set it up where you don’t get the best experience unless you’re running PopOS. It’s little frustrations like this that make me want to go back to a Del laptop for my next computer.
System76 can't feasibly support all the linux distros and their different versions. Especially an unstable cutting edge distro like Fedora. It's too much for such a small company.
back to a Del laptop
Does Dell still offer laptops with official Linux support?
Even though I only really use it on one machine, (mnt pocket) I've contributed repeatedly to Debian. It's the bedrock upon which so much of the Linux ecosystem is built upon.
I would always argue that any distribution which does not prioritize this principle is a hobby project, not a serious distribution for end users.
Which is fine, hobby projects are good, but they should be labeled accordingly to properly set user expectations.
"Kernel regressions" was a little bit too generalizing in this meme. Technically drivers that became part of the kernel can also regress, as recently seen by users of Corsair Void wireless headsets (an unpatched 6.13 kernel is panicing once the headset adapter is plugged in).
Does the headphone use bad vendor/product ID? Or how does a wireless dongle without driver panicking a kernel?
Or is there just a broken driver in the kernel?
Linus likes to break driver interfaces every other Tuesday though. Meaning you can get stuck on an old kernel version, depending on your hardware. This happens pretty regularly for ARM based boards for example.