CPU temperature for AMD A10 7700K APU

English Hardware
1

Hi,
Just upgraded to this new A10 APU 7700K and noticed I can’t read the temperatures correctly either with “sensors” or “inxi”. Is there a package that can do that correctly? Do I need some additional modules?

Here is what inxi reports

**Sensors:  ** **System Temperatures: cpu:** 18.9C **mobo:** N/A **gpu:** 17.00C                                                                                                  
**          ** **Fan Speeds (in rpm): cpu:** N/A

sensors

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

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:           N/A  (crit =  95.07 W)

Yes I did ran “sensors-detect”.

2

Hi
And did it discover any new chip, as in ‘Found unknown chip with ID…’? If so need to see the output, but more likely a new chip not in the Leap kernel, try a live CD of tumbleweed and see if it shows up.

What manufacturer/model hardware etc?

3

Hi,
Hardware

**Machine:  ** **Mobo:** ASRock **model:** FM2A68M-HD+ **serial:** M80-62007600838 **Bios:** American Megatrends **version:** P1.90 **date:** 12/04/2015
**CPU:      ** **Quad core** AMD A10-7700K Radeon R7 10 Compute Cores 4C+6G (-MCP-) **cache:** 8192 KB **flags:** (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm)  
**          ** **Clock Speeds:** **1:** 1900.00 MHz **2:** 1900.00 MHz **3:** 1900.00 MHz **4:** 1900.00 MHz
**Graphics: ** **Card:** Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]  
**          ** **X.org:** 1.17.2 **driver:** fglrx **tty size:** 161x36 **Advanced Data:** N/A for root  
**Audio:    ** **Card-1:** Advanced Micro Devices [AMD] FCH Azalia Controller **driver:** snd_hda_intel
**          ** **Card-2:** Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio Controller **driver:** snd_hda_intel
**          ** **Sound:** Advanced Linux Sound Architecture **ver:** k4.1.27-27-default
**Network:  ** **Card:** Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller **driver:** r8169  
**          ** **IF:** eth1 **state:** up **speed:** 100 Mbps **duplex:** full **mac:** d0:50:99:a8:9b:8c
**Drives:   ** **HDD Total Size:** 280.1GB (74.7% used) **1:** /dev/sda INTEL_SSDSC2CW12 120.0GB  
**          ** **2:** /dev/sdb WDC_WD1600AAJS 160.0GB  
**Partition:** **ID:** / **size:** 20G **used:** 18G (94%) **fs:** ext4 **ID:** /home **size:** 77G **used:** 75G (98%) **fs:** ext4  
**          ** **ID:** swap-1 **size:** 2.15GB **used:** 0.04GB (2%) **fs:** swap  
**Sensors:  ** **System Temperatures: cpu:** 16.0C **mobo:** N/A **gpu:** 11.00C  
**          ** **Fan Speeds (in rpm): cpu:** N/A  
**Info:     ** **Processes:** 229 **Uptime:** 1 day 22:44 **Memory:** 2884.1/4850.8MB **Client:** Shell **inxi:** 1.7.24

Running sensors-detect again gives

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...                           Success!
    (driver `k10temp')
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): YES
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): 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:14.0: AMD Hudson-2 SMBus
Module i2c-dev loaded successfully.



Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
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 `k10temp' (autoloaded):
  * Chip `AMD Family 15h thermal sensors' (confidence: 9)

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

Will download the new version live and see if something changes.

4

Hi
Sounds very much like the issues here: http://forums.opensuse.org/showthread.php?t=519270

As root user run;


modprobe nct6775
sensors

If that kicks things into life… then might just have to add a /etc/modules-load.d/nct6775.conf with nct6775 in it.

5

Loaded that module and now I indeed have much more info

**linux-jspa:/home/roberto #** sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:         +6.6°C  (high = +70.0°C)

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:           N/A  (crit =  95.07 W)

nct6776-isa-0290
Adapter: ISA adapter
Vcore:          +0.93 V  (min =  +0.00 V, max =  +1.74 V)
in1:            +1.83 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:           +3.36 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
+3.3V:          +3.36 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:            +2.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:            +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:            +2.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:           +3.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
Vbat:           +3.36 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:             0 RPM  (min =    0 RPM)
fan2:          1994 RPM  (min =    0 RPM)
fan3:             0 RPM  (min =    0 RPM)
fan4:             0 RPM  (min =    0 RPM)
fan5:             0 RPM  (min =    0 RPM)
SYSTIN:         +39.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:         +39.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:         -62.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
PECI Agent 0:    +0.0°C  (high = +80.0°C, hyst = +75.0°C)
                         (crit =  +0.0°C)
PCH_CHIP_TEMP:   +0.0°C   
PCH_CPU_TEMP:    +0.0°C   
PCH_MCH_TEMP:    +0.0°C   
intrusion0:    ALARM
intrusion1:    ALARM
beep_enable:   disabled

CPUTIN I guess would be the CPU temp? It looks a bit low.

6

Hi
Looks normal to me… if you see the other thread, you can configure the labels (eg CPUTIN) to what you want with a config file.