Philipp Kern <pk...@debian.org> writes: > what does /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor show after > deinstallation of powernowd?
It says "userspace". After further investigation, here is what I understand: * the default governor is "ondemand". * powernowd changes this to "userspace" on startup. * "aptitude purge powernowd" leaves it to "userspace". Therefore, powernowd is indeed obsolete, but one must change the governor manually to "ondemand" upon purging the package, or reboot. I have not needed to install cpufrequtils. > The throttling comments in this bug log are entirely bogus. The fact that the > *frequency* changes means that there's no throttling involved. I thought that "throttling" referred precisely to changing the voltage and frequency of the CPU, as opposed to changing the C-state? > Furthermore this bug report is nowhere "serious". I agree. I hope you didn't think I was the one who claimed it was serious. It wasn't me. Now looking back on this issue: I've had this laptop since November 2006 and I've been running Debian on it ever since. The first version of Linux I installed was 2.6.18 (from Etch). I don't think Linux had the "ondemand" scheduler back then, so a userspace daemon was necessary. I suggest that perhaps a small paragraph should be added to the release notes for Squeeze, explaining this issue to users upgrading their kernel. Thanks for your help. -- Ludovic Brenta. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
