[lm-sensors] ASUS K8V-X SE should be supported?

[lm-sensors] ASUS K8V-X SE should be supported?

[Dogsbody]

Hi,

I have just spent the last four hours on this and I seem to be going around in 
circles.  I really hope that I'm not about to ask a stupid question! :-\

I have a ASUS K8V-X SE motherboard with a VT8237R chip.  The chip seems to be 
discovered fine but all it can see is two eeprom's (two sticks of memory).  I 
can view the temperatures, fan speeds and voltages in the BIOS but not in 
lm_sensors.

Below is my diagnostic info.  I am ignoring the "rivatv" as I believe that is 
just for the graphics card which I don't use anyway and so thought pointless to 
install the drivers for.  I hope that is OK.

Thank you very much in advance for any help.

Regards, Dan


# uname -a
Linux 2.6.9-34.0.1.EL #1 Wed May 24 07:40:56 CDT 2006 i686 athlon i386 GNU/Linux

# sensors -v
sensors version 2.8.7 with libsensors version 2.8.7

# /usr/sbin/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):
Probing for PCI bus adapters...
Use driver `rivatv' for device 01:00.0: GeForce2 MX
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 `rivatv' (say NO if built into your kernel)? (YES/no):
FATAL: Module rivatv not found.
Loading failed... skipping.
** Note: rivatv module is available at http://rivatv.sourceforge.net/
Load `i2c-viapro' (say NO if built into your kernel)? (YES/no):
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 already loaded.

  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 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively):
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 0x51
Probing for `SPD EEPROM'... Success!
     (confidence 8, driver `eeprom')
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):
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 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 IT8705F / IT8712F / 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):
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)

Do you want to scan for secondary Super I/O sensors? (YES/no):
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)

  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' (Algorithm unavailable)
     Busdriver `i2c-viapro', I2C address 0x50
     Chip `SPD EEPROM' (confidence: 8)
   * Bus `SMBus Via Pro adapter at 0400' (Algorithm unavailable)
     Busdriver `i2c-viapro', I2C address 0x51
     Chip `SPD EEPROM' (confidence: 8)


  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)?

To make the sensors modules behave correctly, add these lines to
/etc/modules.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
# I2C chip drivers
modprobe eeprom
# 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.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.

[lm-sensors] ASUS K8V-X SE should be supported?

[Rudolf Marek]

Hi

You are using too old version of lm-sensors. Imho you have W83627EHF chip 
(Failed! (0x88)). Try with the latest version of lm-sensors.

Regards
Rudolf

[lm-sensors] ASUS K8V-X SE should be supported?

[Dogsbody]

> You are using too old version of lm-sensors. Imho you have W83627EHF 
> chip (Failed! (0x88)). Try with the latest version of lm-sensors.


Hi,

Thank you very much.  Downloaded, compiled and installed v2.10.0.  Sure enough 
It finds the W83627EHF chip but W83627EHF isn't supported yet! :-(

I was hoping to force load the w83627hf or w83781d module so that I could at 
least read the variables but I am not quite sure of the syntax for an ISA-bus 
device (magic bus number '9191')??

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

Could someone please help me with the correct modprobe command?

Thank you again for your help.

Regards, Dan

[lm-sensors] ASUS K8V-X SE should be supported?

[Rudolf Marek]

> Could someone please help me with the correct modprobe command?

The force parameter is not worth the trouble I guess more easier would be to
backport the driver to your kernel version.

Unfortunately I do not have time to do do that for you but I can help via the
email. If you need it on comercial basis maybe somebody here can do it for some
kind of reward or money. (I could do that in my regular job)

Regards
Rudolf

[lm-sensors] ASUS K8V-X SE should be supported?

[Yuan Mu]

Hi Dan,

>> Could someone please help me with the correct modprobe command?
> 
> The force parameter is not worth the trouble I guess more easier would be to
> backport the driver to your kernel version.
> 
Maybe it should be redhat ? they sold EL to you ;)

Ok, i try to make 627ehf work on my board this morning, and the attachment is the results.

1. You need to install EL kernel source first(if not installed)
2. unzip the attachment.
3. "cd lm_sensors26/old"
4. "make install"(i hope you have load the bus driver correctly)


I must said i hope it can help you, but without WARRANTY.It's in a hurry.
And hope you can help test the 627ehf driver which Rudolf and David working on :)

-- 
Best Regards
Yuan Mu


=============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such  a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lm_sensors26.tar.gz
Type: application/gzip
Size: 12727 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060615/2bf72771/attachment-0001.bin 

[lm-sensors] ASUS K8V-X SE should be supported?

[Dogsbody]

> Maybe it should be redhat ? they sold EL to you ;)

No they didn't, I'm running CentOS ;)


> Ok, i try to make 627ehf work on my board this morning, and the 
> attachment is the results.
> 
> 1. You need to install EL kernel source first(if not installed)
> 2. unzip the attachment.
> 3. "cd lm_sensors26/old"
> 4. "make install"(i hope you have load the bus driver correctly)

Thank you very much for this unfortunately I have fallen at the first hurdle :-\
I thought I had managed to install the kernel source [1] but I can't get your 
makefile to run properly.  Compiling stuff I am happy with but I have never gone 
near the kernel before so I am not sure what I am doing there I'm afraid.


> I must said i hope it can help you, but without WARRANTY.It's in a hurry.
> And hope you can help test the 627ehf driver which Rudolf and David 
> working on :)

I saw the posts about the driver which is great :-)  I will help where I can but 
I don't want to be a burden.

Thanks again

Dan

[1]
wget http://mirror.centos.org/centos/4/updates/SRPMS/kernel-2.6.9-34.0.1.EL.src.rpm
rpm -iv kernel-2.6.9-34.0.1.EL.src.rpm

[lm-sensors] ASUS K8V-X SE should be supported?

[Yuan Mu]

Dogsbody wrote:
>> Maybe it should be redhat ? they sold EL to you ;)
> 
> No they didn't, I'm running CentOS ;)
> 
> 
>> Ok, i try to make 627ehf work on my board this morning, and the 
>> attachment is the results.
>>
>> 1. You need to install EL kernel source first(if not installed)
>> 2. unzip the attachment.
>> 3. "cd lm_sensors26/old"
>> 4. "make install"(i hope you have load the bus driver correctly)
> 
> Thank you very much for this unfortunately I have fallen at the first hurdle :-\
> I thought I had managed to install the kernel source [1] but I can't get your 
> makefile to run properly.  Compiling stuff I am happy with but I have never gone 
> near the kernel before so I am not sure what I am doing there I'm afraid.
> 

Next time please do "make 2>&1 | tee make.out", give me the make.out :)
> 
>> I must said i hope it can help you, but without WARRANTY.It's in a hurry.
>> And hope you can help test the 627ehf driver which Rudolf and David 
>> working on :)
> 
> I saw the posts about the driver which is great :-)  I will help where I can but 
> I don't want to be a burden.
> 
> Thanks again
> 
> Dan
> 
> [1]
> wget http://mirror.centos.org/centos/4/updates/SRPMS/kernel-2.6.9-34.0.1.EL.src.rpm
> rpm -iv kernel-2.6.9-34.0.1.EL.src.rpm
> 
hmm, a step to install RedhatEL source code, for your reference.
1. rpm -ivh kernel-2.6.9-22.EL.src.rpm
2. rpmbuild -bp --target=noarch /usr/src/redhat/SPECS/kernel-2.6.spec
3. cd /usr/src
4. ln -s redhat/BUILD/kernel-2.6.9/linux-2.6.9  /linux
5. cd /usr/src/linux
6. make mrproper
7. cp ./configs/kernel-2.6.9-x86_64-smp.config ./config
8. vi Makefile   added=> EXTRAVERSION =-22.ELsmp
9. make menuconfig => only save & exit
10. make all
11. make modules_install
12. make install
13. reboot system


-- 
Best Regards
Yuan Mu


=============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such  a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.

[lm-sensors] ASUS K8V-X SE should be supported?

[Dogsbody]

 > hmm, a step to install RedhatEL source code, for your reference.

Perfect, thank you.  I think this has worked fine! :-)


> Next time please do "make 2>&1 | tee make.out", give me the make.out :)

There wasn't much point before as I couldn't install the source (no 
/usr/src/linux).  However thanks to your help I have gotten much further!  it 
still errors though.... :-(

make -C /usr/src/linux M=/tmp/lm_sensors26/old modules
make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
   CC [M]  /tmp/lm_sensors26/old/w83627ehf.o
In file included from /tmp/lm_sensors26/old/w83627ehf.c:44:
/tmp/lm_sensors26/old/wbplatform.h:47: error: conflicting types for 'gfp_t'
include/linux/gfp.h:134: error: previous declaration of 'gfp_t' was here
/tmp/lm_sensors26/old/wbplatform.h:49: error: conflicting types for 'kzalloc'
include/linux/slab.h:101: error: previous declaration of 'kzalloc' was here
/tmp/lm_sensors26/old/wbplatform.h:49: error: conflicting types for 'kzalloc'
include/linux/slab.h:101: error: previous declaration of 'kzalloc' was here
make[2]: *** [/tmp/lm_sensors26/old/w83627ehf.o] Error 1
make[1]: *** [_module_/tmp/lm_sensors26/old] Error 2
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
make: *** [all] Error 2


I hope this helps!

Dan

[lm-sensors] ASUS K8V-X SE should be supported?

[Yuan Mu]

Hi Dan,

> There wasn't much point before as I couldn't install the source (no 
> /usr/src/linux).  However thanks to your help I have gotten much further!  it 
> still errors though.... :-(
> 
> make -C /usr/src/linux M=/tmp/lm_sensors26/old modules
> make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
>    CC [M]  /tmp/lm_sensors26/old/w83627ehf.o
> In file included from /tmp/lm_sensors26/old/w83627ehf.c:44:
> /tmp/lm_sensors26/old/wbplatform.h:47: error: conflicting types for 'gfp_t'
> include/linux/gfp.h:134: error: previous declaration of 'gfp_t' was here
> /tmp/lm_sensors26/old/wbplatform.h:49: error: conflicting types for 'kzalloc'
> include/linux/slab.h:101: error: previous declaration of 'kzalloc' was here
> /tmp/lm_sensors26/old/wbplatform.h:49: error: conflicting types for 'kzalloc'
> include/linux/slab.h:101: error: previous declaration of 'kzalloc' was here
> make[2]: *** [/tmp/lm_sensors26/old/w83627ehf.o] Error 1
> make[1]: *** [_module_/tmp/lm_sensors26/old] Error 2
> make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
> make: *** [all] Error 2

I modify something for you according to the error message, pls use the new attachment :)
I'm really sorry i don't have CentOs and i can not make sure it can work :(
Hope it can compile now.


-- 
Best Regards
Yuan Mu


=============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such  a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lm_sensors26_2.tar.gz
Type: application/gzip
Size: 12861 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060619/2b3f9bd3/attachment-0001.bin 

[lm-sensors] ASUS K8V-X SE should be supported?

[Dogsbody]

> I modify something for you according to the error message, pls use the 
> new attachment :)
> I'm really sorry i don't have CentOs and i can not make sure it can work :(
> Hope it can compile now.


It certainly compiles now :-)  but I haven't had a chance to test it yet I'm afraid!

Dan