[lm-sensors] insane readings on Asus A7M266 motherboard

[lm-sensors] insane readings on Asus A7M266 motherboard

[Audio Phile]

I had to reinstall Linux after a HDD crash.  Before the crash, sensors would work just fine with this board.  I am now unable to get it to work to correctly read the temp sensors.  If I look at them in the BIOS, the CPU is about 50C and the MB is about 35C.  When I view them in sensors, I get:

# sensors
via686a-isa-f000
Adapter: ISA adapter
Vcore:       +3.10 V  (min =  +3.10 V, max =  +3.10 V)   
in1:         +3.10 V  (min =  +3.10 V, max =  +3.10 V)   
+3.3V:       +3.12 V  (min =  +2.98 V, max =  +3.63 V)   
+5V:         +6.44 V  (min =  +4.51 V, max =  +5.50 V)   
+12V:       +15.60 V  (min = +10.81 V, max = +13.20 V)   
fan1:       3026 RPM  (min = 2689 RPM, div = 2)
fan2:          0 RPM  (min =    0 RPM, div = 2)
temp1:      +146.2°C  (high = +146.2°C, hyst = +54.4°C)  
temp2:      +146.2°C  (high = +146.2°C, hyst = +54.4°C)  
temp3:      +135.2°C  (high = +146.2°C, hyst = +146.2°C)  

Hardware: Asus A7M266 (old, I know)
Sensors: sensors version 3.2.0 with libsensors version 3.2.0
Kernel: 2.6.32 or 2.6.37

Note that sensors-detect finds the "via686a" module but loading it does nothing without forcing an address as per the dmesg:
via686a 0000:00:04.4: Sensors disabled, enable with force_addr=0xe300

So I do it via: modprobe via686a force_addr=0xe300

Again, the temps are reasonable in the BIOS so I believe that the sensors are fine.  Suggestions are welcomed.


      

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

Re: [lm-sensors] insane readings on Asus A7M266 motherboard

[Jean Delvare]

Hi,

On Sun, 23 Jan 2011 14:27:26 -0800 (PST), Audio Phile wrote:
> I had to reinstall Linux after a HDD crash.  Before the crash, sensors would work just fine with this board.  I am now unable to get it to work to correctly read the temp sensors.  If I look at them in the BIOS, the CPU is about 50C and the MB is about 35C.  When I view them in sensors, I get:
> 
> # sensors
> via686a-isa-f000
> Adapter: ISA adapter
> Vcore:       +3.10 V  (min =  +3.10 V, max =  +3.10 V)   
> in1:         +3.10 V  (min =  +3.10 V, max =  +3.10 V)   
> +3.3V:       +3.12 V  (min =  +2.98 V, max =  +3.63 V)   
> +5V:         +6.44 V  (min =  +4.51 V, max =  +5.50 V)   
> +12V:       +15.60 V  (min = +10.81 V, max = +13.20 V)   
> fan1:       3026 RPM  (min = 2689 RPM, div = 2)
> fan2:          0 RPM  (min =    0 RPM, div = 2)
> temp1:      +146.2°C  (high = +146.2°C, hyst = +54.4°C)  
> temp2:      +146.2°C  (high = +146.2°C, hyst = +54.4°C)  
> temp3:      +135.2°C  (high = +146.2°C, hyst = +146.2°C)  
> 
> Hardware: Asus A7M266 (old, I know)

There's nothing wrong with running old hardware :)

> Sensors: sensors version 3.2.0 with libsensors version 3.2.0
> Kernel: 2.6.32 or 2.6.37
> 
> Note that sensors-detect finds the "via686a" module but loading it does nothing without forcing an address as per the dmesg:
> via686a 0000:00:04.4: Sensors disabled, enable with force_addr=0xe300
> 
> So I do it via: modprobe via686a force_addr=0xe300

This alone is usually a good hint that the VIA686A/B integrated sensors
aren't used on the board.

> Again, the temps are reasonable in the BIOS so I believe that the sensors are fine.  Suggestions are welcomed.

The A7M266, as most Asus board at the time, is using an Asus-specific
ASIC for hardware monitoring, rather than the sensors integrated in the
south bridge. In your case, that would be an AS99127F, so you should
load the w83781d driver rather than the via686a driver. sensors-detect
should have told you exactly this, BTW. If it did not, please send the
full output of sensors-detect for analysis.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

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

Re: [lm-sensors] insane readings on Asus A7M266 motherboard

[Audio Phile]

--- On Mon, 1/24/11, Jean Delvare <khali@linux-fr.org> wrote:

> This alone is usually a good hint that the VIA686A/B
> integrated sensors
> aren't used on the board.

I thought so too but it worked for years until I had to reinstall.

> The A7M266, as most Asus board at the time, is using an
> Asus-specific
> ASIC for hardware monitoring, rather than the sensors
> integrated in the
> south bridge. In your case, that would be an AS99127F, so
> you should
> load the w83781d driver rather than the via686a driver.
> sensors-detect
> should have told you exactly this,

I tried this:

# rmmod via686a
# modprobe w83781d
# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

> BTW. If it did not,
> please send the
> full output of sensors-detect for analysis.

Attached. 
If it helps, here is the output of dmidecode: http://pastebin.com/neMfZ72L
Here is the output of lsmod: http://pastebin.com/0UNi2j5Z

Thanks again for any help you can provide.

# sensors-detect
# sensors-detect revision 5861 (2010-09-21 17:21:05 +0200)
# Board: ASUSTeK Computer INC. <A7M266>

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): YES
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          Success!
    (driver `via686a')
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom thermal sensor...                                No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): YES
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): YES
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
Using driver `i2c-viapro' for device 0000:00:04.4: VIA Technologies VT82C686 Apollo ACPI
Module i2c-dev loaded successfully.

Next adapter: NVIDIA i2c adapter  (i2c-0)
Do you want to scan it? (YES/no/selectively): YES

Next adapter: NVIDIA i2c adapter  (i2c-1)
Do you want to scan it? (YES/no/selectively): YES

Next adapter: NVIDIA i2c adapter  (i2c-2)
Do you want to scan it? (YES/no/selectively): YES

Now follows a summary of the probes I have just done.
Just press ENTER to continue:   

Driver `via686a':
  * Chip `VIA VT82C686 Integrated Sensors' (confidence: 9)

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/rc.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

Unloading i2c-dev... OK



      

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

Re: [lm-sensors] insane readings on Asus A7M266 motherboard

[Jean Delvare]

On Mon, 24 Jan 2011 13:10:29 -0800 (PST), Audio Phile wrote:
> --- On Mon, 1/24/11, Jean Delvare <khali@linux-fr.org> wrote:
> 
> > This alone is usually a good hint that the VIA686A/B
> > integrated sensors
> > aren't used on the board.
> 
> I thought so too but it worked for years until I had to reinstall.

No, it did not. The VIA686A/B sensors are _not_ used on this board, I
am totally positive on this.

> > The A7M266, as most Asus board at the time, is using an
> > Asus-specific
> > ASIC for hardware monitoring, rather than the sensors
> > integrated in the
> > south bridge. In your case, that would be an AS99127F, so
> > you should
> > load the w83781d driver rather than the via686a driver.
> > sensors-detect
> > should have told you exactly this,
> 
> I tried this:
> 
> # rmmod via686a
> # modprobe w83781d
> # sensors
> No sensors found!
> Make sure you loaded all the kernel drivers you need.
> Try sensors-detect to find out which these are.

So for some reason the AS99127F isn't usable by the w83781d driver.

> > BTW. If it did not,
> > please send the
> > full output of sensors-detect for analysis.
> 
> Attached. 
> (...)
> Lastly, we can probe the I2C/SMBus adapters for connected hardware
> monitoring devices. This is the most risky part, and while it works
> reasonably well on most systems, it has been reported to cause trouble
> on some systems.
> Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
> Using driver `i2c-viapro' for device 0000:00:04.4: VIA Technologies VT82C686 Apollo ACPI
> Module i2c-dev loaded successfully.
> 
> Next adapter: NVIDIA i2c adapter  (i2c-0)
> Do you want to scan it? (YES/no/selectively): YES
> 
> Next adapter: NVIDIA i2c adapter  (i2c-1)
> Do you want to scan it? (YES/no/selectively): YES
> 
> Next adapter: NVIDIA i2c adapter  (i2c-2)
> Do you want to scan it? (YES/no/selectively): YES

The VIA Pro SMBus isn't probed, meaning that the driver failed to bind
to the device. You should see some error message in the kernel logs
when i2c-viapro is loaded.

One possible cause is an ACPI resource conflict [1]. I am a little
surprised as I didn't expect this kind of problem on such an old board.
If this is the case, booting with acpi_enforce_resources=lax should
solve your problem.

[1] http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

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

Re: [lm-sensors] insane readings on Asus A7M266 motherboard

[Audio Phile]

Thank you!  This absolutely solved my problem!  I do remember now having to do this addition to grub2's /boot/grub/grub.conf to make it work in the past.

# sensors
as99127f-i2c-0-2d
Adapter: SMBus Via Pro adapter at e800
in0:         +1.74 V  (min =  +1.65 V, max =  +2.05 V)   
in1:         +2.48 V  (min =  +1.65 V, max =  +2.05 V)   
in2:         +3.22 V  (min =  +2.96 V, max =  +3.63 V)   
in3:         +2.99 V  (min =  +2.67 V, max =  +3.28 V)   
in4:         +3.14 V  (min =  +2.51 V, max =  +3.79 V)   
in5:         +0.51 V  (min =  +0.08 V, max =  +1.02 V)   
in6:         +0.86 V  (min =  +0.54 V, max =  +1.17 V)   
fan1:       2721 RPM  (min = 5273 RPM, div = 2)
fan2:          0 RPM  (min = 337500 RPM, div = 2)
fan3:          0 RPM  (min =   -1 RPM, div = 2)
temp1:       +34.0°C  (high =  +0.0°C, hyst = -128.0°C)  
temp2:       +52.0°C  (high = +100.0°C, hyst = +75.0°C)  
temp3:        -0.5°C  (high = +80.0°C, hyst = +75.0°C)  
cpu0_vid:   +1.750 V
beep_enable:enabled


--- On Mon, 1/24/11, Jean Delvare <khali@linux-fr.org> wrote:

> The VIA Pro SMBus isn't probed, meaning that the driver
> failed to bind
> to the device. You should see some error message in the
> kernel logs
> when i2c-viapro is loaded.
> 
> One possible cause is an ACPI resource conflict [1]. I am a
> little
> surprised as I didn't expect this kind of problem on such
> an old board.
> If this is the case, booting with
> acpi_enforce_resources=lax should
> solve your problem.
> 
> [1] http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
> 
> -- 
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
> 


      

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

Re: [lm-sensors] insane readings on Asus A7M266 motherboard

[Luca Tettamanti]

On Mon, Jan 24, 2011 at 10:41 PM, Audio Phile <da_audiophile@yahoo.com> wrote:
>> --- On Mon, 1/24/11, Jean Delvare <khali@linux-fr.org> wrote:
>>
>> The VIA Pro SMBus isn't probed, meaning that the driver failed to bind
>> to the device. You should see some error message in the kernel logs
>> when i2c-viapro is loaded.
>>
>> One possible cause is an ACPI resource conflict [1]. I am a little
>> surprised as I didn't expect this kind of problem on such an old board.
>> If this is the case, booting with acpi_enforce_resources=lax should
>> solve your problem.
>
> Thank you!  This absolutely solved my problem!

Ok, now I'm curious :) Probably it's the ACPI thermal zone.
Can you send me a copy of /sys/firmware/acpi/tables/DSDT?

Luca

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

Re: [lm-sensors] insane readings on Asus A7M266 motherboard

[Audio Phile]

...AND I should add, after finding the following: http://www.lm-sensors.org/ticket/2126

And using a slightly modified version of it (attached) as my /etc/sensors3.conf my output looks accurate.

# sensors
as99127f-i2c-0-2d
Adapter: SMBus Via Pro adapter at e800
VCore 1:     +1.81 V  (min =  +1.65 V, max =  +2.05 V)   
VCore 2:     +2.46 V  (min =  +1.65 V, max =  +2.05 V)   
+3.3V:       +3.18 V  (min =  +2.96 V, max =  +3.63 V)   
+5V:         +5.03 V  (min =  +4.49 V, max =  +5.51 V)   
+12V:       +11.98 V  (min =  +9.55 V, max = +14.41 V)   
-12V:       -12.95 V  (min = -14.66 V, max = -11.69 V)   
-5V:         -4.95 V  (min =  -6.00 V, max =  -4.04 V)   
CPU0 Fan:   2700 RPM  (min = 5273 RPM, div = 2)
CPU1 Fan:      0 RPM  (min = 337500 RPM, div = 2)
Chas Fan:      0 RPM  (min =   -1 RPM, div = 2)
Mobo Temp:   +34.0°C  (high =  +0.0°C, hyst = -128.0°C)  
CPU0 Temp:   +47.5°C  (high = +100.0°C, hyst = +75.0°C)  
CPU1 Temp:    -0.5°C  (high = +80.0°C, hyst = +75.0°C)  
cpu0_vid:   +1.750 V
beep_enable:enabled


/etc/sensors3.conf

chip "as99127f-*"

# Asus A7M266-D rev 1.04 (dual CPU) AS99127F rev.2
    label in0 "VCore 1"
    label in1 "VCore 2"
    label in2 "+3.3V"
    label in3 "+5V"
    label in4 "+12V"
    label in5 "-12V"
    label in6 "-5V"
    label temp1 "Mobo Temp"
    label temp2 "CPU0 Temp"
    label temp3 "CPU1 Temp"
    label fan1 "CPU0 Fan"
    label fan2 "CPU1 Fan"
    label fan3 "Chas Fan"

    compute in3 ((6.8/10)+1)*@ ,  @/((6.8/10)+1)
    compute in4 ((28/10)+1)*@  ,  @/((28/10)+1)
    compute in5 (3.14 * @) - 14.91  ,  (@ + 14.91) / 3.14
    compute in6 (3.14 * @) -  7.71  ,  (@ +  7.71) / 5.14

    set in0_min vid*0.95
    set in0_max vid*1.05
    set in1_min vid*0.95
    set in1_max vid*1.05
    set in2_min 3.3 * 0.95
    set in2_max 3.3 * 1.05
    set in3_min 5.0 * 0.95
    set in3_max 5.0 * 1.05
    set in4_min 12 * 0.90
    set in4_max 12 * 1.10
    set in5_max -12 * 0.90
    set in5_min -12 * 1.10
    set in6_max -5 * 0.95
    set in6_min -5 * 1.05

    set temp1_over 44
    set temp1_hyst 40
    set temp2_over 64
    set temp2_hyst 61
    set temp3_over 64
    set temp3_hyst 61

    set fan1_min 3000
    set fan2_min 3000
    set fan3_div 4
    set fan3_min 1800




--- On Mon, 1/24/11, Jean Delvare <khali@linux-fr.org> wrote:

> From: Jean Delvare <khali@linux-fr.org>
> Subject: Re: [lm-sensors] insane readings on Asus A7M266 motherboard
> To: "Audio Phile" <da_audiophile@yahoo.com>
> Cc: lm-sensors@lm-sensors.org
> Date: Monday, January 24, 2011, 4:27 PM
> On Mon, 24 Jan 2011 13:10:29 -0800
> (PST), Audio Phile wrote:
> > --- On Mon, 1/24/11, Jean Delvare <khali@linux-fr.org>
> wrote:
> > 
> > > This alone is usually a good hint that the
> VIA686A/B
> > > integrated sensors
> > > aren't used on the board.
> > 
> > I thought so too but it worked for years until I had
> to reinstall.
> 
> No, it did not. The VIA686A/B sensors are _not_ used on
> this board, I
> am totally positive on this.
> 
> > > The A7M266, as most Asus board at the time, is
> using an
> > > Asus-specific
> > > ASIC for hardware monitoring, rather than the
> sensors
> > > integrated in the
> > > south bridge. In your case, that would be an
> AS99127F, so
> > > you should
> > > load the w83781d driver rather than the via686a
> driver.
> > > sensors-detect
> > > should have told you exactly this,
> > 
> > I tried this:
> > 
> > # rmmod via686a
> > # modprobe w83781d
> > # sensors
> > No sensors found!
> > Make sure you loaded all the kernel drivers you need.
> > Try sensors-detect to find out which these are.
> 
> So for some reason the AS99127F isn't usable by the w83781d
> driver.
> 
> > > BTW. If it did not,
> > > please send the
> > > full output of sensors-detect for analysis.
> > 
> > Attached. 
> > (...)
> > Lastly, we can probe the I2C/SMBus adapters for
> connected hardware
> > monitoring devices. This is the most risky part, and
> while it works
> > reasonably well on most systems, it has been reported
> to cause trouble
> > on some systems.
> > Do you want to probe the I2C/SMBus adapters now?
> (YES/no): YES
> > Using driver `i2c-viapro' for device 0000:00:04.4: VIA
> Technologies VT82C686 Apollo ACPI
> > Module i2c-dev loaded successfully.
> > 
> > Next adapter: NVIDIA i2c adapter  (i2c-0)
> > Do you want to scan it? (YES/no/selectively): YES
> > 
> > Next adapter: NVIDIA i2c adapter  (i2c-1)
> > Do you want to scan it? (YES/no/selectively): YES
> > 
> > Next adapter: NVIDIA i2c adapter  (i2c-2)
> > Do you want to scan it? (YES/no/selectively): YES
> 
> The VIA Pro SMBus isn't probed, meaning that the driver
> failed to bind
> to the device. You should see some error message in the
> kernel logs
> when i2c-viapro is loaded.
> 
> One possible cause is an ACPI resource conflict [1]. I am a
> little
> surprised as I didn't expect this kind of problem on such
> an old board.
> If this is the case, booting with
> acpi_enforce_resources=lax should
> solve your problem.
> 
> [1] http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
> 
> -- 
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
> 


      

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

Re: [lm-sensors] insane readings on Asus A7M266 motherboard

[Audio Phile]

--- On Mon, 1/24/11, Luca Tettamanti <kronos.it@gmail.com> wrote:
> Ok, now I'm curious :) Probably it's the ACPI thermal
> zone.
> Can you send me a copy of /sys/firmware/acpi/tables/DSDT?
> 
> Luca

Glad to... It's on its way to your gmail account.  Please let me know what it means!


      

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

Re: [lm-sensors] insane readings on Asus A7M266 motherboard

[Luca Tettamanti]

On Mon, Jan 24, 2011 at 10:55 PM, Audio Phile <da_audiophile@yahoo.com> wrote:
> --- On Mon, 1/24/11, Luca Tettamanti <kronos.it@gmail.com> wrote:
>> Ok, now I'm curious :) Probably it's the ACPI thermal
>> zone.
>> Can you send me a copy of /sys/firmware/acpi/tables/DSDT?
>
> Glad to... It's on its way to your gmail account.  Please let me know what it means!

Nothing is wrong ;-) The system firmware (ACPI) claims the SMBus
interface resources for itself, so newer kernels prevent the
i2a-viapro driver from loading in order to avoid possible conflicts. I
just wanted to see what the BIOS was using the chip for.

ACPI code has methods for fiddling with the i2c bus, not sure why,
I'll have to dig out the specs.
There are two public methods \_SI._MSG, and \_SI.SST, plus other
places where the bus is used.

L

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