[lm-sensors] asus_atk0110 doesn't work on motherboard P8B WS

Guenter Roeck guenter.roeck at ericsson.com
Tue May 15 21:32:57 CEST 2012


On Tue, 2012-05-15 at 15:20 -0400, ACCART Julien wrote:
> Le 14/05/2012 20:57, Jean Delvare a écrit :
> > On Mon, 14 May 2012 20:44:08 +0200, ACCART Julien wrote:
> >> The BIOS of this motherboard can display CPU and M/B temp, voltage, fan
> >> speed.
> >> Do you think we can use the asus wmi modules to read these data?
> >> How can I help?
> > Did you try just running sensors-detect and loading the proper drivers?
> > Who knows, this may just work. If not, booting with
> > acpi_enforce_resources=lax might be a workaround if you can live with
> > the risk.
> >
> 
> Yes I did.
> In kernel 3, loading the w83627ehf fails because of conflicts with ACPI. 
> I tried the acp_enforce_resources=lax but I had freezes. It is useless 
> to have the module loading ability if system freezes
> 
> So, I'm back to 2.6.39 which lets me load w83627ehf module.
> 
> I wanted the atk (or wmi) because of two reasons :
> 1 - w83627ehf doesn't work with kernel 3 and lax acpi resource freezes 
> my system as I said
> 2 - mesures with atk or wmi are reliable but are messed up with 
> w83627ehf module
> For example :
> 
> $ sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +33.0 C  (high = +82.0 C, crit = +102.0 C)
> 
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +29.0 C  (high = +82.0 C, crit = +102.0 C)
> 
> nct6776-isa-0290
> Adapter: ISA adapter
> in0:          +0.90 V  (min =  +0.00 V, max =  +1.74 V)
> in1:          +1.00 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in2:          +3.38 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in3:          +3.38 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in4:          +1.01 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in5:          +2.04 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.33 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> fan1:         967 RPM  (min =    0 RPM)  ALARM
> fan2:        1045 RPM  (min =    0 RPM)  ALARM
> fan3:           0 RPM  (min =    0 RPM)  ALARM
> fan4:        1086 RPM  (min =    0 RPM)  ALARM
> fan5:           0 RPM  (min =    0 RPM)  ALARM
> SYSTIN:       +29.0 C  (high =  +0.0 C, hyst =  +0.0 C)  ALARM  sensor = 
> thermistor
> CPUTIN:       +91.5 C  (high = +58.5 C, hyst = +53.5 C)  ALARM  sensor = 
> thermistor
> AUXTIN:       +26.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
> PECI Agent 0: +19.5 C
> cpu0_vid:    +2.050 V
> 
> 
> Coretemp says 30 C  while w83627ehf says 91.5.
> min and max are not set in both temp, voltage and RPM.
> 
CPUTIN is most likely not connected at all. The CPU temperature is
reported by PECI Agent 0, but the base temperature is not configured
correctly in the BIOS and thus about 10 degrees off. I have seen this on
other Asus boards.

You could try to load the experimental driver from
https://github.com/groeck/nct6775; it will let you configure the limit
temperature for the PECI input. Unfortunately, that driver may also
experience the freeze issue.

Guenter






More information about the lm-sensors mailing list