Re: ASUS Sabertooth Z77 / nct6775.ko report

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

 



On Wed, 2012-05-23 at 05:37 -0400, Dmitriy Pinchukov wrote:
> Hi,
> 
> Got a new ASUS Sabertooth Z77 mobo recently and found out that lm-sensors didn't support
> anything but the core temperatures and also a couple ones from the
> 'acpitz-virtual-0' device. Trying the trunk version of sensors-detect didn't help.
> 
> I then searched and finally found the shiny new 'nct6775' driver. Compiled and loaded it successfully (linux 3.4.0 x86_64):
> 
> [ 1082.377370] nct6775: Found NCT6779D chip at 0x290
> 
> Here's how my sensors output looking now (lm-sensors 3.3.2 from Debian wheezy/sid):
> 
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:        +27.8°C  (crit = +106.0°C)
> temp2:        +29.8°C  (crit = +106.0°C)
> 
> coretemp-isa-0000
> Adapter: ISA adapter
> Physical id 0:  +45.0°C  (high = +85.0°C, crit = +105.0°C)
> Core 0:         +44.0°C  (high = +85.0°C, crit = +105.0°C)
> Core 1:         +45.0°C  (high = +85.0°C, crit = +105.0°C)
> Core 2:         +43.0°C  (high = +85.0°C, crit = +105.0°C)
> Core 3:         +43.0°C  (high = +85.0°C, crit = +105.0°C)
> 
> nct6779-isa-0290
> Adapter: ISA adapter
> in0:                    +1.00 V  (min =  +0.00 V, max =  +1.74 V)
> in1:                    +1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in2:                    +3.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in3:                    +3.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in4:                    +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in5:                    +2.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in6:                    +1.49 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in7:                    +3.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in8:                    +3.36 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in9:                    +1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in10:                   +1.49 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in11:                   +1.49 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in12:                   +0.25 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in13:                   +0.18 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in14:                   +1.49 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> fan1:                     0 RPM  (min =    0 RPM)
> fan2:                  1142 RPM  (min =    0 RPM)
> fan3:                  1011 RPM  (min =    0 RPM)
> fan4:                   922 RPM  (min =    0 RPM)
> fan5:                     0 RPM  (min =    0 RPM)
> SYSTIN:                 +36.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
> CPUTIN:                  +0.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> AUXTIN0:                 +0.0°C    sensor = thermistor
> AUXTIN1:                 +0.0°C    sensor = thermistor
> AUXTIN2:                 +0.0°C    sensor = thermistor
> AUXTIN3:                 +0.0°C    sensor = thermistor
> PCH_CHIP_CPU_MAX_TEMP:   +0.0°C
> PCH_CHIP_TEMP:           +0.0°C
> PCH_CPU_TEMP:            +0.0°C
> PCH_MCH_TEMP:            +0.0°C
> cpu0_vid:              +0.000 V
> intrusion0:            ALARM
> intrusion1:            ALARM
> 
> Here's my thoughts:
> 
Hi Dmitriy,

thanks a lot for the feedback.

> - only 5 fans are shown whereas the mobo has 8 fan connectors (two of which are 3-pin, the rest are 4-pin);

The NCT6779D has only five fan sensors, so that is not surprising. Maybe
the other fans are not monitored, there is a second chip to
control/monitor the other fans, or ASUS started putting a multiplexer at
the fan inputs. I hope they didn't, but maybe they learned the wrong
lesson from AsusTek.

> - this board has a lot of temperature sensors (the windows asus monitoring utility shows around 8 or 9 of them I think), but only the SYSTIN seems to be reported correctly by this driver, the rest are zero;

No idea what is happening here. The temperature values are taken
directly from the chip registers. ASUS might have a another chip to
monitor other temperatures. Interesting that the PECI input is not
shown; it is used on all other ASUS boards I have seen.

> - cpu0_vid has zero value as well;

Frankly, I have never seen useful output from this. No idea if it is
even connected.

> - min/max values are zero for some of the sensors and the ALARM status is reported erroneously there;

This is quite common; limits are rarely programmed by BIOSes for some
reason. You'll have to set the limits yourself. The alarms will go away
if the limits are set.

> - fan control *does* work via the /sys/devices/platform/nct6775.656/pwm* interface, both in PWM and DC control modes; I can reduce their speed and fully stop them.
> 
Sounds good. Can you provide output of
"grep . /sys/devices/platform/nct6775.656/pwm*" and "sensors -u" ?

> What do you guys think of this? My current sensors-detect output is in the attachment and is also available at http://pastebin.com/BUs8e0sn. I also tried the 'lm75' and 'ds1621' drivers that it suggested, but that didn't change the output of sensors and there weren't any messages in dmesg when I loaded them.
> 
> I will gladly present any additional info that might help to debug the issue or improve the
> driver.
> 
Not much I can do right now. A complete register dump would help, but I
don't know how to do that in Linux. I'll may have to start extending
superiotool to support the chip, but that will take some time, which I
don't have right now :(.

Guenter



_______________________________________________
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