Jump to content

I knew Mandrake was hot... but


Recommended Posts

Everything else with gkrellm seems to be reporting correctly but the temperatures. From past releases / experiences, temp 2 should be somewhere around 131 degrees --- about what the bios reports during a restart.


The attached screenshot shows temps of 721, 1063, and 482 degrees fahrenheit, but there is no smoke emanating from my box ;)


Installed are gkrellm and lm_sensors. Ran sensors-detect and also added what it told me to in modules.conf. Running the kernel.


I am thinking I need to set the "factor" and "offset" but how do I figure that out ???




Link to comment
Share on other sites

gkrellm doesn't use the lm_sensors library functions to adjust the raw sensors data for display so, yes, you have to set the factor and/or offset values manually. Without knowing what sensor chip set you have I can only give you the general strategy.


First, use the sensors(1) command to check what the lm_sensors package is reporting. If the values look good then you can proceed to the next step. If not, you'll have to do some research on your motherboard and sensor chips to determine if sensors-detect has given you the correct values, or if there are special options that may have to be set for your particular system. In my case, my ASUS A7V600 has an it87 chip, but I have to set the temperature sensors' type to "2", for themistor.


Once you know your sensor chip type, look in /etc/sensors.conf in the section for your chip for compute temp lines. These have two fomulas, one for reading and one for writing values. You have to simplify the read formula into a factor and offset for gkrellm. In my case, I take the formla (@+128)/3 and derive a factor of 0.3333 and an offset of 42.660.

Link to comment
Share on other sites

Excellant reply Kjel Oslund, but seems I have one of those that hasn't been converted yet. This is on a SOYO K7VTA Pro socket A board.


$ sensors


Adapter: ISA adapter

CPU core:  +1.72 V  (min =  +1.99 V, max =  +2.49 V) ALARM

+2.5V:  +2.45 V  (min =  +2.24 V, max =  +2.74 V)

I/O:    +3.35 V  (min =  +2.95 V, max =  +3.62 V)

+5V:    +4.79 V  (min =  +4.47 V, max =  +5.49 V)

+12V:  +11.92 V  (min = +10.79 V, max = +13.18 V)

CPU Fan:  6081 RPM  (min = 3000 RPM, div = 2)

P/S Fan:  0 RPM  (min = 3000 RPM, div = 2)

SYS Temp:  +37.1°C  (high = +45°C, hyst = +40°C)

CPU Temp:  +56.6°C  (high = +60°C, hyst = +55°C)

SBr Temp:  +25.2°C  (high = +65°C, hyst = +60°C)

(56 degrees C is more realistic, yes?)

chip "via686a-*"


# VIA is very specific about the voltage sensor inputs, and our labels

# reflect what they say.  Unfortunately, they are not at all specific about

# how to convert any of the register values to real units.  Fortunately,

# Jonathan Yew <j.teh@iname.com> and Alex van Kaam <darkside@chello.nl>

# came through with some data for temp conversion and formulae for voltage

# conversion. However, the conversions should be regarded as our best guess-



# On the Tyan S1598, the 2.5V sensor reads 0 and is not displayed in the BIOS.

# Linas Vepstas <linas@linas.org> reports that this sensor shows nothing of

# interest on the Abit KA7 (Athlon), and is also not displayed in the BIOS.

# Likewise, Johannes Drechsel-Burkhard <jdb@chello.at> reports that this

# sensor is unavailable in the BIOS of his MSI K7T Pro (Thunderbird).  So,

# if you have one of these boards you may want to uncomment the 'ignore 2.5V'

# line below.


    label "2.0V" "CPU core"

    label "2.5V" "+2.5V"

    #ignore "2.5V"

    label "3.3V" "I/O"

    label "5.0V" "+5V"

    label "12V" "+12V"


    label fan1  "CPU Fan"

    label fan2  "P/S Fan"


# VIA suggests that temp3 is an internal temp sensor for the 686a.  However,

# on the Tyan S1598 as well as the Abit KA7 (Athalon), the absolute values

# of the readings from that sensor are not valid.  The readings do seem to

# correlate with temp changes, but the conversion factor may be quite

# different from temp1 & temp2 (as noted above, VIA has not provided

# conversion info).  So, you may wish to 'ignore temp3'.


# Johannes Drechsel-Burkhard <jdb@chello.at> notes that on his MSI K7T Pro,

# temp1 is the CPU temp and temp2 is the SYS temp.


    label temp1 "SYS Temp"

    label temp2 "CPU Temp"

    label temp3 "SBr Temp"

    #ignore temp3


# Set your CPU core limits here.  For the other voltage sensors, the

# built-in defaults should be fine.


    set in0_min 2.0

    set in0_max 2.5


# Set your temp limits here.  Remember, 'tempX_over' is the temp at which an

# alarm is triggered, and 'tempX_hyst' is the temp at which an alarm turns off.

# Setting tempX_hyst to a few degrees below the corresponding tempX_over

# prevents an oscillation between alarm on and off states.  This kind of

# oscillation is known as hyteresis, thus the name.  (You typically get the

# most serious and troublesome hysteresis when a sensor triggers something to

# reduce the temp, thus creating a negative feedback loop.  Even without that,

# we would still get some oscillation when the temp hovers around the limit

# due to noise.)


    set temp1_hyst 40

    set temp1_over 45

    set temp2_hyst 55

    set temp2_over 60

    set temp3_hyst 60

    set temp3_over 65


# You could set your fan limits too, but the defaults should be fine.


    #set fan1_min 5000

    #set fan2_min 5000


# For at least one Tyan S1598, the following corrections make the sensors

# readings more in-line with the BIOS readings on boot.  Try these, and

# adjust as necessary.


  #compute "2.0V" 1.02*@ ,  @/1.02

  #compute "3.3V" 1.02*@  ,  @/1.02

  #compute "5.0V" 1.009*@  ,  @/1.009

  #compute "12V" 1.04*@ ,  @/1.04

(that was it for this chip)

Link to comment
Share on other sites

Hum.. It looks like sensors is getting the right value: 56.6C is 133.88F and close to what you are expecting.


Take a look at the raw data from the driver. You can find it under /sys/bus/i2c/drivers/via686a* (driver name may be uppercase). There will be a symbolic link in that directory to another directory containing /proc type files for all sensor chip registers. You'll probably see ones for temp_input[123]. cat these to see the register values.


On my system, gkrellm shows the raw values for temperature sensors and sensors(1) shows the value processed through the compute values. It will be interesting to see what you get.

Link to comment
Share on other sites

me have same prob :angry:

[root@localhost root]# cat /sys/devices/pci0000:00/0000:00:11.0/i2c-0/0-004c/temp_input1


[root@localhost root]# cat /sys/devices/pci0000:00/0000:00:11.0/i2c-0/0-004c/temp_input2


[root@localhost root]# ls /sys/devices/pci0000:00/0000:00:11.0/i2c-0/0-0050

[root@localhost root]# sensors
Adapter: SMBus Via Pro adapter at 5000
Memory type:            DDR SDRAM DIMM
Memory size (MB):       256

Adapter: SMBus Via Pro adapter at 5000
Memory type:            DDR SDRAM DIMM
Memory size (MB):       128

Adapter: SMBus Via Pro adapter at 5000
Memory type:            DDR SDRAM DIMM
Memory size (MB):       128

Adapter: SMBus Via Pro adapter at 5000
M/B Temp:    +56°C  (low  =    +0°C, high =   +70°C)
CPU Temp:  +72.5°C  (low  =  +0.0°C, high = +70.0°C)   ALARM
M/B Crit:   +110°C  (hyst =  +100°C)
CPU Crit:   +120°C  (hyst =  +110°C)


me not asking for help :cheesy: me watching this thread though :cheeky:

Edited by bvc
Link to comment
Share on other sites

I believe we are getting to the root of this problem. Seems something just may be off a decimal point or two.

# cat /sys/devices/platform/i2c-0/0-6000/temp_input1 35800
# cat /sys/devices/platform/i2c-0/0-6000/temp_input2 53200
# cat /sys/devices/platform/i2c-0/0-6000/temp_input3 24500

and IF we change gkrellm to Celsius degrees.

temp1 358
temp2 532
temp3 245

which all looks like what sensors is reporting:

SYS Temp:  +35.8°C 
CPU Temp:  +53.2°C 
SBr Temp:  +24.5°C

Link to comment
Share on other sites

NO... that was too easy. Although I get normal looking readings now and consider mine fixed as well. :D


But did you see that formula in the gkrellm docs to figure this out ?:

                  s - S1     t - T1
                  ------  =  ------
                 S2 - S1    T2 - T1

                                T2 - T1     S2*T1 - S1*T2
                       t  = s * -------  +  -------------
                                S2 - S1         S2 - S1

                         T2 - T1                S2*T1 - S1*T2
               factor =  -------      offset =  -------------
                         S2 - S1                   S2 - S1


THANX Kjel Oslund

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...