|
|
#1 | |
|
Foxie
|
In SLI mode only, the second GPU's temp in the GPUCoreTemp attribute always reports 0. Disabling SLI gives the correct reporting.
See here: Attribute 'GPUCoreTemp' (darius.spykes.net:0[gpu:0]): 50. Attribute 'GPUCoreTemp' (darius.spykes.net:0[gpu:1]): 0. Second GPU's temperature sensor can still be read from the 'ThermalSensorReading' attribute. (In this case 0 and 2 are the GPU core's and 1 and 3 are the PCB sensors) Attribute 'ThermalSensorReading' (darius.spykes.net:0[thermalsensor:0]): 50. Attribute 'ThermalSensorReading' (darius.spykes.net:0[thermalsensor:1]): 44. Attribute 'ThermalSensorReading' (darius.spykes.net:0[thermalsensor:2]): 52. Attribute 'ThermalSensorReading' (darius.spykes.net:0[thermalsensor:3]): 43.
__________________
Gaming: Intel i7 980X @ 4GHz | ASUS Rampage III Extreme | GTX 480 3Way SLI @ 900Mhz | Koolance VID-NX480 | Corsair Obsidian 700D Corsair H70 CPU Cooler | EK-FB RE3 | Corsair AX1200 | Black Ice SR1 360 | 240GB OCZ Revodrive X2 SSD | Windows 7 Ultimate 12GB Corsair Dominator GT @ 8-8-8-24-1T DDR3-1600 | Onkyo TX SR-707 | 70" Sharp Aquos LCD | KEF Audio 5.1 C3/C6LCR/C7 Workstation: Intel i7 920 D0 @ 4GHz | ASUS Rampage II Extreme | GTX 480 @ 800Mhz | Koolance VID-NX480 | Lian-Li V1200B | Corsair HX1000 EK NB ASUS HP | Watercool HeatKiller 3.0 | Feser Extreme X-360 | 2x160GB Intel X25-M SSD RAID0 | 4x2TB WD20EARS RAID10 12GB Corsair Dominator @ 8-8-8-24-1T DDR3-1600 | Creative X-Fi Titanium | Pioneer DVR-212D | Gentoo Linux Dell 3008WFP | JohnBlue JB3 | CityPulse DA2.03e II DAC | KingRex T20U w/ Modded Auricaps & PSU | Glow Audio Sub One Server: Quad Socket Opteron 8356 (16 cores) @ 2.3GHz | Supermicro H8QMi-2 | Supermicro 2U Chassis | Redundant 1200W PSU 32GB 2GBx16 DDR2-667 ECC | 4x 300GB Cheetah SAS RAID10 | Adaptec 5805 512MB w/BBU | Colocated | Gentoo Linux |
|
|
|
|
|
|
#2 | |
|
Foxie
|
I made a clever hack to make gkrellm (or whatever monitoring program that uses nvidia-settings) report the proper temperature of the second GPU.
File: /usr/local/bin/nvidia-settings Code:
#!/bin/sh
if [ "$1" != "-q" ]; then
/usr/bin/nvidia-settings "$@"
else
if [ "$2" = "[gpu:1]/GPUCoreTemp" ]; then
/usr/bin/nvidia-settings -q "[thermalsensor:2]/ThermalSensorReading" | sed -e "s/thermalsensor:2/gpu:1/g" -e "s/ThermalSensorReading/GPUCoreTemp/g"
else
/usr/bin/nvidia-settings "$@"
fi
fi
spike@darius:~> /usr/bin/nvidia-settings -q [gpu:1]/GPUCoreTemp Attribute 'GPUCoreTemp' (darius.spykes.net:0[gpu:1]): 0. 'GPUCoreTemp' is an integer attribute. 'GPUCoreTemp' is a read-only attribute. 'GPUCoreTemp' can use the following target types: X Screen, GPU. Fixed with script: spike@darius:~> /usr/local/bin/nvidia-settings -q [gpu:1]/GPUCoreTemp Attribute 'GPUCoreTemp' (darius.spykes.net:0[gpu:1]): 49. The valid values for 'GPUCoreTemp' are in the range 0 - 191 (inclusive). 'GPUCoreTemp' is a read-only attribute. 'GPUCoreTemp' can use the following target types: Thermal Sensor.
__________________
Gaming: Intel i7 980X @ 4GHz | ASUS Rampage III Extreme | GTX 480 3Way SLI @ 900Mhz | Koolance VID-NX480 | Corsair Obsidian 700D Corsair H70 CPU Cooler | EK-FB RE3 | Corsair AX1200 | Black Ice SR1 360 | 240GB OCZ Revodrive X2 SSD | Windows 7 Ultimate 12GB Corsair Dominator GT @ 8-8-8-24-1T DDR3-1600 | Onkyo TX SR-707 | 70" Sharp Aquos LCD | KEF Audio 5.1 C3/C6LCR/C7 Workstation: Intel i7 920 D0 @ 4GHz | ASUS Rampage II Extreme | GTX 480 @ 800Mhz | Koolance VID-NX480 | Lian-Li V1200B | Corsair HX1000 EK NB ASUS HP | Watercool HeatKiller 3.0 | Feser Extreme X-360 | 2x160GB Intel X25-M SSD RAID0 | 4x2TB WD20EARS RAID10 12GB Corsair Dominator @ 8-8-8-24-1T DDR3-1600 | Creative X-Fi Titanium | Pioneer DVR-212D | Gentoo Linux Dell 3008WFP | JohnBlue JB3 | CityPulse DA2.03e II DAC | KingRex T20U w/ Modded Auricaps & PSU | Glow Audio Sub One Server: Quad Socket Opteron 8356 (16 cores) @ 2.3GHz | Supermicro H8QMi-2 | Supermicro 2U Chassis | Redundant 1200W PSU 32GB 2GBx16 DDR2-667 ECC | 4x 300GB Cheetah SAS RAID10 | Adaptec 5805 512MB w/BBU | Colocated | Gentoo Linux |
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Jul 2004
Posts: 57
|
I have the same problem with my two Gigabyte GTX 460 cards. But I don't have SLI enabled. Second GPU always gives a 0 temperature.
I don't have those ThermalSensorReading attributes, are they only available in a newer version of the driver? I'm running 256.53. Thanks.
__________________
Geforce 6600 256MB RAM Geforce Go 7400 256MB RAM Geforce 9300M GS 256MB RAM (ASUS N10J) ION 512MB RAM (Acer Revo) GTX 460 1G RAM x 2 GeForce GT 335M (Alienware M11X R2) |
|
|
|
|
|
#4 | |
|
Irreverent Heathen
Join Date: Aug 2006
Location: NSW - Australia. Near a lot of hippies
Posts: 21
|
I also have this problem with 2x9600gt in SLI with the 260.19.12 drivers and kernel 2.6.35.1. I load the nvidia kernel module with "options nvidia NVreg_EnableMSI=1". If I update the kernel to 2.6.36(latest ATM) X will not even start and I get the following:
Code:
(**) NVIDIA(0): Option "NoLogo" "1" (**) NVIDIA(0): Option "Coolbits" "1" (**) NVIDIA(0): Option "SLI" "AA" (**) NVIDIA(0): Option "MultiGPU" "AA" (**) NVIDIA(0): Option "TripleBuffer" "True" (**) Oct 23 23:34:24 NVIDIA(0): Enabling RENDER acceleration (**) Oct 23 23:34:24 NVIDIA(0): NVIDIA SLI antialiasing selected. (**) Oct 23 23:34:24 NVIDIA(0): NVIDIA Multi-GPU antialiasing selected. (II) Oct 23 23:34:24 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is (II) Oct 23 23:34:24 NVIDIA(0): enabled. (EE) Oct 23 23:34:29 NVIDIA(0): The NVIDIA kernel module does not appear to be receiving (EE) Oct 23 23:34:29 NVIDIA(0): interrupts generated by the NVIDIA graphics device (EE) Oct 23 23:34:29 NVIDIA(0): PCI:2:0:0. Please see Chapter 8: Common Problems in the (EE) Oct 23 23:34:29 NVIDIA(0): README for additional information. (EE) Oct 23 23:34:29 NVIDIA(0): Failed to initialize one NVIDIA graphics device! (WW) Oct 23 23:34:29 NVIDIA(0): Failed to initialize SLI configuration. Reason: One GPU (WW) Oct 23 23:34:29 NVIDIA(0): failed to initialize; Only one GPU will be used for this X (WW) Oct 23 23:34:29 NVIDIA(0): screen. (EE) Oct 23 23:34:34 NVIDIA(0): The NVIDIA kernel module does not appear to be receiving (EE) Oct 23 23:34:34 NVIDIA(0): interrupts generated by the NVIDIA graphics device (EE) Oct 23 23:34:34 NVIDIA(0): PCI:4:0:0. Please see Chapter 8: Common Problems in the (EE) Oct 23 23:34:34 NVIDIA(0): README for additional information. (EE) Oct 23 23:34:34 NVIDIA(0): Failed to initialize the NVIDIA graphics device! (II) UnloadModule: "nvidia" (II) UnloadModule: "wfb" (II) UnloadModule: "fb" (EE) Screen(s) found, but none have a usable configuration.
__________________
Jeremiah 8:8 (New International Version) 'How can you say, "We are wise, for we have the law of the LORD," when actually the lying pen of the scribes has handled it falsely?' |
|
|
|
|
![]() |
| Thread Tools | |
|
|