Thanks,
root@lnx-a001:~#
sensors-detect
-bash: sensors-detect: command not found
root@lnx-a001:~#
apt-get install lm-sensors
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libsensors4
Suggested packages:
fancontrol sensord read-edid i2c-tools
The following NEW packages will be installed:
libsensors4 lm-sensors
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 182 kB of archives.
After this operation, 444 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1
http://ftp.tr.debian.org/debian/ wheezy/main libsensors4 amd64 1:3.3.2-2+d eb7u1 [55.0 kB]
Get:2
http://ftp.tr.debian.org/debian/ wheezy/main lm-sensors amd64 1:3.3.2-2+de b7u1 [127 kB]
Fetched 182 kB in 0s (533 kB/s)
Selecting previously unselected package libsensors4:amd64.
(Reading database ... 107719 files and directories currently installed.)
Unpacking libsensors4:amd64 (from .../libsensors4_1%3a3.3.2-2+deb7u1_amd64.deb) ...
Selecting previously unselected package lm-sensors.
Unpacking lm-sensors (from .../lm-sensors_1%3a3.3.2-2+deb7u1_amd64.deb) ...
Processing triggers for systemd ...
systemctl: enabling lm-sensors.service
Processing triggers for man-db ...
Setting up libsensors4:amd64 (1:3.3.2-2+deb7u1) ...
Setting up lm-sensors (1:3.3.2-2+deb7u1) ...
insserv: warning: script 'K01ctmilter_initd' missing LSB tags and overrides
insserv: warning: script 'ctmilter_initd' missing LSB tags and overrides
root@lnx-a001:~#
sensors-detect
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# System: VMware, Inc. VMware Virtual Platform [None]
# Board: Intel Corporation 440BX Desktop Reference Platform
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): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... Yes
Found unknown chip with ID 0x0700
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-piix4' for device 0000:00:07.3: Intel 82371AB PIIX4 ACPI
Module i2c-dev loaded successfully.
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
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
#----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/kmod start'
to load them.
Unloading i2c-dev... OK
Unloading cpuid... OK
root@lnx-a001:~# /etc/init.d/kmod start
[ ok ] Starting kmod (via systemctl): kmod.service.
Facebook
Twitter
