* [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708
@ 2006-11-02 17:31 Petar Aleksich
2006-11-04 13:27 ` Jean Delvare
` (5 more replies)
0 siblings, 6 replies; 7+ messages in thread
From: Petar Aleksich @ 2006-11-02 17:31 UTC (permalink / raw)
To: lm-sensors
Hello,
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.
---------------------
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
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%6M]
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\0, secondary\x01,
subordinate\x01, 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 [size2]
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 [size2]
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 [size2]
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\0, secondary\x02, subordinate\x02, sec-latency2
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\x16]
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%6]
I/O ports at 8400 [sized]
Memory at c3000000 (32-bit, non-prefetchable) [sizeQ2]
Memory at c2800000 (32-bit, non-prefetchable) [size%6]
Capabilities: [50] Power Management version 2
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\x128M]
I/O ports at d800 [size%6]
Memory at c7000000 (32-bit, non-prefetchable) [sizedK]
Expansion ROM at d7fe0000 [disabled] [size\x128K]
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\x128M]
Memory at c6800000 (32-bit, non-prefetchable) [sizedK]
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\x128]
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 [sized]
I/O ports at a000 [size\x16]
I/O ports at 9800 [size\x128]
Memory at c5000000 (32-bit, non-prefetchable) [size=4K]
Memory at c4800000 (32-bit, non-prefetchable) [size\x128K]
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) [sizedK]
[virtual] Expansion ROM at c7ff0000 [disabled] [sizedK]
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%6]
Memory at c3800000 (32-bit, non-prefetchable) [size%6]
[virtual] Expansion ROM at c7f00000 [disabled] [sizedK]
Capabilities: [40] Power Management version 2
--
Aleksic Predrag
GPG:41FB 6E3A 418E 8752 520D D0F3 E93C D51E 9972 7570
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708
2006-11-02 17:31 [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708 Petar Aleksich
@ 2006-11-04 13:27 ` Jean Delvare
2006-11-04 16:47 ` Petar Aleksich
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2006-11-04 13:27 UTC (permalink / raw)
To: lm-sensors
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%6M]
> 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\0, secondary\x01,
> subordinate\x01, 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 [size2]
>
> 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 [size2]
>
> 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 [size2]
>
> 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\0, secondary\x02, subordinate\x02, sec-latency2
> 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\x16]
> 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%6]
> I/O ports at 8400 [sized]
> Memory at c3000000 (32-bit, non-prefetchable) [sizeQ2]
> Memory at c2800000 (32-bit, non-prefetchable) [size%6]
> 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Î007ea59729d627f62bb5fa8c1a81e25653a0ad
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\x128M]
> I/O ports at d800 [size%6]
> Memory at c7000000 (32-bit, non-prefetchable) [sizedK]
> Expansion ROM at d7fe0000 [disabled] [size\x128K]
> 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\x128M]
> Memory at c6800000 (32-bit, non-prefetchable) [sizedK]
> 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\x128]
> 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 [sized]
> I/O ports at a000 [size\x16]
> I/O ports at 9800 [size\x128]
> Memory at c5000000 (32-bit, non-prefetchable) [size=4K]
> Memory at c4800000 (32-bit, non-prefetchable) [size\x128K]
> 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) [sizedK]
> [virtual] Expansion ROM at c7ff0000 [disabled] [sizedK]
> 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%6]
> Memory at c3800000 (32-bit, non-prefetchable) [size%6]
> [virtual] Expansion ROM at c7f00000 [disabled] [sizedK]
> Capabilities: [40] Power Management version 2
--
Jean Delvare
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708
2006-11-02 17:31 [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708 Petar Aleksich
2006-11-04 13:27 ` Jean Delvare
@ 2006-11-04 16:47 ` Petar Aleksich
2006-11-19 21:08 ` Jean Delvare
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Petar Aleksich @ 2006-11-04 16:47 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
???? ??????, 04 ??? 2006 ? 14:27:51 +0100, Jean Delvare ??????:
> 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?
ASUS P4PE
http://www.digital-daily.com/motherboard/asus-p4pe/
> > ---------------------
> > 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
Yes it is, to be precise ITE IT8708F-A
> 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").
I can't tell if this chip has any hardware monitoring features or not,
but on kernels prior to 2.6.17 i've used ASB100 successfully.
HTH
> > 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%6M]
> > 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\0,
> > secondary\x01, subordinate\x01, 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
> > [size2]
> >
> > 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
> > [size2]
> >
> > 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
> > [size2]
> >
> > 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\0, secondary\x02, subordinate\x02,
> > sec-latency2 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\x16]
> > 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%6]
> > I/O ports at 8400 [sized]
> > Memory at c3000000 (32-bit, non-prefetchable) [sizeQ2]
> > Memory at c2800000 (32-bit, non-prefetchable) [size%6]
> > 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Î007ea59729d627f62bb5fa8c1a81e25653a0ad
>
>
> 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.
Thank you, removing Sleep States from krenel did the magic thing.
My sensors are back in normal.
$ sensors
asb100-i2c-0-2d
Adapter: SMBus I801 adapter at e800
VCore 1: +1.81 V (min = +1.39 V, max = +2.08 V)
+3.3V: +3.28 V (min = +2.96 V, max = +3.63 V)
+5V: +5.13 V (min = +4.49 V, max = +5.51 V)
+12V: +11.13 V (min = +9.55 V, max = +14.41 V)
-12V (reserved):
-11.62 V (min = -0.00 V, max = -0.00 V)
-5V (reserved):
-4.88 V (min = -0.00 V, max = -0.00 V)
CPU Fan: 3391 RPM (min = -1 RPM, div = 2) ALARM
Chassis Fan:
1997 RPM (min = -1 RPM, div = 4) ALARM
Power Fan: 0 RPM (min = -1 RPM, div = 8) ALARM
M/B Temp: +31?C (high = +80?C, hyst = +75?C)
CPU Temp (Intel):
+42?C (high = +100?C, hyst = +90?C)
Power Temp:
-0?C (high = +60?C, hyst = +50?C)
CPU Temp (AMD):
+25?C (high = +80?C, hyst = +75?C)
vid: +1.750 V (VRM Version 9.0)
alarms:
> > 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\x128M] I/O ports at d800 [size%6]
> > Memory at c7000000 (32-bit, non-prefetchable) [sizedK]
> > Expansion ROM at d7fe0000 [disabled] [size\x128K]
> > 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\x128M]
> > Memory at c6800000 (32-bit, non-prefetchable) [sizedK]
> > 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\x128]
> > 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 [sized]
> > I/O ports at a000 [size\x16]
> > I/O ports at 9800 [size\x128]
> > Memory at c5000000 (32-bit, non-prefetchable) [size=4K]
> > Memory at c4800000 (32-bit, non-prefetchable) [size\x128K]
> > 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) [sizedK]
> > [virtual] Expansion ROM at c7ff0000 [disabled] [sizedK]
> > 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%6]
> > Memory at c3800000 (32-bit, non-prefetchable) [size%6]
> > [virtual] Expansion ROM at c7f00000 [disabled] [sizedK]
> > Capabilities: [40] Power Management version 2
>
--
Aleksic Predrag
GPG:41FB 6E3A 418E 8752 520D D0F3 E93C D51E 9972 7570
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708
2006-11-02 17:31 [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708 Petar Aleksich
2006-11-04 13:27 ` Jean Delvare
2006-11-04 16:47 ` Petar Aleksich
@ 2006-11-19 21:08 ` Jean Delvare
2006-11-20 16:18 ` Jeffrey J. Kosowsky
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2006-11-19 21:08 UTC (permalink / raw)
To: lm-sensors
Hi Jeffrey,
On Sun, 19 Nov 2006 03:35:15 -0500, Jeffrey J. Kosowsky wrote:
> I have been having a similar problem.
> I was able to get lm_sensors to work on 2.4 kernels by using the p4b_smbus.o
> hotplug module.
>
> However, when I upgraded to Fedora 6/Linux 2.6.18, it no longer works.
> My understanding is that in Linux 2.6.x, it is no longer necessary to
> use the p4b_smbus hotplug module since activation of Asus's "hidden"
> SMBus is handled by code in drivers/pci/quirks.c
Correct.
> Now, I learned from the previous post that the SMBus is not enabled if
> suspend is used and that I need to shut off the "Sleep States" in the
> ACPI menu.
>
> Is there any way to do this *without* recompiling the kernel?
> i.e., can I pass parameters to the kernel in grup or even after
> booting to get rid of the sleep states problem and get SMBus enabled?
Unfortunately not. I agree it would be nice to have a kernel boot
parameter for this, but at the moment this is a compilation time
decision. If someone provides a patch to make it a boot time decision,
I'll take that.
--
Jean Delvare
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708
2006-11-02 17:31 [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708 Petar Aleksich
` (2 preceding siblings ...)
2006-11-19 21:08 ` Jean Delvare
@ 2006-11-20 16:18 ` Jeffrey J. Kosowsky
2006-11-21 13:58 ` Jean Delvare
2006-11-21 14:01 ` Jean Delvare
5 siblings, 0 replies; 7+ messages in thread
From: Jeffrey J. Kosowsky @ 2006-11-20 16:18 UTC (permalink / raw)
To: lm-sensors
Jean Delvare wrote at about 22:08:57 +0100 on Sunday, November 19, 2006:
> Hi Jeffrey,
>
> On Sun, 19 Nov 2006 03:35:15 -0500, Jeffrey J. Kosowsky wrote:
> > I have been having a similar problem.
> > I was able to get lm_sensors to work on 2.4 kernels by using the p4b_smbus.o
> > hotplug module.
> >
> > However, when I upgraded to Fedora 6/Linux 2.6.18, it no longer works.
> > My understanding is that in Linux 2.6.x, it is no longer necessary to
> > use the p4b_smbus hotplug module since activation of Asus's "hidden"
> > SMBus is handled by code in drivers/pci/quirks.c
>
> Correct.
>
> > Now, I learned from the previous post that the SMBus is not enabled if
> > suspend is used and that I need to shut off the "Sleep States" in the
> > ACPI menu.
> >
> > Is there any way to do this *without* recompiling the kernel?
> > i.e., can I pass parameters to the kernel in grup or even after
> > booting to get rid of the sleep states problem and get SMBus enabled?
>
> Unfortunately not. I agree it would be nice to have a kernel boot
> parameter for this, but at the moment this is a compilation time
> decision. If someone provides a patch to make it a boot time decision,
> I'll take that.
>
> --
> Jean Delvare
Thanks for the clarification.
Definitely seems like it should be a boot mode decision since it is a
harsh either-or choice (either sleep or sensors) that will change
among different users and even for the same user at different times.
Recompiling the kernel takes forever and is a pita if it means that
you can no longer use stock distro kernels.
Unfortunately, I am not at the level of kernel hacker to supply you
with the patch...
Thanks
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708
2006-11-02 17:31 [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708 Petar Aleksich
` (3 preceding siblings ...)
2006-11-20 16:18 ` Jeffrey J. Kosowsky
@ 2006-11-21 13:58 ` Jean Delvare
2006-11-21 14:01 ` Jean Delvare
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2006-11-21 13:58 UTC (permalink / raw)
To: lm-sensors
Hi Jeffrey,
On Mon, 20 Nov 2006 11:18:25 -0500, Jeffrey J. Kosowsky wrote:
> Jean Delvare wrote at about 22:08:57 +0100 on Sunday, November 19, 2006:
> > On Sun, 19 Nov 2006 03:35:15 -0500, Jeffrey J. Kosowsky wrote:
> > > Now, I learned from the previous post that the SMBus is not enabled if
> > > suspend is used and that I need to shut off the "Sleep States" in the
> > > ACPI menu.
> > >
> > > Is there any way to do this *without* recompiling the kernel?
> > > i.e., can I pass parameters to the kernel in grup or even after
> > > booting to get rid of the sleep states problem and get SMBus enabled?
> >
> > Unfortunately not. I agree it would be nice to have a kernel boot
> > parameter for this, but at the moment this is a compilation time
> > decision. If someone provides a patch to make it a boot time decision,
> > I'll take that.
>
> Thanks for the clarification.
> Definitely seems like it should be a boot mode decision since it is a
> harsh either-or choice (either sleep or sensors) that will change
> among different users and even for the same user at different times.
>
> Recompiling the kernel takes forever and is a pita if it means that
> you can no longer use stock distro kernels.
Agreed, many users complained about this problem already.
> Unfortunately, I am not at the level of kernel hacker to supply you
> with the patch...
You're in luck, Alan Cox just posted a patch on LKML which should fix
the issue.
http://lkml.org/lkml/2006/11/14/161
Users who need the SMBus unhiding quirk, use suspend-to-RAM, and know
how to patch and recompile their kernel, are invited to give it a try
and report.
Thanks,
--
Jean Delvare
^ permalink raw reply [flat|nested] 7+ messages in thread
* [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708
2006-11-02 17:31 [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708 Petar Aleksich
` (4 preceding siblings ...)
2006-11-21 13:58 ` Jean Delvare
@ 2006-11-21 14:01 ` Jean Delvare
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2006-11-21 14:01 UTC (permalink / raw)
To: lm-sensors
Hi Petar,
On Sat, 4 Nov 2006 17:47:44 +0100, Petar Aleksich wrote:
> Thank you, removing Sleep States from krenel did the magic thing.
> My sensors are back in normal.
You might want to give a try to this patch by Alan Cox which should
make it possible to safely use the sleep states and unhide the SMBus:
http://lkml.org/lkml/2006/11/14/161
--
Jean Delvare
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-11-21 14:01 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-02 17:31 [lm-sensors] sensors-detect: Found unknown chip with ID 0x8708 Petar Aleksich
2006-11-04 13:27 ` Jean Delvare
2006-11-04 16:47 ` Petar Aleksich
2006-11-19 21:08 ` Jean Delvare
2006-11-20 16:18 ` Jeffrey J. Kosowsky
2006-11-21 13:58 ` Jean Delvare
2006-11-21 14:01 ` Jean Delvare
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.