(centos) temperaturen auslesen

Seite 1 von 1 - Forum: Linux and other OS auf overclockers.at

URL: https://www.overclockers.at/linux/centos-temperaturen-auslesen_235508/page_1 - zur Vollversion wechseln!

ich würde gerne die temperaturen von meinem server auslesen, der auf centos läuft. ich habe es mit dem lm_sensors package probiert, aber das erkennt keine sensoren (bzw. liest nix sinnvolles aus).

Code:

[root@homeserver prime95]# sensors-detect
# sensors-detect revision 1.1
# System: System manufacturer System Product Name
# Board: ASUSTeK COMPUTER INC. F1A75-I DELUXE

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 11h thermal sensors...                           No
Intel digital thermal sensor...                             No
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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xc333
    (logical device B has address 0x290, could be sensors)
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
Using driver `i2c-piix4' for device 0000:00:14.0: AMD Hudson-2 SMBus
Module i2c-dev loaded successfully.

Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
Do you want to scan it? (YES/no/selectively): y

Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
Do you want to scan it? (YES/no/selectively): y
y
Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
Do you want to scan it? (YES/no/selectively): y

Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
Do you want to scan it? (YES/no/selectively): y

Next adapter: Radeon i2c bit bus 0x94 (i2c-4)
Do you want to scan it? (YES/no/selectively): y

Next adapter: Radeon i2c bit bus 0x95 (i2c-5)
Do you want to scan it? (YES/no/selectively): y

Next adapter: Radeon i2c bit bus 0x96 (i2c-6)
Do you want to scan it? (YES/no/selectively): y

Next adapter: Radeon i2c bit bus 0x97 (i2c-7)
Do you want to scan it? (YES/no/selectively): y

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-8)
Do you want to scan it? (YES/no/selectively): y
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'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
[url]http://www.lm-sensors.org/wiki/Devices[/url] for driver status.
[root@homeserver prime95]# sensors
radeon-pci-0008
Adapter: PCI adapter
temp1:       +11.0°C

k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +11.0°C  (high = +70.0°C, crit = +70.0°C) 

Code:

[root@homeserver /]# acpi -t
-bash: acpi: command not found 

Code:

[root@homeserver thermal_zone]# hddtemp /dev/sda
/dev/sda: WDC WD10EAVS-00D7B1: 39°C 

Zitat von wergor

ich würde gerne die temperaturen von meinem server auslesen, der auf centos läuft. ich habe es mit dem lm_sensors package probiert, aber das erkennt keine sensoren (bzw. liest nix sinnvolles aus).

Zitat

yum install ipmitool
ipmitool sensor

Zitat von Hansmaulwurf

sensors-detect hast du vorher laufen lassen ?

edit:
Zuerst mal lesen

edit2: Doch noch was sinnvolles :

Zitat

yum install ipmitool
ipmitool sensor

Code:

[root@homeserver ~]# service ipmi start
Starting ipmi drivers:                                     [  OK  ]
[root@homeserver ~]# ipmitool sensor
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Get Device ID command failed
Unable to open SDR for reading

Ist deine Sensors-detect aktuell? http://www.lm-sensors.org/wiki/iwiz...SensorsDetected

ich hab von hand auf die aktuelle version updated, geholfen hats aber nix

Code:

[root@homeserver lm_sensors-3.3.4]# sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# Board: ASUSTeK COMPUTER INC. F1A75-I DELUXE

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):
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...                   Success!
    (driver `k10temp')
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital 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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT5577D/NCT6776F Super IO Sensors'          Success!
    (address 0x290, driver `nct6775')
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):
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):
Using driver `i2c-piix4' for device 0000:00:14.0: AMD Hudson-2 SMBus
Module i2c-dev loaded successfully.

Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x94 (i2c-4)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x95 (i2c-5)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x96 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x97 (i2c-7)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-8)
Do you want to scan it? (YES/no/selectively): y
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 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD 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 `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT5577D/NCT6776F Super IO Sensors' (confidence: 9)

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 12h and 14h thermal sensors' (confidence: 9)

Warning: the required module nct6775 is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check [url]http://www.lm-sensors.org/wiki/Devices[/url] for
driver availability.

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

[root@homeserver lm_sensors-3.3.4]# sensors
radeon-pci-0008
Adapter: PCI adapter
temp1:        +8.0°C

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +8.1°C  (high = +70.0°C, crit = +70.0°C)

Code:

Warning: the required module nct6775 is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check [url]http://www.lm-sensors.org/wiki/Devices[/url] for
driver availability.

Code:

[root@homeserver nct6775-nct6775-v1.1]# make
make: *** /usr/src/linux-headers-2.6.32-358.14.1.el6.x86_64: No such file or directory.  Stop.
make: *** [modules] Error 2
[root@homeserver nct6775-nct6775-v1.1]# yum install kernel-headers
Loaded plugins: fastestmirror, refresh-packagekit, security
Repository zeroc-ice is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: ftp.hosteurope.de
 * epel: ftp.astral.ro
 * extras: ftp-stud.fht-esslingen.de
 * rpmforge: mirrors.ircam.fr
 * updates: ftp.hosteurope.de
Setting up Install Process
Package kernel-headers-2.6.32-358.14.1.el6.x86_64 already installed and latest version
Nothing to do
[root@homeserver nct6775-nct6775-v1.1]# make
make: *** /usr/src/linux-headers-2.6.32-358.14.1.el6.x86_64: No such file or directory.  Stop.
make: *** [modules] Error 2

Den Treiber dürfte es erst seit kurzem im Kernel geben, erst bei meinen 3.10er Kernel Sources konnte ich folgendes ergrepen:

Code:

# CONFIG_SENSORS_NCT6775 is not set

Code:

repoquery --list kernel-devel

hab das problem mit den headern gefixed, und den treiber kompiliert. jetzt muss ich ihn noch in den richtigen ordner kopieren- wohin genau? muss ich danach noch was machen, ausser den server neustarten?

Code:

[root@localhost nct6775-nct6775-v1.1]# ls
compat.h  LICENSE  lm75.h  Makefile  modules.order  Module.symvers  nct6775.c  nct6775.ko  nct6775.ko.unsigned  nct6775.mod.c  nct6775.mod.o  nct6775.o  README  README.ASRock
[root@localhost nct6775-nct6775-v1.1]# ls /lib/modules/2.6.32-358.14.1.el6.x86_64/kernel/
arch  crypto  drivers  fs  kernel  lib  mm  net  sound

Code:

[root@localhost nct6775-nct6775-v1.1]# cp nct6775.ko /lib/modules/2.6.32-358.14.1.el6.x86_64/extra/
[root@localhost nct6775-nct6775-v1.1]# ls /lib/modules/2.6.32-358.14.1.el6.x86_64/extra/
nct6775.ko
[root@localhost nct6775-nct6775-v1.1]# depmod -a
[root@localhost nct6775-nct6775-v1.1]# modprobe nct6775

Code:

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
[url]http://www.lm-sensors.org/wiki/Devices[/url] for driver status.

Code:

[root@localhost tmp]# perl sensors-detect
# sensors-detect revision $Revision$
# Board: ASUSTeK COMPUTER INC. F1A75-I DELUXE

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
AMD Family 12h and 14h thermal sensors...                   Success!
    (driver `k10temp')
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital 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/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT5577D/NCT6776F Super IO Sensors'          Success!
    (address 0x290, driver `nct6775')
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): 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
Using driver `i2c-piix4' for device 0000:00:14.0: AMD Hudson-2 SMBus

Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
y
Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x94 (i2c-4)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x95 (i2c-5)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x96 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: Radeon i2c bit bus 0x97 (i2c-7)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-8)
Do you want to scan it? (YES/no/selectively): y
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 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD 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 `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT5577D/NCT6776F Super IO Sensors' (confidence: 9)

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 12h and 14h thermal sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): lm_sensors
Starting lm_sensors: loading module nct6775  
[root@localhost tmp]# sensors
radeon-pci-0008
Adapter: PCI adapter
temp1:        +6.0°C

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +6.6°C  (high = +70.0°C, crit = +70.0°C)

nct6776-isa-0290
Adapter: ISA adapter
in0:           +0.71 V  (min =  +0.00 V, max =  +1.74 V)
in1:           +1.02 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in2:           +3.31 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in3:           +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:           +1.00 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in5:           +0.00 V  (min =  +0.00 V, max =  +0.00 V)
in6:           +0.79 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in7:           +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in8:           +3.30 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:          752 RPM  (min =    0 RPM)
fan2:          507 RPM  (min =    0 RPM)
fan3:            0 RPM  (min =    0 RPM)
fan4:            0 RPM  (min =    0 RPM)
fan5:            0 RPM  (min =    0 RPM)
SYSTIN:        +67.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:        +36.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:        +37.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
PCH_CHIP_TEMP:  +0.0°C
PCH_CPU_TEMP:   +0.0°C
PCH_MCH_TEMP:   +0.0°C
beep_enable:  disabled

overclockers.at v4.thecommunity
© all rights reserved by overclockers.at 2000-2025