© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
Resumé:
************
Remove totally and reinstall
-------
After having experimentet around with tips on some of the links mentioned here, I decided to remove almost everything connected to hibernation and sleep functions, because, clearly, it was the upgrade that broke it.
I ran:
sudo apt-get remove --purge powersaved, kpowersave, acpi*, klaptopdeamon kde-guidance
As expected, suspend to RAM (Fn+F4) and to disk (Fn+F12) does not work anymore (no reaction).
I then installed just the acpi part:
sudo apt-get install acpid acpitools acpi-support kde-guidance
and found, that the scripts installed by acpi-support in /etc/acpi actually worked, but the Fn+F4 and Fn+F12 still don't give anything.
To be exact: hibernation.sh worked as is, but sleep.sh had to be altered and xorg.conf, as described in: http://
I also changed /etc/default/
tpb or kmilo (both will work) actually got most of the other keys to work (but not the Access IBM button--se the mentioned thinkwiki.org pages there are many, linked together in one complex).
Klaptopdaemon
-------------
I then reinstalled the klaptopdaemon, and the keys still does not work, but I can monitor my battery power.
And from the Klaptop menu (a battery icon in the panel) I can choose Suspend to disk and suspend to RAM. This is what happens:
Suspend to RAM: It locks the screen and I am not able to log in again, no matter what password I give it tells me it is wrong. I have tried resetting the password to just "q", but it still don't work. I don't know where this bug resides. Alt+Ctrl+Delete works, though, so I can log in again. Better than starting all over.
Suspend to disk: Same as above.
Kpowersave
----------
Then I tried just powersaved, but it gives the described weird behavior, so I think this package is broken concerning these machines (all or most IBM Thinkpads probably). This is what happens:
Suspend to disk: Logges me out, when I am back, it is as if I had just restarted the machine. It seems it gives me GUI and then throws me out again because the process is similar to the one being performed by hibernation.sh (see above), except this time it don't work
Suspend to RAM: Freezes totally, I can't even use Alt+Ctrl+Escape to restart, I have to use the power button.
Kpowersaved gives the exact same result (as expected since it uses powersaved as its basis).
I still have not tried the manual method of defining keycodes etc. But the thinkwiki-pages (http://