cpufreqd-2.3.4-r1 doesn't see my CPU temperature sensors via sensors-plugin. (I have lm_sensors-3 installed.) sensors-plugin parses config file entries correctly, but it seems to me, that lm_sensors give no sensors for my chip. But if I type "sensors -u", I get the message: "Core0 Temp: temp1_input: 45 Core1 Temp: temp3_input: -49" So I can clearly see, that there ARE temperature sensors on my chip (temp1_input), but cpufreqd ignores the "sensor=temp1_input:61-100", for example, in my cpufreqd.conf file. Reproducible: Always Steps to Reproduce: 1. emerge sys-apps/lm_sensors-3.1.1 sys-power/cpufreqd-2.3.4-r1 2. type "sensors -u" and see the sensors information. 3. start cpufreqd and see the /va/log/messages file to see the "Discarding" messages from cpufreqd. Actual Results: Cpufreqd ignores the temperature sensors. Expected Results: Cpufrqd shouldn't ignore temperature sensors.
Created attachment 215896 [details, diff] cpufreqd-2.3.4-lm_sensors-3.patch Had the same problem, found out there is a bug in the patch in portage that was added in bug #233481. When it browses the chips, it uses the same iterator for the features than for the chips, so it doesn't see the "temp1" feature on Intel Core 2 chips (btw, you also need to change your config to be "sensor=temp1:61-100"). Here's the fixed patch to replace the other one.
(In reply to comment #1) > ... > Here's the fixed patch to replace the other one. > Thank you very much for this patch!!! :) I am happy to see my cpufreqd daemon working properly again on my laptop! Thank you! I have also reported about your patch to upstream developer. I have reported him about this bug earlier, but looks like he hasn't yet figured out what the problem was. Now I hope he will accept this patch and fix this problem upstream. Here's the link to this topic on SourceForge: http://sourceforge.net/tracker/?func=detail&aid=2920219&group_id=58904&atid=489239
cpufreqd-2.3.4-r2 has the proposed patch. thanks for the report and for the solution.
