[Mattia Dongili] > actually I can imagine what happened. You always relied on > cpufrequtils to load the kernel modules and never configured > /etc/default/cpufreqd. There is not much that I can do for that > other than duplicating the approach in cpufrequtils or depending on > it (which is wrong and usually generates confusion).
Actually, I do not believe depending on cpufrequtils is wrong, and even believe it is the best approach for Debian. This way the responsibility for loading the appropriate cpufreq kernel modules is well defined and in the hands of cpufrequtils (which really is the case today, just look at the laptop task :-). There is no need to duplicate the functionallity in cpufreqd, and it will make sure all effort to make this loading work flawlessly is focused on one package. :) Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
