Hello. On Tue, May 15, 2007 at 11:25:24AM +0200, Petter Reinholdtsen wrote: > > Package: cpufrequtils > Version: 002-2 > Tags: patch > > For cpufreq scaling to work properly, the kernel modules needed have > to be loaded during boot. At the moment, there is nothing in Debian > taking care of this. A few bug reports already discusses this problem > (See #396117, #342014 and #367307), but no solution is yet in place. > There is work going on in the kernel to get these modules > automatically loaded by udev, but it will take a while before it is in > place. Check > <URL:http://0pointer.de/blog/projects/dmi-based-module-autoloading.html> > for information about this work. > > As cpufrequtils implement the currently recommended way of doing > frequency scaling, the ondemand kernel governor, I believe it would be > a good place to implement automatic detection and kernel module > loading.
yes, AFAIR I suggested something on the same line during such discussions. Why not implementing something like module detection in postinst and just loading that fixed module at init time? ... > Here is a complete patch to enable it. I inserted it as S05 in > runlevel 2-8. The 05 value is randomly picked, but it has to be below > the ones used by cpufrequtils, powernowd, and all the other tools that > manipulates the cpu frequency. Just a note: as for kernel 2.6.20 (probably even earlier) acpi-cpufreq should be used instead of speedstep-centrino as the former uses the BIOS provided freq tables instead of some harcoded (even if based on specs). So I'd rather invert the detction login around those by loading acpi-cpufreq first and if it fails using speedstep-centrino as a fallback. No? cheers -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
