3 ms·
"it appears they're trying to crash the kernel by locking a region of memory that shouldn't be locked" ...or, they're second-rate programmers who don't test th
by dandelany 18y ago
"it appears they're trying to crash the kernel by locking a region of memory that shouldn't be locked"
...or, they're second-rate programmers who don't test their code very thoroughly.
Yes, he is going overboard by claiming "deliberate sabotage." Every hacker wants his 15 minutes of /., and he got his. However, the important overlooked fact here is about halfway down in his post:
"I've found separate DSDT tables that the BIOS hands to Linux specifically, changing it to point to the DSDT tables Vista gets fixes all Linux issues with this board."
That is, the problem isn't that they screwed up the Linux implementation of their BIOS, it's that they created different rules for Linux to follow when the Vista ones worked just fine. I still have a hard time attributing it to malice, but this is very asinine indeed.
- rit 18y agoInterestingly enough though... FoxConn says in the email replies that they DONT SUPPORT Linux. However, they have code specifically written for it. Strange, even if it isn't deliberate sabotage.
- sysop073 18y agoThis was what made me thing they did it intentionally. They don't support Linux, and yet they intentionally detect Linux and have special code written for it that doesn't work, when the standard code does work. That's incredibly suspicious, it's like when Hotmail decided to "only support Internet Explorer" by sniffing the user agent string when it actually worked fine on Firefox