You are not logged in.
Pages: 1
Suspend works; resume from suspend does not. I get a black screen. And suspend on lid close works, but if I accidentally close the lid, I can't resume.
However, resume from hibernate works great. So I'd like to set suspend on lid close to hibernate instead. Any problems or gotchas I should be aware of?
Offline
I had the same problem on my laptop (Toshiba Satellite A200 Series) - resuming from suspend resulted in black screen.
Solved it by setting some HAL params - quirks.
What is the output of
lshal | grep quirk
on your machine?
I have:
power_management.quirk.s3_bios = true (bool)
power_management.quirk.s3_mode = true (bool)
and I had no problems since I set it.
But the set of quirks you should turn on may be different for your laptop, so try google for it.
good luck
kamil
I tried, I failed, no matter. Try again, fail again, fail better.
Offline
Like kaituel says, you may be able to get your resume from suspend working by adding a quirk to the end of your suspend command. For instance, I have to use "/usr/sbin/pm-suspend --quirk-vbestate-restore". Google and the pm-suspend docs will be useful; but you may also have to do some trial and error.
As to the question you posed: sure, you can set the close-lid command to be hibernate instead of suspend, why not? But uou may have a problem sometimes if you've got too much (unpurgeable) memory in use to fit on the partition you specify.
Offline
I'm feeling too impatient for trial and error right now, so I'll continue with the original plan.
Thanks for the responses
Offline
You could also try uswsusp (s2ram and s2disk) instead. I had troubles on my hp dv6000 not resuming from pm-suspend, but s2ram -f works great. There's a wiki article that covers setup for uswsusp. I changed the default in /etc/acpi/handler.sh to s2ram -f for a lid closed event.
Scott
Offline
Pages: 1