Dynamix - System Temp


Recommended Posts

I like to make a separate topic for the Dynamix system temp plugin and not 'pollute' the webGui discussion, after all system temp is an optional plugin which can be added.

 

I would advice people to look first at the wiki. This is a general guide which can be used as well for people having SimpleFeatures or Dynamix installed (thanks RobJ).

 

The main thing to remember is that the correct labels are used by lm-sensors. The system temp script looks for:

 

CPU Temp - This is the processor temperature

MB Temp - This is the motherboard temperature

 

Any questions or solutions can be placed in this topic, this way it stays grouped together and may benefit others.

 

Link to comment

Anyone found a way to use lm-sensors on X9SCM-F but with unRAID running under ESXi?

 

In that case modprobe w83627ehf complains 'no such device found'. Apparently such devices are not passed-through to a VM.

 

I tried with other modules, but they do not work either.

 

 

Maybe the only way is to read system temp via IPMI linux tools?

 

Edit:

I found this: http://www.thomas-krenn.com/en/wiki/Supermicro_X9SCM-F_Motherboard

 

We would require FreeIPMI package then and modified/alternative version  ;)  of System Temp plugin for IPMI.

Link to comment

Anyone found a way to use lm-sensors on X9SCM-F but with unRAID running under ESXi?

 

In that case modprobe w83627ehf complains 'no such device found'. Apparently such devices are not passed-through to a VM.

 

I tried with other modules, but they do not work either.

 

 

Maybe the only way is to read system temp via IPMI linux tools?

 

Edit:

I found this: http://www.thomas-krenn.com/en/wiki/Supermicro_X9SCM-F_Motherboard

 

We would require FreeIPMI package then and modified/alternative version  ;)  of System Temp plugin for IPMI.

I didn't get the X9SCM-F working under ESXi, but I did get it working on bare metal using the following steps:

 

 

My go file addition:

 

    modprobe w83627ehf

    cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d

    cp /boot/custom/sensors.d/sensors.conf /etc/sensors3.conf

 

My /boot/custom/sensors.d/sensors.conf file:

 

    chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"

 

 

    label in0 "Vcore"

    label in2 "AVCC"

    label in3 "+3.3V"

    label in7 "3VSB"

    label in8 "Vbat"

    label temp2 "CPU Temp"

    label temp1 "MB Temp"

 

 

    set in2_min  3.3 * 0.90

    set in2_max  3.3 * 1.10

    set in3_min  3.3 * 0.90

    set in3_max  3.3 * 1.10

    set in7_min  3.3 * 0.90

    set in7_max  3.3 * 1.10

    set in8_min  3.0 * 0.90

    set in8_max  3.3 * 1.10

Link to comment

ogi->

As stated before that only works on bare-metal X9SCM-F.

 

I just compiled freeIPMI package on separate Slackware VM and it works.

I can only hope bonienl would be interested in adding that option to his plugin.

 

That would require adding freeIPMI package and then parsing its output //see attachment//.

 

1-7-2014_4-23-31_PM.png.7c40da436ad1082c72c2dedd0c2b8ab3.png

Link to comment

ogi->

As stated before that only works on bare-metal X9SCM-F.

 

I just compiled freeIPMI package on separate Slackware VM and it works.

I can only hope bonienl would be interested in adding that option to his plugin.

 

That would require adding freeIPMI package and then parsing its output //see attachment//.

 

For the moment I stick to the lm-sensors approach, but keep this open for future enhancement.

Link to comment

Yes, IPMI version only for those who have server-grade boards equipped with it. If you want to tackle it in the future, just let me know, I can easily test your code.

I believe the user base is quite big and growing as more and more go with Supermicro boards and ESXi.

 

I'm curious whether lm-sensors work in KVM/XEN unRAID (if the VM has access to the MB chip)?

 

Anyway, thanks for your efforts!

 

Link to comment

I have a bit of an issue with the System temp set up, went through the wiki to add the drivers etc, but my sensors output (w83627ehf) for temp 1 & 2 both read -48C.... Not sure why this is, but if I use the temp1 & temp2 its kind of a waste of time...

With Dual chips, I also get  coretemp-ISA-0001 & 0002 consisting of a separate temp for each or the 4 cores of the quad core chips. I have yet to figure out how to get this working with the MB / CPU

 

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +38.0 C  (high = +82.0 C, crit = +100.0 C)

Core 1:      +50.0 C  (high = +82.0 C, crit = +100.0 C)

Core 2:      +42.0 C  (high = +82.0 C, crit = +100.0 C)

Core 3:      +53.0 C  (high = +82.0 C, crit = +100.0 C)

 

coretemp-isa-0001

Adapter: ISA adapter

Core 0:      +53.0 C  (high = +82.0 C, crit = +100.0 C)

Core 1:      +53.0 C  (high = +82.0 C, crit = +100.0 C)

Core 2:      +51.0 C  (high = +82.0 C, crit = +100.0 C)

Core 3:      +49.0 C  (high = +82.0 C, crit = +100.0 C)

 

I will post the further output with the w83627 chip added once I get home this evening, as i didnt bother with further adding the temp's due to the output

Link to comment

so here's my output after running sensors-detect

 

 

Driver `to-be-written':

  * ISA bus, address 0xca2

    Chip `IPMI BMC KCS' (confidence: 8)

 

Driver `coretemp':

  * Chip `Intel digital thermal sensor' (confidence: 9)

 

Driver `w83793':

  * Bus `SMBus I801 adapter at 1100'

    Busdriver `i2c_i801', I2C address 0x2f

    Chip `Winbond W83793R/G' (confidence: 8)

 

Driver `w83627hf':

  * ISA bus, address 0x295

    Chip `Winbond W83627HF/F/HG/G Super IO Sensors' (confidence: 9)

 

Driver `i5k_amb':

  * Chip `Intel AMB FB-DIMM thermal sensor' (confidence: 9)

 

Note: there is no driver for IPMI BMC KCS yet.

Check http://www.lm-sensors.org/wiki/Devices for updates.

 

Warning: the required module w83793 is not currently installed

on your system. If it is built into the kernel then it's OK.

Otherwise, check http://www.lm-sensors.org/wiki/Devices for

driver availability.

 

Warning: the required module i5k_amb is not currently installed

on your system. If it is built into the kernel then it's OK.

Otherwise, check http://www.lm-sensors.org/wiki/Devices for

driver availability.

 

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): no

To load everything that is needed, add this to one of the system

initialization scripts (e.g. /etc/rc.d/rc.local):

 

#----cut here----

# Chip drivers

modprobe coretemp

modprobe w83627hf

/usr/bin/sensors -s

#----cut here----

 

and once modprob W83627hf is added:

 

root@Tower:/mnt/cache/appdata# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +52.0 C  (high = +82.0 C, crit = +100.0 C)

Core 1:      +60.0 C  (high = +82.0 C, crit = +100.0 C)

Core 2:      +45.0 C  (high = +82.0 C, crit = +100.0 C)

Core 3:      +62.0 C  (high = +82.0 C, crit = +100.0 C)

 

coretemp-isa-0001

Adapter: ISA adapter

Core 0:      +63.0 C  (high = +82.0 C, crit = +100.0 C)

Core 1:      +63.0 C  (high = +82.0 C, crit = +100.0 C)

Core 2:      +63.0 C  (high = +82.0 C, crit = +100.0 C)

Core 3:      +60.0 C  (high = +82.0 C, crit = +100.0 C)

 

w83627hf-isa-0290

Adapter: ISA adapter

in0:          +4.08 V  (min =  +0.00 V, max =  +4.08 V)

in1:          +4.08 V  (min =  +0.00 V, max =  +4.08 V)

in2:          +4.08 V  (min =  +2.82 V, max =  +3.79 V)  ALARM

in3:          +3.04 V  (min =  +4.06 V, max =  +2.03 V)  ALARM

in4:          +3.14 V  (min =  +4.08 V, max =  +4.08 V)  ALARM

in5:          +3.17 V  (min =  +3.76 V, max =  +2.54 V)  ALARM

in6:          +3.20 V  (min =  +4.08 V, max =  +4.08 V)  ALARM

in7:          +3.36 V  (min =  +4.08 V, max =  +3.92 V)  ALARM

in8:          +3.18 V  (min =  +4.08 V, max =  +3.57 V)  ALARM

fan1:          0 RPM  (min =    0 RPM, div = 2)

fan2:          0 RPM  (min =    0 RPM, div = 2)

fan3:          0 RPM  (min =    0 RPM, div = 2)

temp1:        -48.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor

temp2:        -48.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor

temp3:        -48.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor

cpu0_vid:    +1.419 V

beep_enable: enabled

Link to comment

Anyone ever got lmsensors working with a HP Microserver?

 

I've attempted to get it working several times, but always given up without success. Googled lmsensors and followed various instructions, but always without success.

 

If anyone has got it working i would be most grateful for some pointers.

Link to comment

Anyone ever got lmsensors working with a HP Microserver?

 

I've attempted to get it working several times, but always given up without success. Googled lmsensors and followed various instructions, but always without success.

 

If anyone has got it working i would be most grateful for some pointers.

Same here. I think you need IPMI support to read the hardware monitoring data beyond CPU temp and I'm not sure if that works with the Dynamix system temp feature.

Link to comment

Yes, IPMI version only for those who have server-grade boards equipped with it. If you want to tackle it in the future, just let me know, I can easily test your code.

I believe the user base is quite big and growing as more and more go with Supermicro boards and ESXi.

 

+1

(on all counts, including testing!)

Link to comment

Is it possible to add the coretemp-ISA adapter to the webpage? I haven't been able to re-name any of the core's so it will show up....

 

Renaming is done using the sensors.conf file, perhaps you can post what you have tried so far.

 

I have added :

 

chip "coretemp-isa-0000"

 

label Core 1 "MB Temp"

 

chip "coretemp-isa-0000"

 

label Core 0 "CPU Temp"

 

and added the Copy command to my go file. I beleive the issue is that the Core's were previously renamed somewhere else as they include a space which is not normal....

 

Link to comment

When you do the sensors command from a telnet session, do you see the modified names ?

 

Sensors output show's

 

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +52.0 C  (high = +82.0 C, crit = +100.0 C)
Core 1:       +60.0 C  (high = +82.0 C, crit = +100.0 C)
Core 2:       +45.0 C  (high = +82.0 C, crit = +100.0 C)
Core 3:       +62.0 C  (high = +82.0 C, crit = +100.0 C)

coretemp-isa-0001
Adapter: ISA adapter
Core 0:       +63.0 C  (high = +82.0 C, crit = +100.0 C)
Core 1:       +63.0 C  (high = +82.0 C, crit = +100.0 C)
Core 2:       +63.0 C  (high = +82.0 C, crit = +100.0 C)
Core 3:       +60.0 C  (high = +82.0 C, crit = +100.0 C)

w83627hf-isa-0290
Adapter: ISA adapter
in0:          +4.08 V  (min =  +0.00 V, max =  +4.08 V)
in1:          +4.08 V  (min =  +0.00 V, max =  +4.08 V)
in2:          +4.08 V  (min =  +2.82 V, max =  +3.79 V)  ALARM
in3:          +3.04 V  (min =  +4.06 V, max =  +2.03 V)  ALARM
in4:          +3.14 V  (min =  +4.08 V, max =  +4.08 V)  ALARM
in5:          +3.17 V  (min =  +3.76 V, max =  +2.54 V)  ALARM
in6:          +3.20 V  (min =  +4.08 V, max =  +4.08 V)  ALARM
in7:          +3.36 V  (min =  +4.08 V, max =  +3.92 V)  ALARM
in8:          +3.18 V  (min =  +4.08 V, max =  +3.57 V)  ALARM
fan1:           0 RPM  (min =    0 RPM, div = 2)
fan2:           0 RPM  (min =    0 RPM, div = 2)
fan3:           0 RPM  (min =    0 RPM, div = 2)
temp1:        -48.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor
temp2:        -48.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
temp3:        -48.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
cpu0_vid:    +1.419 V
beep_enable: enabled

 

I removed the W83627 chip as the temp's shown are incorrect / not useful since they never change from -48. When I try and rename the coretemp-ISA cores it gives me an error unexpected space.

Link to comment

I didn't get the X9SCM-F working under ESXi, but I did get it working on bare metal using the following steps:

 

 

My go file addition:

 

    modprobe w83627ehf

    cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d

    cp /boot/custom/sensors.d/sensors.conf /etc/sensors3.conf

 

My /boot/custom/sensors.d/sensors.conf file:

 

    chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"

 

 

    label in0 "Vcore"

    label in2 "AVCC"

    label in3 "+3.3V"

    label in7 "3VSB"

    label in8 "Vbat"

    label temp2 "CPU Temp"

    label temp1 "MB Temp"

 

 

    set in2_min  3.3 * 0.90

    set in2_max  3.3 * 1.10

    set in3_min  3.3 * 0.90

    set in3_max  3.3 * 1.10

    set in7_min  3.3 * 0.90

    set in7_max  3.3 * 1.10

    set in8_min  3.0 * 0.90

    set in8_max  3.3 * 1.10

 

ogi - I have this same board and tried your same steps here and I am not getting the temps.  I guess I do not fully understand the label command in the conf file.  Here is what I get when I run sensors from the terminal line:

 

nct6776-isa-0a30

Adapter: ISA adapter

in0:          +0.82 V  (min =  +0.60 V, max =  +1.49 V)

in1:          +1.87 V  (min =  +1.62 V, max =  +1.99 V)

in2:          +3.38 V  (min =  +2.96 V, max =  +3.63 V)

in3:          +3.36 V  (min =  +2.96 V, max =  +3.63 V)

in4:          +1.52 V  (min =  +1.35 V, max =  +1.65 V)

in5:          +1.25 V  (min =  +1.13 V, max =  +1.38 V)

in7:          +3.34 V  (min =  +2.96 V, max =  +3.63 V)

in8:          +3.15 V  (min =  +2.96 V, max =  +3.63 V)

fan1:            0 RPM  (min =  300 RPM)  ALARM

fan2:        1069 RPM  (min =  300 RPM)

fan3:        1211 RPM  (min =  300 RPM)

fan4:        1214 RPM  (min =  300 RPM)

fan5:        1187 RPM  (min =  300 RPM)

SYSTIN:        +30.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor

CPUTIN:        +31.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor

AUXTIN:        +2.0 C    sensor = thermistor

PECI Agent 0:  +32.5 C  (high = +95.0 C, hyst = +92.0 C)

cpu0_vid:    +0.000 V

intrusion0:  OK

intrusion1:  ALARM

 

Is the first paramter in label to identify the item and the second is to rename it?

 

Need help in understanding this.

 

StanC

Link to comment

When you do the sensors command from a telnet session, do you see the modified names ?

 

Sensors output show's

 

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +52.0 C  (high = +82.0 C, crit = +100.0 C)
Core 1:       +60.0 C  (high = +82.0 C, crit = +100.0 C)
Core 2:       +45.0 C  (high = +82.0 C, crit = +100.0 C)
Core 3:       +62.0 C  (high = +82.0 C, crit = +100.0 C)

coretemp-isa-0001
Adapter: ISA adapter
Core 0:       +63.0 C  (high = +82.0 C, crit = +100.0 C)
Core 1:       +63.0 C  (high = +82.0 C, crit = +100.0 C)
Core 2:       +63.0 C  (high = +82.0 C, crit = +100.0 C)
Core 3:       +60.0 C  (high = +82.0 C, crit = +100.0 C)

w83627hf-isa-0290
Adapter: ISA adapter
in0:          +4.08 V  (min =  +0.00 V, max =  +4.08 V)
in1:          +4.08 V  (min =  +0.00 V, max =  +4.08 V)
in2:          +4.08 V  (min =  +2.82 V, max =  +3.79 V)  ALARM
in3:          +3.04 V  (min =  +4.06 V, max =  +2.03 V)  ALARM
in4:          +3.14 V  (min =  +4.08 V, max =  +4.08 V)  ALARM
in5:          +3.17 V  (min =  +3.76 V, max =  +2.54 V)  ALARM
in6:          +3.20 V  (min =  +4.08 V, max =  +4.08 V)  ALARM
in7:          +3.36 V  (min =  +4.08 V, max =  +3.92 V)  ALARM
in8:          +3.18 V  (min =  +4.08 V, max =  +3.57 V)  ALARM
fan1:           0 RPM  (min =    0 RPM, div = 2)
fan2:           0 RPM  (min =    0 RPM, div = 2)
fan3:           0 RPM  (min =    0 RPM, div = 2)
temp1:        -48.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor
temp2:        -48.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
temp3:        -48.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
cpu0_vid:    +1.419 V
beep_enable: enabled

 

I removed the W83627 chip as the temp's shown are incorrect / not useful since they never change from -48. When I try and rename the coretemp-ISA cores it gives me an error unexpected space.

 

Clowrym...

 

I've got the same MB as you do.  I found this post...  http://www.lm-sensors.org/wiki/Configurations/SuperMicro/X7DB8

 

But don't know how to translate that into what we need.  I've tried loading the sensors listed... w83627hf-isa-0290 and w83793-i2c-0-2f but they are not found.

 

Any ideas???

Link to comment
  • 3 weeks later...

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  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.