Thinkpad Z60T suspend to ram

[Lei Kong]

Hi,

I have problems with getting suspend-to-ram/resume work on
my thinkpad z60t. When resuming, it always gave me a blank screen.
I know the machine is running because I can ssh onto it.

Z60T comes with Intel 915GM display controller, and I am using
the i810 driver shipped with xorg.6.8.2. My login manager is kdm.
The kernel is 2.6.15 compiled from source, with acpi and thinkpad
acpi extra built-in. I also installed the debian hibernate and vbetool
 packages.

The suspend-to-ram process looks fine. I tried the workaround
on thinkwiki, saving display state to a temp file and recovering
when resuming, but it didn't work. Some resuming information
(acpi ...) was diplayed first, then the screen still went blank.
I have tried both the hibernate script with configuration to suspend
to ram and echo 'mem' > /sys/power/state.

Some says the problem is due to the lack of power management of sata
driver, but that is not my case, since my machine does not hang when
resuming, as described.

The following is my /etc/hibernate/hibernate.conf

UseSysfsPowerState mem
Verbosity 0
LogFile /var/log/hibernate.log
LogVerbosity 1
SaveClock restore-only
UnloadBlacklistedModules yes
LoadModules auto
DownInterfaces eth0
UpInterfaces auto
EnableVbetool yes
SwitchToTextMode yes

Anyone has a clue how to get this work? I would appreciate it
very much if you can share your experience. Laptop without
suspend really sucks!

Lei


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Florian Kulzer]

Lei Kong wrote:

> Hi,
>
> I have problems with getting suspend-to-ram/resume work on
> my thinkpad z60t. When resuming, it always gave me a blank screen.
> I know the machine is running because I can ssh onto it.
>
> Z60T comes with Intel 915GM display controller, and I am using
> the i810 driver shipped with xorg.6.8.2. My login manager is kdm.
> The kernel is 2.6.15 compiled from source, with acpi and thinkpad
> acpi extra built-in. I also installed the debian hibernate and vbetool
> packages.
>
> The suspend-to-ram process looks fine. I tried the workaround
> on thinkwiki, saving display state to a temp file and recovering
> when resuming, but it didn't work. Some resuming information
> (acpi ...) was diplayed first, then the screen still went blank.
> I have tried both the hibernate script with configuration to suspend
> to ram and echo 'mem' > /sys/power/state.
>
> Some says the problem is due to the lack of power management of sata
> driver, but that is not my case, since my machine does not hang when
> resuming, as described.
>
> The following is my /etc/hibernate/hibernate.conf
>
> UseSysfsPowerState mem
> Verbosity 0
> LogFile /var/log/hibernate.log
> LogVerbosity 1
> SaveClock restore-only
> UnloadBlacklistedModules yes
> LoadModules auto
> DownInterfaces eth0
> UpInterfaces auto
> EnableVbetool yes
> SwitchToTextMode yes

Does your display problem occur when you suspend/resume from a virtual
terminal or only when you suspend X? If the problem is with X then the
option "UseDummyXServer yes" in hibernate.conf might fix it. Generally I
would recommend to start from the hibernate.conf which is shipped with
Debian and incorporate your changes/additions. I think the Debian
developers have spent quite some time to tweak this configuration file
and there are a number of comments about additional X-related options
which might be helpful.

Regards,
            Florian


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

On Tue, 24 Jan 2006 22:24:05 -0500
Lei Kong <lei.kong@...> wrote:

> Hi,
>
> I have problems with getting suspend-to-ram/resume work on
> my thinkpad z60t. When resuming, it always gave me a blank screen.
> I know the machine is running because I can ssh onto it.
...

> Anyone has a clue how to get this work? I would appreciate it
> very much if you can share your experience. Laptop without
> suspend really sucks!
>
> Lei

Hi Lei Kong,

the problem is that the video card does not pick up.

Switch to console mode before suspending (example ctrl+alt+F1). Or do it with a script as described in the snip below.

[snip]
chvt 1
sleep 1
echo -n "mem" > /sys/power/state
vbetool post
chvt 7
[/snip]

Also nice to include
[snip]
xscreensaver-command -lock
[/snip]
before the suspension, so your computer is always locked after resume.

Regards,

Rob de Graaf


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Lei Kong]

>
>
>Does your display problem occur when you suspend/resume from a virtual
>terminal or only when you suspend X? If the problem is with X then the
>option "UseDummyXServer yes" in hibernate.conf might fix it. Generally I
>would recommend to start from the hibernate.conf which is shipped with
>Debian and incorporate your changes/additions. I think the Debian
>developers have spent quite some time to tweak this configuration file
>and there are a number of comments about additional X-related options
>which might be helpful.
>
>
>Regards,
>           Florian
>

Thanks for the hint, finially, I managed to make non-X resume
works. But, still no luck with X resume.  UseDummyXServer,
VbePost and SwitchToText does not help.

If I remove kdm from /etc/rc2.d, then after resuming, I can start kde,
no problem at all. However, once X was running, future attempt to
restart X after resuming will  fail, no matter whether I stop X or not
before suspending to ram.

Lei


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Lei Kong]

>
>
>Hi Lei Kong,
>
>the problem is that the video card does not pick up.
>
>Switch to console mode before suspending (example ctrl+alt+F1). Or do it with a script as described in the snip below.
>
>[snip]
>chvt 1
>sleep 1
>echo -n "mem" > /sys/power/state
>vbetool post
>chvt 7
>[/snip]
>
>Also nice to include
>[snip]
>xscreensaver-command -lock
>[/snip]
>before the suspension, so your computer is always locked after resume.
>
>Regards,
>
>Rob de Graaf
>

Thanks for your reply, I tried the switching thing, it didn't work for me.
Actually, debian hibernate script has such an option. I tried both the
hibernate way and the way you suggested, neither worked when X is
running, :-(


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Raúl Sánchez Siles-3]

  I own a Dell i510m, which has an Intel 855GM graphics card. I had very similar
problems, and finally used the attached hibernate script configuration file to
suspend to RAM my laptop.

  For using this in a nice way, I use the acpid and modifify the lid event
file[1] that it executes a script which contains the lines[2].

[1]
action=/etc/acpi/actions/STRam.sh %e

[2]
if (grep -q closed "/proc/acpi/button/lid/$2/state" ) || (test "$2" == 'SBTN'); then
  hibernate -F /etc/hibernate/ram.conf
fi

Before I did all these things I used to do the following:

First and more reliable option, issue a video_post when the console is blank
after the lid has been closed. I can't remember the exact URL to download it,
but a simple google search will lead you to it.

The second option is using the vbetool, which I didn't get to use very much, but
it is the one used by hibernate.

The last one is using the hibernate to disk and then power up the laptop, which
is not very handy, but maybe a last alternative in emergency cases.

The problem comes when the video is power down, but nor properly powered up when
 opening the lid. I don't know which is to blame, but I suppose it should be
either the bios or the video card.

My brain is a little dense now, but if you need more info just ask again. Sorry
for this.

Lei Kong wrote:

>>
>>
>> Hi Lei Kong,
>>
>> the problem is that the video card does not pick up.
>>
>> Switch to console mode before suspending (example ctrl+alt+F1). Or do
>> it with a script as described in the snip below.
>>
>> [snip]
>> chvt 1
>> sleep 1
>> echo -n "mem" > /sys/power/state
>> vbetool post
>> chvt 7
>> [/snip]
>>
>> Also nice to include [snip]
>> xscreensaver-command -lock
>> [/snip]
>> before the suspension, so your computer is always locked after resume.
>>
>> Regards,
>>
>> Rob de Graaf
>>

--
Raúl Sánchez Siles

[Lei Kong]

>
>
>  I own a Dell i510m, which has an Intel 855GM graphics card. I had very similar
>problems, and finally used the attached hibernate script configuration file to
>suspend to RAM my laptop.
>
>  For using this in a nice way, I use the acpid and modifify the lid event
>file[1] that it executes a script which contains the lines[2].
>
>[1]
>action=/etc/acpi/actions/STRam.sh %e
>
>[2]
>if (grep -q closed "/proc/acpi/button/lid/$2/state" ) || (test "$2" == 'SBTN'); then
>  hibernate -F /etc/hibernate/ram.conf
>fi
>
>Before I did all these things I used to do the following:
>
>First and more reliable option, issue a video_post when the console is blank
>after the lid has been closed. I can't remember the exact URL to download it,
>but a simple google search will lead you to it.
>
>The second option is using the vbetool, which I didn't get to use very much, but
>it is the one used by hibernate.
>
>The last one is using the hibernate to disk and then power up the laptop, which
>is not very handy, but maybe a last alternative in emergency cases.
>
>The problem comes when the video is power down, but nor properly powered up when
> opening the lid. I don't know which is to blame, but I suppose it should be
>either the bios or the video card.
>
>My brain is a little dense now, but if you need more info just ask again. Sorry
>for this.
>

Thanks for the info, can you post on the list or send me a copy of
your ram.conf?

Lei


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Raúl Sánchez Siles-3]

  Here you are. I sent it before, but seems that the mailing list filters
removed it.

  Regards,

--
Raúl Sánchez Siles

[8rino]

Hi all,  here is Ottorino from Florence, Italy.
I own a Z60t on which I recently installed Debian lenny kernel 2.6.22-3-686.
I have the same problem with suspend/hibernate.
Pressing the blue keys Fn+moon the computer hibernate
Pressing the same keys again the computer comes back to life, but appparently it is not able to switch on the neon lamps within the monitor.
In fact I can (hardly) see the shades of icons and windows on the desktop.
I tried to find out where the hibernate.conf is, but unsuccessfully.
Could you please give me a hint on where to find informations on how to solve this problem (and learn something in the meanwhile ?)

Lei Kong wrote:

>
>
>Does your display problem occur when you suspend/resume from a virtual
>terminal or only when you suspend X? If the problem is with X then the
>option "UseDummyXServer yes" in hibernate.conf might fix it. Generally I
>would recommend to start from the hibernate.conf which is shipped with
>Debian and incorporate your changes/additions. I think the Debian
>developers have spent quite some time to tweak this configuration file
>and there are a number of comments about additional X-related options
>which might be helpful.
>
>
>Regards,
>           Florian
>
Thanks for the hint, finially, I managed to make non-X resume
works. But, still no luck with X resume.  UseDummyXServer,
VbePost and SwitchToText does not help.

If I remove kdm from /etc/rc2.d, then after resuming, I can start kde,
no problem at all. However, once X was running, future attempt to
restart X after resuming will  fail, no matter whether I stop X or not
before suspending to ram.

Lei

[Florian Kulzer-3]

On Fri, Jan 04, 2008 at 01:39:42 -0800, 8rino wrote:

>
> Hi all,  here is Ottorino from Florence, Italy.
> I own a Z60t on which I recently installed Debian lenny kernel 2.6.22-3-686.
> I have the same problem with suspend/hibernate.
> Pressing the blue keys Fn+moon the computer hibernate
> Pressing the same keys again the computer comes back to life, but
> appparently it is not able to switch on the neon lamps within the monitor.
> In fact I can (hardly) see the shades of icons and windows on the desktop.
> I tried to find out where the hibernate.conf is, but unsuccessfully.
> Could you please give me a hint on where to find informations on how to
> solve this problem (and learn something in the meanwhile ?)

The configuration files are in /etc/hibernate/. Install the "hibernate"
and "vbetool" packages and read the documentation.

Also see here:
http://www.thinkwiki.org/wiki/Problem_with_display_remaining_black_after_resume

--
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[8rino]

Dear Dr Kulzer, thanks for the hints.
I did the following:

apt-get install hibernate
that installed also vbetool

I tried to read the manuals, but I did not understand properly what I'm suppose to do.
But at least, I finally understand the difference between "suspend" and "hibernate".

When I tried to "suspend" the computer (pressing Fn-moon), it failed but I had a pop-up addressing me to
http://people.freedesktop.org/~hughsient/quirk/

There I find many useful information, but stil I'm not able to suspend the computer correctly.
I modified "i810" in "intel" in the xorg.conf file, as requested by  ./quirk-checker.sh  and, as far as I can understand, I must use the quirk "--quirk-s3-bios" to the pm-suspend command.

If i write pm-suspend--quirk-s3-bios, everything seems to work fine, but I do not know where to write this option permanently.

Here (/http://www.thinkwiki.org/wiki/Problem_with_display_remaining_black_after_resume) it is suggested to write
DISPLAY_QUIRK_S3_BIOS=\"true\"  into /etc/pm/config.d/config for FC7.
I did it, but seems not to work with debian.

Moreover, in the manual for pm-suspend I read
FILES
       /etc/pm/config.d
           The files in this directory are evaluated in C sort order. These
           files can be provided by individual packages outside of pm-utils.
           If a global configuration variable is set, the value set to will be
           appended to the previous value. If any other variable is set, it
           will be ignored. The syntax is simply: VAR_NAME = value. See the
           CONFIGURATION VARIABLES section for valid variables defined by
           pm-utils. External packages can define others, see their respective
           documentation for more information.

and the CONFIGURATION VARIABLES section below in the manual seem not to report
DISPLAY_QUIRK_S3_BIOS=\"true\" as a valid variable.

I think that there are some files where I have to write some options, but I'm unclear where they are and in which order they are read/executed
Any hint as to where to learn such things?

Moreover, coming back to hibernate, in the hibernate manual I see that I should compile the kernel in order to let "hibernate" work. Is that true ?
From dmesg I have not any tuxonice non suspend2 item

I went to the http://www.tuxonice.net/ but there there are not yet the directions on how to recompile the kernel.

Thanks again
Ottorino



The configuration files are in /etc/hibernate/. Install the "hibernate"
and "vbetool" packages and read the documentation.

Also see here:
http://www.thinkwiki.org/wiki/Problem_with_display_remaining_black_after_resume

[Florian Kulzer-3]

On Tue, Jan 08, 2008 at 01:40:37 -0800, 8rino wrote:

[...]

> I did the following:
>
> apt-get install hibernate
> that installed also vbetool
>
> I tried to read the manuals, but I did not understand properly what I'm
> suppose to do.

I initially suggested hibernate and vbetool because they helped me to
get suspend to ram working on my laptop (which is not a thinkpad, but I
also have an intel graphics chip). The hibernate configuration files
have a commented-out option to use vbetool after resume, and this
removed my own problems with the black display. However, since your
thinkpad seems to be configured already to use pm-utils, I suggest that
you try a bit more with that.

> When I tried to "suspend" the computer (pressing Fn-moon), it failed but I
> had a pop-up addressing me to
> http://people.freedesktop.org/~hughsient/quirk/
>
> There I find many useful information, but stil I'm not able to suspend the
> computer correctly.
> I modified "i810" in "intel" in the xorg.conf file, as requested by
> ./quirk-checker.sh  and, as far as I can understand, I must use the quirk
> "--quirk-s3-bios" to the pm-suspend command.
>
> If i write pm-suspend--quirk-s3-bios, everything seems to work fine, but I
> do not know where to write this option permanently.

If I understand you correctly, you can suspend and resume without
problems if you use this command directly? That means you almost have it
working already. We just have to figure out how to make sure the
--quirk-s3-bios option is invoked when you press Fn-moon.

> Here
> (/http://www.thinkwiki.org/wiki/Problem_with_display_remaining_black_after_resume)
> it is suggested to write
> DISPLAY_QUIRK_S3_BIOS=\"true\"  into /etc/pm/config.d/config for FC7.
> I did it, but seems not to work with debian.

This might be a misunderstanding: I think you should put

DISPLAY_QUIRK_S3_BIOS="true"

into this file. You only need to type the backslashes ("\") if you use
the echo command to write this line into this file. Can you post the
output of

cat /etc/pm/config.d/config

?

> Moreover, in the manual for pm-suspend I read

[...]

> and the CONFIGURATION VARIABLES section below in the manual seem not to
> report
> DISPLAY_QUIRK_S3_BIOS=\"true\" as a valid variable.

This might simply mean that the manual is not up-to-date. The thinkwiki
pages have the reputation to be the best source of information for
thinkpad users.

> I think that there are some files where I have to write some options, but
> I'm unclear where they are and in which order they are read/executed
> Any hint as to where to learn such things?

In a perfect world the manpages should always list the configuration
files and directories. Sometimes it is necessary to use google or to
list all files of a package and make a guess.

(You can use "dpkg -L pm-utils" to list all files in the pm-utils
 package, for example.)

> Moreover, coming back to hibernate, in the hibernate manual I see that I
> should compile the kernel in order to let "hibernate" work. Is that true ?
> From dmesg I have not any tuxonice non suspend2 item

Only some ways of suspending require a kernel patch. As I said above,
try a bit more with pm-utils since it works from the command line
already.

--
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[8rino]

On Tue, Jan 08, 2008 at 01:40:37 -0800, 8rino wrote:
[...]
If I understand you correctly, you can suspend and resume without
problems if you use this command directly? That means you almost have it
working already. We just have to figure out how to make sure the
--quirk-s3-bios option is invoked when you press Fn-moon.

This is actually the problem.

> Here
> (/http://www.thinkwiki.org/wiki/Problem_with_display_remaining_black_after_resume)
> it is suggested to write
> DISPLAY_QUIRK_S3_BIOS=\"true\"  into /etc/pm/config.d/config for FC7.
> I did it, but seems not to work with debian.

This might be a misunderstanding: I think you should put

DISPLAY_QUIRK_S3_BIOS="true"
into this file.

I made a bad copy&paste from the page.
In  my /etc/pm/config.d/config is written exactly as above

> I think that there are some files where I have to write some options, but
> I'm unclear where they are and in which order they are read/executed
> Any hint as to where to learn such things?

In a perfect world the manpages should always list the configuration
files and directories. Sometimes it is necessary to use google or to
list all files of a package and make a guess.

Thanks to your help and suggestions I've found this
http://en.opensuse.org/Pm-utils
which is a very helpful page indeed.
It explains all the nuts and bolts of pm-utils.

Nevertheless I'm still unable to suspend/hibernate the machine properly,
even if I'm quite happy since I'm starting to understand something.

From
cat /var/log/pm-suspend.log
I get

===== Wed Jan  9 16:02:52 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/00clear =====
/usr/lib/pm-utils/functions: line 28: [: /etc/pm/config.d/config: binary operator expected
/usr/lib/pm-utils/functions: line 28: [: /etc/pm/config.d/config: binary operator expected

where around line 28  in /usr/lib/pm-utils/functions

I find this:

source_configs()
{
        cfgs="/etc/pm/config.d/*[^~]"
        for cfg in $cfgs ; do
                [ -f $cfgs ] || continue
                set -a
                . $cfg
                set +a
        done
}

I'm not a programmer, so do you have any idea, please ?

BTW, thanks for being a good interlocutor. I appreciate it a lot.
I'm quite alone here dealing with Linux. I switched "definitely" to it only 6 months ago or so.

We are somehow colleagues. You can find me here
http://www4.unifi.it/dssnp/english/professors/pantani.htm

[Florian Kulzer-3]

On Wed, Jan 09, 2008 at 08:28:02 -0800, 8rino wrote:

> On Tue, Jan 08, 2008 at 01:40:37 -0800, 8rino wrote:
> [...]
> If I understand you correctly, you can suspend and resume without
> problems if you use this command directly? That means you almost have it
> working already. We just have to figure out how to make sure the
> --quirk-s3-bios option is invoked when you press Fn-moon.
>
> This is actually the problem.
>
> > Here
> > (/http://www.thinkwiki.org/wiki/Problem_with_display_remaining_black_after_resume)
> > it is suggested to write
> > DISPLAY_QUIRK_S3_BIOS=\"true\"  into /etc/pm/config.d/config for FC7.
> > I did it, but seems not to work with debian.
>
> This might be a misunderstanding: I think you should put
>
> DISPLAY_QUIRK_S3_BIOS="true"
> into this file.
>
> I made a bad copy&paste from the page.
> In  my /etc/pm/config.d/config is written exactly as above

[...]

> Thanks to your help and suggestions I've found this
> http://en.opensuse.org/Pm-utils
> which is a very helpful page indeed.
> It explains all the nuts and bolts of pm-utils.
>
> Nevertheless I'm still unable to suspend/hibernate the machine properly,
> even if I'm quite happy since I'm starting to understand something.
>
> >From
> cat /var/log/pm-suspend.log
> I get
>
> ===== Wed Jan  9 16:02:52 CET 2008: running hook:
> /usr/lib/pm-utils/sleep.d/00clear =====
> /usr/lib/pm-utils/functions: line 28: [: /etc/pm/config.d/config: binary
> operator expected
> /usr/lib/pm-utils/functions: line 28: [: /etc/pm/config.d/config: binary
> operator expected
>
> where around line 28  in /usr/lib/pm-utils/functions
>
> I find this:
>
> source_configs()
> {
>         cfgs="/etc/pm/config.d/*[^~]"
>         for cfg in $cfgs ; do
>                 [ -f $cfgs ] || continue
>                 set -a
>                 . $cfg
>                 set +a
>         done
> }
>
> I'm not a programmer, so do you have any idea, please ?

I think the mistake is in this line:

                 [ -f $cfgs ] || continue

It should have "$cfg" instead of "$cfgs":

                 [ -f $cfg ] || continue

This part of the script saves a list of all files in /etc/pm/config.d/
in the variable $cfgs and then it loops over the elements in this list,
assigns one after the other to $cfg, tests if the current $cfg file
exists and executes (sources) it if it is a regular file. The mistake in
the script explains why your configuration commands are not executed.
Maybe it will work if you correct it by removing the superfluous "s".

If that does not make it work then we will have to find out what exactly
happens when you press Fn-moon. After you press it you should find some
information about this in the syslog. I propose that you press Fn-moon,
get the laptop working again (hard reboot, I assume) and then run this:

grep acpid /var/log/syslog

(Normally the ACPI daemon is the one responsible for handling the
 special keys. It should write in the log which script is called. We
 might then be able to adapt this script to your needs.)

> BTW, thanks for being a good interlocutor. I appreciate it a lot.
> I'm quite alone here dealing with Linux. I switched "definitely" to it only
> 6 months ago or so.

There is a lot to learn in the beginning, of course, but the good thing
is that it gets easier quickly and that the overall system design is
much more logical than the one of a certain other OS. Also keep in mind
that specialized laptop hardware and functions like suspend are among
the most difficult to configure under Linux; most other things are much
easier to get working.

> We are somehow colleagues. You can find me here
> http://www4.unifi.it/dssnp/english/professors/pantani.htm

It is nice to find other Chemists using Linux.

--
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[8rino]

[...]
>I think the mistake is in this line:
>                 [ -f $cfgs ] || continue
>It should have "$cfg" instead of "$cfgs":
>                 [ -f $cfg ] || continue
Removing the "s" from that line seems to work, since I do no longer get the message
/usr/lib/pm-utils/functions: line 28: [: /etc/pm/config.d/config: binary operator expected
Also, after the resume I do no longer get the pop-up telling that there's something going wrong
The pop-up is the one linking to http://people.freedesktop.org/~hughsient/quirk/

Moreover now ./quirk.checker responds
                                      Suspend should work!
but actually it does not.

On either
a) pressing Fn+moon
or
b) on executing pm-suspend from the console 1 (Ctrl-Alt F1) as root
the system attempts to suspend, but it resumes immediately after.

After this I get these lines in /var/log/pm-suspend.log

gio gen 10 19:10:20 CET 2008: running suspend hooks.
===== gio gen 10 19:10:20 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/00clear =====
===== gio gen 10 19:10:20 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/05led =====
===== gio gen 10 19:10:20 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
===== gio gen 10 19:10:20 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/20video =====
===== gio gen 10 19:10:20 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/49bluetooth =====
===== gio gen 10 19:10:20 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/50modules =====
===== gio gen 10 19:10:20 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/90clock =====
===== gio gen 10 19:10:22 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/94cpufreq =====
===== gio gen 10 19:10:22 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/95led =====
===== gio gen 10 19:10:22 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/99video =====
gio gen 10 19:10:22 CET 2008: done running suspend hooks.
Machine is unknown.
This machine can be identified by:
    sys_vendor   = "IBM"
    sys_product  = "2511EJG"
    sys_version  = "ThinkPad Z60t"
    bios_version = "77ET60WW (1.20 )"
See http://en.opensuse.org/S2ram for details.

If you report a problem, please include the complete output above.
gio gen 10 19:10:23 CET 2008: running resume hooks.
===== gio gen 10 19:10:23 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/99video =====
===== gio gen 10 19:10:23 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/95led =====
===== gio gen 10 19:10:23 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/94cpufreq =====
===== gio gen 10 19:10:23 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/90clock =====
===== gio gen 10 19:10:24 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/50modules =====
===== gio gen 10 19:10:24 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/49bluetooth =====
===== gio gen 10 19:10:24 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/20video =====
===== gio gen 10 19:10:24 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
===== gio gen 10 19:10:24 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/05led =====
===== gio gen 10 19:10:24 CET 2008: running hook: /usr/lib/pm-utils/sleep.d/00clear =====
gio gen 10 19:10:24 CET 2008: done running resume hooks.

> grep acpid /var/log/syslog
> (Normally the ACPI daemon is the one responsible for handling the
> special keys. It should write in the log which script is called. We
> might then be able to adapt this script to your needs.)

As regards grep acpid /var/log/syslog
if I write the above command, the system is simply responding with the prompt

So it seems that the problem now has shifted to s2ram.
I've been reading http://en.opensuse.org/S2ram many times, but I cannot figure out which could be the solution.

I've tried the following
a) from root in the 1st console: s2ram -f -a 3
   OK. It suspends.
   Pressing the Fn button it resumes back, with no errors, albeit the light of the screen on resuming remain off
   and I have to press Ctrl-Alt-F7 to have the lights on back.
   Other options to s2ram seems not to work, since they are reporting errors.

b) I've added "2511EJG" in
   /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-ibm.fdi
   but nothing changes.

Any further idea ?

PS
Should I report the error "cfgs for cfg" in /usr/lib/pm-utils/functions ?
Where ?  At http://people.freedesktop.org/~hughsient/quirk/,  possibly ?

Regards
8rino

[Florian Kulzer-3]

On Thu, Jan 10, 2008 at 10:54:12 -0800, 8rino wrote:

>
> [...]
> >I think the mistake is in this line:
> >                 [ -f $cfgs ] || continue
> >It should have "$cfg" instead of "$cfgs":
> >                 [ -f $cfg ] || continue
> Removing the "s" from that line seems to work, since I do no longer get the
> message
> /usr/lib/pm-utils/functions: line 28: [: /etc/pm/config.d/config: binary
> operator expected
> Also, after the resume I do no longer get the pop-up telling that there's
> something going wrong
> The pop-up is the one linking to
> http://people.freedesktop.org/~hughsient/quirk/
>
> Moreover now ./quirk.checker responds
>                                       Suspend should work!
> but actually it does not.
>
> On either
> a) pressing Fn+moon
> or
> b) on executing pm-suspend from the console 1 (Ctrl-Alt F1) as root
> the system attempts to suspend, but it resumes immediately after.
>
> After this I get these lines in /var/log/pm-suspend.log

[...]

> gio gen 10 19:10:22 CET 2008: done running suspend hooks.
> Machine is unknown.
> This machine can be identified by:
>     sys_vendor   = "IBM"
>     sys_product  = "2511EJG"
>     sys_version  = "ThinkPad Z60t"
>     bios_version = "77ET60WW (1.20 )"
> See http://en.opensuse.org/S2ram for details.
>
> If you report a problem, please include the complete output above.
> gio gen 10 19:10:23 CET 2008: running resume hooks.

[...]

> So it seems that the problem now has shifted to s2ram.
> I've been reading http://en.opensuse.org/S2ram many times, but I cannot
> figure out which could be the solution.
>
> I've tried the following
> a) from root in the 1st console: s2ram -f -a 3
>    OK. It suspends.
>    Pressing the Fn button it resumes back, with no errors, albeit the light
> of the screen on resuming remain off
>    and I have to press Ctrl-Alt-F7 to have the lights on back.
>    Other options to s2ram seems not to work, since they are reporting
> errors.
>
> b) I've added "2511EJG" in
>    /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-ibm.fdi
>    but nothing changes.
>
> Any further idea ?

I would try to edit the file /usr/lib/pm-utils/defaults. It has this
line:

# S2RAM_OPTS=""

I would change that to

S2RAM_OPTS="-f -a 3"

and try again. (It is important that you remove the "#" at the beginning
of the line, otherwise it remains commented out.)

> PS
> Should I report the error "cfgs for cfg" in /usr/lib/pm-utils/functions ?
> Where ?  At http://people.freedesktop.org/~hughsient/quirk/,  possibly ?

You can report it on the Debian bugs tracking system. The maintainer of
the pm-utils package will forward the information to the upstream author
if necessary. However, you should first make sure that this is really a
new bug:

http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pm-utils

--
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[8rino]

Florian Kulzer-3 wrote:
 
> On Thu, Jan 10, 2008 at 10:54:12 -0800, 8rino wrote:
>>
>> [...]
>> >I think the mistake is in this line:
>> >                 [ -f $cfgs ] || continue
>> >It should have "$cfg" instead of "$cfgs":
>> >                 [ -f $cfg ] || continue
You were right. It is already been fixed and patched
> [...]
 
>> I've tried the following
>> a) from root in the 1st console: s2ram -f -a 3
>>    OK. It suspends.
>>    Pressing the Fn button it resumes back, with no errors, albeit the
>> light
>> of the screen on resuming remain off
>>    and I have to press Ctrl-Alt-F7 to have the lights on back.
>>    Other options to s2ram seems not to work, since they are reporting
>> errors.
>>
>> b) I've added "2511EJG" in
>>    /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-ibm.fdi
>>    but nothing changes.
>>
>> Any further idea ?
>
> I would try to edit the file /usr/lib/pm-utils/defaults. It has this
> line:
>
> # S2RAM_OPTS=""
>
> I would change that to
>
> S2RAM_OPTS="-f -a 3"
I forgot to tell you that I already tried this, but in /etc/pm/config.d/config as somewhere I've read that
the lines in config override the ones in defaults.
Nevertheless another patch was necessary in /usr/lib/pm-utils/bin/pm-action,
since the option --S3-bios* did not allowed other options to be passed to s2ram.
It was a matter of a "+" missing on one line in pm-action.
It is reported in the page you gave me.
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pm-utils
 I had to change the lines

 if [ -n "$ACPI_SLEEP" ]; then
        S2RAM_OPTS=" --acpi_sleep $ACPI_SLEEP"
 fi
 
 if [ -n "$S2RAM_OPTS" ]; then

into

 if [ -n "$ACPI_SLEEP" ]; then
        S2RAM_OPTS+=" --acpi_sleep $ACPI_SLEEP"
 fi
 
 if [ -n "$S2RAM_OPTS" ]; then

Now everything is working properly.
Thanks "A LOT", Dr Kulzer.