[lm-sensors] No sensors detected on the ASUS K8V-MX motherboard

[lm-sensors] No sensors detected on the ASUS K8V-MX motherboard

[David Wu]

Hi Guys,

I am hoping someone can help me to either get the lm_sensors running
or at least give me a explanation as why I can't find any sensor chip
on the ASUS K8V-MX motherboard with VIA VT8237R chip. I have included
the necessary information below. I have the AMD socket 754 AMD Sempron
2500+ running at 1.4GHz.

my sensors-detect output:
===============================[root at localhost ~]# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

 We can start with probing for (PCI) I2C or SMBus adapters.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no): YES
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8237 South Bridge
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): YES
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

 To continue, we need module `i2c-dev' to be loaded.
 If it is built-in into your kernel, you can safely skip this.
 i2c-dev is not loaded. Do you want to load it now? (YES/no): YES
 Module loaded succesfully.

 We are now going to do the adapter probings. Some adapters may hang halfway
 through; we can't really help that. Also, some chips will be double detected;
 we choose the one with the highest confidence value in that case.
 If you found that the adapter hung after probing a certain address, you can
 specify that address to remain unprobed. That often
 includes address 0x69 (clock chip).

Next adapter: SMBus Via Pro adapter at 0400
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x69

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): YES
Probing for `National Semiconductor LM78'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
  Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
  Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
  Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
  Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
  Trying general detect... Failed!
Probing for `ITE IT8712F'
  Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
  Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
  Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
  Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): YES
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83627HF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83627THF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83637HF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x88)
Probing for `Winbond W83697SF/UF Super IO PWM'
  Failed! (0x88)
Probing for `Winbond W83L517D Super IO'
  Failed! (0x88)
Probing for `Winbond W83627EHF Super IO Sensors'
  Success... found at address 0x0290

Do you want to scan for secondary Super I/O sensors? (YES/no): YES
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
  Failed! (skipping family)

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

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus Via Pro adapter at 0400'
    Busdriver `i2c-viapro', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 8)

Driver `to-be-written' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627EHF Super IO Sensors' (confidence: 9)


 I will now generate the commands needed to load the I2C modules.
 Sometimes, a chip is available both through the ISA bus and an I2C bus.
 ISA bus access is faster, but you need to load an additional driver module
 for it. If you have the choice, do you want to use the ISA bus or the
 I2C/SMBus (ISA/smbus)? smbus

To make the sensors modules behave correctly, add these lines to
/etc/modprobe.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-viapro
modprobe i2c-isa
# I2C chip drivers
modprobe eeprom
# no driver for Winbond W83627EHF Super IO Sensors yet
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
=================================

my i2c-detect output:
=================================
[root at localhost ~]# i2cdetect -l
i2c-0   unknown         SMBus Via Pro adapter at 0400          
Algorithm unavailable
[root at localhost ~]# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: 50 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX
=================================

So it appears that it detect the SMBus controller, the VIA 8237R, fine
and loaded the proper i2c adapter bus driver. But there is no sensor
chip found!???  No even the AMD CPU sensor??!!!

Any help would be greatly appreciated.

Sincerely,

David Wu

[lm-sensors] No sensors detected on the ASUS K8V-MX motherboard

[Jean Delvare]

Hi David,

On 2006-02-28, David Wu wrote:
> I am hoping someone can help me to either get the lm_sensors running
> or at least give me a explanation as why I can't find any sensor chip
> on the ASUS K8V-MX motherboard with VIA VT8237R chip. I have included
> the necessary information below. I have the AMD socket 754 AMD Sempron
> 2500+ running at 1.4GHz.

According to the Asus documentation for this board, it does indeed have
hardware monitoring features, so it's really only a matter of finding
the right chip, driver and configuration.

Note that the VT8237R chip is not a hardware monitoring chip by itself,
although it may be used to access such chips (if they use an I2C/SMBus
interface.)

> Next adapter: SMBus Via Pro adapter at 0400
> Do you want to scan it? (YES/no/selectively): YES
> Client found at address 0x50
> Probing for `SPD EEPROM'... Success!
>     (confidence 8, driver `eeprom')
> Probing for `DDC monitor'... Failed!
> Probing for `Maxim MAX6900'... Failed!
> Client found at address 0x69

No hardware monitoring chip on the SMBus (or it is hidden, happens with
Asus boards sometimes).

> Probing for `Winbond W83627EHF Super IO Sensors'
>   Success... found at address 0x0290

This is most probably your hardware monitoring chip.

> # no driver for Winbond W83627EHF Super IO Sensors yet

You must use an old version of the sensors-detect script, as a driver now
exists (unsurprisingly named w83627ehf.)

If you have a 2.6.13 or better kernel, you probably have that driver
already, so just load it ("modprobe w83627ehf" as root) and it should
work. You will most certainly need to upgrade lm_sensors (to 2.9.1 or
better) for the "sensors" command to work though, as your version
seems to predate the writing of the driver and associated user-space
support.

> So it appears that it detect the SMBus controller, the VIA 8237R, fine
> and loaded the proper i2c adapter bus driver. But there is no sensor
> chip found!???  No even the AMD CPU sensor??!!!

It did find the chip, but just didn't know what driver to load. Now you
know.

As an adidtional note, what you call "AMD CPU sensor" is really only a
sensor (most likely a thermal diode), not a hardware monitoring chip. As
such, it is useless until it is wired to a hardware monitoring chip,
such as the W83627EHF you have on your motherboard.

--
Jean Delvare

[lm-sensors] No sensors detected on the ASUS K8V-MX motherboard

[Poul-Erik Andreasen]

Jean Delvare wrote:

>Hi David,
>
>On 2006-02-28, David Wu wrote:
>  
>
>>I am hoping someone can help me to either get the lm_sensors running
>>or at least give me a explanation as why I can't find any sensor chip
>>on the ASUS K8V-MX motherboard with VIA VT8237R chip. I have included
>>the necessary information below. I have the AMD socket 754 AMD Sempron
>>2500+ running at 1.4GHz.
>>    
>>
>
>According to the Asus documentation for this board, it does indeed have
>hardware monitoring features, so it's really only a matter of finding
>the right chip, driver and configuration.
>
>Note that the VT8237R chip is not a hardware monitoring chip by itself,
>although it may be used to access such chips (if they use an I2C/SMBus
>interface.)
>
>  
>
>>Next adapter: SMBus Via Pro adapter at 0400
>>Do you want to scan it? (YES/no/selectively): YES
>>Client found at address 0x50
>>Probing for `SPD EEPROM'... Success!
>>    (confidence 8, driver `eeprom')
>>Probing for `DDC monitor'... Failed!
>>Probing for `Maxim MAX6900'... Failed!
>>Client found at address 0x69
>>    
>>
>
>No hardware monitoring chip on the SMBus (or it is hidden, happens with
>Asus boards sometimes).
>
>  
>
>>Probing for `Winbond W83627EHF Super IO Sensors'
>>  Success... found at address 0x0290
>>    
>>
>
>This is most probably your hardware monitoring chip.
>
>  
>
>># no driver for Winbond W83627EHF Super IO Sensors yet
>>    
>>
>
>You must use an old version of the sensors-detect script, as a driver now
>exists (unsurprisingly named w83627ehf.)
>
>If you have a 2.6.13 or better kernel, you probably have that driver
>already, so just load it ("modprobe w83627ehf" as root) and it should
>work. You will most certainly need to upgrade lm_sensors (to 2.9.1 or
>better) for the "sensors" command to work though, as your version
>seems to predate the writing of the driver and associated user-space
>support.
>
>  
>
>>So it appears that it detect the SMBus controller, the VIA 8237R, fine
>>and loaded the proper i2c adapter bus driver. But there is no sensor
>>chip found!???  No even the AMD CPU sensor??!!!
>>    
>>
>
>It did find the chip, but just didn't know what driver to load. Now you
>know.
>
>As an adidtional note, what you call "AMD CPU sensor" is really only a
>sensor (most likely a thermal diode), not a hardware monitoring chip. As
>such, it is useless until it is wired to a hardware monitoring chip,
>such as the W83627EHF you have on your motherboard.
>
>--
>Jean Delvare  
>
When kan we expect at update on the W83627EHF to include som fancontrol
and some of the other advanced fetures of the chip. I am sitting with a machine
suited with some nice 120 mm fans, but the minimum-setting on the fanspeed
is way to high, an it can not be altered in the BIOS.  

Unfortunatly i am lousy in C in general and i do not know anything about
kernel-development, so i cannot realy paticipate, in development. 
But maybe you can use mee as a  beta tester.

--
Poul-Erik Andreasen

poulerik at pea.dk

[lm-sensors] No sensors detected on the ASUS K8V-MX motherboard

[Jean Delvare]

Hi Poul-Erik,

On 2006-02-28, Poul-Erik Andreasen wrote:
> When kan we expect at update on the W83627EHF to include som fancontrol
> and some of the other advanced fetures of the chip. I am sitting with a
> machine suited with some nice 120 mm fans, but the minimum-setting on the
> fanspeed is way to high, an it can not be altered in the BIOS.
>
> Unfortunatly i am lousy in C in general and i do not know anything about
> kernel-development, so i cannot realy paticipate, in development.
> But maybe you can use mee as a  beta tester.

We have a pending update from Yuan Mu from Winbond, it needs review and
probably some adjustment. I think I remember Rudolf Marek had been
working on it, maybe he will be able to provide me with a patch ready
for inclusion now that he's done with his final exams. If not, you'll
have to wait for me to have some spare time to handle it, which is not
right now for sure.

Thanks for your patience,
--
Jean Delvare

[lm-sensors] No sensors detected on the ASUS K8V-MX motherboard

[Rudolf Marek]

> We have a pending update from Yuan Mu from Winbond, it needs review and
> probably some adjustment. I think I remember Rudolf Marek had been
> working on it, maybe he will be able to provide me with a patch ready
> for inclusion now that he's done with his final exams. If not, you'll
> have to wait for me to have some spare time to handle it, which is not
> right now for sure.

There are some issues and I have already some ideas how to fix that and what to change. I think
I may have some time for this on thursday evening or weekend. Problem is that I must have
physical access to that computer so I can look what a fan is doing ;)

If you want to test it please apply this patches:
http://lists.lm-sensors.org/pipermail/lm-sensors/2006-January/015115.html

Please check my  "preliminary - proprietary - confidental - NDA required" comments about the
patches ;) Some things are not working as expected some has problems and I remember I had the problem with the
fan reglation because the automatic one acted somehow strange...

I hope it helps. Please be patient. I'm converting the website to wiki too and I had to review some drivers
and this is quite time eater.

Regards
Rudolf

/sys files
----------

pwm[1-4] - this file stores PWM duty cycle or DC value (fan speed) in range:
        0 (stop) to 255 (full)
pwm[1-4]_enable - this file controls mode of fan/temperature control:

our iterface specify 0=disable
            * 0 Manual mode
            * 1 Thermal Cruise
            * 2 Fan Speed Cruise
            * 3 Smart FAN III
pwm[1-4]_mode - Select PWM of DC mode
            * 0 DC
            * 1 PWM

For Thermal Cruise mode
------------------------
thermal_cruise[1-4] - Selects the desired temperature for cruise (degC) 0-255? -> wrong limit
tolerance[1-4] - Value in degrees of Celsius (degC) for +- T   limit is 0-15


For Fan speed Cruise mode
------------------------
thermal_cruise[1-4] - Selects desired target speed (limit is 0-255) -> WRONG UNITS USED

what unit is it rotations? or ticks???

tolerance[1-4] - tolerance of desired target speed (limit is 0-15) -> WRONG UNITS USED


SF3
---
Target SF3 temperature should be written to thermal_cruise,
but thermal_cruise2 and thermal_cruise4 is used (regs 0x6 and 0x63)
Tolerance of SF3 (0x7 bit-4-7, +cr62)
but tolerance2 and tolerance4 is used

So this would mean to rename 1->2 and 2->4 to have it sane.

/sys/bus/i2c/devices/9191-0290/sf3_fan_max1  255
/sys/bus/i2c/devices/9191-0290/sf3_fan_max2  255
/sys/bus/i2c/devices/9191-0290/sf3_fan_min1  177
/sys/bus/i2c/devices/9191-0290/sf3_fan_min2  1
/sys/bus/i2c/devices/9191-0290/sf3_fan_step1  1
/sys/bus/i2c/devices/9191-0290/sf3_fan_step2  1
/sys/bus/i2c/devices/9191-0290/sf3_step_time_down  1
/sys/bus/i2c/devices/9191-0290/sf3_step_time_up  1
/sys/bus/i2c/devices/9191-0290/sf3_stop_time1  60
/sys/bus/i2c/devices/9191-0290/sf3_stop_time2  60

sf3_fan_max[1-2]
------------------

When at SMART FANTM III mode, CPUFANOUT0 value will increase to this value. This register should
be written a non-zero value that cannot lower than Stop value.

0-255 is there right now -> 0 is allowed!!!

sf3_fan_min[1-2]
----------------

THIS IS USED ALSO IN THERMAL CRUISE AS BORDER (only for 2 and 4????)


0 is allowed!!!

When at Thermal Cruise mode or SMART FAN TM III mode, CPUFANOUT0-1 value will decrease to this
value. This register should be written a non-zero minimum stop value.

(1)When at PWM output:
The unit of this register is 0.1 second. The default time is 6 seconds.
(2)When at DC Voltage output:
The unit of this register is 0.4 second. The default time is 24 seconds.

sf3_step_time_down
-------------------

This register determines the speed of FANOUT decreasing its value in Smart Fan Control mode.
(1)When at PWM output:
The unit of this register is 0.1 second. The default time is 1 seconds.
(2)When at DC Voltage output:
The unit of this register is 0.4 second. The default time is 4 seconds.


sf3_step_time_up
----------------
This register determines the speed of FANOUT increasing the its value in Smart Fan Control mode.
(1)When at PWM output:
The unit of this register is 0.1 second. The default time is 1 seconds.
(2)When at DC Voltage output:
The unit of this register is 0.4 second. The default time is 4 seconds.



TODO:
Also for the thermal cruise and smartfan STOP VALUE reg (0x15 and others should be implemented)
and start value??? (0xA)