Le dimanche 17 mai 2009 à 13:05 +0100, Richard Hughes a écrit : > 2009/5/17 Benoît Dejean <benoit placenet org>: (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
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=