On Thu, Apr 15, 2010 at 07:31:25AM +0900, Mattia Dongili wrote: > severity 577822 normal
So damaging hardware is a normal bug... Maybe we should readjust all other bugs to wishlist. > Would you mind describing what you're actually experiencing rather than > an ipotetical (and quite unlinkely) situation? I experience that without /etc/sensors.conf no rules (especially not the overheated rule) are matched, so cpufreqd does not change governors. This causes my cpu to overheat. > Also please, provide logs (running cpufreqd with -V7 generates a lot of > useful output to trak down issues). The interesting parts of those logs are: ... sensors_post_conf : no sensors.conf found, sensors disabled! ... plugin_handle_keyword : unandled keyword "sensor". Discarded parse_config_rule : WARNING! skipping config option "sensor" init_configuration : [Rule] name "overheated" has no options. Discarded. ... cpufreqd_loop : No Rule matches current system status. ... > cpufreqd depends on libsensors4, have you considered using > /etc/sensors3.conf? I did, but cpufreqd does not let me configure that path. > I guess a possible issue here is that cpufreqd _requires_ a sensors > config file while it's not really necessary to use one when initializing > the library.. Correct. You can of course change cpufreqd, so it does not require this file. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
