You are not logged in.
Pages: 1
I have a 1.6 GHz Turion X2 processor. Initially, I set up frequency scaling by installing powersave and cpufreqd, and adding powersaved and cpufreqd to /etc/rc.conf. I rebooted and everything was great. Plugged in I'm at 1.6 GHz, unplugged I'm at 800 MHz, great! But at some point in the last day or two, it has stopped working. Now only 1 of my processor cores is scaling (cpu 0), and once it scales down it never scales back up. I don't think I've changed anything to cause this, but am I doing something wrong somewhere?
edit: Just remembered, I also have the powernow-k8 module loading.
Offline
Alrighty, I replaced cpufreqd with powernowd and added cpufreq-userspace to modules, and now powersaved is able to control the cpu frequency. This enables me to scale the speed up and down with "powersave -l" and "powersave -f", which is better in some ways because I don't always want low performance on battery power (Xgl).
Now the only real problem left is that both processors aren't being scaled. Turns out that that isn't entirely accurate either though. They both scale fine when I first boot the computer. However, after I wake it up from suspend to ram, the second core is no longer controlled by the powernow-k8 module. I have tried to add it to the unload/load list in /etc/powersave/sleep, but no luck. I have tried "modprobe powernow-k8" after waking up from suspend, but it says the device doesn't exist. If I remove the module with "modprobe -r", both cores are uncontrolled and then I cannot reload the module (same error).
I have no idea where to go from here.
Offline
Yeah, yesterday I noticed the same problem with powernow-k8 when resuming, using suspend2.
At least your experience means that it's not limited to suspend2.
Offline
What would cause this kind of problem? Kernel? Powersaved? Is it something fixable by changing some settings or installing some packages? Or the kind of thing fixable by switching distros (less desireable)? Or the kind of thing that will just be broke until the upstream developers fix it?
I use my laptop for some CPU intensive stuff, and it scares me to have a processor core that isn't scalable because I don't want to overheat it. For now, I'm just rebooting before any heavy use, but if I can fix this or find a distro that doesn't have this problem that would be preferable.
Offline
I am to pinpoint the issue yet. If at all ;-)
Offline
Would be nice if you could check whether it works properly on 2.6.18 - get package from here. Powersave (suspend1) doesn't seem to work on my scrap of metal and whatelse.
As it's not limited to suspend2, I'm quite unsure which way to go. Maybe it'd work on .18. I tried a bunch of tricks/combinations on .17 already.
Offline
What MB are you using?
Offline
Sorry, I've since moved on to Ubuntu Edgy, where I don't have this problem.
Offline
Pages: 1