[ltp] FN+F4 & APMD?
Mon, 22 Dec 2003 20:30:35 +0100
> Works fine out of the box here. T23, Debian sid, 2.4.21.
> Do you see any apmd messages in the syslog? I assume you have APM
> compiled into the kernel/loaded as a module. I'm not sure what to look
> for -- I have apmd running with the following arguments
Yes, APM support is in kernel, apmd is running, apm gives messages to
syslog only when suspending with the apm utility, but not when pressing
Fn+F4 or using tpctl.
> lsof shows that apmd has /dev/apm_bios opened (for read and write
> access). When I press Fn+F4, here's what I get in syslog:
> Oct 7 13:16:55 perlas apmd: apmd_call_proxy: Executing proxy: '/etc/apm/apmd_proxy' 'suspend' 'system'
> Oct 7 13:16:56 perlas apmd: apmd_call_proxy: + Unmounting remote filesystems.
> Oct 7 13:16:57 perlas apmd: apmd_call_proxy: + kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec] run-parts: /etc/apm/event.d/alsa exited with return code 1
You get that on pressing Fn+F4? Strange...
...from what i found out now, my problem was that i had AC power online
AND a pcmcia card in use.
I found several sources which tell the same story:
When using apm --suspend, apm signals to apmd which calls apmd_proxy and
after that finishes calls kernel apm to suspend.
When using Fn+F4 or tpctl -Z apmd shouldn't even be called, because both
signal the bios directly which acts before apmd has a chance to react at
The problem on my side was now that the bios for some reason rejects a
suspend, when both a pcmcia card and AC power are in place.
I wonder that apmd reacts on the Fn+F4 press on your machine.?.
> The last one results from a bug in /etc/apm/event.d/alsa script.
> Oct 7 13:16:57 perlas apmd: System Suspend
> Marius Gedminas