Re: [Cpufreqd-user] Cpufreqd and sensors_plugin

[Erik d. T. <os...@gm...>]

That would be really great. I know the fancontrol script already has
this support, it allows the sensors to be set as (for example)
hwmon0/temp1 and hwmon1/temp1 according to the paths in
/sys/class/hwmon. In this case i need hwmon1/temp1.

The reason for using cpufreqd 2.2.1 instead of 2.3: I emerged it with
gentoo. 2.3 isn't in the portage tree yet... don't ask me why.

Thanks for the info!

Greets,

Erik den Toom

2009/3/2 Mattia Dongili <mal...@li...>:
> On Sun, Mar 01, 2009 at 07:52:32PM +0100, Erik den Toom wrote:
>> It is indeed possible to relabel the sensors. They do show up when i
>> do a "sensors -u":
>>
>> ------------------------------------------
>> k8temp-pci-00c3
>> Adapter: PCI adapter
>> Core0 Temp: 31.00 (temp1)
>> Core1 Temp: 34.00 (temp3)
>>
>> it8716-isa-0290
>> Adapter: ISA adapter
>> VCore: 0.99 (in0)
> ...
>> The one i want to use is the CPU Temp (motherboard sensor), known as
>> temp1. As you can see temp1 is also the sensor name for a sensor used
>> by k8temp.
>> With the attached cpufreqd.conf i get the following errors in /var/log/messages:
> ...
>> Mar  1 19:41:00 atlantis cpufreqd: plugin_handle_keyword    :
>> sensors_plugin is unable to parse this value "CPU Temp (motherboard
>> sensor):0-50". Discarded
>> Mar  1 19:41:00 atlantis cpufreqd: parse_config_rule        : WARNING!
>> skipping config option "sensor"
> ...
>> The sensors are clearly not recognized by their labels.
>
> Ok, shouldn't be too difficult to add support for this in cpufreqd. And
> I found one of my desktops has an it87 ISA sensor so I can reprouce and
> test your issue.
> ... and eventually implement support for libsensors4 :)
>
> I was wondering though, why cpufreqd 2.2.1 and not some 2.3 version?
>
> cheers
> --
> mattia
> :wq!
>