Re: Supermicro X7DBU configuration

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

 



On 12/17/2014 02:08 AM, Jean Delvare wrote:
Hi Sean,

On Tue, 16 Dec 2014 10:18:40 -0500, Sean M. O'Brien wrote:
Hi. Does anyone have a sensors3.conf for a Supermicro X7DBU chassis? I am in the process of setting this up but without the appropriate config file I am not getting fan readings. This chassis has 8 fans with 1~6 being chassis fans and 7~8 labelled as CPU fans, even though all fans sit in series across the front of the 1U chassis. I currently have 4 extremely noisy 4-pin fans connected to 1,2,3 and 7, and have no ability to control these. They are running at 10K rpm constantly (according to the bios), with a ramp up to 16K when the server starts up. My goal is to get some control of these using pwmconfig, but for now I can’t read the fan speeds at all in Ubuntu 14.04 server edition.

Thanks for any assistance.

As already pointed out by Guenter, IPMI would likely serve you better
on this board than native drivers (and you can't mix.) However if you
want to go the native driver route...

Pertinent output from sensors-detect:
Driver `w83793':
   * Bus `SMBus I801 adapter at 1100'
     Busdriver `i2c_i801', I2C address 0x2f
     Chip `w83793' (confidence: 6)

This chip is missing from the output of "sensors" below. You need to
figure out why. Is the w83793 kernel module available on your system?
Is it loaded? If not, what happens if you try to load it manually? Any
error message in the kernel log? The fans are certainly connected to
that chip.


Hardware monitoring might be disabled for this chip. I have seen this
with other Supermicro boards; on mine, for example, they use the second
SuperIO chip only for additional serial ports. The kernel log might
give a hint if that is the case.

Another option might be that the missing chip is the one used for hardware
monitoring but its register space is reserved by ACPI. That would explain
why the chip listed below doesn't report much useful data. Again, the
kernel log should give a hint.

Guenter


Output from sensors:

w83627hf-isa-0290
Adapter: ISA adapter
Vcore1:       +3.90 V  (min =  +0.82 V, max =  +1.34 V)  ALARM
Vcore2:       +3.89 V  (min =  +0.82 V, max =  +1.34 V)  ALARM
-12V:        +11.11 V  (min = -13.25 V, max = -10.73 V)  ALARM
+1.5V:        +3.04 V  (min =  +4.08 V, max =  +4.08 V)  ALARM
+3.3V:        +3.04 V  (min =  +3.14 V, max =  +3.47 V)  ALARM
+12V:        +36.86 V  (min = +11.33 V, max = +12.67 V)  ALARM
+5V:          +5.65 V  (min =  +4.75 V, max =  +5.25 V)  ALARM
5Vsb:         +3.39 V  (min =  +4.08 V, max =  +4.08 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)
CPU1 CoreA:   -48.0°C  (high =  -1.0°C, hyst =  -1.0°C)  sensor = thermistor
CPU1 CoreB:   -48.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
CPU2 CoreA:   -48.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
cpu0_vid:    +1.419 V
beep_enable: enabled

These are the sensors embedded in the Super-I/O. The board maker added
a dedicated ASIC for monitoring, which means that most of (all?) the
Super-I/O sensors are left unused. I wouldn't even bother loading the
w83627hf driver.



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





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

  Powered by Linux