On Mon, Jul 23, 2007 at 07:44:10PM +0200, Hendrik-Jan Heins wrote:
>
> I just tested the following:
>
> Sidux 2007-2 (tartaros), amd64 on live cd.
> I loaded it to ram and installed uswsusp.
> next I did: "s2ram -f -m -a3", three times.
> Every time the machine suspended correctly and woke up again on touching
> the "Fn" button.
>
> Does this help?
Yes, sort of :-) If you could test if it also works on x86_64 with plain
"s2ram -f -a3" (without "-m") since "-a2" and "-m" _should_ be redundant.
I am this picky because i only recently realized that (some?) 64bit thinkpads
only resume with "-a1 -m" and do not correctly resume with "-a 3", which
means that part of the initialization must be run in the kernel (-a 1, POSTing
of the card) and part of it must be run in userspace ("-m", the re-setting of
the VESA mode), which sounds strange, especially as running the POST from
userspace ("-p -m") did _not_ work. So what i'm trying is to find a pattern,
because up to the 64bit processors, almost all thinkpads worked just fine with
"-a 3" (and most still do, as long as they are running 32bit code).
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
