| View previous topic :: View next topic |
| Author |
Message |
oxEz
Tux's lil' helper
Joined: 18 May 2004
Posts: 115
|
 Posted: Mon Aug 10, 2009 3:00 am Post subject: Sensors not detecting anything besides CPU |
 |
|
Hello.
I'm trying to setup lm_sensors on my gentoo system, and so far all I've got are the CPU temperatures (for the 2 cores).
I have Sager NP9261 laptop, which is based on Clevo D900C.
I've emerged the latest version of lm_sensors (3.1.1, copied the 3.0.3 ebuild and changed version numbers as well as patch, as described here: https://bugs.gentoo.org/show_bug.cgi?id=244598
After emerging, I ran sensors-detect, which gave the following output (It detects my laptop as a Cleve D900C, which was a good sign..)
| Code: | entropy devices # sensors-detect
# sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
# System: CLEVO D900C
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal and voltage sensors... No
Some Super I/O chips contain embedded 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): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' 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
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801H ICH8
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 18c0 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: NVIDIA i2c adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: NVIDIA i2c adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: NVIDIA i2c adapter (i2c-3)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel Core family thermal sensor' (confidence: 9)
Do you want to generate /etc/conf.d/lm_sensors? Enter s to specify other file name?
(YES/no/s): yes
Done.
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
|
So it only loads the "coretemp" module, which (once /etc/init.d/lm_sensors) is started, gives me the following output when I run "sensors":
| Code: |
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +38.0 C (high = +78.0 C, crit = +100.0 C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +40.0 C (high = +78.0 C, crit = +100.0 C)
|
So the temps look fine, but I don't have any other info... such as fan control and voltage. I've seen a lot of people whose sensors-detect gave them a module named "w83781d" (or something close to it there are multiple versions).
Here is what I'm expecting to get when I run "sensors" (example):
| Code: | $ sensors
w83627dhg-isa-0290
Adapter: ISA adapter
VCore: +1.19 V (min = +0.00 V, max = +1.74 V)
in1: +12.14 V (min = +0.00 V, max = +1.11 V) ALARM
AVCC: +3.28 V (min = +0.51 V, max = +0.10 V) ALARM
3VCC: +3.28 V (min = +0.00 V, max = +1.18 V) ALARM
in4: +1.34 V (min = +0.00 V, max = +0.27 V) ALARM
in5: +1.59 V (min = +1.02 V, max = +0.16 V) ALARM
in6: +4.28 V (min = +3.69 V, max = +5.53 V)
VSB: +3.28 V (min = +0.02 V, max = +0.19 V) ALARM
VBAT: +3.22 V (min = +0.05 V, max = +0.70 V) ALARM
Case Fan: 0 RPM (min = 337500 RPM, div = 4) ALARM
CPU Fan: 1350 RPM (min = 5273 RPM, div = 8) ALARM
Aux Fan: 3770 RPM (min = 5075 RPM, div = 2) ALARM
fan4: 0 RPM (min = 21093 RPM, div = 4) ALARM
fan5: 0 RPM (min = 0 RPM, div = 4) ALARM
Sys Temp: +31.0°C (high = +34.0°C, hyst = -30.0°C) sensor = thermistor
CPU Temp: +32.5°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
AUX Temp: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = thermistor
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +51.0°C (high = +84.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +55.0°C (high = +84.0°C, crit = +100.0°C)
|
I've pretty much enabled every driver as modules, so I could test rapidly, but I couldn't figure it out. |
|
| Back to top |
|
 |
oxEz
Tux's lil' helper
Joined: 18 May 2004
Posts: 115
|
| Posted: Mon Aug 10, 2009 3:06 am Post subject: |
|
|
For some reason I cannot paste my whole kernel config in here... so I pastebin'd it: http://pastebin.com/m617a39be
lspci output:
| Code: | 00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801H (ICH8 Family) 2 port SATA IDE Controller (rev 02)
01:00.0 PCI bridge: nVidia Corporation Device 01b3 (rev a3)
02:00.0 PCI bridge: nVidia Corporation Device 01b3 (rev a3)
02:01.0 PCI bridge: nVidia Corporation Device 01b3 (rev a3)
04:00.0 VGA compatible controller: nVidia Corporation GeForce 8700M GT (rev a1)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
09:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
0b:00.0 IDE interface: JMicron Technologies, Inc. JMB368 IDE controller
0d:07.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
0d:07.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller
0d:07.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)
0d:07.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller
|
|
|
| Back to top |
|
|
oxEz
Tux's lil' helper
Joined: 18 May 2004
Posts: 115
|
| Posted: Mon Aug 10, 2009 3:46 am Post subject: |
|
|
Well, after some investigation it appears that my board is not yet supported by lm_sensors.
http://www.lm-sensors.org/wiki/Devices, look up for "ICH8".
I will keep this thread in a bookmark and update it as soon as Intel releases their opensource SDK so lm_sensors dev have a shot at it. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
