Hi Peter, On Sat, 27 Jan 2007 20:49:13 +0100 (CET), Peter Welzien wrote: > Hello everyone. I'm having troubles getting lm_sensors to work. My dist is > Gentoo 2006.1, gentoo-kernel 2.6.18-r6, the motherboard is a Gigabyte > GA-6???? something. I can lookup the exact model if you like. lm_sensors > 2.10.1 Yes, please lookup the exact model. > The problems is that the computer hangs if I run sensors-detect and select > to scan the SMBus PIIx4 adapter. It completly stops responding and I have > to reset it. > > sensors-detect also reports: > Trying family `ITE'... Yes > Found unknown chip with ID 0xdf0e Strange, this really doesn't look like a regular ITE chip ID. Probably a misdetection. Can you visually search for the Super-I/O chip on your motherboard? > > If I load the it87 module the computer also hangs. In 2.6.18, the it87 driver does only probe one SMBus address (0x2d), I guess this probing is hanging the computer just as sensors-detect. Could be that you have a special chip at this address, or that just sending anything on the SMBus locks it. Most probably, loading about any i2c chip driver would lock the system too. Whatever your Super-I/O chip is, it certainly isn't compatible with the it87 driver anyway. > > Below is the output from sensors-detect: > > # sensors-detect revision 4171 (2006-09-24 03:37:01 -0700) > > We can start with probing for (PCI) I2C or SMBus adapters. > Do you want to probe now? (YES/no): > Probing for PCI bus adapters... > Use driver `i2c-piix4' for device 0000:00:0f.0: ServerWorks OSB4 South Bridge > > We will now try to load each adapter module in turn. > Module `i2c-piix4' already loaded. > > Next adapter: SMBus PIIX4 adapter at 0580 > Do you want to scan it? (YES/no/selectively): n > > Do you want to scan the ISA I/O ports? (YES/no): > Probing for `National Semiconductor LM78' at 0x290... No > Probing for `National Semiconductor LM78-J' at 0x290... No > Probing for `National Semiconductor LM79' at 0x290... No > Probing for `Winbond W83781D' at 0x290... No > Probing for `Winbond W83782D' at 0x290... No > Probing for `Winbond W83627HF' at 0x290... No > Probing for `Silicon Integrated Systems SIS5595'... No > Probing for `VIA VT82C686 Integrated Sensors'... No > Probing for `VIA VT8231 Integrated Sensors'... No > Probing for `AMD K8 thermal sensors'... No > Probing for `IPMI BMC KCS' at 0xca0... No > Probing for `IPMI BMC SMIC' at 0xca8... No > > Do you want to scan for Super I/O sensors? (YES/no): > Probing for Super-I/O at 0x2e/0x2f > Trying family `ITE'... Yes > Found unknown chip with ID 0xdf0e > Trying family `National Semiconductor'... No > Trying family `SMSC'... No > Trying family `VIA/Winbond/Fintek'... No > Probing for Super-I/O at 0x4e/0x4f > Trying family `ITE'... No > Trying family `National Semiconductor'... No > Trying family `SMSC'... No > Trying family `VIA/Winbond/Fintek'... No > > Sorry, no sensors were detected. > > lspci: > > 00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 06) > 00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 06) > 00:05.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg > NIC (rev 01) > 00:07.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro > 100] (rev 08) > 00:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro > 100] (rev 08) > 00:09.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) > 00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50) > 00:0f.1 IDE interface: Broadcom OSB4 IDE Controller > 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 04) > > Does anybody have an idea what might be wrong? Just odd hardware, most probably. First of all, do you have a reason to think that this motherboard has hardware monitoring features? Do you see them in the BIOS or using a different OS? It seems to be a rather old model, it wouldn't be all that surprising that it simply doesn't support hardware monitoring. Try using i2cdetect to scan the SMBus. If even that locks the bus, it's probably the SMBus itself which doesn't work. Did you pass specific parameters to the i2c-piix4 driver? Are there messages in the logs when the i2c-piix4 driver is loaded? You should look for BIOS updates, too. -- Jean Delvare
