Linked by Radio on Fri 1st Feb 2013 22:57 UTC
Permalink for comment 551253
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2006-01-14
In this case, since Linux is the only os to suffer this, I'd venture to say that the os is defective and not the laptop. "
No, its not the OS. If you read here:
http://mjg59.dreamwidth.org/22028.html
You will see that the cause of the problem is the arcane way Samsung handles the BIOS. If your software uses the same memory region that Samsung's laptop thinks it should be using, you end up with corruption. Software writing to a non permanent memory should NEVER be able to brick your PC, regardless of the OS.