From: Mahmood Naderan <nt_mahmood@yahoo.com>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lmsensors doesn't detect core-i7 sensors
Date: Wed, 01 Sep 2010 06:38:46 +0000 [thread overview]
Message-ID: <929339.59525.qm@web50002.mail.re2.yahoo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 5491 bytes --]
Dear all,
I ran sensors-detect to detect Core-i7 temperatures but it doesn't show them.
Here is the output of sensors-detect:
mahmood@localhost:~$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Gigabyte Technology Co., Ltd. P55-USB3
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): y
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel Core family thermal sensor... No
Intel Atom thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... 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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8720F Super IO Sensors' Success!
(address 0x290, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/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): y
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): y
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): y
Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
* ISA bus, address 0x290
Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
it87
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!
Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.
Unloading i2c-dev... OK
Then I ran sensors:
mahmood@localhost:~$sudo sensors
it8720-isa-0290
Adapter: ISA adapter
in0: +0.86 V (min = +0.00 V, max = +4.08 V)
in1: +1.58 V (min = +0.00 V, max = +4.08 V)
in2: +3.39 V (min = +0.00 V, max = +4.08 V)
in3: +3.02 V (min = +0.00 V, max = +4.08 V)
in4: +0.05 V (min = +0.00 V, max = +4.08 V) ALARM
in5: +3.12 V (min = +0.00 V, max = +4.08 V)
in6: +0.02 V (min = +0.00 V, max = +4.08 V) ALARM
in7: +2.16 V (min = +0.00 V, max = +4.08 V)
Vbat: +3.10 V
fan1: 1679 RPM (min = 10 RPM)
fan2: 644 RPM (min = 0 RPM)
fan3: 1278 RPM (min = 10 RPM)
fan4: 1205 RPM (min = 0 RPM)
temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp2: +25.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp3: +33.0°C (low = +127.0°C, high = +90.0°C) sensor = thermistor
cpu0_vid: +0.313 V
What can I do then? currently I have kubuntu 10.04
// Naderan *Mahmood;
[-- Attachment #1.2: Type: text/html, Size: 11440 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2010-09-01 6:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 6:38 Mahmood Naderan [this message]
2010-09-01 7:19 ` [lm-sensors] lmsensors doesn't detect core-i7 sensors Nikola Pajkovsky
2010-09-01 7:30 ` Mahmood Naderan
2010-09-01 7:38 ` Nikola Pajkovsky
2010-09-01 7:46 ` Mahmood Naderan
2010-09-01 7:53 ` Nikola Pajkovsky
2010-09-01 8:03 ` Mahmood Naderan
2010-09-01 8:11 ` Nikola Pajkovsky
2010-09-01 8:16 ` Mahmood Naderan
2010-09-01 13:26 ` Guenter Roeck
2010-09-01 13:56 ` Jean Delvare
2010-09-01 14:32 ` Guenter Roeck
2010-09-01 14:58 ` Mahmood Naderan
2010-09-01 15:52 ` Guenter Roeck
2010-09-01 16:57 ` Mahmood Naderan
2010-09-03 14:31 ` Guenter Roeck
2010-09-04 13:49 ` Jean Delvare
2010-09-04 14:25 ` Guenter Roeck
2010-09-04 14:31 ` Mahmood Naderan
2010-09-04 15:55 ` Jean Delvare
2010-09-04 17:28 ` Guenter Roeck
2010-09-06 16:18 ` Jean Delvare
2010-09-07 1:32 ` Guenter Roeck
2010-09-07 8:00 ` Jean Delvare
2010-09-13 8:04 ` Mahmood Naderan
2010-09-14 16:20 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=929339.59525.qm@web50002.mail.re2.yahoo.com \
--to=nt_mahmood@yahoo.com \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.