Hi,
Stefan Seyfried a écrit :
> On Fri, Nov 17, 2006 at 12:29:21AM +0100, Gilles Grandou wrote:
>> Just to let you know that s2ram is working fine on my laptop:
>>
>> # s2ram -i
>> This machine can be identified by:
>> sys_vendor = "CLEVO"
>> sys_product = "D500P"
>> sys_version = "Revision A2"
>> bios_version = "6.00"
>> See http://en.opensuse.org/S2ram for details.
>>
>> s2ram -f is enough to suspend.
>
> Does it work from X only or from Text mode also?
>> I have encountered following incompatibilities:
>> * don't use console framebuffer
>
> What happens if you use a framebuffer?
As it's a thing I didn't try for ages, I've done a full set of
tests.
I'm using two boot configurations:
title test
root (hd0,1)
kernel /boot/vmlinuz-2.6.18-2-686 root=/dev/hda2 ro
resume=/dev/hda7 noapic single
initrd /boot/initrd.img-2.6.18-2-686
title testfb
root (hd0,1)
kernel /boot/vmlinuz-2.6.18-2-686 root=/dev/hda2 ro
resume=/dev/hda7 noapic single video=vesafb vga=792
initrd /boot/initrd.img-2.6.18-2-686
(kernel is the one from official debian sid package)
============================================================
config <test> - from text console
s2ram -f -> suspend ok
-> resume: hang
* screen black
* no caps lock feeback
* ctrl-alt-del does nothing
* alt-sysrq-b ok
s2ram -f -a 1 -> resume: hang / alt-sysrq-b fail
s2ram -f -a 2 -> resume: hang / alt-sysrq-b ok
s2ram -f -a 3 -> resume: hang / alt-sysrq-b ok
s2ram -f -p -m -> resume ok!
* but display is a little bit corrupted
(garbage lines, screen shifted)
s2ram -f -p -s -> resume ok!
-> screen ok!
s2ram -f -m -> resume: hang / alt-sysrq-b ok
s2ram -f -s -> resume: hang / alt-sysrq-b fail
* screen corrupted (rand color chars)
s2ram -f -p -> resume ok!
* screen ok!
s2ram -f -a1 -m -> resume: hang / alt-sysrq-b fail
s2ram -f -a1 -s -> resume: hang / scree corrupted / alt-sysrq-b fail
s2disk -> resume ok
s2both -> suspend ok, but powered off, no S3
-> power on: resume ok
============================================================
config <testfb> - from text console
s2ram -f -> resume: hang / sysrq failed
s2ram -f -a 1 -> resume: hang / sysrq failed
s2ram -f -a 2 -> resume: hang / sysrq failed
s2ram -f -a 3 -> resume: hang / sysrq failed
s2ram -f -p -m -> resume: hang / sysrq failed
s2ram -f -p -s -> resume: hang / sysrq failed
s2ram -f -m -> resume: hang / sysrq failed
s2ram -f -s -> resume: hang / sysrq failed
s2ram -f -p -> resume: hang / sysrq failed
s2ram -f -a1 -m -> resume: hang / sysrq failed
s2ram -f -a1 -s -> resume: hang / sysrq failed
s2disk -> resume ok
s2both -> suspend ok, no S3
-> power: resume ok
============================================================
config <test> - from X
s2ram -f -> resume ok
s2ram -f -p -s -> resume ok
s2ram -f -p -> resume ok
s2disk -> resume ok
s2both -> suspend ok, no S3
-> resume ok
============================================================
config <testfb> - from X
s2ram -f -> resume: hang / sysrq failed
s2ram -f -p -s -> resume: hang / sysrq failed
s2ram -f -p -> resume: hang / sysrq failed
s2disk -> resume ok
s2both -> suspend ok, no S3
-> power: resume ok
============================================================
The best config is definitively:
- no framebuffer
- s2ram -f -p
Regards,
Gilles.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Suspend-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/suspend-devel
