[opensuse] Working k10temp for AMD CPUs?
Hi. I'm trying to do some HW monitoring on a system I'm working on. It's an AMD 965 (Quad core 64 bit - AMD Family 10h) CPU on a Gigabyte motherboard. The sensors-detect script finds the k10temp sensor, but... it says that the CPU is running at 0C, and while I have a decent cooler, I don't think it's that good. The sensor itself is working, and reports believable info in other OSes (ie Windows). Looking at the kernel documentation here: https://www.kernel.org/doc/Documentation/hwmon/k10temp it seems that I should be able to use the force=1 paramter when loading the module... so: # rmmod k10temp # modprobe k10temp force=1 And the kernel module loads: # lsmod | grep k10temp k10temp 13127 0 But... running sensors again gives me this: # sensors k10temp-pci-00c3 Adapter: PCI adapter temp1: +0.0°C (high = +70.0°C) (crit = +89.0°C, hyst = +87.0°C) So now I'm stuck... I've read the docs, tried what makes sense... but not producing results. Anyone here have any luck with this? C -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 07/10/13 14:08, C escribió:
So now I'm stuck... I've read the docs, tried what makes sense... but not producing results. Anyone here have any luck with this?
what kernel version are you running ? (uname -a) -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Oct 7, 2013 at 8:11 PM, Cristian Rodríguez wrote:
El 07/10/13 14:08, C escribió:
So now I'm stuck... I've read the docs, tried what makes sense... but not producing results. Anyone here have any luck with this?
what kernel version are you running ? (uname -a)
I always forget some tidbit of useful information: 3.7.10-1.16-desktop C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Mon, 07 Oct 2013, C wrote:
Hi. I'm trying to do some HW monitoring on a system I'm working on. It's an AMD 965 (Quad core 64 bit - AMD Family 10h) CPU on a Gigabyte motherboard.
What chipset and what i2c/sensors chips? Have a look at the full sensors-detect output and or look into the Motherboard manual. I have a Gigabyte GA-770TA-UD3 with 770 chipset. # lspci 00:00.0 Host bridge: ATI Technologies Inc RX780/RX790 Chipset Host Bridge 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c) 00:14.3 ISA bridge: ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller and the manual lists the relevant chips as: 1-2 Product Specifications [..] Chipset North Bridge: AMD 770 South Bridge: AMD SB710 [..] I/O Controller iTE IT8720 chip (the latter also handles floppy) You need to have sensors-detect also probe the ISA ports. [..]
# sensors k10temp-pci-00c3 Adapter: PCI adapter temp1: +0.0°C (high = +70.0°C) (crit = +89.0°C, hyst = +87.0°C)
# sensors k10temp-pci-00c3 Adapter: PCI adapter temp1: +36.5°C (high = +70.0°C) (crit = +72.0°C, hyst = +70.0°C) # lsmod it87 47720 0 hwmon_vid 12827 1 it87 i2c_dev 13946 0 k8temp 13057 0 k10temp 13166 0 i2c_piix4 13828 0 edac_mce_amd powernow_k8 29481 0 processor 45192 1 powernow_k8 mperf 12667 1 powernow_k8 thermal 22961 0 thermal_sys 25017 2 processor,thermal ==== /etc/sysconfig/lm_sensors ==== HWMON_MODULES="it87 i2c-piix i2c-dev k8temp" MODULE_0=k8temp MODULE_1=i2c-piix4 MODULE_2=i2c-dev MODULE_3=it87 ==== /etc/sysconfig/kernel === INITRD_MODULES="thermal powernow_k8 ..." ==== I guess those modules should be the same on your board except the it87. Otherwise, you'll need to show the output of lspci -v and sensors-detect. HTH, -dhn -- "Sexual harrassment in designated areas only" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Oct 7, 2013 at 9:32 PM, David Haller wrote:
On Mon, 07 Oct 2013, C wrote:
Hi. I'm trying to do some HW monitoring on a system I'm working on. It's an AMD 965 (Quad core 64 bit - AMD Family 10h) CPU on a Gigabyte motherboard.
What chipset and what i2c/sensors chips? Have a look at the full sensors-detect output and or look into the Motherboard manual.
I have a Gigabyte GA-770TA-UD3 with 770 chipset.
Mine is a Gigabyte GA-990XA-UD3
# lspci 00:00.0 Host bridge: ATI Technologies Inc RX780/RX790 Chipset Host Bridge 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c) 00:14.3 ISA bridge: ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller
Same info from my system: 00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (external gfx0 port B) (rev 02) 00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller (rev 42) 00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
and the manual lists the relevant chips as:
Manual is long gone - I can look it up online though I think.
You need to have sensors-detect also probe the ISA ports.
When it probes the ISA ports it gets no positive results. Among all the "No" results in a scan these are the only two "Success!" results: AMD Family 10h thermal sensors... Success! (driver `k10temp') Found `ITE IT8720F Super IO Sensors' Success! (address 0x228, driver `it87')
# sensors k10temp-pci-00c3 Adapter: PCI adapter temp1: +36.5°C (high = +70.0°C) (crit = +72.0°C, hyst = +70.0°C)
That's the kind of output I'm looking for... but not getting
# lsmod it87 47720 0 hwmon_vid 12827 1 it87 i2c_dev 13946 0 k8temp 13057 0 k10temp 13166 0 i2c_piix4 13828 0 edac_mce_amd powernow_k8 29481 0 processor 45192 1 powernow_k8 mperf 12667 1 powernow_k8 thermal 22961 0 thermal_sys 25017 2 processor,thermal
==== /etc/sysconfig/lm_sensors ====
Mine has only these lines (with the comments stripped) HWMON_MODULES="it87" MODULE_0=it87
==== /etc/sysconfig/kernel ===
INITRD_MODULES=""
Otherwise, you'll need to show the output of lspci -v and sensors-detect.
lspci -v --> http://paste.opensuse.org/51854932 sensors-detect --> http://paste.opensuse.org/58795227 /etc/sysconfig/lm_sensors --> http://paste.opensuse.org/61324921 C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Tue, 08 Oct 2013, C wrote:
On Mon, Oct 7, 2013 at 9:32 PM, David Haller wrote:
On Mon, 07 Oct 2013, C wrote:
Hi. I'm trying to do some HW monitoring on a system I'm working on. It's an AMD 965 (Quad core 64 bit - AMD Family 10h) CPU on a Gigabyte motherboard.
What chipset and what i2c/sensors chips? Have a look at the full sensors-detect output and or look into the Motherboard manual.
I have a Gigabyte GA-770TA-UD3 with 770 chipset.
Mine is a Gigabyte GA-990XA-UD3
Which is a related, updated and slightly more featureful version of the 770 IIRC ;) Close enough related tough I think.
# lspci 00:00.0 Host bridge: ATI Technologies Inc RX780/RX790 Chipset Host Bridge 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c) 00:14.3 ISA bridge: ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller
Same info from my system: 00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (external gfx0 port B) (rev 02) 00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller (rev 42) 00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
Ok. (See your RD890 vs. my RX780 ;)
and the manual lists the relevant chips as:
Manual is long gone - I can look it up online though I think.
Please do, might come in handy anyways! But I think the SB has basically not changed since the 7xx series (i.e. 8xx and 9xx are the same, _BUT_ of course the SB[789]10 always has less features than the SB[789]50. But regarding this case that should be irrelevant.
You need to have sensors-detect also probe the ISA ports.
When it probes the ISA ports it gets no positive results. Among all the "No" results in a scan these are the only two "Success!" results:
AMD Family 10h thermal sensors... Success! (driver `k10temp') Found `ITE IT8720F Super IO Sensors' Success! (address 0x228, driver `it87')
Ahh, good, so the same Super IO chip.
# sensors k10temp-pci-00c3 Adapter: PCI adapter temp1: +36.5°C (high = +70.0°C) (crit = +72.0°C, hyst = +70.0°C)
That's the kind of output I'm looking for... but not getting
# lsmod it87 47720 0 hwmon_vid 12827 1 it87 i2c_dev 13946 0 k8temp 13057 0 k10temp 13166 0 i2c_piix4 13828 0 edac_mce_amd powernow_k8 29481 0 processor 45192 1 powernow_k8 mperf 12667 1 powernow_k8 thermal 22961 0 thermal_sys 25017 2 processor,thermal
==== /etc/sysconfig/lm_sensors ====
Mine has only these lines (with the comments stripped)
HWMON_MODULES="it87" MODULE_0=it87
Where's k8temp/k10temp? eh? And you also need i2c dev. So, just copy over my config, as you got the same chip (or at least a later revision driven by the same driver) ...
==== /etc/sysconfig/kernel ===
INITRD_MODULES=""
Yeah, should not be neccessary, but Yast did put "thermal" in there at some time ...
Otherwise, you'll need to show the output of lspci -v and sensors-detect.
lspci -v --> http://paste.opensuse.org/51854932
Ok.
sensors-detect --> http://paste.opensuse.org/58795227
That actually looks just fine. Have you let sensors detect write /etc/sysconfig/lm-sensors?
/etc/sysconfig/lm_sensors --> http://paste.opensuse.org/61324921
... and has it not added k10temp/k8temp? Well, anyway: just copy my config and you should be just fine. Do expect some offset from actual temperatures. I've been using that k10temp + k8temp loaded for years now, with no ill effect. Not sure if k8temp is needed, but as long as it works ;) You do need i2c-dev and i2c-piix modules and it87 though. Well, not neccessarily for the CPU temps, but for fan speeds and regulation. Ask, if you need some tips on how to tune fan speeds, how to monitor them with gkrellm, etc. ;) Gigabyte boards are somewhat weird regarding their BIOS fan-speeds, so a little tweaking may be in order, depending on the cooler/fan combo you use. BTW: I got a rather big honking cooler on my CPU, usually idling along below 700 RPM and still keeping the CPU below 35°C.[1] With the boxed cooler, I had the temp pegged at ~56°C and the cooler already at 1300 RPM with just one core on full load and more with load on both cores (got a Athlon II X2 250 (2 x 3.0 GHz)). Hm. I think I might tune fancontrol again, aim for <500 RPM at idle and ~40°C or so ;) But I think something else is actually the "loud" thing. Either the GPU-card or the disks. The PSU is quite silent. Gotta go put the center roll of some kitchen paper to my ear again and hunt for what's actually causing the noise ;) -dnh PS: *GNA* my sys-fan runs at ~920 RPM but was sold as a 800 RPM one. Oh, well, the more that bugger sucks out the back, the more flow is at the front where the disks are. Come to think of it, I should experiment closing up the holes in the sides so that the air *must* flow from the front, *inbetween the disks*, to the back ... That sucker at the back (and that inside the PSU) may be more useful that way :) [1] under full load on both cores, it'll go up to it's max of ~1300 RPM and still keep the CPU below 45°C or so ;) Should tune that also. E.g. 55°C core temp should be quite ok and be easier on my ears. -- "I guess some Ba'als are bigger than others." -- Vala, SG-1 10x04 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Oct 8, 2013 at 2:40 AM, David Haller wrote:
On Tue, 08 Oct 2013, C wrote:
On Mon, Oct 7, 2013 at 9:32 PM, David Haller wrote:
On Mon, 07 Oct 2013, C wrote: I have a Gigabyte GA-770TA-UD3 with 770 chipset.
Mine is a Gigabyte GA-990XA-UD3
Which is a related, updated and slightly more featureful version of the 770 IIRC ;) Close enough related tough I think.
Yup, they should be pretty much the same
Where's k8temp/k10temp? eh? And you also need i2c dev.
I unloaded k10temp, then loaded k8temp... no changes. Then I loaded k10temp force=1.... no changes. Then I loaded it87.... bam... lots of voltage, fan and temp info. Loading the others did nothing. Unloading k8temp... no changes. and unloading the rest (including k10temp)... no changes. The key one to load was it87. If that's loaded I get the info I'm looking for. Well info of sorts anyway. # sensors it8720-isa-0228 Adapter: ISA adapter in0: +0.98 V (min = +0.00 V, max = +4.08 V) in1: +1.50 V (min = +0.00 V, max = +4.08 V) in2: +3.34 V (min = +0.00 V, max = +4.08 V) +5V: +3.04 V (min = +0.00 V, max = +4.08 V) in4: +3.07 V (min = +0.00 V, max = +4.08 V) in5: +1.17 V (min = +0.00 V, max = +4.08 V) in6: +4.08 V (min = +0.00 V, max = +4.08 V) 5VSB: +3.02 V (min = +0.00 V, max = +4.08 V) Vbat: +3.23 V fan1: 685 RPM (min = 10 RPM) fan2: 837 RPM (min = 10 RPM) fan3: 1038 RPM (min = 10 RPM) fan5: 0 RPM (min = 10 RPM) ALARM temp1: +39.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +30.0°C (low = +127.0°C, high = +90.0°C) sensor = thermal diode temp3: +12.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode cpu0_vid: +0.375 V intrusion0: OK
Do expect some offset from actual temperatures.
That's OK, as long as I can see a temperature at idle... fan at idle... and then some "new" values under load. It doesn't have be perfect.
Ask, if you need some tips on how to tune fan speeds, how to monitor them with gkrellm, etc. ;) Gigabyte boards are somewhat weird regarding their BIOS fan-speeds, so a little tweaking may be in order, depending on the cooler/fan combo you use.
That's the next step. The CPU is an AMD 965, and the cooler is Noctua NH-D14. A bit of a silly cooler, but it wasn't expensive (on sale) and it works rather well. I'd like to tune things a little to drop the system noise just a touch more. It's pretty quiet now, but there is that constant hum that I know I can eliminate (I know it can run silent based on tests with another unnamed OS). So with help from everyone, that's one minor issue resolved. I need to write it down so I remember for the re-install to 13.1. :-P C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Tue, 08 Oct 2013, C wrote:
On Tue, Oct 8, 2013 at 2:40 AM, David Haller wrote:
On Tue, 08 Oct 2013, C wrote:
On Mon, Oct 7, 2013 at 9:32 PM, David Haller wrote:
On Mon, 07 Oct 2013, C wrote: I have a Gigabyte GA-770TA-UD3 with 770 chipset.
Mine is a Gigabyte GA-990XA-UD3
Which is a related, updated and slightly more featureful version of the 770 IIRC ;) Close enough related tough I think.
Yup, they should be pretty much the same
Where's k8temp/k10temp? eh? And you also need i2c dev.
I unloaded k10temp, then loaded k8temp... no changes. Then I loaded k10temp force=1.... no changes. Then I loaded it87.... bam... lots of voltage, fan and temp info. Loading the others did nothing. Unloading k8temp... no changes. and unloading the rest (including k10temp)... no changes.
Did you also load i2c-dev and i2c-piix?
The key one to load was it87. If that's loaded I get the info I'm looking for. Well info of sorts anyway.
# sensors it8720-isa-0228 Adapter: ISA adapter in0: +0.98 V (min = +0.00 V, max = +4.08 V) in1: +1.50 V (min = +0.00 V, max = +4.08 V) in2: +3.34 V (min = +0.00 V, max = +4.08 V) +5V: +3.04 V (min = +0.00 V, max = +4.08 V) in4: +3.07 V (min = +0.00 V, max = +4.08 V) in5: +1.17 V (min = +0.00 V, max = +4.08 V) in6: +4.08 V (min = +0.00 V, max = +4.08 V) 5VSB: +3.02 V (min = +0.00 V, max = +4.08 V) Vbat: +3.23 V fan1: 685 RPM (min = 10 RPM) fan2: 837 RPM (min = 10 RPM) fan3: 1038 RPM (min = 10 RPM) fan5: 0 RPM (min = 10 RPM) ALARM temp1: +39.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +30.0°C (low = +127.0°C, high = +90.0°C) sensor = thermal diode temp3: +12.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode cpu0_vid: +0.375 V intrusion0: OK
Well, those are the temps read from sensors on the MoBo, not the CPU temp. Compare: # sensors k10temp-pci-00c3 Adapter: PCI adapter temp1: +43.5°C (high = +70.0°C) (crit = +72.0°C, hyst = +70.0°C) it8720-isa-0228 Adapter: ISA adapter in0: +1.42 V (min = +0.00 V, max = +4.08 V) [..] fan1: 1310 RPM (min = 0 RPM) fan3: 914 RPM (min = 0 RPM) temp1: +43.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +54.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode temp3: +84.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor cpu0_vid: +1.250 V Temp3 is obvious bull, temp1 and temp2 I've called t_SYS and t_CPU respectively. Should tweak the offsets (at least in gkrellm ;) BTW: the temps show up as k10temp@c3/temp1 and it8720@228/temp[123] in gkrellm and as /sys/devices/platform/it87.552/temp?_input and /sys/devices/pci0000:00/0000:00:18.3/temp1_input (the latter also being available as /sys/bus/pci/drivers/k10temp/0000\:00\:18.3/hwmon/hwmon0/device/temp1_input and /sys/module/k10temp/drivers/pci\:k10temp/0000\:00\:18.3/temp1_input BTW: from lspci: 00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control Have a look at those dirs /sys/devices/pci0000:00/0000:00:18.3/ /sys/bus/pci/drivers/k10temp/ /sys/module/k10temp/ replacing the PCI id accordingly. Oh, do you have any messages in dmesg / /v/l/m when you load k10temp etc.?
Do expect some offset from actual temperatures.
That's OK, as long as I can see a temperature at idle... fan at idle... and then some "new" values under load. It doesn't have be perfect.
My thoughts ;)
Ask, if you need some tips on how to tune fan speeds, how to monitor them with gkrellm, etc. ;) Gigabyte boards are somewhat weird regarding their BIOS fan-speeds, so a little tweaking may be in order, depending on the cooler/fan combo you use.
That's the next step. The CPU is an AMD 965, and the cooler is Noctua NH-D14. A bit of a silly cooler, but it wasn't expensive (on sale) and it works rather well.
Yeah.
I'd like to tune things a little to drop the system noise just a touch more. It's pretty quiet now, but there is that constant hum that I know I can eliminate (I know it can run silent based on tests with another unnamed OS).
man pwmconfig You can tweak it's output in /etc/fancontrol manually afterwards, but it's a very good start esp. with those pesky strings. I have e.g.: ==== my /etc/fancontrol, won't work elsewhere ==== # Configuration file generated by pwmconfig, changes will be lost INTERVAL=5 DEVPATH=hwmon0=devices/pci0000:00/0000:00:18.3 hwmon1=devices/platform/it87.552 DEVNAME=hwmon0=k10temp hwmon1=it8720 FCTEMPS= hwmon1/device/pwm1=hwmon0/device/temp1_input FCFANS= hwmon1/device/pwm1=hwmon1/device/fan1_input MINTEMP= hwmon1/device/pwm1=30 MAXTEMP= hwmon1/device/pwm1=60 MINSTART= hwmon1/device/pwm1=130 MINSTOP= hwmon1/device/pwm1=90 MINPWM=hwmon1/device/pwm1=90 MAXPWM= hwmon1/device/pwm1=230 ==== (that's manually tweaked, despite the comment ;) I have only that one fan controlled by PWM (case fan is unregulated). So, what's that "/etc/fancontrol" do? It takes the input of k10temp (hwmon0/device/temp1_input) and regulates the fan on hwmon1/device/pwm1 according to it. FCTEMPS= hwmon1/device/pwm1=hwmon0/device/temp1_input The relation from PWM value and how fast the fan turns is defined by this relation: FCFANS= hwmon1/device/pwm1=hwmon1/device/fan1_input (i.e. what I put in hwmon1/device/pwm1 results in changes of hwmon1/device/fan1_input (where you can read the RPMs of the fan)). MINTEMP/MAXTEMP set the temps at which the fan should reach the lowest resp. the maximum defined PWM value defined in MINPWM/MAXPWM. MINSTART is the PWM to issue to be sure the fan starts if it was stopped, MINSTOP is the lowest PWM value where the fan is safely still spinning... Read up in 'man fancontrol'. BTW: fancontrol should already be running if you got lm_sensors running (at least it was that way), fancontrol got started in the lm_sensors init-script. Dunno what's now with systemd. If it's running, a 'ps ax|grep fan' shows: [PID] ... /bin/bash /usr/sbin/fancontrol HTH, -dnh -- Someone suggested going out into the big blue room and playing frisbee which met with general approval (primarily because the big blue room was closer to black and lacked that annoying bright thing that was there earlier) [..] -- T. W. Strong Jr. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Oct 9, 2013 at 12:19 PM, David Haller wrote:
I unloaded k10temp, then loaded k8temp... no changes. Then I loaded k10temp force=1.... no changes. Then I loaded it87.... bam... lots of voltage, fan and temp info. Loading the others did nothing. Unloading k8temp... no changes. and unloading the rest (including k10temp)... no changes.
Did you also load i2c-dev and i2c-piix?
I did, but loading.. or not loading, I see zero difference in the temp/fan monitoring
Well, those are the temps read from sensors on the MoBo, not the CPU temp.
Yup, but they are the only temps that make any sense. I loaded all of the modules we discussed, including using the force=1 on k10temp and nothing else shows up... k10temp never shows anything except 0C I've installed gkrelm and am using that to keep an eye on the MB temps and the fan speeds. So far it's pretty uneventful. The only temp that really ever spikes is the Nvidia GPU temp when I put it under some load... it's also the owner of the loudest fan in my system. The CPU fans (2) are running at 600ish... the rear case fan at 800 and the front fan at 1000. I can slow the front fan down a bit.. I don't have a case heat issue at all, even under load.
Have a look at those dirs /sys/devices/pci0000:00/0000:00:18.3/ /sys/bus/pci/drivers/k10temp/ /sys/module/k10temp/
replacing the PCI id accordingly.
Hmmm.. haven't done that yet. Will look later today.
Oh, do you have any messages in dmesg / /v/l/m when you load k10temp etc.?
Didn't think of that. I'll tinker with that tonight. I had to do a full system reinstall last night (unrelated to this discussion) so... hopefully after work today I can poke this a bit and see what's reported when i load the kernel module.
You can tweak it's output in /etc/fancontrol manually afterwards, but it's a very good start esp. with those pesky strings. I have e.g.: snip Read up in 'man fancontrol'.
This is all a massive help. I've got some reading to do :-) It should be interesting to see where I can take this now that I've got some info to work with. C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/10/13 16:45, C wrote:
On Wed, Oct 9, 2013 at 12:19 PM, David Haller wrote:
I unloaded k10temp, then loaded k8temp... no changes. Then I loaded k10temp force=1.... no changes. Then I loaded it87.... bam... lots of voltage, fan and temp info. Loading the others did nothing. Unloading k8temp... no changes. and unloading the rest (including k10temp)... no changes. Did you also load i2c-dev and i2c-piix? I did, but loading.. or not loading, I see zero difference in the temp/fan monitoring
Well, those are the temps read from sensors on the MoBo, not the CPU temp. Yup, but they are the only temps that make any sense. I loaded all of the modules we discussed, including using the force=1 on k10temp and nothing else shows up... k10temp never shows anything except 0C
I've installed gkrelm and am using that to keep an eye on the MB temps and the fan speeds. So far it's pretty uneventful. The only temp that really ever spikes is the Nvidia GPU temp when I put it under some load... it's also the owner of the loudest fan in my system. The CPU fans (2) are running at 600ish... the rear case fan at 800 and the front fan at 1000. I can slow the front fan down a bit.. I don't have a case heat issue at all, even under load.
Have a look at those dirs /sys/devices/pci0000:00/0000:00:18.3/ /sys/bus/pci/drivers/k10temp/ /sys/module/k10temp/
replacing the PCI id accordingly. Hmmm.. haven't done that yet. Will look later today.
Oh, do you have any messages in dmesg / /v/l/m when you load k10temp etc.? Didn't think of that. I'll tinker with that tonight. I had to do a full system reinstall last night (unrelated to this discussion) so... hopefully after work today I can poke this a bit and see what's reported when i load the kernel module.
You can tweak it's output in /etc/fancontrol manually afterwards, but it's a very good start esp. with those pesky strings. I have e.g.: snip Read up in 'man fancontrol'. This is all a massive help. I've got some reading to do :-) It should be interesting to see where I can take this now that I've got some info to work with.
C.
I remember a loooooong time ago when I was running XP that one needed (in XP) some special app which would make all the sensors work - but I don't remember what this app was nor what it actually did to make all the sensors work. From what I read earlier, I have the same - or equivalent - Gigabyte mobo as yourself and I know that I cannot get all the sensors to work. But I am not worried about it as I know that with 10 fans in the box the temp is not of a major concern :-) . However, I DO know that when the cpu is pushed by one particular app the temp of the cpu exceeds 70C because I have the alarm in the BIOS to go off at 70C but had to up this to 80C 'cause I got fed up with listening to the mobo complaining about the temp :-) . BC -- "If you read the books that everyone else is reading, you can only think what everyone else is thinking." - Haruki Murakami -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Basil Chupin -
C -
Cristian Rodríguez -
David Haller