Unfortunately this has been going on for 20 years and people refuse to learn.

"My [GPU/whatever] doesn't work right"

"Why don't you buy hardware that officially supports Linux?"

"I couldn't possibly"

PennRobotics a day ago | parent | next [-]

I bought multiple ThinkPads with "official Linux support" that had diverse, show-stopping bugs. Because Lenovo is a difficult partner (for one, their service centers don't test against Linux) I don't hesitate anymore to instantly return a new computer if it has even minor bugs while running Fedora or Ubuntu. If ANY feasible alternative to Lenovo existed, I would've switched five years ago.

▲

skywhopper 2 days ago | parent | prev | next [-]

Wild to limit yourself to what the manufacturers “officially support”. May as well just run macOS with that attitude.

	▲	renehsz 2 days ago \| parent [-]
		I agree that you shouldn't rule out devices that don't have official support for Linux. And it's amazing that the community brings it to some many devices. But if you already know at purchase that you'll install Linux on the device, you might as well prefer those with official support rather than just a community port, simply to show support for companies that agree with your priorities. Also you should inform yourself beforehand. Don't just buy random hardware and then make the surprised pikachu face when it happens not to support Linux.

▲

oefrha 2 days ago | parent | prev [-]

Because sometimes people don’t go out of their way to buy Linux but want to repurpose old stuff they already own to experiment a bit and/or extend its life? For instance, I recently installed Ubuntu on my 10yo Intel MBP from 2015, and had to tweak lots of things to get it to a somewhat usable state that doesn’t flicker/tear/freeze. Had to use X11 instead of Wayland for anything Chromium-based. One of the most amusing ones (for some definition of amusing) is Bluetooth audio not working, turns out Ubuntu uses hot garbage codec that can’t fit into the available bandwidth due to AAC licensing (?), possibly among other problems, and switching to an AAC-enabled build made it reasonably stable.