Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If your computer fails to sleep, or fails to wake up correctly after sleeping, when running Linux then the problem is almost always the hardware manufacturer’s fault. Many motherboards come with frankly broken ACPI tables that should never have made it out of QA. Remember this (<https://news.ycombinator.com/item?id=45271484>) recent story? This is just the tip of the iceberg. For every well–researched story we have about ACPI problems there are a dozen more that are quietly fixed by Linux kernel developers (who instruct the kernel to simply ignore the broken ACPI tables and write a custom kernel driver to do the work instead) and an unknown but presumably large number that never come to the attention of a kernel developer.


It's not that Linux is "bad" when the hardware is incompatible, it's not "Linux's fault". It's that, at a certain age, I don't want to spend my precious few hours of free time working _on_ my computer, I just want it to work.

(big fan of MacOS, and esp. third-party Mac software, the quality of which simply does not exist on any other platform)

(Also, I have huge affection for Linux. I used Linux exclusively for years personally, and any place I could sneak it into my work environment)


Sure. But if it doesn’t work then _return the hardware_. It’s the manufacturer’s fault.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: