Re: [gpm] documentation about what privileges are required to get cpufreq/suspend work
- From: Richard Hughes <hughsient gmail com>
- To: Benoît Dejean <benoit placenet org>
- Cc: gnome-power-manager-list gnome org
- Subject: Re: [gpm] documentation about what privileges are required to get cpufreq/suspend work
- Date: Sun, 17 May 2009 13:05:44 +0100
2009/5/17 Benoît Dejean <benoit placenet org>:
> I'm on Debian/SID. I used to be happy with gpm 2.22 and debian has
> upgraded to 2.24 (quite old i know).
Very old...
> Now with 2.24, looks like the entire privileges stack has move to
> polkit, and i have no idea how it works (i don't really want to know),
Quite a few other components of GNOME have switched to PolicyKit too.
> can't find any documentation on gnome-power-manager about what is needed
> for a user in order to get cpufreq and suspend work.
It depends. What error are you getting? Debian does some things
different to upstream, so it's quite likely there might be debian
specific tweaks too.
> Surprisingly, suspend to ram still works through gpm but i have no idea
> why. But cpufreq is totally broken, nothing work anymore, back to
> cpufreq-selector :)
We've removed all the cpufreq stuff in newer versions. The ondemand
governor is sufficient now that it can be used on AC and on battery,
and there only exist a very few embedded and specialist targets that
ever need to specify performance. I've written loads about this
before, but mjg put it much better. Read
http://www.codon.org.uk/~mjg59/power/good_practices.html
Thanks,
Richard.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]