The problem is no longer that the userpace governor not stays.
I get the wanted behaviour with powernowd:
On Cpu-Load increasy frequency step by step.
On no Cpu-Load immediately fall back to the minimum frequency.
But this i only get for 30 - 60 seconds.
Also there is no CPU-Load after a short time the frequency automatically changed to the maximum. If this happens and i look for the used governor, its the userpace governor (as expected, the switching governors was caused by the gnome-power-manager I think). The frequency then also stays at the maximum. I watched the Cpu-Load and frequency for 5 minutes and also load was always beetween 0 and 5 % the frequency remains at the maximum.
I had to manually set it to the minimum. Then powernowd works again for some time, till i had to set the frequency manually back to the minimum. This also happens when using other tools like cpudyn.
My current workaround is a script that sets the cpufrequency to the minimum every 30 sec. Im not happy with this, but it works.
James
]]>I installed powernowd and running it with the options "-m 2 -l 50 -u 90"
So the expected behavior is:
1 - Cpuload reaches 90% increases the cpufreq step by step.
2 - Cpuload falls below 50% immediately switch to lowest possible Frequenze.
But this is not what i get. The smallest CPULoad leads to the immediately switch to the maximum frequency. And also there is no Load anylonger it tooks several seconds (20-30 seconds) to switch back to the minimum Frequency. Thats not what I want.
I searched for the reason and I think I found it, but don't know how to solve:
The Powerscaling Daemons like Powernowd neeeds the userspace governor to be able to work, right?
I think this is the problem. The governors are switched automatically on my Laptop. I set to userspace, produce some cpuload and the used governor is automatically switsched to performance :shock:
Then after some idle time the governor is switched to powersave.
I think this is the reason that powernowd don't work as expected.
Any idea why this happens or better how to solve this problem?
btw:
Speedstepping in general works with no problems. I can manually switch to any frequency supported by my cpu. The acpi daemon is also started.
//edit:
Removed gnome-power-manager and now powernowd works, but not without problems:
It works only for a short period of time (1-5 minutes), then the the cpu freq is set to the maximum end stays there until i set it manually to the minimum. Then powernowd shows for some minutes again the behavior i want. But even if i do nothing after a while cpu freq is again set to maximum and stays there.
Tried to replace powernowd with cpudyn: same effect: works for some minutes as expected, then maximum frequency
Its really annoying.