My Samsung doesnt hibernate

Hi
I have a Samsung 700G7C and immediately installed gentoo linux when i unwrapped it.

I got everything working, including Wifi.

The only thing i can't do is Hibernation. It looks as if hibernation starts when i call 'pm-hibernate' - an image is apparently written to disc, but the computer does not power off (the screen is black but the power, wifi and loudspeaker LED as all lit). I don't know if hibernation would work on my Samsung at all, because i never started it in the originally installed windows, or if it is a OS problem (although i tried to different kernels...)

Has any body got similar experiences with a Samsung? Or even a suggestion what i could try (e.g. find out if this is a hardware problem or a OS problem)?

Thank You
Jody

 

There are a bunch of quirks that you can read about in the manpage for pm-hibernate. Have you tried any of those? If so, and they don't work...

To get around buggy ACPI code in your BIOS, you can try passing the:

Code:

acpi_osi="Windows 2009"

boot parameter at your grub boot screen. There are other values like "!Linux" or "Windows 2006" that you can try.

If that doesn't work out, you can try s2disk from uswsusp.

 

Hi ALLurGroceries (arebelongtous? )

Thanks for your suggestions.
I have not yet gotten around to try them, yet.

I have looked at the pm-hibernate man page, but i must
admit that i don't understand (e.g. "calls the video BIOS")

Can you tell me why you suggest the "acpi_osi" boot parameter?
As far as i understand it tells grub to think my computer is
not a linux machine (but windows)...


Thanks
Jody

 

Well, the Linux kernel by default assumes that the BIOS is not "broken", i.e. respects the ACPI spec, which sadly is not often the case. So to "trick" the machine into working and responding to ACPI stuff like hotkeys and triggers such as the lid and power state changes, you can try experimenting with the ACPI OS string.

The quirks for pm-hibernate are really shots in the dark (unless you can find reports from people that know otherwise), you can try them as long as you don't have any open applications with data that you need to save. Being in the middle of writing a document and then trying these quirks is a bad idea, because your system may lock up forcing you to hold the power button to turn it off. To be safe, before you try each of them do a:

Code:

sudo touch /forcefsck

This will force a filesystem check regardless of its health the next time the system boots.

Really though, a cheap way out is usually s2disk from uswsusp.