Package: lm-sensors
Version: 1:3.3.2-1
Severity: normal
Dear Maintainer,
I was running sensors-detect when I got the following :-
$ sudo sensors-detect
[sudo] password for shirish:
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# Board: ASUSTeK Computer INC. P5KPL-AM IN
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
Module cpuid loaded successfully.
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
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
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/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8720F Super IO Sensors' Success!
(address xxxx, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... 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): 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 xxxx:xx:xx.x: Intel 82801G ICH7
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 0400 (i2c-0)
Do you want to scan it? (YES/no/selectively): Yes
Client found at address xxxx
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
Next adapter: i915 gmbus disabled (i2c-1)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 gmbus ssc (i2c-2)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 GPIOB (i2c-3)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 gmbus vga (i2c-4)
Do you want to scan it? (YES/no/selectively): Yes
Client found at address xxxx
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)
Client found at address xxxx
Probing for `Analog Devices ADT7462'... No
Probing for `Andigilog aSC7512'... No
Next adapter: i915 GPIOA (i2c-5)
Do you want to scan it? (YES/no/selectively): Yes
Client found at address xxxx
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)
Client found at address 0x58
Probing for `Analog Devices ADT7462'... No
Probing for `Andigilog aSC7512'... No
Next adapter: i915 gmbus panel (i2c-6)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 GPIOC (i2c-7)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 gmbus dpc (i2c-8)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 GPIOD (i2c-9)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 gmbus dpb (i2c-10)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 GPIOE (i2c-11)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 gmbus reserved (i2c-12)
Do you want to scan it? (YES/no/selectively): Yes
Next adapter: i915 gmbus dpd (i2c-13)
Do you want to scan it? (YES/no/selectively): YES
Next adapter: i915 GPIOF (i2c-14)
Do you want to scan it? (YES/no/selectively): YES
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
* ISA bus, address xxxx
Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
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
Unloading cpuid... OK
Now couple of things to note here. I have changed the addresses from
wherever they are to using 'xx' just for privacy reasons.
Now the actual issue is at the very bottom where it says
"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."
It should be talking about kmod for IIRC kmod has replaced
module-init-tools few months back as module-init-tools is dead
upstream.
$ aptitude show kmod
Package: kmod
State: installed
Automatically installed: yes
Multi-Arch: foreign
Version: 6-2
Priority: important
Section: admin
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Uncompressed Size: 185 k
Depends: libc6 (>= 2.8), libkmod2 (>= 5~), lsb-base (>= 3.0-6)
Breaks: module-init-tools (< 4)
Replaces: module-init-tools (< 4)
Description: tools for managing Linux kernel modules
This package contains a set of programs for loading, inserting, and
removing kernel modules for Linux. It replaces module-init-tools.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lm-sensors depends on:
ii libc6 2.13-30
ii libsensors4 1:3.3.2-1
ii lsb-base 4.1+Debian1
ii perl 5.14.2-9
ii sed 4.2.1-9
lm-sensors recommends no packages.
Versions of packages lm-sensors suggests:
ii fancontrol 1:3.3.2-1
ii i2c-tools 3.0.3-5
ii read-edid 2.0.0-3.1
ii sensord 1:3.3.2-1
-- no debconf information
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
