documentation about what privileges are required to get cpufreq/suspend work

View: New views
3 Messages — Rating Filter:   Alert me  

documentation about what privileges are required to get cpufreq/suspend work

by Benoît Dejean-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

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).

With 2.22, everything used to work fine:
- cpufreq scaling on AC, switching to power save on battery
- suspend to RAM.

All i remember is adding myself to the powerdev group + a few patches to
uswusp and i was good.

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), i
can't find any documentation on gnome-power-manager about what is needed
for a user in order to get cpufreq and suspend work.

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 :)

Anyone please point me to something about how to get things back.
Thanks.

(The debian bug i've opened
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528596 )
--
Benoît Dejean
GNOME http://www.gnomefr.org/
LibGTop http://directory.fsf.org/libgtop.html


_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

signature.asc (204 bytes) Download Attachment

Re: documentation about what privileges are required to get cpufreq/suspend work

by Richard Hughes-6 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2009/5/17 Benoît Dejean <benoit@...>:
> 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.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: documentation about what privileges are required to get cpufreq/suspend work

by Benoît Dejean-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Le dimanche 17 mai 2009 à 13:05 +0100, Richard Hughes a écrit :
> 2009/5/17 Benoît Dejean <benoit@...>:

(oops forgot to CC)

> 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.

I don't get any error, i'd like to know what makes me privileged enough
to be able to call s2ram/pm-suspend through gpm while i can't do it from
a terminal.

> > 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
OK, so all these gconf keys are dead.

Unfortunately, ondemand/conservative is not available on linux/ppc, so
this is a regression for me, this means that i have to get back to
cpufreqd/powernowd.

Anyway, are ondemand/conservative aware of battery/AC ? Or do you think
that powersave/sticking to the lowest freq is useless ?

Thanks.
--
Benoît Dejean
GNOME http://www.gnomefr.org/
LibGTop http://directory.fsf.org/libgtop.html


_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

signature.asc (204 bytes) Download Attachment