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 551212
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Return the laptop!
by darknexus on Sat 2nd Feb 2013 06:49 UTC in reply to "Return the laptop!"
darknexus
Member since:
2008-07-15

It is defective and they need to either correct the mistake at their cost and pay a bit more for your troubles or you should be able to return the defective laptop.

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.

Reply Parent Score: 0

RE[2]: Return the laptop!
by lucas_maximus on Sat 2nd Feb 2013 16:22 in reply to "RE: Return the laptop!"
lucas_maximus Member since:
2009-08-18

I would love to know why you got voted down.

Ubuntu’s development team has worked with Samsung and identified the kernel’s Samsung-laptop driver as the prime suspect, and there are other workarounds proposed already to address the issue.


It does seem likely at this stage that you are correct.

Edited 2013-02-02 16:23 UTC

Reply Parent Score: 3

RE[3]: Return the laptop!
by darknexus on Sat 2nd Feb 2013 20:46 in reply to "RE[2]: Return the laptop!"
darknexus Member since:
2008-07-15

I would love to know why you got voted down.

Oh, come now, you already know why. I dared to criticize the amazing, wonderful, cannot possibly have any bugs, everyone should use it Linux. It's not cool to do that, even when it's true.

Reply Parent Score: 2

RE[3]: Return the laptop!
by segedunum on Sun 3rd Feb 2013 21:55 in reply to "RE[2]: Return the laptop!"
segedunum Member since:
2005-07-06

I would love to know why you got voted down.

Because, as usual, neither he nor you read.

The problem here is the device itself is doing things that only Samsung truly knows about, and it diverges away from any kind of reasonably expected behaviour. It's ACPI all over again. The Samsung kernel code was also built from Samsung's own code and yet it still fails.

Edited 2013-02-03 21:57 UTC

Reply Parent Score: 3

RE[2]: Return the laptop!
by TechGeek on Sat 2nd Feb 2013 20:51 in reply to "RE: Return the laptop!"
TechGeek Member since:
2006-01-14

"It is defective and they need to either correct the mistake at their cost and pay a bit more for your troubles or you should be able to return the defective laptop.

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.

Reply Parent Score: 3

RE[2]: Return the laptop!
by WereCatf on Sun 3rd Feb 2013 09:09 in reply to "RE: Return the laptop!"
WereCatf Member since:
2006-02-15

"It is defective and they need to either correct the mistake at their cost and pay a bit more for your troubles or you should be able to return the defective laptop.

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.
"

I'll just chime in that the culprit is actually Samsung's UEFI-implementation. Their implementation doesn't follow the spec properly and handles some corner-cases in an unexpected way. Specifically, it apparently expects a 104-byte structure whereas Linux provides it with a standards-compliant 1024-byte structure and therefore it proceeds to crap all over itself and corrupt NVRAM. The odd thing is that most of the driver-code was provided by Samsung themselves.

Later on it the thread someone said that emptying the NVRAM is enough to fix some (all?) of the affected machines, but it still requires you to open the laptop and removing the NVRAM-battery for 30 seconds or disabling it otherwise if it's soldered-on.

Reply Parent Score: 2