CPU Temperatur

  • Thread starter Thread starter freakshow10000
  • Start date Start date
F

freakshow10000

Guest
Hi,

Ich versuche mit Sensors die CPU Temperatur auszulesen, jedoch findet er mit sensors-detect keinen CPU Temperaturfühler.

Als Kernel ist 3.1.1 eingesetzt.

Sensors-detect:
Code: 
sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: To Be Filled By O.E.M. To Be Filled By O.E.M.
# Board: ASRock 970 Extreme3

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
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):
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):
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):
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: ATI Technologies Inc SB600/SB700/SB800 SMBus

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively):
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
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
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
http://www.lm-sensors.org/wiki/Devices for driver status.
Code: 
 sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +26.9°C  (high = +70.0°C, crit = +70.0°C)

Jetzt steht da ja "Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes", meine Frage also. Was ist das? Die CPU eher nicht oder?
Achja es ist ein FX-8120.

MfG
 
freakshow10000 said:
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found unknown chip with ID 0xc333
(logical device B has address 0x290, could be sensors)
Click to expand...

http://www.google.de/search?q=Found...s=org.mozilla:en-US:official&client=firefox-a

-> http://forums.overclockers.com.au/showthread.php?t=934277

-> http://cateee.net/lkddb/web-lkddb/SENSORS_W83627EHF.html

-> CONFIG_SENSORS_W83627EHF=Y

probiers aus.

edit2: Du hast wirklich in einem Server eine übertaktete CPU (bisher) ohne Sensors laufen? Nun denn, erlaubt ist was gefällt.
 
Last edited by a moderator:
mojodoll said:
edit2: Du hast wirklich in einem Server eine übertaktete CPU (bisher) ohne Sensors laufen? Nun denn, erlaubt ist was gefällt.
Click to expand...

Übertaktet habe ich per KVM ...

Erstmal danke für die Hilfe aber aus den Links werde ich nicht ganz schlau.

CONFIG_SENSORS_W83627EHF=Y Wo muss das jetzt hin? oO In die Makefile?
 
Last edited by a moderator:
Na, lm_sensors will das Kernelmodul für die Sensoren laden, also brauchst du das.
Weil ich Modulsupport gerne vermeide wenn ichs nicht unbedingt brauche, compile ich halt die Treiber in den Kernel.
Ergo: die relevante Zeile in der .config deines Kernels editieren und recompilen.

Wenn man denn unbedingt ein Modul haben möchte kann man statt "=Y" auch "=M" setzen.
 
Gehört halt dazu.
Du verwendest doch ohnehin einen sehr aktuellen Kernel, daher der Vorschlag: kündige deinen Gamerfreunden Downtime an (angenommen du kannst dir das wirtschaftlich erlauben), setz dich einen Mittag dran und beschäftige dich mit make menuconfig und dem lspci Output, befreie deinen Kernel von unnötiger Last und bedenke dabei vielleicht auch meine oben genannten Ansätze eben keinen Module Support mit in den Kernel zu compilen, sondern wie gesagt ausschliesslich das was du brauchst in den Kernel direkt packen.

Wieso eigtl. keine Modules? Weil sich rootkits gerne als Kernelmodul tarnen und sobald sie da drin sind relativ schwer zu entfernen sind. Es ist einfach unnötig auf einem Server, hier auf den Workstations zuhause brauch ichs auch für die nvidia-Treiber.
 
Hi,

Der Server wurde so von GPortal installiert.
Ich habe lediglich 3.1.1 runtergeladen und die gleiche config von 2.6 übernommen.
Tja dann werde ich mich wohl heute noch ans Komplieren machen :)

MfG
 
*Thread wieder ausgrab*

Kernel neu gemacht, jedoch kein Erfolg:

Code: 
sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: To Be Filled By O.E.M. To Be Filled By O.E.M.
# Board: ASRock 970 Extreme3

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):
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...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             Success!
    (driver `fam15h_power')
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 NCT6776F Super IO Sensors'                   Success!
    (address 0x290, driver `w83627ehf')
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):

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: ATI Technologies Inc SB600/SB700/SB800 SMBus
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively):

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `w83627ehf':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)

Driver `fam15h_power':
  * Chip `AMD Family 15h power sensors' (confidence: 9)

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

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

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

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK
Unloading cpuid... OK
Code: 
sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +18.2°C  (high = +70.0°C)
                       (crit = +70.0°C, hyst = +67.0°C)

MfG
 
Der sensors-detect Output ist ja mittlerweile wesentlich vielversprechender.
Ich hab grad festgestellt ich nutze auf dem Rechner hier auch den w83627ehf Treiber, hab aber wohl einen anderen Sensorchip:

Code: 
<snip>
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Winbond W83627EHF/EF/EHG/EG Super IO Sensors'        Success!
    (address 0x290, driver `w83627ehf')
<snip>
Driver `w83627ehf':
  * ISA bus, address 0x290
    Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9)

Driver `coretemp':
  * Chip `Intel Core family thermal sensor' (confidence: 9)
<snip>

Hier geht aber alles (bis auf die Fans, das ist aber schon ok so):

Code: 
$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +39.0 C  (high = +82.0 C, crit = +100.0 C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +39.0 C  (high = +82.0 C, crit = +100.0 C)  

coretemp-isa-0002
Adapter: ISA adapter
Core 2:      +34.0 C  (high = +82.0 C, crit = +100.0 C)  

coretemp-isa-0003
Adapter: ISA adapter
Core 3:      +37.0 C  (high = +82.0 C, crit = +100.0 C)  

w83627ehf-isa-0290
Adapter: ISA adapter
Vcore:       +1.29 V  (min =  +0.00 V, max =  +1.74 V)   
in1:         +1.30 V  (min =  +0.94 V, max =  +2.04 V)   
AVCC:        +3.34 V  (min =  +1.73 V, max =  +2.14 V)   ALARM
+3.3V:       +3.34 V  (min =  +4.08 V, max =  +4.00 V)   ALARM
in4:         +1.70 V  (min =  +1.90 V, max =  +0.34 V)   ALARM
in5:         +1.68 V  (min =  +1.82 V, max =  +1.02 V)   ALARM
in6:         +1.85 V  (min =  +0.99 V, max =  +0.18 V)   ALARM
3VSB:        +3.30 V  (min =  +3.71 V, max =  +3.89 V)   ALARM
Vbat:        +3.14 V  (min =  +2.96 V, max =  +1.52 V)   ALARM
in9:         +1.59 V  (min =  +0.76 V, max =  +1.50 V)   ALARM
fan1:          0 RPM  (min =  781 RPM, div = 32)  ALARM
fan2:          0 RPM  (min =    0 RPM, div = 32)
fan3:          0 RPM  (min =    0 RPM, div = 32)
fan5:          0 RPM  (min = 1622 RPM, div = 32)  ALARM
temp1:       +40.0 C  (high = +251.0 C, hyst = +242.0 C)  ALARM  sensor = thermistor
temp2:       +36.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
temp3:       +44.5 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
cpu0_vid:   +1.219 V

Wieso das trotz dem erfolgreichen sensors-detect Output bei dir nicht geht? Ich habe keine Ahnung.
Das einzige was mir einfällt ist die sensors.conf, ich hab mal die Originale die ich hier auf dem System hab attached, das kannst du ja mal vergleichen und generell anschauen, vielleicht ergeben sich daraus ja neue clues.
Ich weiss allerdings quasi garnichts über die Konfiguration von lm_sensors unter Debian (ich bin so frei davon auszugehen dass du Debian nutzt), die .conf ist halt von Gentoo - ich musste da nichts dran ändern, ging einfach so out of the box :o
 

Attachments

Cool danke,
Ich paste die mal 1 zu 1 rein (natürlich mit Backup.. aber viel schlimmer kann es nicht kommen :D)

MfG

*edit*
Reinkopiert und bringt immernoch nichts. Genau der gleiche Output.
Oder muss ich evtl. neustarten?

MfG
 
Last edited by a moderator:
Ne, neustarten musste an und für sich nicht.
Dann weiss ich jetz nichts mehr dazu, musst du mal schauen ob Freund Google iwas tolles über "Nuvoton NCT6776F" bescheid weiss, Mailing-Listen oder sowas.

Oder jmd. anderes ist bewanderter als wir!
 
You must log in or register to reply here.
Back
Top