Comment 9 for bug 223812
Revision history for this message
| Hanno Stock (hefe_bia) (hanno-stock) wrote Re: [hardy] Regression: powernowd no longer works with nforce2 cpufreq driver | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> I checked it, and whenever I select Ondemand governor with the applet, it does not work. Instead, the applet switches to performance mode.
Yes, that's right. The ondemand governor does not work with the nforce2 driver. Actually, when ondemand is used, powernowd (the daemon) is not used at all. The correct governor for powernowd is "userspace".
When you try to activate ondemand with the nforce2 driver it will switch to performance mode because of the error mentioned in my original report.
My patch should prevent the startup script from using the ondemand governor instead of powernowd on systems where ondemand is not supported.
However even with powernowd and the userspace governor activated, my system occasionally tries to switch back to the ondemand governor and therefore ends up with the performance governor because of the error mentioned above.
I have not yet figured out whether this is a problem with Ubuntu or powernowd. I'd appreciate any suggestions on how to debug this further.