kde guidance does not display cpu frequency

[sk0rp10]

Binary package hint: kde-guidance-powermanager

Distribution: Feisty (current)

Package: Kde-guidance-powermanager

Kde-guidance powermanager wrongly displays 0 frequency for my Intel Core Duo CPU,
while /proc/cpuinfo reports :

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2400 @ 1.83GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr
bogomips : 3660.88
clflush size : 64

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2400 @ 1.83GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr
bogomips : 3657.07
clflush size : 64

[Gianluca Varisco (gvarisco)]

I can confirm the problem (Centrino - 1.73 GHz). /proc/cpuinfo reports:

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.73GHz
stepping : 8
cpu MHz : 1729.169
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe est tm2
bogomips : 3461.51
clflush size : 64

[quickgun (quikgun)]

I can also confirm this.

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.86GHz
stepping : 8
cpu MHz : 1862.051
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx est tm2
bogomips : 3726.33
clflush size : 64

[tomasz2006 (karzelek)]

Hi,

I have performed the upgrade to Feisty today and I think I have the same problem as above.

Also, I am not sure whether this is related (sorry), but I cannot see the options to change the CPU frequency scaling in the GUI dialog (see screenshot attached). In my BIOS I have the `stepping' option on: automatic (as opposed to disabled).

Output from cat /proc/cpuinfo:

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.86GHz
stepping : 8
cpu MHz : 798.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up est tm2
bogomips : 1598.11
clflush size : 64

[tomasz2006 (karzelek)]

Hi,

I have an update - I have reinstalled edgy from the CD and then did a distr upgrade and the bug disappeared. My non-it-guy observation it could be something to do with packages: powersaved and powernowd. In my initial isntallation I had installed powersaved and package powernowd was missing. Now it is the other way round - I have only powernowd installed. I enclose a screenshot as a proof:-) Output from cat /proc/cpuinfo is the same as above.

[Gianluca Varisco (gvarisco)]

I can confirm what tomasz2006 said above: I removed "powersaved" and re-installed "powernowd", so kde-guidance now works correctly. Probably it would be better to flag 'powernowd' mandatory dependency of "kde-guidance"?

[Sebastian Kügler (sebasje)]

On Monday 23 April 2007 22:23:17 Gianluca Varisco wrote:
> I can confirm what tomasz2006 said above: I removed "powersaved" and re-
> installed "powernowd", so kde-guidance now works correctly. Probably it
> would be better to flag 'powernowd' mandatory dependency of "kde-
> guidance"?

Does it also work without powernowd? (It should, at least if HAL isn't doing
strange things.)
--
sebas

[quickgun (quikgun)]

On 4/24/07, sebas <email address hidden> wrote:
>
> On Monday 23 April 2007 22:23:17 Gianluca Varisco wrote:
> > I can confirm what tomasz2006 said above: I removed "powersaved" and re-
> > installed "powernowd", so kde-guidance now works correctly. Probably it
> > would be better to flag 'powernowd' mandatory dependency of "kde-
> > guidance"?
>
> Does it also work without powernowd? (It should, at least if HAL isn't
> doing
> strange things.)
> --
> sebas
>
> --
> kde guidance does not display cpu frequency
> https://bugs.launchpad.net/bugs/102345
> You received this bug notification because you are a direct subscriber
> of the bug.
>

None of that works for me. All cpufreq modules are loaded. I don't think
you should need powersaved or powernowd. guidance-powermanager I thought,
was designed to replace them using just dbus calls to HAL.

--
Mark Merriken

[Sebastian Kügler (sebasje)]

On Tuesday 24 April 2007 16:26:56 quickgun wrote:
> None of that works for me.  All cpufreq modules are loaded.  I don't think
> you should need powersaved or powernowd.  guidance-powermanager I thought,
> was designed to replace them using just dbus calls to HAL.

This is a bit unclear to me, could you explain which scenario's do work, and
which don't? That'd give me a better basis to test it.
--
sebas

[quickgun (quikgun)]

With powersaved running - doesn't work.
With powernowd running - doesn't work.
With neither - doesn't work.

On 4/24/07, sebas <email address hidden> wrote:
>
> On Tuesday 24 April 2007 16:26:56 quickgun wrote:
> > None of that works for me. All cpufreq modules are loaded. I don't think
> > you should need powersaved or powernowd. guidance-powermanager I
> thought,
> > was designed to replace them using just dbus calls to HAL.
>
> This is a bit unclear to me, could you explain which scenario's do work,
> and
> which don't? That'd give me a better basis to test it.
> --
> sebas
>
> --
> kde guidance does not display cpu frequency
> https://bugs.launchpad.net/bugs/102345
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Mark Merriken

[jperl (johannes-perl)]

i can confirm for my laptop what quickgun said.
-> deinstalled powersaved
-> installed powernowd
-> reboot
and it worked for my Intel(R) Pentium(R) M processor 1.86GHz

[Luka Renko (lure)]

Can you provide output of the following commands:

  cat /sys/devices/system/cpu/*/cpufreq/scaling_*
  cat /var/lib/acpi-support/*-*

[sk0rp10 (matteo-andreozzi)]

cat /sys/devices/system/cpu/*/cpufreq/scaling_*

Output:

1833000 1333000 1000000
ondemand userspace powersave performance
1833000
acpi-cpufreq
ondemand
1833000
1000000
1833000 1333000 1000000
ondemand userspace powersave performance
1000000
acpi-cpufreq
ondemand
1833000
1000000

cat /var/lib/acpi-support/*-*

OUTPUT:

R0074J3
Sony Corporation
VGN-FE11S
C3LLYUFR

[Luka Renko (lure)]

Can you also provide output of:

  ls -l /sys/devices/system/cpu

[sk0rp10 (matteo-andreozzi)]

ls -l /sys/devices/system/cpu

OUTPUT:

totale 0
drwxr-xr-x 5 root root 0 2007-05-04 18:01 cpu0
drwxr-xr-x 5 root root 0 2007-05-04 18:01 cpu1
-rw-r--r-- 1 root root 4096 2007-05-04 18:08 sched_mc_power_savings

[Mark Thompson (mjthfx)]

This also effects me.... my system is a dell d620 with dual core intel, yet my colleague is running same laptop with same os and config Kubuntu 7.04 and his power management reports cpu ok.

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2300 @ 1.66GHz
stepping : 8
cpu MHz : 1664.531
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor est tm2 xtpr
bogomips : 3332.32
clflush size : 64

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2300 @ 1.66GHz
stepping : 8
cpu MHz : 1664.531
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor est tm2 xtpr
bogomips : 3329.04
clflush size : 64

~$ ls -l /sys/devices/system/cpu
total 0
drwxr-xr-x 4 root root 0 2007-05-11 12:32 cpu0
drwxr-xr-x 4 root root 0 2007-05-11 12:32 cpu1
-rw-r--r-- 1 root root 4096 2007-05-11 12:33 sched_mc_power_savings

[Gene (gbarrier)]

I have also experienced this problem. I have a Gateway MX7118, AMD64 Mobile Athlon and using Kubuntu 7.04 installed from CD. My CPU freq. was reported OK until yesterday, when I did a system upgrade. I did the same as the others, removed "powersaved" and reinstalled "powernowd", and now it works again.

cat /sys/devices/system/cpu/*/cpufreq/scaling_*

2200000 2000000 1800000 1600000 800000
userspace powersave conservative ondemand performance
800000
powernow-k8
ondemand
2200000
800000

cat /proc/cpuinfo

processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 36
model name : Mobile AMD Athlon(tm) 64 Processor 3400+
stepping : 2
cpu MHz : 800.000
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up pni lahf_lm ts fid vid ttp tm stc
bogomips : 1593.56
clflush size : 64

ls -l /sys/devices/system/cpu

total 0
drwxr-xr-x 5 root root 0 2007-05-29 10:43 cpu0

cat /var/lib/acpi-support/*-*

65.08.00
Gateway
MX7118
0100

[Fernando Díaz (fernio)]

It seems to me that this bug is a duplicate of bug #89750.

[sk0rp10 (matteo-andreozzi)]

Yes this is a duplicate, you can close

[Mark Thompson (mjthfx)]

How do you restart hal ? and the applet?

[Luis Alberto Pabón (copong)]

sudo /etc/dbus-1/event.d/20hal restart

for the applet, just right click > quit, then KMenu > run command >
guidance-power-manager

for a permanent workaround that will spare you all this mess, edit as root
/etc/rc.local and add this to the bottom of the script:
/etc/dbus-1/event.d/20hal restart

Last line on rc.local must always be exit 0 afaik

On 25/07/07, Mark Thompson <email address hidden> wrote:
>
> How do you restart hal ? and the applet?
>
> --
> kde guidance does not display cpu frequency
> https://bugs.launchpad.net/bugs/102345
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Luis Pabón

[Roman Shtylman (shtylman)]

I tried restarting both hal and the applet and it did not work. Are there plans to fix this? or should I just be getting the source code and looking at it myself?

[Sebastian Kügler (sebasje)]

First make sure that HAL reports the right values in the first place. lshal
|grep -i gives me the following information (working system):

  info.addons = {'hald-addon-cpufreq', 'hald-addon-acpi'} (string list)
  info.capabilities = {'cpufreq_control'} (string list)
  info.interfaces = {'org.freedesktop.Hal.Device.SystemPowerManagement', 'org.freedesktop.Hal.Device.CPUFreq'} (string list)
udi = '/org/freedesktop/Hal/devices/acpi_CPU0'
  info.product = 'Genuine Intel(R) CPU T2400 @ 1.83GHz' (string)
  info.udi = '/org/freedesktop/Hal/devices/acpi_CPU0' (string)
  linux.acpi_path = '/proc/acpi/processor/CPU0' (string)
udi = '/org/freedesktop/Hal/devices/acpi_CPU1'
  info.product = 'Genuine Intel(R) CPU T2400 @ 1.83GHz' (string)
  info.udi = '/org/freedesktop/Hal/devices/acpi_CPU1' (string)
  linux.acpi_path = '/proc/acpi/processor/CPU1' (string)

If that looks good on your system, add some debugging to powermanage.py and see where it goes wrong. The methods getCpu*() are probably the most interesting for you. If lshal output looks different to you, complain to HAL people.

[Sebastian Kügler (sebasje)]

Gnarrrr. Launchpad mangles my command. You want "lshal (pipe) grep -i cpu"

[getriebesand (getriebesand)]

I have upgraded my Edgy to Feisty and the upgrade tool is crashed at the end. Power Manager shows 0 MHz and Adept says powernowd and powersaved are not installed but in /etc/init.d the startup scripts exists and also in rc2.d

The workaround to restart hal with rc.local works fine.

Than I have installed powernowd and powersaved and purged they again.
Than the work around doesnt' work anymore. (because powernowd is not installed)
I have reinstalled powernowd, removed the work around in rc.local and all works fine.

I think powernowd was not upgraded or something goes wrong during the upgrade process.

[Luis Alberto Pabón (copong)]

Works for me in Gutsy without the rc.local workaround.

[Pascal d'Hermilly (pascal-tipisoft)]

Doesn't work for me in gutsy

[Karmo Rosental (karmux)]

Kubuntu Gutsy 7.10

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 3
cpu MHz : 497.890
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse up
bogomips : 996.76
clflush size : 32

kde-guidance shows that battery is not present and CPU frequency is 0 MHz.
In Feisty, battery and cpu monitoring was fine in kde-guidance.

[Harald Sitter (apachelogger)]

Please try with the KDE 4 version (as used in Intrepid)

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!