sensors with kernel 2.4, but not with kernel 2.6 (Examined/Unsolved - lm_sensors in kernel 2.6.8)

[contact]

Before I switched to the test-releases of kernel-2.6 I used a regular

2.4-series-kernel. I had no problems with readings from my ASUS A7V8X (asb100,

i2c-viapro, w83781d).

I got all Fans, the two temperature-readings and some other stuff I can't

remember right now.

From Kernel-2.6 on, I never got these values back. sensors detect detects the

asb100 as well as i2c-viapro and w83781d -- exactly the modules it used to use

when I was running a 2.4-series kernel.

However, when I execute "sensors" I only get output representing my

bttv-tv-card, but no readings.

I waited that long with my report cos' I thought "hey, maybe it's a general

porting problem" but when I got back to fiddling around and examining why it

doesn't work with 2.6 for me I soon recognized that I am in a dead end. I simply

don't have any ideas remaining now.

Conclusive Output of sensors detect (skipped scanning of ISA-Bus and bt878 and

Super-IO):

Driver 'asb100' (should be inserted):

Detects correctly:

• Bus 'SMBus Via Pro adapter at e800' (Algorithm unavailable)

Busdriver 'i2c-viapro', I2C address 0x2d (and 0x48 0x49)

Chip 'Asus ASB100 Bach' (confidence: 8)

Driver 'w83781d' (may not be inserted):

Misdetects:

• Bus 'SMBus Via Pro adapter at e800' (Algorithm unavailable)

Busdriver 'i2c-viapro', I2C address 0x2f (and 0x48 0x49)

Chip 'Winbond W83791D' (confidence: 8)

Driver 'lm75' (may not be inserted):

Misdetects:

• Bus 'SMBus Via Pro adapter at e800' (Algorithm unavailable)

Busdriver 'i2c-viapro', I2C address 0x48

Chip 'National Semiconductor LM75' (confidence: 6)

• Bus 'SMBus Via Pro adapter at e800' (Algorithm unavailable)

Busdriver 'i2c-viapro', I2C address 0x49

Chip 'National Semiconductor LM75' (confidence: 4)

Driver 'smbus-arp' (should be inserted):

Detects correctly:

• Bus 'SMBus Via Pro adapter at e800' (Algorithm unavailable)

Busdriver 'i2c-viapro', I2C address 0x61

Chip 'SMBus 2.0 ARP-Capable Device' (confidence: 1)

List of i2c-/sensors-related modules loaded:

Module Size Used by

i2c_dev 9920 0

asb100 23488 0

i2c_sensor 2944 1 asb100

i2c_viapro 7052 0

Output of sensors:

Philips PAL_BG -i2c-0-61

Adapter: bt878 #0 [sw]

i2c IR -i2c-0-18

Adapter: bt878 #0 [sw]

tda9840-i2c-0-42

Adapter: bt878 #0 [sw]

MSP3410D-i2c-0-40

Adapter: bt878 #0 [sw]

"/dev"-information

2.4-kernel with devfs : worked

2.6-kernel with devfs : didn't work

2.6-kernel with udev : doesn't work

Thanks in advance - I hope you guys have an idea what's wrong.

Regards,

Benjamin

--- First, do NOT load the w83781d driver. You board has an ASB100 chip which is far

better supported by the new asb100 driver than by the w83781d driver. Also, make

sure that you are not loading the via686a driver, since it conflicts with

i2c-viapro in Linux 2.6.

Second, you do not mention the version of lm_sensors you are using, just like it

doesn't matter for a 2.6 kernel. It does. The lm_sensors package may not provide

kernel drivers for the 2.6 series, but it still provides the user-space library

and tools. Since the kernel-space/user-space interface changed several times

between the early 2.6 kernels, you should ensure that you use a recent version.

2.8.6 or later is required for proper operations with a 2.6.8 kernel. Newer is

even better.

If it still doesn't help, then you have to figure out what's going wrong. It

could be three things: the bus driver (i2c-viapro), the chip driver (asb100) or

the user-space interface or tools.

You should take a look at the logs (/var/log/syslog, /var/log/messages, dmesg)

when you load the i2c kernel modules. If anything goes wrong it should tell you.

If you compiled your kernel with I2C debugging enabled, you may also gather

useful additional information.

If both drivers load properly, you should take a look at /sys/bus/i2c/devices/.

In this directory, you should find a subdirectory for the asb100. If you don't,

then either kernel driver is faulty. If you do, then the kernel is fine and the

user-space if faulty.

Please follow-up on the mailing-list, reference your ticket number.

Khali 2004-11-03

[mmh]

Almost two years without reply from user. Sorry. [Probably just needed to upgrade user-space packages]