SMBus of Sis650/961 P4 system not recognised
Problem: sensors-detect, revision 5249, doesn't detect any sensors.
System:
A928 ECS Desknote
HW: P4, SiS 650/961 motherboard
SW: Debian Etch 40R1, Linux 2.6.18-6, lm-sensors 3.0.2
Analysis, yet without solution:
Under Windows XP (FanSpeed programme) a Winbond W83L784R and two LM75 are detected and temperatures properly represented.
Linux loads the i2c-sis96x busses driver.
The chipset presents itself with vendor ID 1039 and devices IDs 0008 and 0650 and 6325 (and 5513, 7012, 0001, 7012 but irrelevant here).
FanSpeed (WinXP on dual-boot system) reports:
SiS650 SMBus at $0B80
ISA Bus at $0290 SuperIO Winbond W83L517D SiSx30 SMBus at $0B80 Winbond W83L784R (ID=$51) @ $2D LM75 @ $48 LM75 @ $49
How can I make lm-sensors / sensors-detect, and/or Linux 2.6.18-6 to discover this SMBus @ $0B80 with the sensors on it ??
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2c
Hi person-with-no-name,
Quoted 23 lines · On Sun, 14 Sep 2008 12:29:41 +0100, subscriptions-EwJsF0SrM7dWk0Htik3J/w@public…
Problem: sensors-detect, revision 5249, doesn't detect any sensors.
System:
A928 ECS Desknote
HW: P4, SiS 650/961 motherboard
SW: Debian Etch 40R1, Linux 2.6.18-6, lm-sensors 3.0.2Analysis, yet without solution:
Under Windows XP (FanSpeed programme) a Winbond W83L784R and two LM75 are detected and temperatures properly represented.
Linux loads the i2c-sis96x busses driver.
The chipset presents itself with vendor ID 1039 and devices IDs 0008 and 0650 and 6325 (and 5513, 7012, 0001, 7012 but irrelevant here).FanSpeed (WinXP on dual-boot system) reports:
SiS650 SMBus at $0B80ISA Bus at $0290 SuperIO Winbond W83L517D SiSx30 SMBus at $0B80 Winbond W83L784R (ID=$51) @ $2D LM75 @ $48 LM75 @ $49
Quoted 2 lines
How can I make lm-sensors / sensors-detect, and/or Linux 2.6.18-6 to discover this SMBus @ $0B80 with the sensors on it ??
There are two separate issues here, which you are apparently mixing.
* The SiS south bridge itself doesn't include any sensors. It implements an SMBus master. You need to get this one to work first. You say that Linus loads the i2c-sis96x driver, which may or may not mean that it works (SiS chips are very odd to identify, as can be seen with FanSpeed too.) So, first of all, please do:
modprobe i2c-dev
i2cdetect -l
And see if there's an SMBus listed for the SiS chip. If it is, you can additionally run i2cdetect on it to see if devices connected to the bus are seen.
* The sensor chip itself is, in your case, connected to the SMBus. You need a separate driver for it. This is not the right list to discuss this though, please use the lm-sensors list instead.
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
A message that is not in the archive (sent off-list or not yet received): 1221928948.32367.4.camel@localhost
Hi Martin,
Please keep the i2c list Cc'd.
Quoted 5 lines · On Sat, 20 Sep 2008 17:42:27 +0100, subscriptions-EwJsF0SrM7dWk0Htik3J/w@public…
your response is most appreciated. ! However after loading the 12c-dev module successfully I cannot run i2cdetect as it seems not to be a part of the latest lm-sensors (3.0.2) for 2.6 kernels.
What should I do to cure the absence of this detection utility ?
i2cdetect is part of the i2c-tools package:
http://www.lm-sensors.org/wiki/I2CTools
Signature · 6 lines
Jean Delvare _______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
A message that is not in the archive (sent off-list or not yet received): [email protected]
Thanks; had not seen a reference to the separate tools package; now compiled the i2ctools and ran i2cdetect:
------------------------------------------------------------------
Installed I2C busses:
i2c-0 smbus SiS96x SMBus adapter at 0x0c00
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: -- -- -- -- -- 08 -- -- -- -- -- -- --
10: 10 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- 2d -- --
30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 49 -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- 69 6a -- -- -- -- --
70: -- -- -- -- -- -- -- --
-------------------------------------------------------------------
So the bus is seen; 2d, 48, and 49 correspond to what Fanspeed reported to be a Winbond W83L517D and two LM75, albeit that Fanspeed reported the SMBus to be at $0B80 and i2cdetect reports it to be at $0c00.
Will post my question about how to get a driver istalled for the W83L517D and used by lm-sensors in the other mailing list. Thanks for your help Jean !
Quoted 5 lines · Jean Delvare
Hi Martin,
Please keep the i2c list Cc'd.
On Sat, 20 Sep 2008 17:42:27 +0100, subscriptions-EwJsF0SrM7dWk0Htik3J/[email protected] wrote:
Quoted 9 lines
Quoted 5 lines
your response is most appreciated. ! However after loading the 12c-dev module successfully I cannot run i2cdetect as it seems not to be a part of the latest lm-sensors (3.0.2) for 2.6 kernels.
What should I do to cure the absence of this detection utility ?
i2cdetect is part of the i2c-tools package:
http://www.lm-sensors.org/wiki/I2CTools
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2c