Comment 7 for bug 134282

As the thread's initiator did not answer the question of Andreas, I'll take over. I am running hardy KDE desktop on a Dell Latitude D600 with a 1.7Mhz Pentium M. With feisty, suspend to RAM, suspend to disk, and the display of current CPU frequency worked well. After the upgrade to hardy, suspend to RAM and disk did not work any more but the CPU frequency was still displayed correctly. Yesterday I installed kpowersave in addition to kde-guidance-powermanager and, voila, suspend to RAM works again. After that, the CPU frequency was still displayed correctly. Then I decided to play around with the packages recommended by kpowersave, namely pm-utils, powersaved, acpi-tools, and hibernate, hoping to fix suspend to disk as well. I started with powersaved; after requesting its installation in adept_manager and without checking the request's consequences on my installation, adept_manager removed apmd, system-config-printer-kde, hal-cups-utils, hwdb-client-kde, hwdb-client-common, kde-core, kde-hal-device-manager, kdebase, knetworkmanager, network-manager-kde, and network-manager, powernowd, and ubuntu-laptop-mode. I undid this change immediately, but now neither kde-guidance-powermanager nor kpowersave display the CPU frequency. (To be precise, kde-guidance-powermanager always displays 0 Mhz while kpowersave always displays 598 Mhz, even when the CPU is running at full speed.)

Here is the output of hal-device `hal-find-by-capability --capability 'processor'`:

udi = '/org/freedesktop/Hal/devices/acpi_CPU0'
  processor.number = 0 (0x0) (int)
  processor.can_throttle = true (bool)
  info.parent = '/org/freedesktop/Hal/devices/computer' (string)
  info.product = 'Intel(R) Pentium(R) M processor 1.70GHz' (string)
  info.udi = '/org/freedesktop/Hal/devices/acpi_CPU0' (string)
  linux.hotplug_type = 4 (0x4) (int)
  info.category = 'processor' (string)
  info.capabilities = { 'processor' } (string list)
  linux.acpi_path = '/proc/acpi/processor/CPU0' (string)
  linux.acpi_type = 1 (0x1) (int)