https://bugzilla.novell.com/show_bug.cgi?id=794680
https://bugzilla.novell.com/show_bug.cgi?id=794680#c0
Summary: 12.3/MS2/x64, lm-sensors.org (sensors-detect) cant
deal with amd apu temperature etc.
Classification: openSUSE
Product: openSUSE Factory
Version: 12.3 Milestone 1
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: abittner@abittner.de
QAContact: qa-bugs@suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101
Firefox/17.0
hwinfo:
Hardware Class: cpu
Arch: X86-64
Vendor: "AuthenticAMD"
Model: 21.16.1 "AMD A10-5800K APU with Radeon(tm) HD Graphics "
dmesg
[ 4.016862] microcode: CPU0: patch_level=0x06001116
[ 4.044284] microcode: CPU0: new patch_level=0x06001119
[ 4.044296] microcode: CPU1: patch_level=0x06001116
[ 4.052538] microcode: CPU1: new patch_level=0x06001119
[ 4.052612] microcode: CPU2: patch_level=0x06001116
[ 4.060674] microcode: CPU2: new patch_level=0x06001119
[ 4.060685] microcode: CPU3: patch_level=0x06001116
[ 4.068908] microcode: CPU3: new patch_level=0x06001119
[ 4.068956] microcode: Microcode Update Driver: v2.00
, Peter Oruba
...
[ 4.741741] powernow-k8: Found 1 AMD A10-5800K APU with Radeon(tm) HD
Graphics (4 cpu cores) (version 2.20.00)
lm-sensors.org doesnt detect anything usable regarding the cpu/apu itself
mailinglist as of december 2012 says there is an amd/cpu/apu patch even
directly added by some amd developer folks
http://lists.lm-sensors.org/pipermail/lm-sensors/2012-December/thread.html
http://lists.lm-sensors.org/pipermail/lm-sensors/2012-December/037841.html
please include latest lm-sensors.org package if possible
thank you.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
sensors-detect
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# Board: ASUSTeK COMPUTER INC. F2A85-V PRO
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... No
AMD Family 15h 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 NCT6779D Super IO Sensors' Success!
(address 0x290, driver `to-be-written')
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: 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):
Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
Do you want to scan it? (yes/NO/selectively):
Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
Do you want to scan it? (yes/NO/selectively):
Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
Do you want to scan it? (yes/NO/selectively):
Next adapter: Radeon i2c bit bus 0x94 (i2c-4)
Do you want to scan it? (yes/NO/selectively):
Next adapter: Radeon i2c bit bus 0x95 (i2c-5)
Do you want to scan it? (yes/NO/selectively):
Next adapter: Radeon aux bus DP-auxch (i2c-6)
Do you want to scan it? (yes/NO/selectively):
Next adapter: Radeon aux bus DP-auxch (i2c-7)
Do you want to scan it? (yes/NO/selectively):
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-8)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'...
Yes
(confidence 8, not a hardware monitoring chip)
Client found at address 0x53
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 `to-be-written':
* ISA bus, address 0x290
Chip `Nuvoton NCT6779D Super IO Sensors' (confidence: 9)
Note: there is no driver for Nuvoton NCT6779D Super IO Sensors yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.
No modules to load, skipping modules configuration.
Unloading i2c-dev... OK
Unloading cpuid... OK
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.