Linked by Radio on Fri 1st Feb 2013 22:57 UTC
Permalink for comment 551272
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/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
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2006-02-15
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.