Though I disabled cpufreq service at boot time through MCC, cpu frequency is still less than half the maximum frequency on processor 1 : cat /proc/cpuinfo|grep 'cpu MHz' shows : cpu MHz : 1800.000 (processor 0) cpu MHz : 800.000 (processor 1)
CC: (none) => denis.prost
please provide the result of: cat /sys/devices/system/cpu/cpu?/cpufreq/scaling_governor If you really want your cpus/cores to run at maximum speed all the time you need to change all those settings (2 of them) to performance You can also have them set to ondemand in order to have automatic cpu frequency switching without a daemon.
CC: (none) => cjw
Hi, and thanks for paying attention to my report. Output to "cat /sys/devices/system/cpu/cpu?/cpufreq/scaling_governor" : ondemand ondemand I'll change both of them to "performance" to get what I want (tried several times ondemand but it terribly slows down my computer, whereas one would expect it to save energy while making no sensible change to computer performance). Since Mageia philosophy, as I understand it, is like Mandriva one - make everything configurable through GUI, which is necessary to bring Linux to beginners - it would be nice if cpufreq policy could be chosen through a GUI. I know it is possible with KDE 4, but there are also GNOME users - to which I belong - and gnome-power-manager does not offer such a feature. Regards, Denis
So ondemand doesn't work well - but what happens with cpufreqd? You could try to install powernowd instead. Now I'm starting to wonder what kind of CPU you have (: About a GUI - I think it's supposed to work automatically already. It seems that the only reason you want to change something is that it doesn't work correctly. So the proper solution will be to make sure it works out-of-the box for everyone. On the other hand, switching cpu scaling governors would be a nice feature, but that would probably end up in the 'mageia control center', not in gnome-power-manager.
(In reply to comment #3) > So ondemand doesn't work well Yes or so it seems : for example, running KDE4 is a pain, simple thing like alt-tabbing or prompting the main menu are slow responding. > - but what happens with cpufreqd? You could try > to install powernowd instead. I didn't know there were different ways to manage frequency scaling. I'd like to try powernowd but I didn't find any package by that name in mageia software installer. > Now I'm starting to wonder what kind of CPU you > have (: Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz > > About a GUI - I think it's supposed to work automatically already. It seems > that the only reason you want to change something is that it doesn't work > correctly. > So the proper solution will be to make sure it works out-of-the box > for everyone. Yes, the best solution would be that it works fine out of the box but we have to deal with the fact that until now it doesn't, at least with cpufreqd. > On the other hand, switching cpu scaling governors would be a > nice feature, but that would probably end up in the 'mageia control center', > not in gnome-power-manager. I agree, it would be desktop environment independant. A button to launch a configuration tool in the "hardware list"/processors MCC section would be fine (like for other hardware like sound cards, ethernet cards...) Regards, Denis
On my CPU 800MHz is fast enough for basic GUI things and your CPU is probably even faster at the same clock frequency. But I don't use any GUI effects because I don't like to wait. powernowd is in the archive, no idea why you couldn't find it. (I modified one of its settings locally because I thought switching took a bit long, so I set options to "-p 500" in /etc/sysconfig/powernowd to reduce the polling interval from 1s to 0.5s .) But it sounds like using the "performance" setting is the solution for the GUI slowness.
Sorry Christiaan, I guess I forgot to set the left popup to "all" in mageia software installer before searching for powernowd. Now that I did it, I could find it. I installed it and will try it with the "-p 500" option. I'll let you know whether my system responsiveness is OK like that.
I did some testing with or without powernowd, performances are good and quite similar in ondemand cpu mode. I did also some testing in performance cpu mode : no difference. The bad performances I had in the past with ondemand don't seem to exist anymore. So that bug report is no more justified and I close it.
Status: NEW => RESOLVEDResolution: (none) => FIXED