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."
Thread beginning with comment 551203
To view parent comment, click here.
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"
darknexus
Member since:
2008-07-15

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

TechGeek Member since:
2006-01-14

Its not a cure all. But it does make fixing broken things a hell of a lot easier. It also makes spotting errors before they have this affect a lot easier. Its a matter of practicality not morality.

Reply Parent Score: 5

darknexus Member since:
2008-07-15

Its not a cure all. But it does make fixing broken things a hell of a lot easier. It also makes spotting errors before they have this affect a lot easier. Its a matter of practicality not morality.

In point of fact, it does not. How many open source projects are out there that actually concentrate on fixing bugs? Most of the time, the 80/20 rule plagues them, and they end up implementing more features rather than fixing anything. Debugging and optimizing are not fun and, since most people who work on open source software are unpaid, they do not usually want to do that which is not fun. Every open source project I can think of that does concentrate even somewhat on fixes (the Linux kernel, Firefox, Chromium) has commercial developers working on them and the fixes come from there. Contrary to popular belief, there's not an endless supply of talented programmers willing to fix bugs in other peoples' projects for free. Speaking of that, as the kernel's Samsung laptop driver has been identified as the problem, you already have your wish for this bug to be in an open source component. Again I ask you, what good did that do?

Reply Parent Score: 2

segedunum Member since:
2005-07-06

That wouldn't solve a thing. Open source, closed source, doesn't matter.

It would. The problem here is not the kernel code but understanding what on Earth this silly device is doing. If the source for that was known this would be a thread on the kernel list with some commits at the end for both the kernel and firmware.

Reply Parent Score: 5