Comment 97 for bug 971061

Hello!! After reading all the comments, and many tests of my own, I can conclude the following:

1) Kernel version / linux distro doesn't affect the issue.

2) It is a problem specific to suspending. If you don't suspend, you don't loose power monitoring/lid close.

3) There are two temporary fixes (let me contribute (B) here):

       A) Unplug laptop, then hit reset button through small hole in the back, then re-plug power to the laptop.

       B) Or: Reflash BIOS, any version, even the same one over (see my post at http://forum.notebookreview.com/samsung/683727-where-lid-closure-sensor-series-5-ultra-np530u3c.html#post9455595 in particular, please observe the "/n" switch of the flash utility mentioned in my post).

The (B) method explains why the problem goes away with a new BIOS update (the flashing tool clears the bios internal options (see sflash.exe /n switch)

Either fix is temporary and will return with an unlucky suspend/resume from sleep.

4) It is a BIOS problem, triggered by suspending in linux (and it got triggered by suspending in windows twice too in my case). The bios stops sending certain events (power, lid), because its state is corrupted somehow. When the laptop is in this state, dual booting windows has symptoms too (no lid detection, and unplug/replug events are reflected in windows' tray icon many seconds later, instead of instantaneously, as if by polling). Turning it off and on has no effect. Draining the battery has no effect. Toggling all options in the bios screen has no effect. The only fix is to do as in (3).

Now, Samsung uses some technology to have a mixed sleep, with the capability to hibernate after a threshold (time? battery-low?).
It has to do with "Intel Rapid Start" and Samsung Optimized power plan mode.

After reading the comments, I theorize that it's related to the fact that samsung expects some kind of hook to be present for when the laptop decides to quit regular sleep and ask Samsung/Intel's windows drivers to enter a deeper pseudo hibernation. (See option "Samsung Optimized" power plan in "Samsung Easy Settings" in windows).

I guess that both linux devs and samsung devs should work together to either: provide the second sleep hook, or a new bios that doesn't corrupt itself when not present.

Will this never get fixed? Will the same behavior happen with next generation Samsung models? Or some other model/brand that has intel rapid start?

BTW, I have a NP530U3C and been dealing with this issue as all of you guys. I hope this gets fixed since it is a nice ultrabook at a nice price, and this is the only problem that keeps me from fully enjoying it.