[lm-sensors] CPU fan with full speed

[lm-sensors] CPU fan with full speed

[Philipp Kraus]

Hello,

I'm using on a dual xeon system lmsensors and pwmconfig for listing and 
controlling the fan speed.
Lmsensors is configurated and checks the temperature of the CPUs, but 
the fans rotate every time with
full speed:

CPU1 Fan:    5555 RPM  (min = 2000 RPM)
CPU2 Fan:    5895 RPM  (min = 2000 RPM)

CPU 1 Temp:   +50.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
CPU 2 Temp:   +53.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI

On booting up the fans have got around 2000 RPMs but some minuts the 
system speeds up on idle status
Can you help me please to configure the options correctly, that the 
RPMs are only gown up if needed?

Thanks

Phil



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Sat, Jun 30, 2012 at 07:52:06AM +0200, Philipp Kraus wrote:
> Hello,
> 
> I'm using on a dual xeon system lmsensors and pwmconfig for listing
> and controlling the fan speed.
> Lmsensors is configurated and checks the temperature of the CPUs,
> but the fans rotate every time with
> full speed:
> 
> CPU1 Fan:    5555 RPM  (min = 2000 RPM)
> CPU2 Fan:    5895 RPM  (min = 2000 RPM)
> 
> CPU 1 Temp:   +50.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
> CPU 2 Temp:   +53.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
> 
> On booting up the fans have got around 2000 RPMs but some minuts the
> system speeds up on idle status
> Can you help me please to configure the options correctly, that the
> RPMs are only gown up if needed?
> 
Hi Phil,

imagine you are an expert in the area. Then imagine someone sends you this
e-mail. Do you think you would be able to help based on the information in the
e-mail ?

Or, in other words, please provide sufficient information for people to actually
be able to help. Kernel version, lm-sensors version, complete sensors command
output, and all relevant configuration (including pwm configuration) would be
a start.

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Philipp Kraus]

On 2012-06-30 15:41:06 +0200, Guenter Roeck said:

> On Sat, Jun 30, 2012 at 07:52:06AM +0200, Philipp Kraus wrote:
>> Hello,
>> 
>> I'm using on a dual xeon system lmsensors and pwmconfig for listing
>> and controlling the fan speed.
>> Lmsensors is configurated and checks the temperature of the CPUs,
>> but the fans rotate every time with
>> full speed:
>> 
>> CPU1 Fan:    5555 RPM  (min = 2000 RPM)
>> CPU2 Fan:    5895 RPM  (min = 2000 RPM)
>> 
>> CPU 1 Temp:   +50.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
>> CPU 2 Temp:   +53.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
>> 
>> On booting up the fans have got around 2000 RPMs but some minuts the
>> system speeds up on idle status
>> Can you help me please to configure the options correctly, that the
>> RPMs are only gown up if needed?
>> 
> Hi Phil,
> 
> imagine you are an expert in the area. Then imagine someone sends you this
> e-mail. Do you think you would be able to help based on the information in the
> e-mail ?
> 
> Or, in other words, please provide sufficient information for people to 
> actually
> be able to help. Kernel version, lm-sensors version, complete sensors command
> output, and all relevant configuration (including pwm configuration) would be
> a start.


Sorry my mistake, I have forgot to past the full data (it was a little 
bit early on this morning and I was tired):

kernel version 3.2.11
lm sensors 3.3.1
Gentoo Linux 64 Bit

pmwconfig found this devices
   hwmon0/device is i5k_amb
   hwmon1/device is w83793

which are also used on lm sensors. The sensors config has stored only 
the min/max values (the min values on the CPUs are set to 2000 RPM),
labels and some ignore values

Only the two kernel modules are build
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_W83793=m
all other are disabled

I hope this additional kernel modules are helpful:
CONFIG_THERMAL=m
CONFIG_THERMAL_HWMON=y
CONFIG_X86_THERMAL_VECTOR=y
CONFIG_ACPI_THERMAL=m

I don't know which option can be modifies to change this settings and 
where I can start my search to find the problem. If I boot up the 
system the CPU
fans do some "pulse", so the speed rises up and slows down, rise up, .......
If I run only once sensors the pulse is gone away, but the RPM increses

Thanks

Phil



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Sat, Jun 30, 2012 at 04:06:39PM +0200, Philipp Kraus wrote:
> On 2012-06-30 15:41:06 +0200, Guenter Roeck said:
> 
> >On Sat, Jun 30, 2012 at 07:52:06AM +0200, Philipp Kraus wrote:
> >>Hello,
> >>
> >>I'm using on a dual xeon system lmsensors and pwmconfig for listing
> >>and controlling the fan speed.
> >>Lmsensors is configurated and checks the temperature of the CPUs,
> >>but the fans rotate every time with
> >>full speed:
> >>
> >>CPU1 Fan:    5555 RPM  (min = 2000 RPM)
> >>CPU2 Fan:    5895 RPM  (min = 2000 RPM)
> >>
> >>CPU 1 Temp:   +50.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
> >>CPU 2 Temp:   +53.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
> >>
> >>On booting up the fans have got around 2000 RPMs but some minuts the
> >>system speeds up on idle status
> >>Can you help me please to configure the options correctly, that the
> >>RPMs are only gown up if needed?
> >>
> >Hi Phil,
> >
> >imagine you are an expert in the area. Then imagine someone sends you this
> >e-mail. Do you think you would be able to help based on the information in the
> >e-mail ?
> >
> >Or, in other words, please provide sufficient information for
> >people to actually
> >be able to help. Kernel version, lm-sensors version, complete sensors command
> >output, and all relevant configuration (including pwm configuration) would be
> >a start.
> 
> 
> Sorry my mistake, I have forgot to past the full data (it was a
> little bit early on this morning and I was tired):
> 
> kernel version 3.2.11
> lm sensors 3.3.1
> Gentoo Linux 64 Bit
> 
> pmwconfig found this devices
>   hwmon0/device is i5k_amb
>   hwmon1/device is w83793
> 
> which are also used on lm sensors. The sensors config has stored
> only the min/max values (the min values on the CPUs are set to 2000
> RPM),
> labels and some ignore values
> 
> Only the two kernel modules are build
> CONFIG_SENSORS_I5K_AMB=m
> CONFIG_SENSORS_W83793=m
> all other are disabled
> 
> I hope this additional kernel modules are helpful:
> CONFIG_THERMAL=m
> CONFIG_THERMAL_HWMON=y
> CONFIG_X86_THERMAL_VECTOR=y
> CONFIG_ACPI_THERMAL=m
> 
> I don't know which option can be modifies to change this settings
> and where I can start my search to find the problem. If I boot up
> the system the CPU
> fans do some "pulse", so the speed rises up and slows down, rise up, .......
> If I run only once sensors the pulse is gone away, but the RPM increses
> 
Do you have "fancontrol" running ? If yes, pelase provide the configuration
file. Also, please provide output of "grep . /sys/class/hwmon/hwmon1/device/*"
and the output of the "sensors" command.

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Philipp Kraus]

On 2012-06-30 16:21:25 +0200, Guenter Roeck said:

> On Sat, Jun 30, 2012 at 04:06:39PM +0200, Philipp Kraus wrote:
>> On 2012-06-30 15:41:06 +0200, Guenter Roeck said:
>> 
>>> On Sat, Jun 30, 2012 at 07:52:06AM +0200, Philipp Kraus wrote:
>>>> Hello,
>>>> 
>>>> I'm using on a dual xeon system lmsensors and pwmconfig for listing
>>>> and controlling the fan speed.
>>>> Lmsensors is configurated and checks the temperature of the CPUs,
>>>> but the fans rotate every time with
>>>> full speed:
>>>> 
>>>> CPU1 Fan:    5555 RPM  (min = 2000 RPM)
>>>> CPU2 Fan:    5895 RPM  (min = 2000 RPM)
>>>> 
>>>> CPU 1 Temp:   +50.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
>>>> CPU 2 Temp:   +53.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
>>>> 
>>>> On booting up the fans have got around 2000 RPMs but some minuts the
>>>> system speeds up on idle status
>>>> Can you help me please to configure the options correctly, that the
>>>> RPMs are only gown up if needed?
>>>> 
>>> Hi Phil,
>>> 
>>> imagine you are an expert in the area. Then imagine someone sends you this
>>> e-mail. Do you think you would be able to help based on the information in the
>>> e-mail ?
>>> 
>>> Or, in other words, please provide sufficient information for
>>> people to actually
>>> be able to help. Kernel version, lm-sensors version, complete sensors command
>>> output, and all relevant configuration (including pwm configuration) would be
>>> a start.
>> 
>> 
>> Sorry my mistake, I have forgot to past the full data (it was a
>> little bit early on this morning and I was tired):
>> 
>> kernel version 3.2.11
>> lm sensors 3.3.1
>> Gentoo Linux 64 Bit
>> 
>> pmwconfig found this devices
>> hwmon0/device is i5k_amb
>> hwmon1/device is w83793
>> 
>> which are also used on lm sensors. The sensors config has stored
>> only the min/max values (the min values on the CPUs are set to 2000
>> RPM),
>> labels and some ignore values
>> 
>> Only the two kernel modules are build
>> CONFIG_SENSORS_I5K_AMB=m
>> CONFIG_SENSORS_W83793=m
>> all other are disabled
>> 
>> I hope this additional kernel modules are helpful:
>> CONFIG_THERMAL=m
>> CONFIG_THERMAL_HWMON=y
>> CONFIG_X86_THERMAL_VECTOR=y
>> CONFIG_ACPI_THERMAL=m
>> 
>> I don't know which option can be modifies to change this settings
>> and where I can start my search to find the problem. If I boot up
>> the system the CPU
>> fans do some "pulse", so the speed rises up and slows down, rise up, .......
>> If I run only once sensors the pulse is gone away, but the RPM increses
>> 
> Do you have "fancontrol" running ? If yes, pelase provide the configuration
> file. Also, please provide output of "grep . /sys/class/hwmon/hwmon1/device/*"
> and the output of the "sensors" command.

sensors shows:

i5k_amb-isa-0000
Adapter: ISA adapter
Ch. 0 DIMM 0:  +71.5 C  (low  = +92.0 C, high = +124.0 C)
Ch. 0 DIMM 1:  +72.0 C  (low  = +102.0 C, high = +124.0 C)
Ch. 1 DIMM 0:  +73.5 C  (low  = +92.0 C, high = +124.0 C)
Ch. 1 DIMM 1:  +65.0 C  (low  = +102.0 C, high = +124.0 C)

w83793-i2c-0-2f
Adapter: SMBus I801 adapter at 1100
VcoreA:       +1.07 V  (min =  +0.93 V, max =  +1.49 V)
VcoreB:       +1.07 V  (min =  +0.93 V, max =  +1.49 V)
in2:          +1.01 V  (min =  +1.00 V, max =  +1.33 V)
in3:          +0.53 V  (min =  +0.38 V, max =  +0.69 V)
in4:          +0.56 V  (min =  +0.50 V, max =  +1.65 V)
in5:          +3.41 V  (min =  +2.96 V, max =  +3.63 V)
in6:          +0.99 V  (min =  +0.90 V, max =  +1.10 V)
+5V:          +5.07 V  (min =  +4.52 V, max =  +5.50 V)
5VSB:         +5.12 V  (min =  +4.52 V, max =  +5.50 V)
Vbat:         +3.23 V  (min =  +2.70 V, max =  +3.30 V)
Front Fan1:  1914 RPM  (min = 1500 RPM)
Front Fan2:  2076 RPM  (min = 1500 RPM)
Rear Fan1:   1277 RPM  (min =  900 RPM)
CPU1 Fan:    6250 RPM  (min = 2000 RPM)
CPU2 Fan:    6221 RPM  (min = 2000 RPM)
CPU 1 Temp:   +52.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
CPU 2 Temp:   +54.0 C  (high = +75.0 C, hyst = +60.0 C)  sensor = Intel PECI
RAM 1 Temp:   +75.2 C  (high = +87.0 C, hyst = +82.0 C)  sensor = Intel PECI
RAM 2 Temp:   +78.0 C  (high = +87.0 C, hyst = +82.0 C)  sensor = Intel PECI
System Temp:  +47.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor
cpu0_vid:    +2.050 V
intrusion0:  OK
beep_enable: disabled

the grep command shows
grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory

and within the directory are the in*, pwm* temp* files

I have only configures lm sensors and setup the values with pwmconfig, 
that has create the /etc/fancontrol file with this content
INTERVAL\x10
DEVPATH=hwmon1Þvices/pci0000:00/0000:00:1f.3/i2c-0/0-002f
DEVNAME=hwmon1=w83793
FCTEMPSFCFANS=hwmon1/device/pwm2MINTEMPMAXTEMPMINSTARTMINSTOP
Thanks

Phil



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
> 
> the grep command shows
> grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
> grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
> grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
> grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
> 
> and within the directory are the in*, pwm* temp* files
> 
Not sure I understand.

I'll need the names and output for the pwm* and temp* files. They _should_ be in
/sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Philipp Kraus]

On 2012-06-30 17:33:38 +0200, Guenter Roeck said:

> On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
>> 
>> the grep command shows
>> grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
>> grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
>> grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
>> grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
>> 
>> and within the directory are the in*, pwm* temp* files
>> 
> Not sure I understand.
> 
> I'll need the names and output for the pwm* and temp* files. They 
> _should_ be in
> /sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.

the command grep /sys.... does not work, I have run an ls -l and grep 
the pwm files,
I think this is the correct output

-rw-r--r-- 1 root root 4096 Jun 30 16:31 /sys/class/hwmon/hwmon1/device/pwm1
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm1_nonstop
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm1_start
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm1_stop_time
-rw-r--r-- 1 root root 4096 Jun 30 16:31 /sys/class/hwmon/hwmon1/device/pwm2
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm2_nonstop
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm2_start
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm2_stop_time
-rw-r--r-- 1 root root 4096 Jun 30 16:31 /sys/class/hwmon/hwmon1/device/pwm3
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm3_nonstop
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm3_start
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm3_stop_time
-rw-r--r-- 1 root root 4096 Jun 30 16:31 /sys/class/hwmon/hwmon1/device/pwm4
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm4_nonstop
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm4_start
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm4_stop_time
-rw-r--r-- 1 root root 4096 Jun 30 16:31 /sys/class/hwmon/hwmon1/device/pwm5
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm5_nonstop
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm5_start
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm5_stop_time
-rw-r--r-- 1 root root 4096 Jun 30 16:31 /sys/class/hwmon/hwmon1/device/pwm6
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm6_nonstop
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm6_start
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm6_stop_time
-rw-r--r-- 1 root root 4096 Jun 30 16:31 /sys/class/hwmon/hwmon1/device/pwm7
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm7_nonstop
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm7_start
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm7_stop_time
-rw-r--r-- 1 root root 4096 Jun 30 16:31 /sys/class/hwmon/hwmon1/device/pwm8
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm8_nonstop
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm8_start
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm8_stop_time
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm_default
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm_downtime
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/pwm_uptime

and my temp files

-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp1_alarm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point1_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point1_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point2_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point2_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point3_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point3_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point4_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point4_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point5_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point5_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point6_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point6_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point7_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_auto_point7_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp1_beep
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp1_input
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp1_max
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp1_max_hyst
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_pwm_enable
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp1_type
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_warn
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp1_warn_hyst
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp2_alarm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point1_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point1_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point2_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point2_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point3_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point3_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point4_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point4_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point5_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point5_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point6_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point6_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point7_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_auto_point7_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp2_beep
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp2_input
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp2_max
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp2_max_hyst
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_pwm_enable
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp2_type
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_warn
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp2_warn_hyst
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp3_alarm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_channels_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point1_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point1_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point2_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point2_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point3_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point3_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point4_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point4_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point5_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point5_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point6_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point6_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point7_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_auto_point7_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp3_beep
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp3_input
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp3_max
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp3_max_hyst
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_pwm_enable
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp3_type
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_warn
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp3_warn_hyst
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp4_alarm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_channels_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point1_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point1_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point2_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point2_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point3_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point3_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point4_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point4_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point5_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point5_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point6_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point6_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point7_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_auto_point7_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp4_beep
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp4_input
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp4_max
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp4_max_hyst
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_pwm_enable
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp4_type
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_warn
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp4_warn_hyst
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp5_alarm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_channels_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point1_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point1_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point2_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point2_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point3_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point3_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point4_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point4_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point5_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point5_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point6_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point6_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point7_pwm
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_auto_point7_temp
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp5_beep
-r--r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp5_input
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp5_max
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp5_max_hyst
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_pwm_enable
-rw-r--r-- 1 root root 4096 Jun 30 16:02 
/sys/class/hwmon/hwmon1/device/temp5_type
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_warn
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp5_warn_hyst
-rw-r--r-- 1 root root 4096 Jun 30 16:29 
/sys/class/hwmon/hwmon1/device/temp_critical

Thanks

Phil



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
> On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
> 
> >On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
> >>
> >>the grep command shows
> >>grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
> >>grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
> >>grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
> >>grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
> >>
> >>and within the directory are the in*, pwm* temp* files
> >>
> >Not sure I understand.
> >
> >I'll need the names and output for the pwm* and temp* files. They
> >_should_ be in
> >/sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
> 
> the command grep /sys.... does not work, I have run an ls -l and

Phil,

It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
The "." is important. Your output gives me the file names, but I need names and
content, not names and permissions.

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Philipp Kraus]

On 2012-06-30 19:03:44 +0200, Guenter Roeck said:

> On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
>> On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
>> 
>>> On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
>>>> 
>>>> the grep command shows
>>>> grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
>>>> grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
>>>> grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
>>>> grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
>>>> 
>>>> and within the directory are the in*, pwm* temp* files
>>>> 
>>> Not sure I understand.
>>> 
>>> I'll need the names and output for the pwm* and temp* files. They
>>> _should_ be in
>>> /sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
>> 
>> the command grep /sys.... does not work, I have run an ls -l and
> 
> Phil,
> 
> It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
> The "." is important. Your output gives me the file names, but I need names and
> content, not names and permissions.

Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
Hope this the correct output now

/sys/class/hwmon/hwmon1/device/beep_enable:0
/sys/class/hwmon/hwmon1/device/chassis:0
/sys/class/hwmon/hwmon1/device/cpu0_vid:2050
/sys/class/hwmon/hwmon1/device/fan1_alarm:1
/sys/class/hwmon/hwmon1/device/fan1_beep:0
/sys/class/hwmon/hwmon1/device/fan1_input:0
/sys/class/hwmon/hwmon1/device/fan1_min:712
/sys/class/hwmon/hwmon1/device/fan2_alarm:0
/sys/class/hwmon/hwmon1/device/fan2_beep:0
/sys/class/hwmon/hwmon1/device/fan2_input:1904
/sys/class/hwmon/hwmon1/device/fan2_min:1500
/sys/class/hwmon/hwmon1/device/fan3_alarm:0
/sys/class/hwmon/hwmon1/device/fan3_beep:0
/sys/class/hwmon/hwmon1/device/fan3_input:2023
/sys/class/hwmon/hwmon1/device/fan3_min:1500
/sys/class/hwmon/hwmon1/device/fan4_alarm:1
/sys/class/hwmon/hwmon1/device/fan4_beep:0
/sys/class/hwmon/hwmon1/device/fan4_input:0
/sys/class/hwmon/hwmon1/device/fan4_min:712
/sys/class/hwmon/hwmon1/device/fan5_alarm:0
/sys/class/hwmon/hwmon1/device/fan5_beep:0
/sys/class/hwmon/hwmon1/device/fan5_input:1277
/sys/class/hwmon/hwmon1/device/fan5_min:900
/sys/class/hwmon/hwmon1/device/fan6_alarm:1
/sys/class/hwmon/hwmon1/device/fan6_beep:0
/sys/class/hwmon/hwmon1/device/fan6_input:0
/sys/class/hwmon/hwmon1/device/fan6_min:712
/sys/class/hwmon/hwmon1/device/fan7_alarm:0
/sys/class/hwmon/hwmon1/device/fan7_beep:0
/sys/class/hwmon/hwmon1/device/fan7_input:6108
/sys/class/hwmon/hwmon1/device/fan7_min:2000
/sys/class/hwmon/hwmon1/device/fan8_alarm:0
/sys/class/hwmon/hwmon1/device/fan8_beep:0
/sys/class/hwmon/hwmon1/device/fan8_input:6428
/sys/class/hwmon/hwmon1/device/fan8_min:2000
/sys/class/hwmon/hwmon1/device/in0_alarm:0
/sys/class/hwmon/hwmon1/device/in0_beep:0
/sys/class/hwmon/hwmon1/device/in0_input:1068
/sys/class/hwmon/hwmon1/device/in0_max:1486
/sys/class/hwmon/hwmon1/device/in0_min:926
/sys/class/hwmon/hwmon1/device/in1_alarm:0
/sys/class/hwmon/hwmon1/device/in1_beep:0
/sys/class/hwmon/hwmon1/device/in1_input:1070
/sys/class/hwmon/hwmon1/device/in1_max:1486
/sys/class/hwmon/hwmon1/device/in1_min:926
/sys/class/hwmon/hwmon1/device/in2_alarm:0
/sys/class/hwmon/hwmon1/device/in2_beep:0
/sys/class/hwmon/hwmon1/device/in2_input:1014
/sys/class/hwmon/hwmon1/device/in2_max:1326
/sys/class/hwmon/hwmon1/device/in2_min:1000
/sys/class/hwmon/hwmon1/device/in3_alarm:0
/sys/class/hwmon/hwmon1/device/in3_beep:0
/sys/class/hwmon/hwmon1/device/in3_input:528
/sys/class/hwmon/hwmon1/device/in3_max:688
/sys/class/hwmon/hwmon1/device/in3_min:384
/sys/class/hwmon/hwmon1/device/in4_alarm:0
/sys/class/hwmon/hwmon1/device/in4_beep:0
/sys/class/hwmon/hwmon1/device/in4_input:560
/sys/class/hwmon/hwmon1/device/in4_max:1648
/sys/class/hwmon/hwmon1/device/in4_min:496
/sys/class/hwmon/hwmon1/device/in5_alarm:0
/sys/class/hwmon/hwmon1/device/in5_beep:0
/sys/class/hwmon/hwmon1/device/in5_input:3408
/sys/class/hwmon/hwmon1/device/in5_max:3632
/sys/class/hwmon/hwmon1/device/in5_min:2960
/sys/class/hwmon/hwmon1/device/in6_alarm:0
/sys/class/hwmon/hwmon1/device/in6_beep:0
/sys/class/hwmon/hwmon1/device/in6_input:992
/sys/class/hwmon/hwmon1/device/in6_max:1104
/sys/class/hwmon/hwmon1/device/in6_min:896
/sys/class/hwmon/hwmon1/device/in7_alarm:0
/sys/class/hwmon/hwmon1/device/in7_beep:0
/sys/class/hwmon/hwmon1/device/in7_input:5070
/sys/class/hwmon/hwmon1/device/in7_max:5502
/sys/class/hwmon/hwmon1/device/in7_min:4518
/sys/class/hwmon/hwmon1/device/in8_alarm:0
/sys/class/hwmon/hwmon1/device/in8_beep:0
/sys/class/hwmon/hwmon1/device/in8_input:5118
/sys/class/hwmon/hwmon1/device/in8_max:5502
/sys/class/hwmon/hwmon1/device/in8_min:4518
/sys/class/hwmon/hwmon1/device/in9_alarm:0
/sys/class/hwmon/hwmon1/device/in9_beep:0
/sys/class/hwmon/hwmon1/device/in9_input:3232
/sys/class/hwmon/hwmon1/device/in9_max:3296
/sys/class/hwmon/hwmon1/device/in9_min:2704
/sys/class/hwmon/hwmon1/device/intrusion0_alarm:0
/sys/class/hwmon/hwmon1/device/modalias:i2c:w83793
/sys/class/hwmon/hwmon1/device/name:w83793
/sys/class/hwmon/hwmon1/device/pwm1:252
/sys/class/hwmon/hwmon1/device/pwm1_nonstop:152
/sys/class/hwmon/hwmon1/device/pwm1_start:32
/sys/class/hwmon/hwmon1/device/pwm1_stop_time:0
/sys/class/hwmon/hwmon1/device/pwm2:252
/sys/class/hwmon/hwmon1/device/pwm2_nonstop:16
/sys/class/hwmon/hwmon1/device/pwm2_start:32
/sys/class/hwmon/hwmon1/device/pwm2_stop_time:10000
/sys/class/hwmon/hwmon1/device/pwm3:252
/sys/class/hwmon/hwmon1/device/pwm3_nonstop:16
/sys/class/hwmon/hwmon1/device/pwm3_start:32
/sys/class/hwmon/hwmon1/device/pwm3_stop_time:10000
/sys/class/hwmon/hwmon1/device/pwm4:252
/sys/class/hwmon/hwmon1/device/pwm4_nonstop:16
/sys/class/hwmon/hwmon1/device/pwm4_start:32
/sys/class/hwmon/hwmon1/device/pwm4_stop_time:10000
/sys/class/hwmon/hwmon1/device/pwm5:252
/sys/class/hwmon/hwmon1/device/pwm5_nonstop:16
/sys/class/hwmon/hwmon1/device/pwm5_start:32
/sys/class/hwmon/hwmon1/device/pwm5_stop_time:10000
/sys/class/hwmon/hwmon1/device/pwm6:252
/sys/class/hwmon/hwmon1/device/pwm6_nonstop:16
/sys/class/hwmon/hwmon1/device/pwm6_start:32
/sys/class/hwmon/hwmon1/device/pwm6_stop_time:10000
/sys/class/hwmon/hwmon1/device/pwm7:252
/sys/class/hwmon/hwmon1/device/pwm7_nonstop:16
/sys/class/hwmon/hwmon1/device/pwm7_start:32
/sys/class/hwmon/hwmon1/device/pwm7_stop_time:10000
/sys/class/hwmon/hwmon1/device/pwm8:252
/sys/class/hwmon/hwmon1/device/pwm8_nonstop:16
/sys/class/hwmon/hwmon1/device/pwm8_start:32
/sys/class/hwmon/hwmon1/device/pwm8_stop_time:10000
/sys/class/hwmon/hwmon1/device/pwm_default:252
/sys/class/hwmon/hwmon1/device/pwm_downtime:300
/sys/class/hwmon/hwmon1/device/pwm_uptime:200
/sys/class/hwmon/hwmon1/device/temp1_alarm:0
/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
/sys/class/hwmon/hwmon1/device/temp1_auto_point1_pwm:152
/sys/class/hwmon/hwmon1/device/temp1_auto_point1_temp:50000
/sys/class/hwmon/hwmon1/device/temp1_auto_point2_pwm:152
/sys/class/hwmon/hwmon1/device/temp1_auto_point2_temp:50000
/sys/class/hwmon/hwmon1/device/temp1_auto_point3_pwm:152
/sys/class/hwmon/hwmon1/device/temp1_auto_point3_temp:50000
/sys/class/hwmon/hwmon1/device/temp1_auto_point4_pwm:152
/sys/class/hwmon/hwmon1/device/temp1_auto_point4_temp:72000
/sys/class/hwmon/hwmon1/device/temp1_auto_point5_pwm:152
/sys/class/hwmon/hwmon1/device/temp1_auto_point5_temp:72000
/sys/class/hwmon/hwmon1/device/temp1_auto_point6_pwm:152
/sys/class/hwmon/hwmon1/device/temp1_auto_point6_temp:77000
/sys/class/hwmon/hwmon1/device/temp1_auto_point7_pwm:192
/sys/class/hwmon/hwmon1/device/temp1_auto_point7_temp:82000
/sys/class/hwmon/hwmon1/device/temp1_beep:0
/sys/class/hwmon/hwmon1/device/temp1_input:52000
/sys/class/hwmon/hwmon1/device/temp1_max:75000
/sys/class/hwmon/hwmon1/device/temp1_max_hyst:60000
/sys/class/hwmon/hwmon1/device/temp1_pwm_enable:2
/sys/class/hwmon/hwmon1/device/temp1_type:6
/sys/class/hwmon/hwmon1/device/temp1_warn:85000
/sys/class/hwmon/hwmon1/device/temp1_warn_hyst:80000
/sys/class/hwmon/hwmon1/device/temp2_alarm:0
/sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm:1
/sys/class/hwmon/hwmon1/device/temp2_auto_point1_pwm:152
/sys/class/hwmon/hwmon1/device/temp2_auto_point1_temp:50000
/sys/class/hwmon/hwmon1/device/temp2_auto_point2_pwm:152
/sys/class/hwmon/hwmon1/device/temp2_auto_point2_temp:50000
/sys/class/hwmon/hwmon1/device/temp2_auto_point3_pwm:152
/sys/class/hwmon/hwmon1/device/temp2_auto_point3_temp:50000
/sys/class/hwmon/hwmon1/device/temp2_auto_point4_pwm:152
/sys/class/hwmon/hwmon1/device/temp2_auto_point4_temp:72000
/sys/class/hwmon/hwmon1/device/temp2_auto_point5_pwm:152
/sys/class/hwmon/hwmon1/device/temp2_auto_point5_temp:72000
/sys/class/hwmon/hwmon1/device/temp2_auto_point6_pwm:152
/sys/class/hwmon/hwmon1/device/temp2_auto_point6_temp:77000
/sys/class/hwmon/hwmon1/device/temp2_auto_point7_pwm:192
/sys/class/hwmon/hwmon1/device/temp2_auto_point7_temp:82000
/sys/class/hwmon/hwmon1/device/temp2_beep:0
/sys/class/hwmon/hwmon1/device/temp2_input:54000
/sys/class/hwmon/hwmon1/device/temp2_max:75000
/sys/class/hwmon/hwmon1/device/temp2_max_hyst:60000
/sys/class/hwmon/hwmon1/device/temp2_pwm_enable:2
/sys/class/hwmon/hwmon1/device/temp2_type:6
/sys/class/hwmon/hwmon1/device/temp2_warn:85000
/sys/class/hwmon/hwmon1/device/temp2_warn_hyst:80000
/sys/class/hwmon/hwmon1/device/temp3_alarm:0
/sys/class/hwmon/hwmon1/device/temp3_auto_channels_pwm:1
/sys/class/hwmon/hwmon1/device/temp3_auto_point1_pwm:152
/sys/class/hwmon/hwmon1/device/temp3_auto_point1_temp:50000
/sys/class/hwmon/hwmon1/device/temp3_auto_point2_pwm:152
/sys/class/hwmon/hwmon1/device/temp3_auto_point2_temp:50000
/sys/class/hwmon/hwmon1/device/temp3_auto_point3_pwm:152
/sys/class/hwmon/hwmon1/device/temp3_auto_point3_temp:50000
/sys/class/hwmon/hwmon1/device/temp3_auto_point4_pwm:152
/sys/class/hwmon/hwmon1/device/temp3_auto_point4_temp:72000
/sys/class/hwmon/hwmon1/device/temp3_auto_point5_pwm:152
/sys/class/hwmon/hwmon1/device/temp3_auto_point5_temp:72000
/sys/class/hwmon/hwmon1/device/temp3_auto_point6_pwm:152
/sys/class/hwmon/hwmon1/device/temp3_auto_point6_temp:77000
/sys/class/hwmon/hwmon1/device/temp3_auto_point7_pwm:192
/sys/class/hwmon/hwmon1/device/temp3_auto_point7_temp:82000
/sys/class/hwmon/hwmon1/device/temp3_beep:0
/sys/class/hwmon/hwmon1/device/temp3_input:75250
/sys/class/hwmon/hwmon1/device/temp3_max:87000
/sys/class/hwmon/hwmon1/device/temp3_max_hyst:82000
/sys/class/hwmon/hwmon1/device/temp3_pwm_enable:2
/sys/class/hwmon/hwmon1/device/temp3_type:6
/sys/class/hwmon/hwmon1/device/temp3_warn:85000
/sys/class/hwmon/hwmon1/device/temp3_warn_hyst:80000
/sys/class/hwmon/hwmon1/device/temp4_alarm:0
/sys/class/hwmon/hwmon1/device/temp4_auto_channels_pwm:1
/sys/class/hwmon/hwmon1/device/temp4_auto_point1_pwm:152
/sys/class/hwmon/hwmon1/device/temp4_auto_point1_temp:50000
/sys/class/hwmon/hwmon1/device/temp4_auto_point2_pwm:152
/sys/class/hwmon/hwmon1/device/temp4_auto_point2_temp:50000
/sys/class/hwmon/hwmon1/device/temp4_auto_point3_pwm:152
/sys/class/hwmon/hwmon1/device/temp4_auto_point3_temp:50000
/sys/class/hwmon/hwmon1/device/temp4_auto_point4_pwm:152
/sys/class/hwmon/hwmon1/device/temp4_auto_point4_temp:72000
/sys/class/hwmon/hwmon1/device/temp4_auto_point5_pwm:152
/sys/class/hwmon/hwmon1/device/temp4_auto_point5_temp:72000
/sys/class/hwmon/hwmon1/device/temp4_auto_point6_pwm:152
/sys/class/hwmon/hwmon1/device/temp4_auto_point6_temp:77000
/sys/class/hwmon/hwmon1/device/temp4_auto_point7_pwm:192
/sys/class/hwmon/hwmon1/device/temp4_auto_point7_temp:82000
/sys/class/hwmon/hwmon1/device/temp4_beep:0
/sys/class/hwmon/hwmon1/device/temp4_input:78000
/sys/class/hwmon/hwmon1/device/temp4_max:87000
/sys/class/hwmon/hwmon1/device/temp4_max_hyst:82000
/sys/class/hwmon/hwmon1/device/temp4_pwm_enable:2
/sys/class/hwmon/hwmon1/device/temp4_type:6
/sys/class/hwmon/hwmon1/device/temp4_warn:85000
/sys/class/hwmon/hwmon1/device/temp4_warn_hyst:80000
/sys/class/hwmon/hwmon1/device/temp5_alarm:0
/sys/class/hwmon/hwmon1/device/temp5_auto_channels_pwm:0
/sys/class/hwmon/hwmon1/device/temp5_auto_point1_pwm:32
/sys/class/hwmon/hwmon1/device/temp5_auto_point1_temp:30000
/sys/class/hwmon/hwmon1/device/temp5_auto_point2_pwm:48
/sys/class/hwmon/hwmon1/device/temp5_auto_point2_temp:35000
/sys/class/hwmon/hwmon1/device/temp5_auto_point3_pwm:64
/sys/class/hwmon/hwmon1/device/temp5_auto_point3_temp:40000
/sys/class/hwmon/hwmon1/device/temp5_auto_point4_pwm:96
/sys/class/hwmon/hwmon1/device/temp5_auto_point4_temp:45000
/sys/class/hwmon/hwmon1/device/temp5_auto_point5_pwm:128
/sys/class/hwmon/hwmon1/device/temp5_auto_point5_temp:50000
/sys/class/hwmon/hwmon1/device/temp5_auto_point6_pwm:192
/sys/class/hwmon/hwmon1/device/temp5_auto_point6_temp:55000
/sys/class/hwmon/hwmon1/device/temp5_auto_point7_pwm:224
/sys/class/hwmon/hwmon1/device/temp5_auto_point7_temp:60000
/sys/class/hwmon/hwmon1/device/temp5_beep:0
/sys/class/hwmon/hwmon1/device/temp5_input:46000
/sys/class/hwmon/hwmon1/device/temp5_max:75000
/sys/class/hwmon/hwmon1/device/temp5_max_hyst:70000
/sys/class/hwmon/hwmon1/device/temp5_pwm_enable:2
/sys/class/hwmon/hwmon1/device/temp5_type:4
/sys/class/hwmon/hwmon1/device/temp5_warn:85000
/sys/class/hwmon/hwmon1/device/temp5_warn_hyst:80000
/sys/class/hwmon/hwmon1/device/temp_critical:127000
/sys/class/hwmon/hwmon1/device/thermal_cruise1:40000
/sys/class/hwmon/hwmon1/device/thermal_cruise2:40000
/sys/class/hwmon/hwmon1/device/thermal_cruise3:40000
/sys/class/hwmon/hwmon1/device/thermal_cruise4:40000
/sys/class/hwmon/hwmon1/device/thermal_cruise5:32000
/sys/class/hwmon/hwmon1/device/tolerance1:5000
/sys/class/hwmon/hwmon1/device/tolerance2:5000
/sys/class/hwmon/hwmon1/device/tolerance3:5000
/sys/class/hwmon/hwmon1/device/tolerance4:5000
/sys/class/hwmon/hwmon1/device/tolerance5:2000
/sys/class/hwmon/hwmon1/device/uevent:DRIVER=w83793
/sys/class/hwmon/hwmon1/device/uevent:MODALIAS=i2c:w83793
/sys/class/hwmon/hwmon1/device/vrm:82

Phil



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
> On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
> 
> >On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
> >>On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
> >>
> >>>On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
> >>>>
> >>>>the grep command shows
> >>>>grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
> >>>>grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
> >>>>grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
> >>>>grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
> >>>>
> >>>>and within the directory are the in*, pwm* temp* files
> >>>>
> >>>Not sure I understand.
> >>>
> >>>I'll need the names and output for the pwm* and temp* files. They
> >>>_should_ be in
> >>>/sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
> >>
> >>the command grep /sys.... does not work, I have run an ls -l and
> >
> >Phil,
> >
> >It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
> >The "." is important. Your output gives me the file names, but I need names and
> >content, not names and permissions.
> 
> Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
> Hope this the correct output now
> 
> /sys/class/hwmon/hwmon1/device/pwm1:252

Looks like all pwm values report the "default" pwm value.

> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1

If I understand the code and the data sheet correectly, this attribute
is a bit map used to map a temperature source to one or multiple fans.
And it looks like all temperature sources are mapped to fan1, which
in turn means that effectively temp4 controls the speed of fan1 (the highest
temperature determines the fan speed), and all other fans are not mapped to
a temperature input.

What you should probably do is to find the association between tempX and pwmX
and program tempX_auto_channels_pwm such that the two map. For example, if temp1
is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.

You might have to play with the values a bit to find the correct mapping.

Hope this helps,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Michael Zintakis]

> If I understand the code and the data sheet correectly, this attribute
> is a bit map used to map a temperature source to one or multiple fans.
>   
I was just about to fire-up a question regarding that point! My 
pwm3_auto_channels_pwm has a value of 4 and I was a bit baffled why 4 
and not 3 - the above explains it very well.

Related to this query: as part of my censors setup, I have 3 different 
temperature monitors which supply reading for my CPU. 2 of them are in 
hwmon0/device/tempX_input (Intel's own coretemp module, X=2,3) and one 
of them is part of my f71882fg chip-supported reading: 
hwmon1/device/temp1_input. There are 2 Intel readings, because the CPU 
is multi-core.

Now, the f71882fg CPU reading is a bit off. What I mean by that is that 
it shows temperature which is between 3-7 degrees cooler than the 
Intel's own (coretemp) readings. Is there a way (via 
pwm1_auto_channels_pwm perhaps) to force f71882fg to take the coretemp 
reading into account instead of using its own?

I tried to "cheat" by executing "ln -s 
/sys/class/hwmon/hwmon0/device/temp2_input 
/sysclass/hwmon/hwmon1/device/temp4_input" but that didn't work - I get 
"No such file or directory" error. I cannot write anything to that 
hwmon1/device directory. Is there any way of pointing my f71882fg driver 
to read the 2 Intel temperatures temperatures instead of using its own, 
not very accurate reading?


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Philipp Kraus]

On 2012-06-30 21:24:59 +0200, Guenter Roeck said:

> On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
>> On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
>> 
>>> On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
>>>> On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
>>>> 
>>>>> On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
>>>>>> 
>>>>>> the grep command shows
>>>>>> grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
>>>>>> grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
>>>>>> grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
>>>>>> grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
>>>>>> 
>>>>>> and within the directory are the in*, pwm* temp* files
>>>>>> 
>>>>> Not sure I understand.
>>>>> 
>>>>> I'll need the names and output for the pwm* and temp* files. They
>>>>> _should_ be in
>>>>> /sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
>>>> 
>>>> the command grep /sys.... does not work, I have run an ls -l and
>>> 
>>> Phil,
>>> 
>>> It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
>>> The "." is important. Your output gives me the file names, but I need names and
>>> content, not names and permissions.
>> 
>> Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
>> Hope this the correct output now
>> 
>> /sys/class/hwmon/hwmon1/device/pwm1:252
> 
> Looks like all pwm values report the "default" pwm value.
> 
>> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
> 
> If I understand the code and the data sheet correectly, this attribute
> is a bit map used to map a temperature source to one or multiple fans.
> And it looks like all temperature sources are mapped to fan1, which
> in turn means that effectively temp4 controls the speed of fan1 (the highest
> temperature determines the fan speed), and all other fans are not mapped to
> a temperature input.
> 
> What you should probably do is to find the association between tempX and pwmX
> and program tempX_auto_channels_pwm such that the two map. For example, 
> if temp1
> is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
> 0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
> Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
> write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.

Okay, I will test in the next days and write a report to thisl ist. But 
why fails this mapping?
I think if I get a correct order, I must past the values on each boot 
into the hwmon files
with a little script.

Thanks

Phil



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Sun, Jul 01, 2012 at 02:06:27AM +0200, Philipp Kraus wrote:
> On 2012-06-30 21:24:59 +0200, Guenter Roeck said:
> 
> >On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
> >>On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
> >>
> >>>On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
> >>>>On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
> >>>>
> >>>>>On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
> >>>>>>
> >>>>>>the grep command shows
> >>>>>>grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
> >>>>>>grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
> >>>>>>grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
> >>>>>>grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
> >>>>>>
> >>>>>>and within the directory are the in*, pwm* temp* files
> >>>>>>
> >>>>>Not sure I understand.
> >>>>>
> >>>>>I'll need the names and output for the pwm* and temp* files. They
> >>>>>_should_ be in
> >>>>>/sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
> >>>>
> >>>>the command grep /sys.... does not work, I have run an ls -l and
> >>>
> >>>Phil,
> >>>
> >>>It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
> >>>The "." is important. Your output gives me the file names, but I need names and
> >>>content, not names and permissions.
> >>
> >>Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
> >>Hope this the correct output now
> >>
> >>/sys/class/hwmon/hwmon1/device/pwm1:252
> >
> >Looks like all pwm values report the "default" pwm value.
> >
> >>/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
> >
> >If I understand the code and the data sheet correectly, this attribute
> >is a bit map used to map a temperature source to one or multiple fans.
> >And it looks like all temperature sources are mapped to fan1, which
> >in turn means that effectively temp4 controls the speed of fan1 (the highest
> >temperature determines the fan speed), and all other fans are not mapped to
> >a temperature input.
> >
> >What you should probably do is to find the association between tempX and pwmX
> >and program tempX_auto_channels_pwm such that the two map. For
> >example, if temp1
> >is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
> >0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
> >Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
> >write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.
> 
> Okay, I will test in the next days and write a report to thisl ist.
> But why fails this mapping?
> I think if I get a correct order, I must past the values on each
> boot into the hwmon files
> with a little script.
> 
Yes, that will be necessary, unless you can somehow configure it in the BIOS.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Sat, Jun 30, 2012 at 11:46:14PM +0100, Michael Zintakis wrote:
> 
> >If I understand the code and the data sheet correectly, this attribute
> >is a bit map used to map a temperature source to one or multiple fans.
> I was just about to fire-up a question regarding that point! My
> pwm3_auto_channels_pwm has a value of 4 and I was a bit baffled why
> 4 and not 3 - the above explains it very well.
> 
> Related to this query: as part of my censors setup, I have 3
> different temperature monitors which supply reading for my CPU. 2 of
> them are in hwmon0/device/tempX_input (Intel's own coretemp module,
> X=2,3) and one of them is part of my f71882fg chip-supported
> reading: hwmon1/device/temp1_input. There are 2 Intel readings,
> because the CPU is multi-core.
> 
> Now, the f71882fg CPU reading is a bit off. What I mean by that is
> that it shows temperature which is between 3-7 degrees cooler than
> the Intel's own (coretemp) readings. Is there a way (via
> pwm1_auto_channels_pwm perhaps) to force f71882fg to take the
> coretemp reading into account instead of using its own?
> 
> I tried to "cheat" by executing "ln -s
> /sys/class/hwmon/hwmon0/device/temp2_input
> /sysclass/hwmon/hwmon1/device/temp4_input" but that didn't work - I
> get "No such file or directory" error. I cannot write anything to
> that hwmon1/device directory. Is there any way of pointing my
> f71882fg driver to read the 2 Intel temperatures temperatures
> instead of using its own, not very accurate reading?
>
No ... those are separate drivers, and different sensors. Also, the coretemp
reading is not really that exact. Especially at low temperatures it can be quite
a bit off, as far as I remember by 10 degrees C or more. It is more accurate at
very high temperatures.

Also, keep in mind that you have a different chip. pwm3_auto_channels_pwm
means something completely different on the f71882fg. For that chip, it is
not a bit map, but the temperature sensor index. 1..4 in pwmX_auto_channels_pwm
reflects temp[1..4]_input.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Michael Zintakis]

> No ... those are separate drivers, and different sensors. Also, the coretemp
> reading is not really that exact. Especially at low temperatures it can be quite
> a bit off, as far as I remember by 10 degrees C or more. It is more accurate at
> very high temperatures.
>   
I see, interesting - for some reason I always thought the Intel censors 
are more accurate (judging by their measurements, because when I place a 
load on that machine, both Intel CPU readings jump, but the f71882fg 
driver barely moves a degree or two and stays in line with the rest of 
the sensors, which doesn't really makes sense - when the CPU is under 
load its temperature should rise rapidly).

> Also, keep in mind that you have a different chip. pwm3_auto_channels_pwm
> means something completely different on the f71882fg. For that chip, it is
> not a bit map, but the temperature sensor index. 1..4 in pwmX_auto_channels_pwm
> reflects temp[1..4]_input.
>   
I am totally confused now! :-\

The driver has only 3 temperature readings: temp[1..3]_input, 
corresponding to CPU (single censor, even though I've got 2 cores) and 2 
motherboard readings (one on the PC board extension card and another one 
on the main board itself).

So, I have the following values by default:

pwm1_auto_channels_pwm = 1 (1 binary - fan1)
pwm2_auto_channels_pwm = 2 (10 binary - fan2)
pwm3_auto_channels_pwm = 4 (100 binary - fan3)

Makes perfect sense since I do not have a 4th temperature reading 
anywhere on the system, unless you take into account the coretemp 
driver, which is in a different subdirectory: hwmon0 and not hwmon1 as 
the f71882fg driver is.



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Sun, Jul 01, 2012 at 04:46:11AM +0100, Michael Zintakis wrote:
> 
> >No ... those are separate drivers, and different sensors. Also, the coretemp
> >reading is not really that exact. Especially at low temperatures it can be quite
> >a bit off, as far as I remember by 10 degrees C or more. It is more accurate at
> >very high temperatures.
> I see, interesting - for some reason I always thought the Intel
> censors are more accurate (judging by their measurements, because
> when I place a load on that machine, both Intel CPU readings jump,
> but the f71882fg driver barely moves a degree or two and stays in
> line with the rest of the sensors, which doesn't really makes sense
> - when the CPU is under load its temperature should rise rapidly).
> 
> >Also, keep in mind that you have a different chip. pwm3_auto_channels_pwm
> >means something completely different on the f71882fg. For that chip, it is
> >not a bit map, but the temperature sensor index. 1..4 in pwmX_auto_channels_pwm
> >reflects temp[1..4]_input.
> I am totally confused now! :-\
> 
> The driver has only 3 temperature readings: temp[1..3]_input,
> corresponding to CPU (single censor, even though I've got 2 cores)
> and 2 motherboard readings (one on the PC board extension card and
> another one on the main board itself).
> 
> So, I have the following values by default:
> 
> pwm1_auto_channels_pwm = 1 (1 binary - fan1)
> pwm2_auto_channels_pwm = 2 (10 binary - fan2)
> pwm3_auto_channels_pwm = 4 (100 binary - fan3)
> 
Guess you mean pwm[1-3]_auto_channels_temp.

> Makes perfect sense since I do not have a 4th temperature reading
> anywhere on the system, unless you take into account the coretemp
> driver, which is in a different subdirectory: hwmon0 and not hwmon1
> as the f71882fg driver is.
> 
You are right - sorry for that. I looked into the driver. The chip
understands [1, 2, 3], but the driver maps those values into a bit map,
where only one bit can be true at any given time.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Michael Zintakis]

>> So, I have the following values by default:
>>
>> pwm1_auto_channels_pwm = 1 (1 binary - fan1)
>> pwm2_auto_channels_pwm = 2 (10 binary - fan2)
>> pwm3_auto_channels_pwm = 4 (100 binary - fan3)
>>
>>     
> Guess you mean pwm[1-3]_auto_channels_temp.
>   
Yeah, that's right.

> You are right - sorry for that. I looked into the driver. The chip
> understands [1, 2, 3], but the driver maps those values into a bit map,
> where only one bit can be true at any given time.
>   
OK, nice to know as when I set it up (with "echo X > ...") I can't use 
anything other than 1, 2 or 4 so was a bit surprised that 3 is supposed 
to be the correct value.


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Philipp Kraus]

On 2012-06-30 21:24:59 +0200, Guenter Roeck said:

> On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
>> On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
>> 
>>> On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
>>>> On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
>>>> 
>>>>> On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
>>>>>> 
>>>>>> the grep command shows
>>>>>> grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
>>>>>> grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
>>>>>> grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
>>>>>> grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
>>>>>> 
>>>>>> and within the directory are the in*, pwm* temp* files
>>>>>> 
>>>>> Not sure I understand.
>>>>> 
>>>>> I'll need the names and output for the pwm* and temp* files. They
>>>>> _should_ be in
>>>>> /sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
>>>> 
>>>> the command grep /sys.... does not work, I have run an ls -l and
>>> 
>>> Phil,
>>> 
>>> It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
>>> The "." is important. Your output gives me the file names, but I need names and
>>> content, not names and permissions.
>> 
>> Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
>> Hope this the correct output now
>> 
>> /sys/class/hwmon/hwmon1/device/pwm1:252
> 
> Looks like all pwm values report the "default" pwm value.
> 
>> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
> 
> If I understand the code and the data sheet correectly, this attribute
> is a bit map used to map a temperature source to one or multiple fans.
> And it looks like all temperature sources are mapped to fan1, which
> in turn means that effectively temp4 controls the speed of fan1 (the highest
> temperature determines the fan speed), and all other fans are not mapped to
> a temperature input.
> 
> What you should probably do is to find the association between tempX and pwmX
> and program tempX_auto_channels_pwm such that the two map.
> For example, if temp1
> is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
> 0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
> Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
> write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.

You are write, temp1 and temp2 are the values for the CPU 1 and CPU 2. 
The fans for the CPU
are fan7 = CPU 1 and fan8 = CPU 2

Can you explane me in detail how you create the map 0b00001000 = 0x08 ?
I think 0x08 = 0x8 = 8 is a hexadecimal value but is this 0b00001000 
also a hexadecimal value, in this case both values are not equal !?
Should I write with echo -e "\x8" > 
/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm ?

IMHO I must enable (1) the n-th bit on the auto_channels_pwm value for 
the n-th fan, so in my configuration the 7 and 8 bit (begin = 0)?

Thanks

Phil



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Philipp Kraus]

On 2012-07-02 03:14:03 +0200, Philipp Kraus said:

> On 2012-06-30 21:24:59 +0200, Guenter Roeck said:
> 
>> On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
>>> On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
>>> 
>>>> On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
>>>>> On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
>>>>> 
>>>>>> On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
>>>>>>> 
>>>>>>> the grep command shows
>>>>>>> grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
>>>>>>> grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
>>>>>>> grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
>>>>>>> grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
>>>>>>> 
>>>>>>> and within the directory are the in*, pwm* temp* files
>>>>>>> 
>>>>>> Not sure I understand.
>>>>>> 
>>>>>> I'll need the names and output for the pwm* and temp* files. They
>>>>>> _should_ be in
>>>>>> /sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
>>>>> 
>>>>> the command grep /sys.... does not work, I have run an ls -l and
>>>> 
>>>> Phil,
>>>> 
>>>> It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
>>>> The "." is important. Your output gives me the file names, but I need names and
>>>> content, not names and permissions.
>>> 
>>> Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
>>> Hope this the correct output now
>>> 
>>> /sys/class/hwmon/hwmon1/device/pwm1:252
>> 
>> Looks like all pwm values report the "default" pwm value.
>> 
>>> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
>> 
>> If I understand the code and the data sheet correectly, this attribute
>> is a bit map used to map a temperature source to one or multiple fans.
>> And it looks like all temperature sources are mapped to fan1, which
>> in turn means that effectively temp4 controls the speed of fan1 (the highest
>> temperature determines the fan speed), and all other fans are not mapped to
>> a temperature input.
>> 
>> What you should probably do is to find the association between tempX and pwmX
>> and program tempX_auto_channels_pwm such that the two map.
>> For example, if temp1
>> is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
>> 0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
>> Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
>> write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.
> 
> You are write, temp1 and temp2 are the values for the CPU 1 and CPU 2.
> The fans for the CPU
> are fan7 = CPU 1 and fan8 = CPU 2
> 
> Can you explane me in detail how you create the map 0b00001000 = 0x08 ?
> I think 0x08 = 0x8 = 8 is a hexadecimal value but is this 0b00001000
> also a hexadecimal value, in this case both values are not equal !?
> Should I write with echo -e "\x8" >
> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm ?
> 
> IMHO I must enable (1) the n-th bit on the auto_channels_pwm value for
> the n-th fan, so in my configuration the 7 and 8 bit (begin = 0)?

I have set with
echo 128 >  /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm
echo 256 >  /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm

the 7th and 8th fan-bit but nothing is changed

phil



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Mon, Jul 02, 2012 at 03:28:19AM +0200, Philipp Kraus wrote:
> On 2012-07-02 03:14:03 +0200, Philipp Kraus said:
> 
> >On 2012-06-30 21:24:59 +0200, Guenter Roeck said:
> >
> >>On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
> >>>On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
> >>>
> >>>>On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
> >>>>>On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
> >>>>>
> >>>>>>On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
> >>>>>>>
> >>>>>>>the grep command shows
> >>>>>>>grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
> >>>>>>>grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
> >>>>>>>grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
> >>>>>>>grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
> >>>>>>>
> >>>>>>>and within the directory are the in*, pwm* temp* files
> >>>>>>>
> >>>>>>Not sure I understand.
> >>>>>>
> >>>>>>I'll need the names and output for the pwm* and temp* files. They
> >>>>>>_should_ be in
> >>>>>>/sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
> >>>>>
> >>>>>the command grep /sys.... does not work, I have run an ls -l and
> >>>>
> >>>>Phil,
> >>>>
> >>>>It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
> >>>>The "." is important. Your output gives me the file names, but I need names and
> >>>>content, not names and permissions.
> >>>
> >>>Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
> >>>Hope this the correct output now
> >>>
> >>>/sys/class/hwmon/hwmon1/device/pwm1:252
> >>
> >>Looks like all pwm values report the "default" pwm value.
> >>
> >>>/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
> >>
> >>If I understand the code and the data sheet correectly, this attribute
> >>is a bit map used to map a temperature source to one or multiple fans.
> >>And it looks like all temperature sources are mapped to fan1, which
> >>in turn means that effectively temp4 controls the speed of fan1 (the highest
> >>temperature determines the fan speed), and all other fans are not mapped to
> >>a temperature input.
> >>
> >>What you should probably do is to find the association between tempX and pwmX
> >>and program tempX_auto_channels_pwm such that the two map.
> >>For example, if temp1
> >>is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
> >>0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
> >>Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
> >>write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.
> >
> >You are write, temp1 and temp2 are the values for the CPU 1 and CPU 2.
> >The fans for the CPU
> >are fan7 = CPU 1 and fan8 = CPU 2
> >
> >Can you explane me in detail how you create the map 0b00001000 = 0x08 ?
> >I think 0x08 = 0x8 = 8 is a hexadecimal value but is this 0b00001000
> >also a hexadecimal value, in this case both values are not equal !?
> >Should I write with echo -e "\x8" >
> >/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm ?
> >
> >IMHO I must enable (1) the n-th bit on the auto_channels_pwm value for
> >the n-th fan, so in my configuration the 7 and 8 bit (begin = 0)?
> 
> I have set with
> echo 128 >  /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm
> echo 256 >  /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm
> 
> the 7th and 8th fan-bit but nothing is changed
> 
Does pwm7 and pwm8 still report 252 ? If so, we must be missing something.

What do you get if you read back
/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm and
/sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm ?

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Mon, Jul 02, 2012 at 03:14:03AM +0200, Philipp Kraus wrote:
> On 2012-06-30 21:24:59 +0200, Guenter Roeck said:
> 
> >On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
> >>On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
> >>
> >>>On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
> >>>>On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
> >>>>
> >>>>>On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
> >>>>>>
> >>>>>>the grep command shows
> >>>>>>grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
> >>>>>>grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
> >>>>>>grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
> >>>>>>grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
> >>>>>>
> >>>>>>and within the directory are the in*, pwm* temp* files
> >>>>>>
> >>>>>Not sure I understand.
> >>>>>
> >>>>>I'll need the names and output for the pwm* and temp* files. They
> >>>>>_should_ be in
> >>>>>/sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
> >>>>
> >>>>the command grep /sys.... does not work, I have run an ls -l and
> >>>
> >>>Phil,
> >>>
> >>>It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
> >>>The "." is important. Your output gives me the file names, but I need names and
> >>>content, not names and permissions.
> >>
> >>Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
> >>Hope this the correct output now
> >>
> >>/sys/class/hwmon/hwmon1/device/pwm1:252
> >
> >Looks like all pwm values report the "default" pwm value.
> >
> >>/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
> >
> >If I understand the code and the data sheet correectly, this attribute
> >is a bit map used to map a temperature source to one or multiple fans.
> >And it looks like all temperature sources are mapped to fan1, which
> >in turn means that effectively temp4 controls the speed of fan1 (the highest
> >temperature determines the fan speed), and all other fans are not mapped to
> >a temperature input.
> >
> >What you should probably do is to find the association between tempX and pwmX
> >and program tempX_auto_channels_pwm such that the two map.
> >For example, if temp1
> >is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
> >0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
> >Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
> >write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.
> 
> You are write, temp1 and temp2 are the values for the CPU 1 and CPU
> 2. The fans for the CPU
> are fan7 = CPU 1 and fan8 = CPU 2
> 
> Can you explane me in detail how you create the map 0b00001000 = 0x08 ?
> I think 0x08 = 0x8 = 8 is a hexadecimal value but is this 0b00001000
> also a hexadecimal value, in this case both values are not equal !?
> Should I write with echo -e "\x8" >
> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm ?
> 
"8" decimal is equivalent to hex, so you can just write "8".
With 0b00001000 I meant binary, not hex.


> IMHO I must enable (1) the n-th bit on the auto_channels_pwm value
> for the n-th fan, so in my configuration the 7 and 8 bit (begin =
> 0)?
> 
Correct.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Philipp Kraus]

On 2012-07-02 04:09:16 +0200, Guenter Roeck said:

> On Mon, Jul 02, 2012 at 03:28:19AM +0200, Philipp Kraus wrote:
>> On 2012-07-02 03:14:03 +0200, Philipp Kraus said:
>> 
>>> On 2012-06-30 21:24:59 +0200, Guenter Roeck said:
>>> 
>>>> On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
>>>>> On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
>>>>> 
>>>>>> On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
>>>>>>> On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
>>>>>>> 
>>>>>>>> On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
>>>>>>>>> 
>>>>>>>>> the grep command shows
>>>>>>>>> grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
>>>>>>>>> grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
>>>>>>>>> grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
>>>>>>>>> grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
>>>>>>>>> 
>>>>>>>>> and within the directory are the in*, pwm* temp* files
>>>>>>>>> 
>>>>>>>> Not sure I understand.
>>>>>>>> 
>>>>>>>> I'll need the names and output for the pwm* and temp* files. They
>>>>>>>> _should_ be in
>>>>>>>> /sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
>>>>>>> 
>>>>>>> the command grep /sys.... does not work, I have run an ls -l and
>>>>>> 
>>>>>> Phil,
>>>>>> 
>>>>>> It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
>>>>>> The "." is important. Your output gives me the file names, but I need names and
>>>>>> content, not names and permissions.
>>>>> 
>>>>> Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
>>>>> Hope this the correct output now
>>>>> 
>>>>> /sys/class/hwmon/hwmon1/device/pwm1:252
>>>> 
>>>> Looks like all pwm values report the "default" pwm value.
>>>> 
>>>>> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
>>>> 
>>>> If I understand the code and the data sheet correectly, this attribute
>>>> is a bit map used to map a temperature source to one or multiple fans.
>>>> And it looks like all temperature sources are mapped to fan1, which
>>>> in turn means that effectively temp4 controls the speed of fan1 (the highest
>>>> temperature determines the fan speed), and all other fans are not mapped to
>>>> a temperature input.
>>>> 
>>>> What you should probably do is to find the association between tempX and pwmX
>>>> and program tempX_auto_channels_pwm such that the two map.
>>>> For example, if temp1
>>>> is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
>>>> 0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
>>>> Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
>>>> write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.
>>> 
>>> You are write, temp1 and temp2 are the values for the CPU 1 and CPU 2.
>>> The fans for the CPU
>>> are fan7 = CPU 1 and fan8 = CPU 2
>>> 
>>> Can you explane me in detail how you create the map 0b00001000 = 0x08 ?
>>> I think 0x08 = 0x8 = 8 is a hexadecimal value but is this 0b00001000
>>> also a hexadecimal value, in this case both values are not equal !?
>>> Should I write with echo -e "\x8" >
>>> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm ?
>>> 
>>> IMHO I must enable (1) the n-th bit on the auto_channels_pwm value for
>>> the n-th fan, so in my configuration the 7 and 8 bit (begin = 0)?
>> 
>> I have set with
>> echo 128 >  /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm
>> echo 256 >  /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm
>> 
>> the 7th and 8th fan-bit but nothing is changed
>> 
> Does pwm7 and pwm8 still report 252 ? If so, we must be missing something.
> 
> What do you get if you read back
> /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm and
> /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm ?

I can insert each value [0,255] and than I can get back the value with cat
but after setting the value, the RPM are alway around 6000, no changes also.
I have tested on temp1 each bit value, but also no changes

I have found a file /etc/fancontrol, but no process fancontrol, can be 
create this a problem?



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] CPU fan with full speed

[Guenter Roeck]

On Mon, Jul 02, 2012 at 05:25:10AM +0200, Philipp Kraus wrote:
> On 2012-07-02 04:09:16 +0200, Guenter Roeck said:
> 
> >On Mon, Jul 02, 2012 at 03:28:19AM +0200, Philipp Kraus wrote:
> >>On 2012-07-02 03:14:03 +0200, Philipp Kraus said:
> >>
> >>>On 2012-06-30 21:24:59 +0200, Guenter Roeck said:
> >>>
> >>>>On Sat, Jun 30, 2012 at 07:27:49PM +0200, Philipp Kraus wrote:
> >>>>>On 2012-06-30 19:03:44 +0200, Guenter Roeck said:
> >>>>>
> >>>>>>On Sat, Jun 30, 2012 at 06:04:53PM +0200, Philipp Kraus wrote:
> >>>>>>>On 2012-06-30 17:33:38 +0200, Guenter Roeck said:
> >>>>>>>
> >>>>>>>>On Sat, Jun 30, 2012 at 04:37:28PM +0200, Philipp Kraus wrote:
> >>>>>>>>>
> >>>>>>>>>the grep command shows
> >>>>>>>>>grep: /sys/class/hwmon/hwmon1/device/driver: Is a directory
> >>>>>>>>>grep: /sys/class/hwmon/hwmon1/device/hwmon: Is a directory
> >>>>>>>>>grep: /sys/class/hwmon/hwmon1/device/power: Is a directory
> >>>>>>>>>grep: /sys/class/hwmon/hwmon1/device/subsystem: Is a directory
> >>>>>>>>>
> >>>>>>>>>and within the directory are the in*, pwm* temp* files
> >>>>>>>>>
> >>>>>>>>Not sure I understand.
> >>>>>>>>
> >>>>>>>>I'll need the names and output for the pwm* and temp* files. They
> >>>>>>>>_should_ be in
> >>>>>>>>/sys/class/hwmon/hwmon1/device/pwm* and /sys/class/hwmon/hwmon1/device/temp*.
> >>>>>>>
> >>>>>>>the command grep /sys.... does not work, I have run an ls -l and
> >>>>>>
> >>>>>>Phil,
> >>>>>>
> >>>>>>It wasn't "grep /sys/...", it was "grep . /sys/class/hwmon/hwmon1/device/*".
> >>>>>>The "." is important. Your output gives me the file names, but I need names and
> >>>>>>content, not names and permissions.
> >>>>>
> >>>>>Sorry, my mistake, I haven't seen that it ist "grep . <space> /sys..."
> >>>>>Hope this the correct output now
> >>>>>
> >>>>>/sys/class/hwmon/hwmon1/device/pwm1:252
> >>>>
> >>>>Looks like all pwm values report the "default" pwm value.
> >>>>
> >>>>>/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm:1
> >>>>
> >>>>If I understand the code and the data sheet correectly, this attribute
> >>>>is a bit map used to map a temperature source to one or multiple fans.
> >>>>And it looks like all temperature sources are mapped to fan1, which
> >>>>in turn means that effectively temp4 controls the speed of fan1 (the highest
> >>>>temperature determines the fan speed), and all other fans are not mapped to
> >>>>a temperature input.
> >>>>
> >>>>What you should probably do is to find the association between tempX and pwmX
> >>>>and program tempX_auto_channels_pwm such that the two map.
> >>>>For example, if temp1
> >>>>is the CPU1 temperature, and pwm4 (fan4) is connected to the CPU1 fan, write
> >>>>0b00001000 = 0x08 into /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm.
> >>>>Similar, if temp2 is the CPU2 temperature and fan5/pwm5 controls its fan,
> >>>>write 0x10 (\x16) into /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm.
> >>>
> >>>You are write, temp1 and temp2 are the values for the CPU 1 and CPU 2.
> >>>The fans for the CPU
> >>>are fan7 = CPU 1 and fan8 = CPU 2
> >>>
> >>>Can you explane me in detail how you create the map 0b00001000 = 0x08 ?
> >>>I think 0x08 = 0x8 = 8 is a hexadecimal value but is this 0b00001000
> >>>also a hexadecimal value, in this case both values are not equal !?
> >>>Should I write with echo -e "\x8" >
> >>>/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm ?
> >>>
> >>>IMHO I must enable (1) the n-th bit on the auto_channels_pwm value for
> >>>the n-th fan, so in my configuration the 7 and 8 bit (begin = 0)?
> >>
> >>I have set with
> >>echo 128 >  /sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm
> >>echo 256 >  /sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm
> >>
> >>the 7th and 8th fan-bit but nothing is changed
> >>
> >Does pwm7 and pwm8 still report 252 ? If so, we must be missing something.
> >
> >What do you get if you read back
> >/sys/class/hwmon/hwmon1/device/temp1_auto_channels_pwm and
> >/sys/class/hwmon/hwmon1/device/temp2_auto_channels_pwm ?
> 
> I can insert each value [0,255] and than I can get back the value with cat
> but after setting the value, the RPM are alway around 6000, no changes also.
> I have tested on temp1 each bit value, but also no changes
> 
> I have found a file /etc/fancontrol, but no process fancontrol, can
> be create this a problem?
> 
No, I don't think so.

Time to try manual fan control. Set
/sys/class/hwmon/hwmon1/device/temp[1-5]_auto_channels_pwm to 0, then set
pwm[1-8] directly to some value and see if it affects the fnn speed.

My concern right now is that temp6 (which does not seem to be enabled in your
system) may be configured to control all fans. If it is not connected, it may
report a super-high temperature, which in turn would result in the high fan
speeds. If the above does not work, this may be the case. If so, you may have
to try a patched driver. Is this possible ?

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors