about tempX information (fwd)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ah, that's an old FAQ.  We report what the chip reports.  Bios' usually 
add some 'fudge factor' to try to compensate for some condition (which 
may or may exist!) like the temp sensor probe being a few milimeters 
away from the CPU.  Read the FAQ's, docs, and perhaps even the datasheet 
of the chip in question for more info.


Phil


Miquel Rubio wrote:

> ok, my problem is that "actual reading" is not the same temperature as 
> the reading I get from MS Windows or the BIOS, and I don't know how to 
> adjust it. I've read sensors.conf explanations, but... I don't 
> understand it.
>
>
> Thank you.
>
> Philip Edelbrock wrote:
>
>>
>>
>> The numbers are 'max alarm limit', 'min alarm limit' and 'actual 
>> reading'.  For more details on this chip, take a look at 
>> doc/chips/via686a.  Also take a look at the other documention which 
>> describes how the files in /proc/sys/dev/sensors works.  Normally, 
>> though, user-space apps will want to access the files using 
>> libsensors. Or, if you just want intelligable text output, run 
>> 'sensors'.
>>
>>
>> Phil
>>
>>> I've installed lm-sensors 2.6.5 and I use i2c-isa and via686a modules.
>>>
>>> I get:
>>>
>>> S01:/proc# cat /proc/sys/dev/sensors/via686a-isa-6000/temp2
>>> 59.9 55.1 41.3
>>> S01:/proc# cat /proc/sys/dev/sensors/via686a-isa-6000/temp1
>>> 44.9 39.9 45.3
>>> S01:/proc# cat /proc/sys/dev/sensors/via686a-isa-6000/temp3
>>> 65.4 59.9 26.4
>>>
>>>
>>> What is the meaning of thins numbers ?
>>>
>>>
>>>
>>> Thank you
>>>
>>>  
>>>
>>
>>
>



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux