You are not logged in.
I'm trying to get temperature monitoring working my my build, and I've had no success. I've tried acpi, lm sensors, and coretemp and nothing appears to work. My motherboard is the ASRock M3A770DE, with an Athlon II 640 X4 processor. The thermal folder for ACPI is empty, coretemp won't load, and lm sensors works but doesn't display my processor temps. Anyone have any suggestions?
Last edited by alex404 (2010-09-16 09:52:19)
Offline
What is the output of sensors-detect? Coretemp is only for Intel processors. You probably want k10temp.
[fp@viron ~]$ modprobe -l *temp
kernel/drivers/hwmon/coretemp.ko
kernel/drivers/hwmon/k8temp.ko
kernel/drivers/hwmon/k10temp.ko
kernel/drivers/hwmon/via-cputemp.koOffline
k10temp is indeed the correct module, and is detected by sensors-detect:
---
Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Winbond W83627DHG-P Super IO Sensors' (confidence: 9)
Driver `k10temp' (autoloaded):
* Chip `AMD Family 10h thermal sensors' (confidence: 9)
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/rc.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
---
However, it still only reports the temperature on my pcie card when I run sensors. One thing I'm just noting now is that it's telling me to copy some lm_sensors.init file. However, I can't find it anywhere.
Offline
You can ignore the suggestion about copying because you already have /etc/rc.d/sensors installed by the package. Put "sensors" in the DAEMONS array in rc.conf. If you still don't get temps with the modules loaded, check dmesg for error messages.
Have you seen our lm_sensors wiki article?
Offline
Yah, I've sensors is written into the DAEMONS array, and I've checked the wiki article.
I have an ASRock motherboard, so I tried loading the asus mobo module, but it doesn't seem to do anything. Also adding the mentioned line into my menu.lst doesn't have any effect either. But in any case I'm not getting the error messages mentioned in the faq linked to near the top of the wiki.
I've googled around for sites from the last month concerning 'k10temp no cpu temps', and there's a few people reporting similar issues, but none of them have been resolved. I'm pretty flumoxed - I'm kind of inclined to believe it's just a problem with the module. I'd try to contact the developers but I can't find an email address.
Oh, and after reboot, dmesg doesn't report anything new to me.
Last edited by alex404 (2010-09-15 11:26:51)
Offline
It looks like a recent processor. The k10temp module just made it into the kernel in January for older models. It may not support yours yet.
Email or IRC:
http://lm-sensors.org/wiki/FeedbackAndSupport
If you don't subscribe to the mailing list, ask them to Cc: you so you will receive replies.
So no errors in dmesg when loading either module? What is the output of sensors with both modules loaded?
Offline
This is the only thing that dmesg reports when I manually reload the two modules:
w83627ehf: Found W83627DHG-P chip at 0x290
w83627ehf w83627ehf.656: VID pins in output mode, CPU VID not available
I'm pretty sure this isn't relevant. This is the output of sensors:
Adapter: ISA adapter
Vcore: +1.42 V (min = +0.00 V, max = +1.74 V)
in1: +0.07 V (min = +1.36 V, max = +1.78 V) ALARM
AVCC: +3.34 V (min = +2.98 V, max = +3.63 V)
VCC: +3.34 V (min = +2.98 V, max = +3.63 V)
in4: +1.88 V (min = +0.94 V, max = +0.85 V) ALARM
in5: +1.70 V (min = +1.72 V, max = +0.97 V) ALARM
in6: +1.68 V (min = +1.29 V, max = +0.92 V) ALARM
3VSB: +3.50 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.46 V (min = +2.70 V, max = +3.30 V) ALARM
fan1: 0 RPM (min = 21093 RPM, div = 16) ALARM
fan2: 1350 RPM (min = 1140 RPM, div = 8)
fan3: 0 RPM (min = 14062 RPM, div = 16) ALARM
fan5: 0 RPM (min = 28125 RPM, div = 16) ALARM
temp1: +26.0°C (high = -71.0°C, hyst = +25.0°C) ALARM sensor = thermistor
temp2: +36.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
temp3: +37.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +25.4°C (high = +70.0°C)
Offline
So everything is working, although the cpu temp may not be correct. CPU sensors have been problematic, both Intel and AMD from time to time, usually because of hardware errata.
Offline
Sorry if I'm being extremely dense, but where are you reading off my cpu temps, incorrect or otherwise? What's listed under k10temp is my PCIe card, from what I can tell. I don't think any of the ISA Adapter values are CPUs either.
Offline
Try unloading k10temp and modprobing it with force=1.
sudo modprobe k10temp force=1EDIT: Not sure if that requires restarting 'sensors' so I'd do it anyways.
Last edited by codycarey (2010-09-16 01:49:22)
Offline
What's listed under k10temp is my PCIe card, from what I can tell. I don't think any of the ISA Adapter values are CPUs either.
No, w83627ehf is giving you temp1,temp2,temp3,fan2 and some voltages, and k10temp gives you the CPU temp (25C). Whether it says PCI or ISA doesn't matter, its just the method used to retrieve the register values. k10temp isn't going to give you a value from a PCIe card unless you have a K10 CPU on a PCIe card. If you google "k10temp pci adapter" you'll get more examples of similar sensors output. coretemp, on the other hand, says something like this:
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +45.0°C (high = +100.0°C, crit = +100.0°C)Offline
Huh. And what I thought was the k10temp temperature being entirely useless was just it consistently reporting my cpu temp about 10 degrees less than the actual temp (as reported by my BIOS). Thanks for all your help.
Offline
Found this to be interesting for this thread
http://lkml.org/lkml/2009/11/20/39
AMD's sensor does not give a temperature. it gives a temperature range below the maximum. The thread is actually fairly interesting.
see also
Date: Monday, January 11, 2010 - 11:59 am
http://kerneltrap.org/mailarchive/git-c … 1/11/21791
Supported chips:
* AMD Family 10h processors:
- Socket F: Quad-Core/Six-Core/Embedded Opteron
- Socket AM2+: Opteron, Phenom (II) X3/X4
+ Socket F: Quad-Core/Six-Core/Embedded Opteron (but see below)
+ Socket AM2+: Quad-Core Opteron, Phenom (II) X3/X4, Athlon X2 (but see below)
Socket AM3: Quad-Core Opteron, Athlon/Phenom II X2/X3/X4, Sempron II
Socket S1G3: Athlon II, Sempron, Turion II
* AMD Family 11h processors:
@@ -36,10 +36,15 @@ Description
This driver permits reading of the internal temperature sensor of AMD
Family 10h and 11h processors.
+Kernel driver k10temp
+=====================
+
+Supported chips:
+* AMD Family 10h processors:
+ Socket F: Quad-Core/Six-Core/Embedded AMD Opteron
+ Socket AM2+: Phenom II X3/X4
+ Socket AM3: Quad-Core Opteron, Athlon/Phenom II X2/X3/X4, Sempron II
+ mobile: Athlon II, Sempron, Turion II
+
+ Prefix: 'k10temp'
+ Addresses scanned: PCI space
+ Datasheets: see http://developer.amd.com/documentation/guides/
+ #31116: BIOS and Kernel Developer's Guide For AMD Family 10h Processors
+ #41322: Revision Guide for AMD Family 10h Processors
+
+* AMD Family 11h processors:
+ mobile: Athlon (X2), Sempron (X2), Turion X2 (Ultra)
+
+ Prefix: 'k10temp'
+ Addresses scanned: PCI space
+ Datasheets: see http://developer.amd.com/documentation/guides/
+ #41256: BIOS and Kernel Developer's Guide For AMD Family 11h Processors
+ #41788: Revision Guide for AMD Family 11h Processors
+
+Author: Clemens Ladisch <clemens@ladisch.de>
+
+Description
+-----------
+
+This driver permits reading of the internal temperature sensor of AMD
+Family 10h and 11h processors.
+
+All these processors have a sensor, but on older revisions of Family 10h
+processors, the sensor returns inconsistent values (erratum 319). The driver
+refuses to load with these revisions (DR-BA, DR-B2, DR-B3: some Embedded
+Opterons on Socket F; and Quad-Core Opteron, Phenom Triple/Quad-Core, and
+Athon Dual-Core on Socket AM2+). All later revisions (RB-C2, BL-C2, DA-C2,
+RB-C3, HY-D0) work fine; see the list above.
+
+There is one temperature value, available as temp1_input in sysfs. It is
+measured in degrees Celsius with a resolution of 1/8th degree. Please note
+that it is defined as a relative value; to quote the AMD manual:
+
+ Tctl is the processor temperatur control value, used by the platform to
+ control cooling systems. Tctl is a non-physical temperature on an arbitrary
+ scale measured in degrees. It does _not_ represent an actual physical
+ temperature like die or case temperature. Instead, it specifies the
+ processor temperature relative to the point at which the system must supply
+ the maximum cooling for the processor's specified maximum case temperature
+ and maximum thermal power dissipation.
+
+The maximum value for Tctl is usually defined as 70 degrees, so, as a rule of
+thumb, this value should not exceed 60 degrees.
--- linux-2.6/drivers/hwmon/Kconfig
+++ linux-2.6/drivers/hwmon/Kconfig
@@ -222,6 +222,18 @@ config SENSORS_K8TEMP
This driver can also be built as a module. If so, the module
will be called k8temp.
+config SENSORS_K10TEMP
+ tristate "AMD Phenom/Sempron/Turion/Opteron temperature sensor"
+ depends on X86 && PCI
+ help
+ If you say yes here you get support for the temperature
+ sensor inside your CPU. Supported are later revisions of
+ the AMD Family 10h and all revisions of the AMD Family 11h
+ microarchitectures.
+
+ This driver can also be built as a module. If so, the module
+ will be called k10temp.
Offline