"Linux supported hardware" is an outdated phrase only used in windows propaganda today.
this post was submitted on 13 Jul 2026
860 points (97.4% liked)
Programmer Humor
32543 readers
1115 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 3 years ago
MODERATORS
System 76, Tuxedo Linux, Mint, and several other Linux developing OEMs I can think of exist?...
Absolutely not.
Signed, owner of half-supported hardware.
Out of curiosity what hardware are you using that's not supported?
Printers 🤣
In my experience, the only OS where printers won't have drivers is Windows.
But I don't deal often with dark demoniac systems, so there are probably lots of niche hellish devices that I don't know the details.
load more comments
(15 replies)
Certain fingerprint readers and touchscreens
ex. Goodix
It's not the fault of Linux, it's the hardware manufacturers. Still, you need to consider it before buying the device
HP Reverb G2 for me. Still waiting on Monado to get it fully working but no such luck yet. Hugely appreciative to the dev team for all of their amazing work, of course.
Audio gear.
Peripheral devices, mostly. I have some half-supported, like Logitech mouse (G-shift doesn't work), and for some I rely on open-source devs (like Corsair keyboard for certain keys/modes/connectivity fix). Sure, you can say just buy compatible devices, but it's not always viable to replace everything you owned before moving to Linux.
Broadcom hardware (WiFi cards an webcams in particular). Plus there are quirks with some proprietary driver version not building against some kernel version...
With unsupported hardware and closed drivers you are always on the lookout for some breakage.
And it's not a Linux problem nor a complaint on distro maintainers. It's manufacturers that are shit.
load more comments
(9 replies)
What Linux kernel are you running which isn't supporting your hardware?
My case: I have an nvidia GTX 980. It's old but it's what I have.
Nvidia dropped its support from driver version 595.
Driver 580 is what I need, it worked until 7.0 but no longer in 7.1 (was using Fedora 44). Since my hardware is old I switched to Debian Trixie.
Another example is the facetime HD Webcam of macbook pro: to make it work you have to install OSx or download a recovery image, compile a C program to extract a specific binary blob, then use that blob to recompile the driver on your kernel.
There are lots of examples: it's a big world, with lots of hardware and mostly no producer interested in the Linux world.
load more comments
(3 replies)
For desktop? Probably. For laptop, linux support can be awful, because manufacturers keep introducing hardware that don't support standard drivers. Webcam? How about an IPU6 that needs kernel modules just to be detected and then special calibration files just so the image is not a stripey corrupted mess... How about no on-board sound because screw you I guess. How about a non standard USB controller so that you cannot even communicate over your USB ethernet dongle when the wifi is once again some special sauce non standard shit...
These are Dell and Lenovo Yoga machines at the University I work at. Some are absolute garbage where the USB is always powered and will drain the battery when the computer is turned off and no BIOS setting will disable this.
We are now looking into Tuxedo and Framework...
PS.: even windows has issues with these, where you have no touchpad and no USB anything (mouse, keyboard) until you somehow install a driver...
load more comments
(1 replies)
Psht. I wish! This is wrong and will set people up for failure. There is absolutely hardware that will work well with Linux and hardware that will not.
I tend to run into problems with brand new laptops. Microphones don't work, web cams don't work, fingerprint readers don't work.
I have a Dell Dell Pro next to me with a web cam that doesn't work. Arch, btw.
I also have a Lenovo T14 where everything does work.
The point is you have to RESEARCH before you buy. Otherwise, you're gonna get mad a Linux for not supporting your hardware, instead of being mad at yourself for not researching first.
Hardware that's too old is problematic and hardware that's too new can be problematic.
load more comments
(3 replies)
Unfortunately this is not true. If manufacturers do not support Linux, then it is up to dedicated community members to reverse engineer drivers. Much love to these amazing people ❤️
Things have gotten much better in recent years because now Linux is seen as a legitimate operating system and not just a platform for hobbyists.
load more comments
(1 replies)
There's still tons of devices where Linux doesn't work properly with them.
My Intel wireless cards cannot maintain a 6ghz wireless connection for shit despite some of them being over 5 years old. And Intel. Latest stuff, older kernels, none work well. Oddly whatever version of Fedora I had worked the best. My wifi wasn't unusable when 6ghz was an option. It only dropped to 5/2.4ghz once a minute instead of every 5-20 seconds.
load more comments
(7 replies)
Different disks if you must at all.
2 separate bootloader partitions. Grub launches the windows bootloader on a different partition so it isn't aware of anything other than itself. Then the 2nd bootloader actually launches windows. Don't try to share one partition or else windows will inevitably wind up clobbering the Linux loader.
Windows will know, its lik a cancer
This assumes windows is not maliciously checking for other bootloaders in order to fuck with them, which I'm not willing to give MS the benefit of the doubt on tbh.
It does work.
If you have two EFI partitions, Windows will stop looking once it finds the first one.
Which is actually a problem sometimes, as it will stop looking and use the first one it finds, even if it's on different drive than windows.
Imagine installing windows on a machine with two drives. Drive A already has an OS and an EFI partition, so you install Windows to drive B.
Except Windows will still go ahead and drop the bootloader onto drive A. Potentially breaking the OS that's there, plus setting up Windows in such a way that it requires drive A to boot. EVEN THOUGH THAT ISN'T WHERE YOU INSTALLED IT.
This is why guides tell you to install windows with only one drive connected. It's the only way to ensure it puts the bootloader and OS on the same drive.
load more comments
(1 replies)
load more comments
(2 replies)
My gaming PC dual boots Debian and Ubuntu
Kirk : I use a computer with an AI assistant and 1 gb of free ram. How about you?
Homer : I have a normal computer that lets me do what I want with my hardware.
Dual booting us viable, if you're curious its good to try linux via dual boot. Windows doesnt break the linux bootloader. The incident referencing was a bug I believe. I know plenty of people who've been dual booting for 2+ years keeping both OSs up to date with no issue.
I have had Windows update completely obliterate my Linux partitions at least twice.
load more comments
(2 replies)
I’ve had windows nuke my bootloader at least thrice. Stopped dual booting a few years ago so I’m free of that nonsense.
That wasn't "an incident." The notion of Windows breaking Linux's bootloader has been a known thing for at least a decade.
I have had it break my bootloader when I was dual booting, if it wasn't my main pc then I might risk it but I'm not rolling the dice on if windows decides to break it again.
load more comments
(4 replies)
My bootloader has survived just fine despite being dual boot for the past 2 years. It may have something to do with me only having booted windows once in all that time (to fix a borked NTFS drive) 😁
That certainly helps.
In my case the solution is two EFI partitions.
Windows finds the first and doesn't bother looking for a second one, which happens to contain grub and my efistubs.
Windows will go ahead and clear the UEFI menu sometimes, but manually booting an efi file and then re-adding the grub and stub boot entries is small compared to having my stuff actually deleted.
Only evil if you use one disk. :)
I'd had a dedicated windows drive for a little while... Maybe a bug and not malice, but the forced Windows 8 -> 10 upgrade deleted everything on my second drive that windows wasn't installed on
The Windows installer partition manager also does not ask for confirmation before formatting a drive. That was a costly misclick
load more comments
(1 replies)
I had two disks and windows still fucked my secure boot keys somehow in a way that I wasn't able to fix so I had to reinstall the linux side. I turned secure boot off afterwards so should be fine now but it was a thing that happened.
load more comments
(1 replies)
i've quadbooted a lot before (linux/freebsd/osx/windows), it works pretty well these days with uefi. was pretty hard to handle with legacy bios though
Why no Plan9? Are you even an OS enthusiast?
What no TempleOS? YOU'LL BURN IN FLAMES!!!!
load more comments
(2 replies)
The reason I just overwrote the Windows partition, instead of futzing with fixing dual boot was GDID. MSFTs global ID that tracks, literally, everything you do.
load more comments
(2 replies)
Put Windows in a virtual machine where it belongs!
Windows does stupid things with boot because it's apparently alone in the world.
Like this NTFS lock up thing because it's not really shutting down anymore but going into hibernate.
I had to change that setting but other than that dual boot works. Just realized that's still win 10 on this machine. When that runs out time for fresh Linux only install.
Microsoft’s boot killing shenanigans convinced me to just scrub the taint of 11 off this time.
view more: next ›