On Wed, Feb 15, 2012 at 7:17 AM, Andreas Herrmann <andreas.herrmann3@xxxxxxx> wrote:
Hi Kenneth,On Wed, Feb 15, 2012 at 06:21:19AM -0800, Kenneth Cox wrote:
> Jean,
>
> Thanks for the response.
>
> On Tue, Feb 14, 2012 at 11:29 PM, Jean Delvare <khali@xxxxxxxxxxxx> wrote:
>
> Hi Kenneth,
>
> On Mon, 13 Feb 2012 16:46:33 -0800, Kenneth Cox wrote:
> > I am having trouble getting lm-sensors to work as it should I believe
> that
> > part of the problem is support for a newer chip set. here are the specs:
> >
> > CPU: AMD A4-3400 APU with Radeon(tm) HD Graphics
> > family(18) model(1) stepping(0)
> >
> > MoBo: ASRock A75M-HVS
> >
> > I'm using the onboard Radeon graphics.
> >
> > I ran the sensors-detect script saying yes to everything. The output of
> > sensors:
> > k10temp-pci-00c3
> > Adapter: PCI adapter
> > temp1: +9.8°C (high = +70.0°C)
> > (crit = +70.0°C, hyst = +69.0°C)
> >
> > That's much colder than room temp and only gives data for the PCI
> adapter.
>
> This isn't the temperature of "the PCI adapter", the value is from your
> CPU. This happens to be implemented as a PCI device in AMD processors,
> which is why you see "PCI adapter" in the output, but this is rather
> misleading I admit.
>
> The reported temperature indeed looks wrong, however it isn't
> necessarily surprising. This isn't an absolute temperature, but rather
> a temperature margin from the CPU's max, and it is only accurate when
> you get close to the limit. So from the above, one can say that your
> CPU is running very cool ans safe, and that's about it.
>
> That being said, I think this is the first report I see for this family
> of CPU. Andreas, Andre, do you think there's any bug to be fixed here?
>
>
> Got it. That's excellent news. At least I know I can trust the output to let me
> know if it's getting to warm. I did not trust it at all before.
>
>
> > I also tried downloading the latest version of sensors-detect from
> > http://www.lm-sensors.org/wiki/Devices and rerunning. It did not change
> > anything.
> >
> > Is there a way to get sensor data for the CPU and accurate data from the
> > PCI adapter? Any help would be appreciated.
>
> What kind of system is this? If this is a laptop you're probably out of
> luck. If this is a desktop system, I would expect a hardware monitoring
> chip on the SMBus or in the Super-I/O chip. Maybe it is too recent and
> we don't know about it yet. Please provide the full output of
> sensors-detect.
I just can second what Jean already said. The reported temperature
(Tctl) is
"on its own scale aligned to the processors cooling
requirements. Therefore Tctl does not represent a temperature which
could be measured on the die or the case of the processor. Instead,
it specifies the processor temperature relative to the maximum
operating temperature, Tctl_max."
(Quoted from the AMD Family 12h Processor BKDG.) You have a FM1 socket
processor. Tctl_max is 70 in your case. So the reported temperature
of 9.8 is far below that maximum operating temperature.
HTH,
Andreas
Thank you Andreas.
Here is the results of sensors-detect as promised:
# sensors-detect revision 5946 (2011-03-23 11:54:44 +0100)
# System: To Be Filled By O.E.M. To Be Filled By O.E.M.
# Board: ASRock A75M-HVS
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... Success!
(driver `k10temp')
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'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found `Nuvoton NCT6776F Super IO Sensors' Success!
(address 0x290, driver `to-be-written')
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): 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):
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 `to-be-written':
* ISA bus, address 0x290
Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
Driver `k10temp' (autoloaded):
* Chip `AMD Family 12h and 14h thermal sensors' (confidence: 9)
Note: there is no driver for Nuvoton NCT6776F 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
Thanks,
Ken
_______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
