I am running Debian testing (lenny) amd64+32 bit chroot with kernel 2.6.27.6 (2.6.26 does not support the wireless card properly). Acpid does not react on the lid closure, neither does kpowersave. What is really weird is that no error messages can be found in the logs.
echo mem > /sys/power/state works;
suspend to ram invoked by kpowersave works, but the laptop does not wake up afterwards (and again, no error messages in the logs).

This part was working with Fedora 10-Beta.

CPU: CORE 2 DUO T5800
Graphics: Intel MEDIA ACCEL 4500MHD

Any suggestions will be greatly appreciated.

Hi!

You have to:
* install acpid package
* install pm-utils package
* install powersaved package
* edit "/etc/powersave/events" and in the line
EVENT_BUTTON_LID_CLOSED="ignore"
replace "ignore" with "suspend_to_ram"
* then restart powersaved (issue "/etc/init.d/powersaved restart" as root)
* install the guidance power manager (present as "kde-guidance-powermanager" package)
* start guidance-power-manager
* left-click on the newly appeared button in the icon-bar, and in the window that appear, set "When laptop Lid Closed" to "Suspend"
* then simply close your lid.
* enjoy

Take care: if the computer doesn't suspend/resume correctly, change in the "/usr/lib/pm-utils/defaults" the line "#SLEEP_MODULE="kernel" " to "SLEEP_MODULE="uswsusp" ". Then restart computer, and close the lid.

Mate

Thank you very much. I tried all this, but the effect is still the same: when I close the lid, nothing happens. If I use "suspend" option from the menu which appears on right-clicking the powersave button at the icon-bar, the laptop suspends, but does not wake up (on pressing the power button; since there aren't any traces of what happens in the logs, I would assume that the hard drive does not start).

I had exactly the same behaviour with kpowersave (including the fact that it fails to resume after a manual suspend from the menu). Strangely,
echo mem >/sys/power/state (or acpitool -s, which I suspect does the same thing) suspends the laptop, and it can be resumed afterwards. I would settle for this for now and wait for a new kernel or something. However, since I am not the main user of this laptop, I need to find a very simple (one click, in the worst case) solution.

I'm having the same problems with the addition of not being able to suspend to disk with kpowersave. I am running Debian lenny as well with kernel 2.6.26-1. If I use the echo commands like you, echo disk > /sys/power/state or echo mem > /sys/power/state, things seem to work fine.

It seems there is something with the scripts that kpowersave uses along with the s2disk, s2ram or s2both that don't work right with my Toshiba.

It seems to go through part of the process to suspend, but then quickly reverts the process and takes me back to my session. If by chance it did suspend to RAM, 9 times out of 10 it would not resume.

Some digging that I did into the scripts it runs showed that it uses s2disk, s2ram and s2both. The following is an output from s2ram --test on my machine.

Machine unknown
This machine can be identified by:
sys_vendor = "TOSHIBA"
sys_product = "Satellite P100"
sys_version = "PSPADC-MA605C"
bios_version = "V4.40 "

I know this doesn't get things running again, but might help if further diagnosing the issue.

Finally, I got it working on the Satellite U400-10I (BIOS updated using isoimage by BIOS updated tool). I am using Ubuntu Intrepid. I tried and didn't work with:
* kpowersave with pm-utils set to "kernel" (suspend hanged)
* kpowersave with pm-utils set to "uswsusp" (suspend hanged)
* echo mem > /sys/power/blahblah (suspend hanged)
* s2disk (hibernate hanged)
* s2ram doesn't exist on Intrepid (what a pain!), so couldn't test
* acpitool -s (suspend hanged)

Finally, gnome-power-manager did the job, without so much as a touch! (I had to configure it to suspend instead of hibernate, though, through gnome-power-preferences). Hibernation also works through the grome-power-manager. I configured the *-manager through the *-preferences to show the icon in the system tray, I think that is very useful.

I am a happy user now (now only if the U400 didn't have that problem with the rtl8187 module because of the rtl8187B wireless chipset)

Glad to hear you got it working.

Unfortunately it doesn't seem to work on my machine. It gets to the point of freezing user space processes, then pauses for a moment then rips through some commands and goes back to my desktop.

Guess I'll have to keep digging.

I wrote a simple script that tests the state of lid (using /proc/acpi/button.....) Well, it does show when the lid is closed! Yet guidance-power-manager, kpowersave, gnome-power-save, acpid etc. do nothing
when the lid is closed. I now installed Fedora 10, nothing new.