Scanning for the sensors seems to indicate the presence of a SIS5595 and probably a SIS950, which would make sense as it is a SIS based MB.
Probing for `Silicon Integrated Systems SIS5595' Trying general detect... Success! (confidence 9, driver `sis5595') Probing for `ITE IT8705F / IT8712F / SiS 950' Trying address 0x0290... Success! (confidence 8, driver `it87')
The it87 module loads ok but does not seem to show any sensor data and the SIS5595 module does not seem to load.
[root@leila root]# modprobe -d sis5595
=============================================
Module i2c-core
kname i2c-core
objkey i2c-core
names: i2c-core
mode: NORMAL
Module matching i2c-core: /lib/modules/2.4.22-1.2149.nptl/kernel/drivers/i2c/i2c-core.o
=============================================
=============================================
Module i2c-proc
kname i2c-proc
objkey i2c-proc
names: i2c-proc
mode: NORMAL
Module matching i2c-proc: /lib/modules/2.4.22-1.2149.nptl/kernel/drivers/i2c/i2c-proc.o
=============================================
=============================================
Module sis5595
kname sis5595
objkey sis5595
names: sis5595
mode: NORMAL
Module matching sis5595: /lib/modules/2.4.22-1.2149.nptl/kernel/drivers/sensors/sis5595.o
=============================================
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/sensors/sis5595.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/sensors/sis5595.o: insmod /lib/modules/2.4.22-1.2149.nptl/kernel/drivers/sensors/sis5595.o failed
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/sensors/sis5595.o: insmod sis5595 failed
[root@leila root]# dmesg sis5595.o version 2.6.5 (20020915) sis5595.o: Error: Looked for SIS5595 but found unsupported device 0630 sis5595.o: SIS5595 not detected, module not inserted.
A little knowledge may be dangerous. I did some research and found out where to look for the 5595 sensor data. Apparently all 0xff would indicate no data but that does not seem to be the case.
[root@leila root]# isadump 0x295 0x296 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 11 00 ff 00 00 00 00 00 00 00 00 5b 00 ff ff ff 10: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 7c 99 cd ba bc d4 47 b8 cf 23 1f c9 00 00 00 00 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 40: ff ff ff ff ff ff 00 00 2d 00 00 00 00 00 00 00 50: ff 38 7f 7f 7f 00 00 00 90 30 02 00 80 00 00 00 60: 7f 7f 7f 7f 7f 00 00 00 7f 7f 7f 7f 7f 00 00 00 70: 7f 7f 7f 7f 7f 00 00 00 00 00 00 00 00 00 00 00 80: 11 00 00 00 00 00 00 00 00 00 00 5b 00 ff ff ff 90: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 7c 99 cd ba bc d4 47 b8 cf 23 1f c9 00 00 00 00 b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff c0: ff ff ff ff ff ff 00 00 2d 00 00 00 00 00 00 00 d0: ff 38 7f 7f 7f 00 00 00 90 30 02 00 80 00 00 00 e0: 7f 7f 7f 7f 7f 00 00 00 7f 7f 7f 7f 7f 00 00 00 f0: 7f 7f 7f 7f 7f 00 00 00 00 00 00 00 00 00 00 00
Does this mean that I need to get the sis5595.o source and remove the 630 blocking or am I misinterpreting this somewhere along the way.
Kind regards,
Mike