LinuxLinks has kindly given me the space to publish a semi-regular blog where I share my thoughts on open source, the Linux ecosystem, Windows, and other topics. It’s a place for my opinions and personal perspectives. As you might expect, everything I write here reflects my own views and prejudices.
A computer boots Ubuntu without any obvious problems. Does that mean it supports Linux? Not necessarily.
Linux hardware compatibility has improved enormously over the past couple of decades. On a modern PC, there is a good chance that graphics, storage, USB, Ethernet, Wi-Fi and Bluetooth will work without much intervention. That is a major achievement, but it has also made the phrase “Linux supported” increasingly vague.
Reaching the desktop is only the beginning. A machine can appear perfectly functional until you test suspend and resume, multiple display outputs, hardware video decoding, audio jack detection, webcams, card readers or Bluetooth after a reboot. Modern systems can also depend on vendor-specific performance modes, fan controls, firmware interfaces and NPU software stacks that may exist only for Windows.
The distinction I would make is between Linux compatibility and Linux support.
Linux compatible means the hardware works with Linux, often because its individual components already have upstream kernel drivers. The manufacturer may have done little or nothing to make that happen.
Linux supported should imply that the manufacturer has actually tested the product with Linux, documented any limitations, provided a sensible firmware update path and is willing to investigate Linux-specific regressions.
Canonical’s Ubuntu certification programme shows what proper support testing looks like. Certified systems go through hundreds of compatibility tests covering areas such as audio, networking, Bluetooth, USB, firmware and power management. That is considerably more meaningful than confirming that Ubuntu boots. For transparency, I have worked with Canonical previously.
Firmware is an important part of the distinction. Linux has ‘fwupd’ and the Linux Vendor Firmware Service, giving manufacturers a proper way to distribute firmware updates to Linux users. Yet plenty of otherwise Linux-compatible hardware still requires a Windows executable for BIOS or device firmware updates. I would call that Linux compatible, but not fully Linux supported.
Manufacturers should also be more precise about what support actually means. Which distributions and kernel versions have been tested? Are there known limitations? Do suspend and resume work? Are all network controllers supported? Does GPU acceleration work correctly? Can every advertised feature actually be used under Linux?
This distinction matters more with modern hardware, where an increasing number of features depend on firmware and vendor software. Modern processors combine CPUs, GPUs, NPUs and increasingly sophisticated power-management systems. Simply detecting the hardware is not the same as supporting everything it can do.
Linux hardware reviews therefore need to go beyond ‘lspci’, ‘lsusb’ and a screenshot of the desktop. Real testing means exercising networking, displays, power management, audio, firmware updating and any unusual hardware features.
If a manufacturer has only established that Ubuntu boots, “Linux compatible” is a fair description.
“Linux supported” should mean that the manufacturer has done some of the work too.
Please read our Comment Policy before commenting.