There was a Slashdot story a few weeks ago, on HP voiding your warranty if you install Linux. Linux geeks responded with an outrage, predictably, claiming that ever since CRT monitors come with safeguards that prevent the screen being fried through out-of-range settings, there is no way that a piece of software could destroy a hardware, and even if that’s the case, then it’s a bug in the hardware design itself.
In the case of the woman mentioned in the story, Linux is clearly not at fault — the keyboard was just broken, and the tech support person was too clueless (or the support regulations structured in such a way) to notice. However, there could be valid cases where the combination of crappy hardware and running Linux *would* ruin your hardware. I know, because it just happened to me.
The recipe is as such:
- Broken ACPI implementation (hello, HP! To be fair, the most recent dv2000, dv6000 and equivalent Compaq lines are probably fixed; by the lack of complaints), so that Linux’s ACPI subsystem cannot control the fan and CPU voltage properly
- A CPU that runs hot (first-generation “mobile” Turion 64)
- 2 years of frequent use, tolerating occasional crashes due to overheating
- OMG!!! LINUKS KILLZ ME PC!!
I guess the writing is on the wall when I had to remove my second memory module to keep the laptop running at all. The poor fans must be getting to their end of life. And today, after a freeze while the laptop was on battery power (previously almost unheard-of, it’s normally stable if running at 800 MHz, which it does when unplugged), it just never woke up again. The power indicators would be on, the optical drive would operate properly, and the AC indicator too, but apart from that, zilch. Nothing displayed to the screen, no error beep, nothing.
One begins to wonder whether the buggy Microsoft ACPI AML compiler was actually intentionally buggy. After all, if you load Windows onto your machine “as it is intended”, you’ll be using a Microsoft-written AML interpreter, and everything would be just fine. If you use the Intel reference AML interpreter, well, … Very disturbing indeed. The same way Microsoft abused its IE market share by intentionally not making it standards-compliant, making life a nightmare for web designers and thus the easy way out is to only support IE ..
RIP, HP L2000 “Lance Armstrong special edition”. It’s ironic that a record winner of an endurance cycling race, who also happens to be a cancer survivor, would lend his name to a buggy laptop with poor noise insulation and heat issues that didn’t even last two years. I was planning to replace it with an HP dv2000t once the Santa Rosa models are out (late April — early May), but after this, I wonder. I’ve never had a laptop dying on me before; my previous write-offs are either due to inexpert disassembly (Vaio C1) or drop damage (Vaio C140). Perhaps I’ll get a Macbook after all, though my Apple purchasing track record is notoriously bad (I’d buy just before a new model is launched — I barely managed to cancel a Dell laptop purchase when the Powerbook G4 12″ was released, and I jumped the gun and bought the Sony C140 — now with a broken LCD — and before it even arrived, the Core 2 Macbooks came out).
Could I wait this time for the don’t-know-when Santa Rosa? Come on, Apple, update the line before Leopard comes out!
Update – 2007/04/16 – OSnews has an article on a Bill Gates memo showing Microsoft’s intention to cripple ACPI. You’re not paranoid if people really are out to get you! And shame on that abusive monopolist — this is straight out of The Corporate, folks. It figures that after screwing over DR-DOS in a very similar way, they’d try the same trick again.