[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file for

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file for

[Udo van den Heuvel]

Hello,

Since booting into 2.6.19 on my VIA SP8000 I have a small problem with
the vt1211 sensors driver:

sensors -s gives:

vt1211-isa-6000: Can't access procfs/sysfs file for writing;


Also the temperature sensors are not shown.

sysfs is of course mounted and accessible.
lm_sensors 2.10.1 we have installed before rebooting.

The vt1211 sensors stuff has moved to
/sys/bus/platform/drivers/vt1211/vt1211.24576. In that directory the
files with sensors info for rpm, voltage etc can be found.

Of course the sensor's location on the bus was not changed so I am
wondering what is wrong, why can't the sensors command find the files in
/sys/bus/platform/drivers/vt1211/vt1211.24576?

How do I fix this problem?

Kind regards,
Udo

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file

[Jean Delvare]

Hi Udo,

On Sun, 03 Dec 2006 09:18:45 +0100, Udo van den Heuvel wrote:
> Since booting into 2.6.19 on my VIA SP8000 I have a small problem with
> the vt1211 sensors driver:
> 
> sensors -s gives:
> 
> vt1211-isa-6000: Can't access procfs/sysfs file for writing;

Are you root when running this command?

> 
> Also the temperature sensors are not shown.

Please provide the complete output of "sensors".

> 
> sysfs is of course mounted and accessible.
> lm_sensors 2.10.1 we have installed before rebooting.

What does "sensors -v" return?

> 
> The vt1211 sensors stuff has moved to
> /sys/bus/platform/drivers/vt1211/vt1211.24576. In that directory the
> files with sensors info for rpm, voltage etc can be found.

Yes, this is OK. You should also have a link in /sys/class/hwmon
pointing to it.

> 
> Of course the sensor's location on the bus was not changed so I am
> wondering what is wrong, why can't the sensors command find the files in
> /sys/bus/platform/drivers/vt1211/vt1211.24576?

Please provide a detailed listing (ls -l) of the files present in this
directory.

-- 
Jean Delvare

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file

[Udo van den Heuvel]

Hello Jean,

Jean Delvare wrote:
> On Sun, 03 Dec 2006 09:18:45 +0100, Udo van den Heuvel wrote:
>> Since booting into 2.6.19 on my VIA SP8000 I have a small problem with
>> the vt1211 sensors driver:
>>
>> sensors -s gives:
>>
>> vt1211-isa-6000: Can't access procfs/sysfs file for writing;
> 
> Are you root when running this command?

Sure!

>> Also the temperature sensors are not shown.
> 
> Please provide the complete output of "sensors".

# sensors
vt1211-isa-6000
Adapter: ISA adapter
VCore1:    +1.04 V  (min =  +1.13 V, max =  +1.27 V)   ALARM
+5V:       +4.93 V  (min =  +4.74 V, max =  +5.26 V)
+12V:     +12.05 V  (min = +11.38 V, max = +12.61 V)
+3.3V:     +5.28 V  (min =  +3.14 V, max =  +3.47 V)   ALARM
System:   4070 RPM  (min = 2580 RPM, div = 2)
vid:      +1.850 V  (VRM Version 9.1)


>> sysfs is of course mounted and accessible.
>> lm_sensors 2.10.1 we have installed before rebooting.
> 
> What does "sensors -v" return?

sensors version 2.10.1 with libsensors version 2.10.1

>> The vt1211 sensors stuff has moved to
>> /sys/bus/platform/drivers/vt1211/vt1211.24576. In that directory the
>> files with sensors info for rpm, voltage etc can be found.
> 
> Yes, this is OK. You should also have a link in /sys/class/hwmon
> pointing to it.

Indeed. /sys/class/hwmon/hwmon0/device points to the directory I
mentioned earlier.

>> Of course the sensor's location on the bus was not changed so I am
>> wondering what is wrong, why can't the sensors command find the files in
>> /sys/bus/platform/drivers/vt1211/vt1211.24576?
> 
> Please provide a detailed listing (ls -l) of the files present in this
> directory.

# pwd
/sys/class/hwmon/hwmon0/device
[root at recorder device]# ls -l
total 0
-r--r--r-- 1 root root 4096 Dec  3 11:38 alarms
lrwxrwxrwx 1 root root    0 Dec  3 11:38 bus -> ../../../bus/platform
-r--r--r-- 1 root root 4096 Dec  3 11:38 cpu0_vid
lrwxrwxrwx 1 root root    0 Dec  3 11:38 driver ->
../../../bus/platform/drivers/vt1211
-r--r--r-- 1 root root 4096 Dec  3 11:39 fan1_alarm
-rw-r--r-- 1 root root 4096 Dec  3 09:10 fan1_div
-r--r--r-- 1 root root 4096 Dec  3 11:39 fan1_input
-rw-r--r-- 1 root root 4096 Dec  3 09:10 fan1_min
-r--r--r-- 1 root root 4096 Dec  3 11:39 fan2_alarm
-rw-r--r-- 1 root root 4096 Dec  3 09:10 fan2_div
-r--r--r-- 1 root root 4096 Dec  3 11:38 fan2_input
-rw-r--r-- 1 root root 4096 Dec  3 09:10 fan2_min
lrwxrwxrwx 1 root root    0 Dec  3 11:39 hwmon:hwmon0 ->
../../../class/hwmon/hwmon0
-r--r--r-- 1 root root 4096 Dec  3 11:39 in0_alarm
-r--r--r-- 1 root root 4096 Dec  3 11:39 in0_input
-rw-r--r-- 1 root root 4096 Dec  3 11:39 in0_max
-rw-r--r-- 1 root root 4096 Dec  3 11:39 in0_min
-r--r--r-- 1 root root 4096 Dec  3 11:39 in1_alarm
-r--r--r-- 1 root root 4096 Dec  3 11:39 in1_input
-rw-r--r-- 1 root root 4096 Dec  3 11:39 in1_max
-rw-r--r-- 1 root root 4096 Dec  3 11:39 in1_min
-r--r--r-- 1 root root 4096 Dec  3 11:39 in2_alarm
-r--r--r-- 1 root root 4096 Dec  3 11:38 in2_input
-rw-r--r-- 1 root root 4096 Dec  3 09:10 in2_max
-rw-r--r-- 1 root root 4096 Dec  3 09:10 in2_min
-r--r--r-- 1 root root 4096 Dec  3 11:39 in3_alarm
-r--r--r-- 1 root root 4096 Dec  3 11:38 in3_input
-rw-r--r-- 1 root root 4096 Dec  3 09:10 in3_max
-rw-r--r-- 1 root root 4096 Dec  3 09:10 in3_min
-r--r--r-- 1 root root 4096 Dec  3 11:39 in4_alarm
-r--r--r-- 1 root root 4096 Dec  3 11:38 in4_input
-rw-r--r-- 1 root root 4096 Dec  3 09:10 in4_max
-rw-r--r-- 1 root root 4096 Dec  3 09:10 in4_min
-r--r--r-- 1 root root 4096 Dec  3 11:39 in5_alarm
-r--r--r-- 1 root root 4096 Dec  3 11:38 in5_input
-rw-r--r-- 1 root root 4096 Dec  3 09:10 in5_max
-rw-r--r-- 1 root root 4096 Dec  3 09:10 in5_min
-r--r--r-- 1 root root 4096 Dec  3 11:39 modalias
-r--r--r-- 1 root root 4096 Dec  3 11:38 name
drwxr-xr-x 2 root root    0 Dec  3 09:02 power
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_channels_temp
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point1_pwm
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point1_temp
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point2_pwm
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point2_temp
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point3_pwm
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point3_temp
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point4_pwm
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point4_temp
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_enable
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_freq
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_channels_temp
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point1_pwm
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point1_temp
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point2_pwm
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point2_temp
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point3_pwm
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point3_temp
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point4_pwm
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point4_temp
-rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_enable
-r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_freq
lrwxrwxrwx 1 root root    0 Dec  3 11:39 subsystem -> ../../../bus/platform
-r--r--r-- 1 root root 4096 Dec  3 11:39 temp1_alarm
-r--r--r-- 1 root root 4096 Dec  3 11:39 temp1_input
-rw-r--r-- 1 root root 4096 Dec  3 11:39 temp1_max
-rw-r--r-- 1 root root 4096 Dec  3 11:39 temp1_max_hyst
-r--r--r-- 1 root root 4096 Dec  3 11:39 temp2_alarm
-r--r--r-- 1 root root 4096 Dec  3 11:39 temp2_input
-rw-r--r-- 1 root root 4096 Dec  3 11:39 temp2_max
-rw-r--r-- 1 root root 4096 Dec  3 11:39 temp2_max_hyst
--w------- 1 root root 4096 Dec  3 11:39 uevent
-rw-r--r-- 1 root root 4096 Dec  3 09:10 vrm

Kind regards,
Udo

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file

[Jean Delvare]

On Sun, 03 Dec 2006 11:41:38 +0100, Udo van den Heuvel wrote:
> Jean Delvare wrote:
> > On Sun, 03 Dec 2006 09:18:45 +0100, Udo van den Heuvel wrote:
> > > Also the temperature sensors are not shown.
> > 
> > Please provide the complete output of "sensors".
> 
> # sensors
> vt1211-isa-6000
> Adapter: ISA adapter
> VCore1:    +1.04 V  (min =  +1.13 V, max =  +1.27 V)   ALARM
> +5V:       +4.93 V  (min =  +4.74 V, max =  +5.26 V)
> +12V:     +12.05 V  (min = +11.38 V, max = +12.61 V)
> +3.3V:     +5.28 V  (min =  +3.14 V, max =  +3.47 V)   ALARM
> System:   4070 RPM  (min = 2580 RPM, div = 2)
> vid:      +1.850 V  (VRM Version 9.1)

No errors for temperatures, they are simply missing, so I guess there
are ignore statements for them in your configuration file. Can we
please see the vt1211 section of your configuration file? BTW, I hope
you started from the default configuration file shipped with lm_sensors
2.10.1 and not an older version, as it was significantly updated to
properly support the new Linux 2.6 version of the driver.

Please also provide the output of "sensors -c /dev/null".

> > What does "sensors -v" return?
> 
> sensors version 2.10.1 with libsensors version 2.10.1

So it's all OK.

> > Please provide a detailed listing (ls -l) of the files present in this
> > directory.
> 
> # pwd
> /sys/class/hwmon/hwmon0/device
> [root at recorder device]# ls -l
> total 0
> -r--r--r-- 1 root root 4096 Dec  3 11:38 alarms
> lrwxrwxrwx 1 root root    0 Dec  3 11:38 bus -> ../../../bus/platform
> -r--r--r-- 1 root root 4096 Dec  3 11:38 cpu0_vid
> lrwxrwxrwx 1 root root    0 Dec  3 11:38 driver -> ../../../bus/platform/drivers/vt1211
> -r--r--r-- 1 root root 4096 Dec  3 11:39 fan1_alarm
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 fan1_div
> -r--r--r-- 1 root root 4096 Dec  3 11:39 fan1_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 fan1_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 fan2_alarm
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 fan2_div
> -r--r--r-- 1 root root 4096 Dec  3 11:38 fan2_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 fan2_min
> lrwxrwxrwx 1 root root    0 Dec  3 11:39 hwmon:hwmon0 -> ../../../class/hwmon/hwmon0
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in0_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in0_input
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 in0_max
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 in0_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in1_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in1_input
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 in1_max
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 in1_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in2_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:38 in2_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in2_max
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in2_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in3_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:38 in3_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in3_max
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in3_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in4_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:38 in4_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in4_max
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in4_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in5_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:38 in5_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in5_max
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in5_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 modalias
> -r--r--r-- 1 root root 4096 Dec  3 11:38 name
> drwxr-xr-x 2 root root    0 Dec  3 09:02 power
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_channels_temp
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point1_pwm
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point1_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point2_pwm
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point2_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point3_pwm
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point3_temp
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point4_pwm
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point4_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_enable
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_freq
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_channels_temp
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point1_pwm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point1_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point2_pwm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point2_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point3_pwm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point3_temp
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point4_pwm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point4_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_enable
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_freq
> lrwxrwxrwx 1 root root    0 Dec  3 11:39 subsystem -> ../../../bus/platform
> -r--r--r-- 1 root root 4096 Dec  3 11:39 temp1_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 temp1_input
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 temp1_max
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 temp1_max_hyst
> -r--r--r-- 1 root root 4096 Dec  3 11:39 temp2_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 temp2_input
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 temp2_max
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 temp2_max_hyst
> --w------- 1 root root 4096 Dec  3 11:39 uevent
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 vrm

This looks all OK to me. As you can see the temperature files are
there.

-- 
Jean Delvare

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file

[Udo van den Heuvel]

Jean Delvare wrote:
> On Sun, 03 Dec 2006 11:41:38 +0100, Udo van den Heuvel wrote:
>> Jean Delvare wrote:
>>> On Sun, 03 Dec 2006 09:18:45 +0100, Udo van den Heuvel wrote:
>>>> Also the temperature sensors are not shown.
>>> Please provide the complete output of "sensors".
>> # sensors
>> vt1211-isa-6000
>> Adapter: ISA adapter
>> VCore1:    +1.04 V  (min =  +1.13 V, max =  +1.27 V)   ALARM
>> +5V:       +4.93 V  (min =  +4.74 V, max =  +5.26 V)
>> +12V:     +12.05 V  (min = +11.38 V, max = +12.61 V)
>> +3.3V:     +5.28 V  (min =  +3.14 V, max =  +3.47 V)   ALARM
>> System:   4070 RPM  (min = 2580 RPM, div = 2)
>> vid:      +1.850 V  (VRM Version 9.1)
> 
> No errors for temperatures, they are simply missing, 

As I wrote.

> are ignore statements for them in your configuration file. 

Sure. But not for the temperatures.

> please see the vt1211 section of your configuration file? 

I only have a vt1211 section:

##########################################################################

chip "vt1211-*" "vt8231-*"
#
#
#ignore in6
#set config 12
ignore in0
ignore in1
ignore temp1
ignore temp2
ignore temp4
ignore temp5
ignore temp6
ignore temp7
#ignore fan1
#ignore fan2
#
label in3 "+5V"
label in2 "VCore1"
label in5 "+3.3V"
label in4 "+12V"

label temp3 "CPU"

label fan2 "System"
label fan1 "CPU"
ignore fan1


#
# All voltage calculations have the form
# ((@ * 100) - 3) / (K * 95.8), (@ * K * 0.958) + .03
# where K = R2 / (R1 + R2).
# Use the following K values based on input voltage.
# This of course assumes the mobo has the resistors
# recommended by Via in the datasheet.
# Voltage K
# VCore 1.0
# 2.5 0.833333333
# 3.3 (in5 internal) 0.62962963
# 3.3 (3.3V ext.) 0.595238095
# 5.0 0.4
# 12.0 0.175438596
# ok, whatever ... I fudged these below to get them to agree with the values
# that were shown in bios.

# VCORE1
compute in2 ((@ * 100) - 3) / (1.0000 * 95.8), (@ * 1.0000 * 0.958) + .03
# +3.3V
compute in5 ((@ * 100) - 3) / (0.6296 * 95.8), (@ * 0.6296 * 0.958) + .03
# +12v
compute in4 ((@ * 100) - 3) / (0.175438596 * 95.8), (@ * 0.175438596 *
0.958) +
               .03
# +5V
compute in3 ((@ * 100) - 3) / (0.4 * 95.8), (@ * 0.4 * 0.958) + .03

set vrm 9.1
set in2_min 1.2 * 0.95
set in2_max 1.2 * 1.05
set in3_min 5.0 * 0.95
set in3_max 5.0 * 1.05
set in4_min 12.0 * 0.95
set in4_max 12.0 * 1.05
set in5_min 3.3 * 0.95
set in5_max 3.3 * 1.05
# compute temp3 (@ - 65) / 0.9686, (@ * 0.9686) + 65
# Guido Brunner found this formula to copy with the non-
# linearity in temp3
#
# compute temp3 (@*@*0.0046)-(@*0.088)-0.748, (@*0.9686)+65
compute temp3 @ * 0.9756097 - 73.439, (@ + 73.439) / 0.9756097

set temp3_hyst 65
set temp3_over 70
# fan2 (system fan)
set fan1_div 2
set fan2_div 2
set fan1_min 1500
set fan2_min 1500

> BTW, I hope
> you started from the default configuration file shipped with lm_sensors
> 2.10.1 and not an older version, as it was significantly updated to
> properly support the new Linux 2.6 version of the driver.

And go though all of that config stuff that does not make sense for my
board?
I just see that temp sensors might have been renumbered?
It looks like I was using temp3 but now they are called temp1 and temp2.

> This looks all OK to me. As you can see the temperature files are
> there.

Indeed.
Temp3 was renamed to temp1.
Thanks!

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file

[Jean Delvare]

On Sun, 03 Dec 2006 12:13:50 +0100, Udo van den Heuvel wrote:
> Jean Delvare wrote:
> > are ignore statements for them in your configuration file. 
> 
> Sure. But not for the temperatures.
> (...)
> chip "vt1211-*" "vt8231-*"
> #
> #
> #ignore in6
> #set config 12
> ignore in0
> ignore in1
> ignore temp1
> ignore temp2
> ignore temp4
> ignore temp5
> ignore temp6
> ignore temp7

"No, Sir, I don't have ignore statements for temperatures. I swear!"

Tsss...

> > BTW, I hope
> > you started from the default configuration file shipped with lm_sensors
> > 2.10.1 and not an older version, as it was significantly updated to
> > properly support the new Linux 2.6 version of the driver.
> 
> And go though all of that config stuff that does not make sense for my
> board?

Or you can be smart and only copy the vt1211 section. It's up to you.

> I just see that temp sensors might have been renumbered?

Yes, they have been, and the values have been changed as well, so the
compute statements are different.

-- 
Jean Delvare

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file

[Udo van den Heuvel]

Jean Delvare wrote:
> On Sun, 03 Dec 2006 12:13:50 +0100, Udo van den Heuvel wrote:
>> Jean Delvare wrote:
>>> are ignore statements for them in your configuration file. 
>> Sure. But not for the temperatures.
>> (...)
>> chip "vt1211-*" "vt8231-*"
>> #
>> #
>> #ignore in6
>> #set config 12
>> ignore in0
>> ignore in1
>> ignore temp1
>> ignore temp2
>> ignore temp4
>> ignore temp5
>> ignore temp6
>> ignore temp7
> 
> "No, Sir, I don't have ignore statements for temperatures. I swear!"
> 
> Tsss...

As you can see the situation was edited for temp3 which was the cpu temp
sensor. All other temp sesnors are of no interest at all.
So my answer should be read as 'not for the temperatures that are
interesting'. The Tsss could show a lack of something.
You are moving way off the focus of this quest which is very clear.

>> I just see that temp sensors might have been renumbered?
> 
> Yes, they have been, and the values have been changed as well, so the
> compute statements are different.

That's very nice to do! Why oh why keep something that works?
Where can I find the very simple knowledge to build new compute
statments, my only interesting hobby?

Udo

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file

[Jean Delvare]

Hi Udo,

On Sun, 03 Dec 2006 13:33:59 +0100, Udo van den Heuvel wrote:
> Jean Delvare wrote:
> > On Sun, 03 Dec 2006 12:13:50 +0100, Udo van den Heuvel wrote:
> >> Jean Delvare wrote:
> >>> are ignore statements for them in your configuration file. 
> >> Sure. But not for the temperatures.
> >> (...)
> >> chip "vt1211-*" "vt8231-*"
> >> #
> >> #
> >> #ignore in6
> >> #set config 12
> >> ignore in0
> >> ignore in1
> >> ignore temp1
> >> ignore temp2
> >> ignore temp4
> >> ignore temp5
> >> ignore temp6
> >> ignore temp7
> > 
> > "No, Sir, I don't have ignore statements for temperatures. I swear!"
> > 
> > Tsss...
> 
> As you can see the situation was edited for temp3 which was the cpu temp
> sensor. All other temp sesnors are of no interest at all.
> So my answer should be read as 'not for the temperatures that are
> interesting'.

As the person asking for help here, it's your job to make complete
answers, that don't require me to "read as". I am no seer.

> The Tsss could show a lack of something.
> You are moving way off the focus of this quest which is very clear.

It looks like you are missing a very important point here. You are the
one asking for help. I am the one providing the help FOR FREE, on my
SPARE TIME. The least you can do is make it easy for me, provide
correct answers to my questions, and assist as much as you can, instead
of waiting for me to do all the work based on incomplete information.

Your question is NOT very clear. If it were, it would have been
answered already. First of all you omitted to tell us that you were
migrating from a different system where the vt1211 was working. At this
point I still don't know what was that system. 2.4 kernel? Or 2.6 with
Lars Ekman's unofficial driver?

> That's very nice to do! Why oh why keep something that works?

Why did you upgrade your system if it was working?

Our main point with that change, as you can easily imagine, was to
gratuitously break as many user systems as possible. And make them
angry after us, to trigger many complaints on this list. If it works
well, we'll make sure to do it again with every new kernel version,
it'll be great fun.

(Seriously, if you're not happy with what we do, feel tree to join the
development team and show us how to make things better. I'm eager to
improve. There's plenty of work for everyone interested.)

> Where can I find the very simple knowledge to build new compute
> statments, my only interesting hobby?

Start from etc/sensors.conf.eg in lm_sensors 2.10.1, as I suggested
already. Then read the vt1211 driver documentation
(Documentation/hwmon/vt1211 in the kernel tree), which Juerg Haefliger
was nice enough to update and extend. Most probably, you don't actually
need to change the formula, just replace "compute temp3" by "compute
temp1".

-- 
Jean Delvare

[lm-sensors] new vt1211 driver: Can't access procfs/sysfs file

[Udo van den Heuvel]

Jean Delvare wrote:
>> The Tsss could show a lack of something.
>> You are moving way off the focus of this quest which is very clear.
> 
> It looks like you are missing a very important point here. You are the
> one asking for help. I am the one providing the help FOR FREE, on my
> SPARE TIME. The least you can do is make it easy for me, provide
> correct answers to my questions, and assist as much as you can, instead
> of waiting for me to do all the work based on incomplete information.

Sure. I agree completely.
On the other hand you can be sure that in most sensors.conf there will
be ignore statemnts so that the abuser is not overwhelmed with sensors
giving nonsense values.
The sensors that /made/ sense had no ignore statments in my config.
Of coure I was not so clear.

> point I still don't know what was that system. 2.4 kernel? Or 2.6 with
> Lars Ekman's unofficial driver?

2.6 on FC6 with Lars' driver (and various changes in the recent past).

> Why did you upgrade your system if it was working?

To keep up. It is routine. Vt1211 would be one of the reasons to
actually gain something. `Official` support. No more patching to make
things work.

> (Seriously, if you're not happy with what we do, feel tree to join the
> development team and show us how to make things better. I'm eager to
> improve. There's plenty of work for everyone interested.)

lm-sensors was not the cause. it was the new driver and associated
expectations ('drop-in replacement')

>> Where can I find the very simple knowledge to build new compute
>> statments, my only interesting hobby?

[..]

> Most probably, you don't actually
> need to change the formula, just replace "compute temp3" by "compute
> temp1".

Done.