Powerdevil: No Frequency scaling + no suspend (4.2 packages from current)

frandalla · 01-29-2009, 10:29 AM

I've switched to 4.2 and now we have Powerdevil and it's controls related to cpu frequency scaling and others. The problem is: My pc is listed as having no cpu frequency scaling capability but in fact I do! I can change the frequency using changing the scaling governor with a simple:

Code:

echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

What powerdevil is checking to see if I have frequency scaling capability?

Apart from that I have suspend working currently with "s2ram -f" command.
Closing the lid and clicking "suspend" worked fine in KDE3 but now I just can't seem to get it work and I just don't know what else to check anymore.

allend · 01-29-2009, 07:20 PM

Some things to check.
1. Are you a member of the 'power' group?
2. With suspend on my laptop, I am using pm-utils to handle the lid switch. Within KDE4, I have the suspend settings set to take no action, so that pm-utils is used instead. This allows suspend to work from within other window managers. I have found that suspend will not resume correctly with this setup unless I disable the lock screen on suspend option in KDE4.

I cannot help on the frequency scaling as my processor does not support this.

grissiom · 01-29-2009, 09:02 PM

IMHO, scaling governor is one thing, cpu frequency is an other. Could you please run

Code:

$cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

and post the output?

frandalla · 01-29-2009, 09:34 PM

grissiom: Here's the ouput:

Code:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1600000 800000

They might be different things but as far as I dealt with this, the only way to change the frequency is by checking the scaling governor. Any ideas?

Allend: No I was not part of it! gonna check if it works right now and I'll reply back!
EDIT: It worked! Suspending now works fine. My last problem is Cpu frequency scaling.

grissiom · 01-30-2009, 12:14 AM

As far as I know, the governor scale the frequency after some algorithm. Your post noticed my that I have the same problem on my box... ;( What kernel are you using? I'm using a self-compiled git version, so my case may not be so general. If you are using the kernel shipped with slackware, we may find a bug here

frandalla · 02-01-2009, 05:01 PM

I think I'm gonna test that then. I'm using 2.6.28.2 (self-compiled) here but I still have the old ones here. Keep you posted about any results

Aivurn · 02-06-2009, 05:43 PM

Quote:

Originally Posted by frandalla

I think I'm gonna test that then. I'm using 2.6.28.2 (self-compiled) here but I still have the old ones here. Keep you posted about any results

I have the same problem with self compiled kernel. It worked earlier, when I was Using KDE 3.5.x. The governors are compiled into the kernel, not as modules, maybe that's the problem, but why then "ondemand" governor works with Powertop? It's a Core Duo based system.

rworkman · 02-06-2009, 11:04 PM

I'm not sure about *all* of this, as testing is still ongoing, but I think some of the governor settings might be related to hal's dbus config file settings. If you want to find out, put the contents below into /etc/dbus-1/system.d/hal.conf (back up the original first):

http://slackware.com/~rworkman/hal.conf.txt

Code:

edit: removed in favor of the link above

Feedback on this is welcome, of course. I'm mostly sure that these are sane/secure defaults, but as always, I'm not perfect and thus may be wrong.

grissiom · 02-08-2009, 07:19 PM

The hal.conf doesn't work either... The governors is complied as modules now. Maybe there is something else I should to configure...

rworkman · 02-08-2009, 07:41 PM

You might consider updating your dbus package to 1.2.12 -- that version logs any dbus errors to /var/log/messages, so it should help with troubleshooting (assuming the problem is dbus related). (url redacted) has a build script if you're interested.

EDIT: I removed the url, as it's no longer valid. If you need to build it on 12.2, use the build script from -current.

nuxrl · 02-08-2009, 07:50 PM

Is acpi-cpufreq module loaded or included in the kernel? If pm-utils is used, acpi-cpufreq is needed for cpu scaling to work.

grissiom · 02-09-2009, 12:04 AM

Quote:

Originally Posted by rworkman

You might consider updating your dbus package to 1.2.12 -- that version logs any dbus errors to /var/log/messages, so it should help with troubleshooting (assuming the problem is dbus related). http://slackware.com/~rworkman/dbus/ has a build script if you're interested.

After upgrading dbus to 1.2.12, I got nearly 200 error messages in /var/log/messages:

Code:

Feb  9 13:53:34 localhost dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=       500 pid=1673 comm="/usr/bin/plasma ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="       (unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1403 comm="/usr/sbin/hald --daemon=yes "))

After upgradepkg, I have run "slackpkg --new-config" to over write all the configs. I don't know whether the error is related to this topic...

grissiom · 02-09-2009, 12:05 AM

Quote:

Originally Posted by nuxrl

Is acpi-cpufreq module loaded or included in the kernel? If pm-utils is used, acpi-cpufreq is needed for cpu scaling to work.

Yes, acpi-cpufreq is compiled into the kernel.

rworkman · 02-09-2009, 12:40 AM

Quote:

Originally Posted by grissiom

After upgrading dbus to 1.2.12, I got nearly 200 error messages in /var/log/messages:

Code:

Feb  9 13:53:34 localhost dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=       500 pid=1673 comm="/usr/bin/plasma ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="       (unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1403 comm="/usr/sbin/hald --daemon=yes "))

After upgradepkg, I have run "slackpkg --new-config" to over write all the configs. I don't know whether the error is related to this topic...

Add this to hal.conf:

Code:

edit: removed in favor of the linked hal.conf

grissiom · 02-09-2009, 06:15 AM

Thanks rworkman, I think we may get a step closer to the problem:

Code:

Feb  9 20:09:08 localhost dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=500 pid=1824 comm="kded4 ") interface="org.freedesktop.Hal.Device.LaptopPanel" member="SetBrightness" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1443 comm="/usr/sbin/hald --daemon=yes "))
Feb  9 20:09:08 localhost dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=500 pid=1824 comm="kded4 ") interface="org.freedesktop.Hal.Device.SystemPowerManagement" member="SetPowerSave" error name="(unset)"requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1443 comm="/usr/sbin/hald --daemon=yes "))
Feb  9 20:09:31 localhost dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=500 pid=1824 comm="kded4 ") interface="org.freedesktop.Hal.Device.CPUFreq" member="GetCPUFreqAvailableGovernors" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1443 comm="/usr/sbin/hald --daemon=yes "))
Feb  9 20:09:33 localhost dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=500 pid=1824 comm="kded4 ") interface="org.freedesktop.Hal.Device.CPUFreq" member="GetCPUFreqAvailableGovernors" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1443 comm="/usr/sbin/hald --daemon=yes "))
Feb  9 20:09:33 localhost dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=500 pid=1824 comm="kded4 ") interface="org.freedesktop.Hal.Device.CPUFreq" member="GetCPUFreqAvailableGovernors" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1443 comm="/usr/sbin/hald --daemon=yes "))