cpufreqd-user

[Cpufreqd-user] Cpufreqd and sensors_plugin

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

Hi everybody,

I've almost got cpufreqd 2.2.1 to work now, using gentoo 2.6.28 r2.
However, since there is an unresolved bug in my bios, my
/proc/acpi/thermal_zone/THRM/temperature value remains fixed at 40
degrees C. Therefore i want to use the sensors defined at "sensors
-u".
There is where my problem is: since i've got two hardware monitoring
chips (one from k8temp and one from IT8716*) i've got two variables
named temp1. I need the one from IT8716, but how do i specify that in
cpufreqd.conf?

Thanks a lot in advance!

Erik den Toom

Re: [Cpufreqd-user] Cpufreqd and sensors_plugin

[Mattia D. <mal...@li...>]

On Sat, Feb 28, 2009 at 11:45:31PM +0100, Erik den Toom wrote:
> Hi everybody,
> 
> I've almost got cpufreqd 2.2.1 to work now, using gentoo 2.6.28 r2.
> However, since there is an unresolved bug in my bios, my
> /proc/acpi/thermal_zone/THRM/temperature value remains fixed at 40
> degrees C. Therefore i want to use the sensors defined at "sensors
> -u".
> There is where my problem is: since i've got two hardware monitoring
> chips (one from k8temp and one from IT8716*) i've got two variables
> named temp1. I need the one from IT8716, but how do i specify that in
> cpufreqd.conf?

It's been a while since I last played with sensors here but you should
be able to relabel your sensors in your /etc/sensors.conf

cheers
-- 
mattia
:wq!

Re: [Cpufreqd-user] Cpufreqd and sensors_plugin

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

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)
  in0_min: 0.80 (in0_min)
  in0_max: 1.25 (in0_max)
+3.3V: 3.23 (in1)
  in1_min: 0.00 (in1_min)
  in1_max: 4.08 (in1_max)
in2: 0.00 (in2)
  in2_min: 0.00 (in2_min)
  in2_max: 4.08 (in2_max)
+5V: 4.68 (in3)
  in3_min: 0.00 (in3_min)
  in3_max: 6.85 (in3_max)
+12V: 11.46 (in4)
  in4_min: 0.00 (in4_min)
  in4_max: 16.32 (in4_max)
-12V: -16.97 (in5)
  in5_min: -16.97 (in5_min)
  in5_max: 4.01 (in5_max)
-5V: -8.78 (in6)
  in6_min: -8.78 (in6_min)
  in6_max: 4.05 (in6_max)
5VSB: 4.60 (in7)
  in7_min: 0.00 (in7_min)
  in7_max: 6.85 (in7_max)
VBat: 2.94 (in8)
CPU Fan: 3260.00 (fan1)
  fan1_min: 500.00 (fan1_min)
Case Fan: 2732.00 (fan2)
  fan2_min: 1000.00 (fan2_min)
CPU Temp (motherboard sensor): 34.00 (temp1)
  temp1_low: -1.00 (temp1_low)
  temp1_over: 127.00 (temp1_over)
  sensor1: 3.00 (sensor1)
Case Temp (motherboard sensor): 34.00 (temp2)
  temp2_low: -1.00 (temp2_low)
  temp2_over: 127.00 (temp2_over)
  sensor2: 4.00 (sensor2)
VID: 1.08 (vid)
alarms: 25616.00 (alarms)
-----------------------------------------------

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: pmu_init                 :
/proc/pmu/info: No such file or directory
Mar  1 19:41:00 atlantis cpufreqd: apm_init                 :
/proc/apm: No such file or directory
Mar  1 19:41:00 atlantis cpufreqd: parse_config_general     : Remote
control enabled.
Mar  1 19:41:00 atlantis cpufreqd: parse_config_general     : Remote
controls will be r/w for group wheel (10).
Mar  1 19:41:00 atlantis cpufreqd: nforce2_post_conf        :
Unconfigured, exiting.
Mar  1 19:41:00 atlantis cpufreqd: plugins_post_conf        : Unable
to configure plugin nforce2_atxp1, removing
Mar  1 19:41:00 atlantis cpufreqd: acpi_battery_init        : error,
acpi_battery module not compiled or inserted (/proc/acpi/battery/: No
such file or direc
tory)?
Mar  1 19:41:00 atlantis cpufreqd: acpi_battery_init        : exiting.
Mar  1 19:41:00 atlantis acpid: client connected from 5830[0:0]
Mar  1 19:41:00 atlantis acpid: 1 client rule loaded
Mar  1 19:41:00 atlantis cpufreqd: sensor_parse             : feature
"CPU Temp (motherboard sensor)" does not exist, try 'sensors -u' to
see a full list of
available feature names.
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"
Mar  1 19:41:00 atlantis cpufreqd: sensor_parse             : feature
"CPU Temp (motherboard sensor)" does not exist, try 'sensors -u' to
see a full list of
available feature names.
Mar  1 19:41:00 atlantis cpufreqd: plugin_handle_keyword    :
sensors_plugin is unable to parse this value "CPU Temp (motherboard
sensor):50-100". Discarded
Mar  1 19:41:00 atlantis cpufreqd: parse_config_rule        : WARNING!
skipping config option "sensor"
Mar  1 19:41:00 atlantis cpufreqd: sensor_parse             : feature
"CPU Temp (motherboard sensor)" does not exist, try 'sensors -u' to
see a full list of
available feature names.
Mar  1 19:41:00 atlantis cpufreqd: plugin_handle_keyword    :
sensors_plugin is unable to parse this value "CPU Temp (motherboard
sensor):50-100". Discarded
Mar  1 19:41:00 atlantis cpufreqd: parse_config_rule        : WARNING!
skipping config option "sensor"
Mar  1 19:41:00 atlantis cpufreqd: sensor_parse             : feature
"CPU Temp (motherboard sensor)" does not exist, try 'sensors -u' to
see a full list of
available feature names.
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"
Mar  1 19:41:00 atlantis cpufreqd: sensor_parse             : feature
"CPU Temp (motherboard sensor)" does not exist, try 'sensors -u' to
see a full list of
available feature names.
Mar  1 19:41:00 atlantis cpufreqd: plugin_handle_keyword    :
sensors_plugin is unable to parse this value "CPU Temp (motherboard
sensor):50-65". 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.

--------------------------------------------------------------------------------------------------------------------------------------------
# this is a comment
# see CPUFREQD.CONF(5) manpage for a complete reference

##
# General/plugins config
##

[General]
pidfile=/var/run/cpufreqd.pid
poll_interval=2
verbosity=4
enable_remote=1
remote_group=wheel
[/General]

[sensors_plugin]
sensors_conf=/etc/sensors.conf
[/sensors_plugin]

##
# Profiles
##

[Profile]
name=On Demand High
minfreq=40%
maxfreq=100%
policy=ondemand
[/Profile]

[Profile]
name=On Demand Low
minfreq=20%
maxfreq=80%
policy=ondemand
[/Profile]

[Profile]
name=Performance High
minfreq=100%
maxfreq=100%
policy=performance
[/Profile]

[Profile]
name=Performance Low
minfreq=80%
maxfreq=80%
policy=performance
[/Profile]

[Profile]
name=Powersave High
minfreq=70%
maxfreq=70%
policy=powersave
[/Profile]

[Profile]
name=Powersave Low
minfreq=30%
maxfreq=30%
policy=powersave
[/Profile]


##
# Rules
##

# Normal situations

[Rule]
name=Standard
acpi_temperature=0-55
cpu_interval=ANY:0-70
profile=On Demand High
[/Rule]

# High load situations

[Rule]
name=High Load
sensor=CPU Temp (motherboard sensor):0-50
cpu_interval=ANY:70-100
profile=Performance High
[/Rule]

# CPU Too hot!

[Rule]
name=Hot CPU Idle
sensor=CPU Temp (motherboard sensor):50-100
cpu_interval=ANY:0-50
profile=Powersave Low
[/Rule]

[Rule]
name=Hot CPU High Load
sensor=CPU Temp (motherboard sensor):50-100
cpu_interval=ANY:50-100
profile=On Demand Low
[/Rule]

# use performance mode if I'm watching a movie but don't heat too much.

[Rule]
name=Movie Watcher
programs=xine,mplayer,gmplayer
sensor=CPU Temp (motherboard sensor):0-50
profile=Performance High
[/Rule]

[Rule]
name=Movie Watcher Hot
programs=xine,mplayer,gmplayer
sensor=CPU Temp (motherboard sensor):50-65
profile=Performance Low
[/Rule]
--------------------------------------------------------------------------------------------------------------------------------------------

Greets,

Erik den Toom

2009/3/1 Mattia Dongili <mal...@li...>:
> On Sat, Feb 28, 2009 at 11:45:31PM +0100, Erik den Toom wrote:
>> Hi everybody,
>>
>> I've almost got cpufreqd 2.2.1 to work now, using gentoo 2.6.28 r2.
>> However, since there is an unresolved bug in my bios, my
>> /proc/acpi/thermal_zone/THRM/temperature value remains fixed at 40
>> degrees C. Therefore i want to use the sensors defined at "sensors
>> -u".
>> There is where my problem is: since i've got two hardware monitoring
>> chips (one from k8temp and one from IT8716*) i've got two variables
>> named temp1. I need the one from IT8716, but how do i specify that in
>> cpufreqd.conf?
>
> It's been a while since I last played with sensors here but you should
> be able to relabel your sensors in your /etc/sensors.conf
>
> cheers
> --
> mattia
> :wq!
>

Re: [Cpufreqd-user] Cpufreqd and sensors_plugin

[Mattia D. <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!

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!
>

Re: [Cpufreqd-user] Cpufreqd and sensors_plugin

[Mattia D. <mal...@li...>]

On Mon, Mar 02, 2009 at 01:05:14AM +0100, Erik den Toom wrote:
> 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.

I implemented the label support for cpufreqd in the sensors plugin now,
what I would like to add is support for addressing the sensor feature
via <chip>:<feature> so that ambiguous names can be resolved uniquely.
In your case you would have:
	it8716-isa-0290:temp1
or your label instead of 'temp1', but for now only the label is
supported. I will probably add the chip name later on when I finally
decide to move to libsensors4.

> 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.

well actually I know ;) the released 2.3 is a bit buggy and you need a
couple of patches to actually make it usable.

Anyway, the current source is here:
http://git.kamineko.org/cgi-bin/gitweb.cgi?p=cpufreqd.git;a=summary

can you give it a try?
You should be able to clone the repository with
git clone git://git.kamineko.org/cpufreqd.git
let me know if it doesn't work.

thanks
-- 
mattia
:wq!