Linked by Radio on Fri 1st Feb 2013 22:57 UTC
Hardware, Embedded Systems The title is pretty much self-explanatory - oh UEFI. "You can read more of what is known at H-Online, but the short summary is this: Samsung's UEFI implementation appears to be faulty. It was most likely tested with Windows only and found to work, but thorough testing with other operating systems doesn't appear to have been a priority - or perhaps a consideration at all. At present, the bug appears to affect Samsung 530U3C, 300E5C, NP700Z5C, NP700Z7C, and NP900X4C series laptops; if you have one of those laptops, we recommend you exercise extreme caution if you have a need to boot into a Linux environment."
Permalink for comment 551203
To read all comments associated with this story, please click here.
RE: not clear where the bug is
by darknexus on Sat 2nd Feb 2013 04:03 UTC in reply to "not clear where the bug is"
Member since:

Its not clear where exactly the bug is I don't think. This apparently happens on some machines without uEFI. The problem is that bad data is written to the NVRAM. The BIOS/UEFI then tries to act on it, and crashes. Clearing the NVRAM by removing all power, including the cmos battery, solves the issue.

This is just another example of why this all needs to be open source.

That wouldn't solve a thing. Open source, closed source, doesn't matter. Honestly, people seem to think that open sourcing something is some sort of cure-all. If the bug is in the Linux kernel or associated drivers (and I'd say that's a good place to start since no other os has reported an issue like this) then the thing's already open sourced, and look what good it did.

Reply Parent Score: 4