[lm-sensors] Detection of W83L771AWG/ASG in lm90

[lm-sensors] Detection of W83L771AWG/ASG in lm90

[Alexander Stein]

Hello,

'sensors-detect' shows me there is W83L771W/G on my board:
> Probing for `Winbond W83L771W/G'...                         Success!
>     (confidence 6, driver `to-be-written')
According to this wiki page http://www.lm-sensors.org/wiki/Devices support 
should be handles by the lm90 driver. But after loading the lm90 driver, 
'sensors' doesn't show any new device. Also loading the driver by the alias 
"i2c:w83l771" doesn't help. Oh, i nearly forgot, I'm running 2.6.34-gentoo-
r11.
Any comments/suggestions?

Regards,
Alexander

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

Re: [lm-sensors] Detection of W83L771AWG/ASG in lm90

[Jean Delvare]

Hallo Alexander,

On Wed, 13 Oct 2010 15:40:18 +0200, Alexander Stein wrote:
> 'sensors-detect' shows me there is W83L771W/G on my board:
> > Probing for `Winbond W83L771W/G'...                         Success!
> >     (confidence 6, driver `to-be-written')
> According to this wiki page http://www.lm-sensors.org/wiki/Devices support 
> should be handles by the lm90 driver. But after loading the lm90 driver, 
> 'sensors' doesn't show any new device. Also loading the driver by the alias 
> "i2c:w83l771" doesn't help. Oh, i nearly forgot, I'm running 2.6.34-gentoo-
> r11.
> Any comments/suggestions?

Which I2C adapter is your W83L771W/G sitting on? The sensors-detect
script will probe any adapter, however the lm90 driver can only
auto-detect devices on I2C adapters which have properly set their class
to I2C_CLASS_HWMON.

-- 
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] Detection of W83L771AWG/ASG in lm90

[Alexander Stein]

Hello Jean,

On Wednesday 13 October 2010, 15:57:41 you wrote:
> On Wed, 13 Oct 2010 15:40:18 +0200, Alexander Stein wrote:
> > 'sensors-detect' shows me there is W83L771W/G on my board:
> > > Probing for `Winbond W83L771W/G'...                         Success!
> > > 
> > >     (confidence 6, driver `to-be-written')
> > 
> > According to this wiki page http://www.lm-sensors.org/wiki/Devices
> > support should be handles by the lm90 driver. But after loading the lm90
> > driver, 'sensors' doesn't show any new device. Also loading the driver
> > by the alias "i2c:w83l771" doesn't help. Oh, i nearly forgot, I'm
> > running 2.6.34-gentoo- r11.
> > Any comments/suggestions?
> 
> Which I2C adapter is your W83L771W/G sitting on? The sensors-detect
> script will probe any adapter, however the lm90 driver can only
> auto-detect devices on I2C adapters which have properly set their class
> to I2C_CLASS_HWMON.

Here is a part from my sensors-detect output:
> Using driver `i2c-nforce2' for device 0000:00:01.1: nVidia Corporation
> nForce SMBus (MCP61)
> 
> Next adapter: SMBus nForce2 adapter at 5000 (i2c-0)
> Do you want to scan it? (yes/NO/selectively): yes
> Client found at address 0x4c
> Probing for `National Semiconductor LM75'...                No
> Probing for `Dallas Semiconductor DS75'...                  No
> Probing for `Analog Devices ADT7466'...                     No
> Probing for `Andigilog aSC7511'...                          No
> Probing for `Dallas Semiconductor DS1621/DS1631'...         No
> Probing for `Analog Devices ADM1021'...                     No
> Probing for `Analog Devices ADM1021A/ADM1023'...            No
> Probing for `Maxim MAX1617'...                              No
> Probing for `Maxim MAX1617A'...                             No
> Probing for `Maxim MAX1668'...                              No
> Probing for `Maxim MAX1805'...                              No
> Probing for `Maxim MAX1989'...                              No
> Probing for `Maxim MAX6655/MAX6656'...                      No
> Probing for `TI THMC10'...                                  No
> Probing for `National Semiconductor LM84'...                No
> Probing for `Genesys Logic GL523SM'...                      No
> Probing for `Onsemi MC1066'...                              No
> Probing for `Maxim MAX1618'...                              No
> Probing for `Maxim MAX1619'...                              No
> Probing for `National Semiconductor LM82/LM83'...           No
> Probing for `National Semiconductor LM90'...                No
> Probing for `National Semiconductor LM89/LM99'...           No
> Probing for `National Semiconductor LM86'...                No
> Probing for `Analog Devices ADM1032'...                     No
> Probing for `Maxim MAX6654/MAX6690'...                      No
> Probing for `Maxim MAX6657/MAX6658/MAX6659'...              No
> Probing for `Maxim MAX6648/MAX6649/MAX6692'...              No
> Probing for `Maxim MAX6680/MAX6681'...                      No
> Probing for `Winbond W83L771W/G'...                         Success!
> 
>     (confidence 6, driver `to-be-written')
> 
> Probing for `Winbond W83L771AWG/ASG'...                     No
> Probing for `Texas Instruments TMP401'...                   No
> Probing for `Texas Instruments TMP411'...                   No
> Probing for `Texas Instruments TMP421'...                   No
> Probing for `Texas Instruments TMP422'...                   No
> Probing for `Texas Instruments TMP423'...                   No
> Probing for `Texas Instruments AMC6821'...                  No
> Probing for `National Semiconductor LM63'...                No
> Probing for `Fintek F75363SG'...                            No
> Probing for `National Semiconductor LM73'...                No
> Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
> Probing for `Analog Devices ADT7461'...                     No
> Probing for `Analog Devices ADT7481'...                     No
> Probing for `Fintek F75383S/M'...                           No
> Client found at address 0x50
> Probing for `Analog Devices ADM1033'...                     No
> Probing for `Analog Devices ADM1034'...                     No
> Probing for `SPD EEPROM'...                                 Yes
> 
>     (confidence 8, not a hardware monitoring chip)
> 
> Probing for `EDID EEPROM'...                                No
> Client found at address 0x51
> Probing for `Analog Devices ADM1033'...                     No
> Probing for `Analog Devices ADM1034'...                     No
> Probing for `SPD EEPROM'...                                 Yes
> 
>     (confidence 8, not a hardware monitoring chip)
> 
> Client found at address 0x52
> Probing for `Analog Devices ADM1033'...                     No
> Probing for `Analog Devices ADM1034'...                     No
> Probing for `SPD EEPROM'...                                 Yes
> 
>     (confidence 8, not a hardware monitoring chip)
> 
> Client found at address 0x53
> Probing for `Analog Devices ADM1033'...                     No
> Probing for `Analog Devices ADM1034'...                     No
> Probing for `SPD EEPROM'...                                 Yes
> 
>     (confidence 8, not a hardware monitoring chip)

So it seems, it's the i2c-nforce2 driver for a SMBus nForce2 adapter. From a 
short grep in i2c-nforce2.c it seems that I2C_CLASS_HWMON is passed to the 
supported flags. Anyway, how can I name the exact device to be used by lm90?

Best regards,
Alexander

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

Re: [lm-sensors] Detection of W83L771AWG/ASG in lm90

[Jean Delvare]

Hi again Alexander,

On Wed, 13 Oct 2010 17:02:17 +0200, Alexander Stein wrote:
> > Probing for `Winbond W83L771W/G'...                         Success!
> > 
> >     (confidence 6, driver `to-be-written')
> > 
> > Probing for `Winbond W83L771AWG/ASG'...                     No

Oh, I get it now. What the lm90 driver currently supports is the recent
W83L771AWG/ASG. It doesn't have detection for the old W83L771W/G. In
all honesty I wasn't sure if that one had ever been used in a public
product, and its detection is somewhat weak, which is why I didn't add
support (if I remember correctly, at least.)

First thing to do is ensure this isn't a misdetection. Please send a
dump of the chip:

# (install i2c-tools)
# modprobe i2c-dev
# i2cdump 0 0x4c b

If you really have that old chip then I'll add support to the lm90
driver. Meanwhile you can force the lm90 driver to attach to it by
using the following command:

# echo w83L771 0x4c > /sys/devices/i2c-0/new_device

(I hope the path is right for kernel 2.6.34 already.)

> (...)
> So it seems, it's the i2c-nforce2 driver for a SMBus nForce2 adapter. From a 
> short grep in i2c-nforce2.c it seems that I2C_CLASS_HWMON is passed to the 
> supported flags. Anyway, how can I name the exact device to be used by lm90?

Yes, you're right. My first guess was wrong.

-- 
Jean Delvare

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

Re: [lm-sensors] Detection of W83L771AWG/ASG in lm90

[Guenter Roeck]

On Wed, 2010-10-13 at 11:43 -0400, Jean Delvare wrote:
[ ... ]
> # echo w83L771 0x4c > /sys/devices/i2c-0/new_device
> 
Does that work, or would it have to be w83l771 (lower case) ?

Guenter



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

Re: [lm-sensors] Detection of W83L771AWG/ASG in lm90

[Jean Delvare]

On Wed, 13 Oct 2010 08:54:08 -0700, Guenter Roeck wrote:
> On Wed, 2010-10-13 at 11:43 -0400, Jean Delvare wrote:
> [ ... ]
> > # echo w83L771 0x4c > /sys/devices/i2c-0/new_device
> > 
> Does that work, or would it have to be w83l771 (lower case) ?

Oh, good catch. This is a typo! I definitely meant w83l771 (lower case).

-- 
Jean Delvare

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

Re: [lm-sensors] Detection of W83L771AWG/ASG in lm90

[Alexander Stein]

Hello Jean,

On Wednesday 13 October 2010, 17:43:50 Jean Delvare wrote:
> On Wed, 13 Oct 2010 17:02:17 +0200, Alexander Stein wrote:
> > > Probing for `Winbond W83L771W/G'...                         Success!
> > > 
> > >     (confidence 6, driver `to-be-written')
> > > 
> > > Probing for `Winbond W83L771AWG/ASG'...                     No
> 
> Oh, I get it now. What the lm90 driver currently supports is the recent
> W83L771AWG/ASG. It doesn't have detection for the old W83L771W/G. In
> all honesty I wasn't sure if that one had ever been used in a public
> product, and its detection is somewhat weak, which is why I didn't add
> support (if I remember correctly, at least.)

It is from my motherboard, it's a ASRock ALiveNF6G-DVI.

> First thing to do is ensure this isn't a misdetection. Please send a
> dump of the chip:
> 
> # (install i2c-tools)
> # modprobe i2c-dev
> # i2cdump 0 0x4c b

Here is the output:
> # i2cdump 0 0x4c b
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-0, address 0x4c, mode byte
> Continue? [Y/n] 
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
> 00: 21 1f 80 01 06 46 00 46 00 ff ff ff ff ff ff ff    !????F.F........
> 10: 20 00 00 00 00 ff ff ff ff 6e ff ff ff ff ff ff     ........n......
> 20: 55 0a ff ff ff ff ff ff ff ff ff ff ff ff ff ff    U?..............
> 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 06    ...............?
> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> e0: bb c0 82 bb c0 1f 21 24 82 ff ff 4b 06 ff ff ff    ??????!$?..K?...
> f0: ff 20 00 10 80 00 ff 00 00 02 00 50 4a 16 5c 01    . .??....?.PJ?\?

> If you really have that old chip then I'll add support to the lm90
> driver. Meanwhile you can force the lm90 driver to attach to it by
> using the following command:
> 
> # echo w83L771 0x4c > /sys/devices/i2c-0/new_device
> 
> (I hope the path is right for kernel 2.6.34 already.)

Nope, one possible path is /sys/bus/i2c/devices/i2c-0/new_device, but with the 
lower case name, as Guenter pointed out, it seems to work. Even with kernel 
module autoloading.

Thanks a lot you two so far. If you want some testing on chip detection, drop 
me a line.

Best regards,
Alexander

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