Bug#452909: hal: there is big regressions about the pmu support
Package: hal
Version: 0.5.10-2
Severity: normal
Due to the last upload of hal, there is regression in the support of pmu.
None of them seems complicated to fix as I was able to find workarounds
without prior knowledge of hal and dbus stuff..
The symptom was that I was no longer able to suspend to ram using kpowersave.
I used qdbusviewer to interacts with hald and also executed hals in a console.
I found that /usr/lib/hal/hal-system-power-pm-is-supported reports to hal that
my computer cannot suspend to ram. This is wrong. Since the regression, I was
able to suspend my computer using:
/usr/lib/hal/hal-system-power-pmu sleep
I believe that /usr/lib/hal/hal-system-power-pm-is-supported should be fixed to
at least say yes when an hal helper is able to do the job.
So I have added:
dbus-send --system --type=method_call --print-reply --dest=org.freedesktop.Hal \
/org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SetPropertyBoolean \
string:'power_management.can_suspend' boolean:true
dbus-send --system --type=method_call --print-reply --dest=org.freedesktop.Hal \
/org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SetPropertyBoolean \
string:'power_management.can_suspend_to_ram' boolean:true
to my /etc/rc.local to enforce hal to believe that my computer can suspend to ram.
Now kpowersave offers the command. Yeah !!!
Second problem, /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux is not
able to suspend to ram my computer. There the problem is that hal apparently only
supports pm-utils. Again, adding those some lines solved the problem:
if [ $HAL_PROP_POWER_MANAGEMENT_TYPE == "pmu" ] ; then
if [ -x "/usr/lib/hal/hal-system-power-pmu" ] ; then
/usr/lib/hal/hal-system-power-pmu sleep
RET=$?
else
unsupported
fi
else
[...]
fi
My computer is an iBook G4 with those informations:
cat /proc/cpuinfo
processor : 0
cpu : 7447A, altivec supported
clock : 666.666000MHz
revision : 0.2 (pvr 8003 0102)
bogomips : 36.73
timebase : 18432000
platform : PowerMac
machine : PowerBook6,5
motherboard : PowerBook6,5 MacRISC3 Power Macintosh
detected as : 287 (iBook G4)
pmac flags : 0000001b
L2 cache : 512K unified
pmac-generation : NewWorld
So I submit this report to debian as I know that other debian users have the
problem. I do not really have time to forward it to hal bug tracking system,
even if I think that the regression is theirs. Do not hesitate to ask for more
informations.
So, I do not know what you can do, but it had to be reported.
Thanks for your work on hal.
Thanks in advance for your attention.
Best regards
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'testing'), (2, 'stable'), (1, 'experimental')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.22-2-powerpc
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages hal depends on:
ii adduser 3.105 add and remove users and groups
ii dbus 1.1.1-3 simple interprocess messaging syst
ii hal-info 20071030-1 Hardware Abstraction Layer - fdi f
ii libc6 2.6.1-6 GNU C Library: Shared libraries
ii libdbus-1-3 1.1.1-3 simple interprocess messaging syst
ii libdbus-glib-1-2 0.74-1 simple interprocess messaging syst
ii libexpat1 1.95.8-4 XML parsing C library - runtime li
ii libglib2.0-0 2.14.3-1 The GLib library of C routines
ii libhal-storage1 0.5.10-2 Hardware Abstraction Layer - share
ii libhal1 0.5.10-2 Hardware Abstraction Layer - share
ii libusb-0.1-4 2:0.1.12-7 userspace USB programming library
ii libvolume-id0 0.114-2 libvolume_id shared library
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii mount 2.13-10 Tools for mounting and manipulatin
ii pciutils 1:2.2.4-1.1 Linux PCI Utilities
ii pm-utils 0.99.2-3 utilities and scripts for power ma
ii udev 0.114-2 /dev/ and hotplug management daemo
ii usbutils 0.73-4 Linux USB utilities
Versions of packages hal recommends:
ii eject 2.1.5-6 ejects CDs and operates CD-Changer
-- no debconf information
Reply to: