Re: Ticket #116 (Examined/Solved - lm_sensors 2.3.4 Linux 2.2.10 (Slackware 4.0))

[contact]

This is strange. The first thing I'd think about is a bus hang. This is usually solved by rebooting, but if you use an ATX case (which is optional on the TX97E, IIRC), the boots may not be 'cold' enough. Reboot after making sure you have disconnected the power for about a minute.

This is an option, but I've got it hooked up in an AT case with an AT power supply - I went ahead and unplugged anyway, but that probably wasn't it.

If this does not help, I suspect you have a hardware failure. Please recompile lm_sensors with DEBUG=1 and send us the output of dmesg after you inserted module i2c-piix4.

OK, when I start it up: i2c-piix4.o Transaction (pre): CNT=04, CMD=48, ADD=c9, DAT0=1c, DAT1=7f i2c-piix4.o: Error: no response! i2c-piix4.o Transaction (post): CNT=04, CMD=48, ADD=c9, DAT0=1c, DAT1=7f Could be a hardware failure then? Which is DAT2? I'm assuming that DAT0-DAT6 correspond with IN0-IN6? Incidentally, when I re-compiled this time, I end up with 2 errors when I run depmod -a: modprobe: not an ELF file /lib/modules/2.2.10/misc/gl518sm.o: unresolved symbol(s) This shouldn't affect me because I don't use the gl518sm module, but now I can't find any mention of sensors in /proc/*. (I think it used to be in /proc/sys/dev or something). Thanks again, -- Elliott

Frodo

--- Those logs from i2c-piix4.o are 'packet-level' debugging output from the SMBus host. The registers are different parts of the SMBus/I2C packet. A 'no response' means that there wasn't a response from the packet which usually means that the device isn't at the address specified. During normal operation there are several 'no responses' which occur, so don't worry. BTW- If you are getting wierd errors like that 'not an ELF file', then I suspect that you have other issues happening (a filled harddrive, a dying harddrive?, something else?!). Please follow up to lm78@… if needed, and don't post another ticket (tickets don't 'thread' well :'). --Phil