Hi Aleksic, On Thu, 2 Nov 2006 18:31:40 +0100, Petar Aleksich wrote: > I've been using lm_sensors ( i2c-i801, asb100, eeprom ) for > months without any problems , recently after kernel upgrade from 2.6.16 > series to >=2.6.17 sensors-detect can't find any modules. What motherboard is this, please? > --------------------- > Used: > sysfsutils-2.1.0 > lm_sensors-2.10.1 > gcc-4.4.1 > glibc-2.4 > > --------------------------- > # uname -a > Linux phearless 2.6.18-ck1-r1 #2 PREEMPT Thu Nov 2 13:38:21 CET 2006 > i686 Intel(R) Celeron(R) CPU 1.70GHz GenuineIntel GNU/Linux > --------------------------- > # sensors-detect > > Do you want to scan the ISA I/O ports? (YES/no): Y > 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 > > Some Super I/O chips may also contain sensors. We have to write to > standard I/O ports to probe them. This is usually safe. > Do you want to scan for Super I/O sensors? (YES/no): Y > Probing for Super-I/O at 0x2e/0x2f > Trying family `ITE'... No > Trying family `National Semiconductor'... No > Trying family `SMSC'... No > Trying family `VIA/Winbond/Fintek'... Yes > Found unknown chip with ID 0x8708 This is unrelated with your problem, but thanks for reporting. This is most certainly an ITE IT8708 chip, although I'm surprised it is detected in the wrong family. If you have physical access to the system, can you please take a look and locate the Super-I/O chip to confirm that it is an ITE IT8708? It should look like this but with a different top marking: http://www.beareyes.net/2/lib/200603/31/007/DSCN9815.jpg We don't have any documentation for this chip, I doubt it has any hardware monitoring features, and if it had, they would certainly not be used on your motherboard, as you say it has a dedicated chip for that (Asus ASB100 "Bach"). > 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. > Either your sensors are not supported, or they are connected to an > I2C or SMBus adapter that is not supported. See doc/FAQ, > doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ > (FAQ #4.24.3) for further information. > If you find out what chips are on your board, check > http://www.lm-sensors.org/wiki/Devices for driver status. > > ---------------------------- > # sensors -s > No sensors found! > Make sure you loaded all the kernel drivers you need. > Try sensors-detect to find out which these are. > ---------------------------- > > # grep "I2C" /usr/src/linux-`uname -r`/.config > > # I2C support > CONFIG_I2C=m > CONFIG_I2C_CHARDEV=m > # I2C Algorithms > CONFIG_I2C_ALGOBIT=m > CONFIG_I2C_ALGOPCF=m > CONFIG_I2C_ALGOPCA=m > # I2C Hardware Bus support > CONFIG_I2C_ALI1535=m > CONFIG_I2C_ALI1563=m > CONFIG_I2C_ALI15X3=m > CONFIG_I2C_AMD756=m > CONFIG_I2C_AMD756_S4882=m > CONFIG_I2C_AMD8111=m > CONFIG_I2C_ELEKTOR=m > CONFIG_I2C_I801=m > CONFIG_I2C_I810=m > CONFIG_I2C_PIIX4=m > CONFIG_I2C_ISA=m > CONFIG_I2C_NFORCE2=m > CONFIG_I2C_OCORES=m > CONFIG_I2C_PARPORT=m > CONFIG_I2C_PARPORT_LIGHT=m > CONFIG_I2C_PROSAVAGE=m > CONFIG_I2C_SAVAGE4=m > CONFIG_I2C_SIS5595=m > CONFIG_I2C_SIS630=m > CONFIG_I2C_SIS96X=m > CONFIG_I2C_STUB=m > CONFIG_I2C_VIA=m > CONFIG_I2C_VIAPRO=m > CONFIG_I2C_VOODOO3=m > CONFIG_I2C_PCA_ISA=m > # Miscellaneous I2C Chip support > # CONFIG_I2C_DEBUG_CORE is not set > # CONFIG_I2C_DEBUG_ALGO is not set > # CONFIG_I2C_DEBUG_BUS is not set > # CONFIG_I2C_DEBUG_CHIP is not set > > ----------------------- > # egrep "(HWM|SENSORS)" /usr/src/linux-`uname -r`/.config > > CONFIG_SENSORS_DS1337=m > CONFIG_SENSORS_DS1374=m > CONFIG_SENSORS_EEPROM=m > CONFIG_SENSORS_PCF8574=m > CONFIG_SENSORS_PCA9539=m > CONFIG_SENSORS_PCF8591=m > CONFIG_SENSORS_MAX6875=m > CONFIG_HWMON=m > CONFIG_HWMON_VID=m > CONFIG_SENSORS_ABITUGURU=m > CONFIG_SENSORS_ADM1021=m > CONFIG_SENSORS_ADM1025=m > CONFIG_SENSORS_ADM1026=m > CONFIG_SENSORS_ADM1031=m > CONFIG_SENSORS_ADM9240=m > CONFIG_SENSORS_ASB100=m > CONFIG_SENSORS_ATXP1=m > CONFIG_SENSORS_DS1621=m > CONFIG_SENSORS_F71805F=m > CONFIG_SENSORS_FSCHER=m > CONFIG_SENSORS_FSCPOS=m > CONFIG_SENSORS_GL518SM=m > CONFIG_SENSORS_GL520SM=m > CONFIG_SENSORS_IT87=m > CONFIG_SENSORS_LM63=m > CONFIG_SENSORS_LM75=m > CONFIG_SENSORS_LM77=m > CONFIG_SENSORS_LM78=m > CONFIG_SENSORS_LM80=m > CONFIG_SENSORS_LM83=m > CONFIG_SENSORS_LM85=m > CONFIG_SENSORS_LM87=m > CONFIG_SENSORS_LM90=m > CONFIG_SENSORS_LM92=m > CONFIG_SENSORS_MAX1619=m > CONFIG_SENSORS_PC87360=m > CONFIG_SENSORS_SIS5595=m > CONFIG_SENSORS_SMSC47M1=m > CONFIG_SENSORS_SMSC47M192=m > CONFIG_SENSORS_SMSC47B397=m > CONFIG_SENSORS_VIA686A=m > CONFIG_SENSORS_VT8231=m > CONFIG_SENSORS_W83781D=m > CONFIG_SENSORS_W83791D=m > CONFIG_SENSORS_W83792D=m > CONFIG_SENSORS_W83L785TS=m > CONFIG_SENSORS_W83627HF=m > CONFIG_SENSORS_W83627EHF=m > CONFIG_SENSORS_HDAPS=m > # CONFIG_HWMON_DEBUG_CHIP is not set > > ------------- > > # lspci -v > 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE > DRAM Controller/Host-Hub Interface (rev 02) Subsystem: ASUSTeK Computer > Inc. Unknown device 80b2 Flags: bus master, fast devsel, latency 0 > Memory at e0000000 (32-bit, prefetchable) [size=256M] > Capabilities: [e4] Vendor Specific Information > Capabilities: [a0] AGP version 2.0 > > 00:01.0 PCI bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE > Host-to-AGP Bridge (rev 02) (prog-if 00 [Normal decode]) Flags: bus > master, 66MHz, fast devsel, latency 64 Bus: primary=00, secondary=01, > subordinate=01, sec-latency=0 I/O behind bridge: 0000d000-0000dfff > Memory behind bridge: c6800000-c7efffff > Prefetchable memory behind bridge: c8000000-dfffffff > > 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) (prog-if 00 > [UHCI]) Subsystem: ASUSTeK Computer Inc. Unknown device 8089 Flags: bus > master, medium devsel, latency 0, IRQ 5 I/O ports at b800 [size=32] > > 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) (prog-if 00 > [UHCI]) Subsystem: ASUSTeK Computer Inc. Unknown device 8089 Flags: bus > master, medium devsel, latency 0, IRQ 9 I/O ports at b400 [size=32] > > 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) (prog-if 00 > [UHCI]) Subsystem: ASUSTeK Computer Inc. Unknown device 8089 Flags: bus > master, medium devsel, latency 0, IRQ 9 I/O ports at b000 [size=32] > > 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) > USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI]) Subsystem: ASUSTeK > Computer Inc. Unknown device 8089 Flags: bus master, medium devsel, > latency 0, IRQ 11 Memory at c6000000 (32-bit, non-prefetchable) > [size=1K] Capabilities: [50] Power Management version 2 > Capabilities: [58] Debug port > > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82) > (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 > I/O behind bridge: 00009000-0000afff > Memory behind bridge: c3800000-c5ffffff > Prefetchable memory behind bridge: c7f00000-c7ffffff > > 00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC > Interface Bridge (rev 02) Flags: bus master, medium devsel, latency 0 > > 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller > (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: ASUSTeK Computer > Inc. Unknown device 8089 Flags: bus master, medium devsel, latency 0, > IRQ 9 I/O ports at <unassigned> > I/O ports at <unassigned> > I/O ports at <unassigned> > I/O ports at <unassigned> > I/O ports at f000 [size=16] > Memory at 30000000 (32-bit, non-prefetchable) [size=1K] > > 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02) Subsystem: ASUSTeK > Computer Inc. Unknown device 80b0 Flags: bus master, medium devsel, > latency 0, IRQ 9 I/O ports at 8800 [size=256] > I/O ports at 8400 [size=64] > Memory at c3000000 (32-bit, non-prefetchable) [size=512] > Memory at c2800000 (32-bit, non-prefetchable) [size=256] > Capabilities: [50] Power Management version 2 The SMBus device is missing, it should show at address 00:1f.3. That explains why sensors-detect didn't find your hardware monitoring chips. You are most certainly affected by this change: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ce007ea59729d627f62bb5fa8c1a81e25653a0ad Long story short, Asus is hiding the SMBus on many boards, Linux tries to unhide them, but it is dangerous to do so when suspend/resume support is enabled, so since 2.6.17 the quirk which unhides the SMBus is disabled when suspend support is enabled. If you want your sensors back, you'll need to disable suspend support for now ("Sleep States" in the ACPI menu.) I know it is a regression for some users, but that's the only safe way until the kernel is taught how to replay PCI quirks on resume. Alternatively you can go bug Asus and ask them why they hide the SMBus in the first place. > 01:00.0 VGA compatible controller: ATI Technologies Inc R420 JP [Radeon > X800XT] (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Unknown > device 0002 Flags: bus master, 66MHz, medium devsel, latency 255, IRQ 5 > Memory at d8000000 (32-bit, prefetchable) [size=128M] > I/O ports at d800 [size=256] > Memory at c7000000 (32-bit, non-prefetchable) [size=64K] > Expansion ROM at d7fe0000 [disabled] [size=128K] > Capabilities: [58] AGP version 2.0 > Capabilities: [50] Power Management version 2 > > 01:00.1 Display controller: ATI Technologies Inc R420 [X800XT-PE] > (Secondary) Subsystem: ATI Technologies Inc Unknown device 0003 > Flags: bus master, 66MHz, medium devsel, latency 64 > Memory at c8000000 (32-bit, prefetchable) [size=128M] > Memory at c6800000 (32-bit, non-prefetchable) [size=64K] > Capabilities: [50] Power Management version 2 > > 02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host > Controller (rev 80) (prog-if 10 [OHCI]) Subsystem: VIA Technologies, > Inc. IEEE 1394 Host Controller Flags: bus master, stepping, medium > devsel, latency 32, IRQ 9 Memory at c5800000 (32-bit, non-prefetchable) > [size=2K] I/O ports at a800 [size=128] > Capabilities: [50] Power Management version 2 > > 02:04.0 RAID bus controller: Promise Technology, Inc. PDC20376 > (FastTrak 376) (rev 02) Subsystem: ASUSTeK Computer Inc. A7V8X > motherboard Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 11 > I/O ports at a400 [size=64] > I/O ports at a000 [size=16] > I/O ports at 9800 [size=128] > Memory at c5000000 (32-bit, non-prefetchable) [size=4K] > Memory at c4800000 (32-bit, non-prefetchable) [size=128K] > Capabilities: [60] Power Management version 2 > > 02:05.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X > Gigabit Ethernet (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown > device 80a9 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10 > Memory at c4000000 (64-bit, non-prefetchable) [size=64K] > [virtual] Expansion ROM at c7ff0000 [disabled] [size=64K] > Capabilities: [40] PCI-X non-bridge device > Capabilities: [48] Power Management version 2 > Capabilities: [50] Vital Product Data > Capabilities: [58] Message Signalled Interrupts: 64bit+ > Queue=0/3 Enable- > > 02:0a.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] > (rev 86) Subsystem: D-Link System Inc DFE-530TX rev C > Flags: bus master, stepping, medium devsel, latency 32, IRQ 9 > I/O ports at 9400 [size=256] > Memory at c3800000 (32-bit, non-prefetchable) [size=256] > [virtual] Expansion ROM at c7f00000 [disabled] [size=64K] > Capabilities: [40] Power Management version 2 -- Jean Delvare
