Jump to content

GPU Temp higher than ML +10


11 posts in this topic

Recommended Posts

I made a modification for AGPM with my device ID, and removed NulCPUManagement kext and still same problem

Are you sure AGPM is working?

I have exactly the same problem.

 

I have an NVIDIA GT610. On Mountain Lion (without any AGPM) it was running at the right clock (270Mhz when idle) resulting in a temperature of about 39 degrees.

 

With 10.9 GM it runs everytime at 810MHz staying at 51 degrees in medium.

 

It inserted my device id under MacPro5,1 in agpm.

 

It says

 

08/10/13 15:57:45,000 kernel[0]: [AGPM Controller] build GPUDict by Vendor10deDevice104a
 
 
and 
08/10/13 16:01:24,224 com.apple.kextd[14]: WARNING - Invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/System/Library/Extensions/AppleGraphicsPowerManagement.kext"
 
It doesn't seems to stay loaded.
 
Please find a solution.
 
Thanks 

 

It's the same.. GPU scaling works... than when i start to use the PC it stuck at full speed also when I close all apps.

 

What can be?!?!?

 

EDIT

 

AGPM: updateGPUHwPstate(1, 0): fHwPstate = 0 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 1. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 1 from 0, ControlID = 18. SW occupancy updated.

AGPM: updateGPUHwPstate(2, 0): fHwPstate = 1 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 2. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 2 from 1, ControlID = 18. SW occupancy updated.

AGPM: updateGPUHwPstate(3, 0): fHwPstate = 2 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 3. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 3 from 2, ControlID = 18. SW occupancy updated.

AGPM: updateGPUHwPstate(2, 0): fHwPstate = 3 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 2. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 2 from 3, ControlID = 18. SW occupancy updated.

AGPM: updateGPUHwPstate(3, 0): fHwPstate = 2 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 3. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 3 from 2, ControlID = 18. SW occupancy updated.

AGPM: updateGPUHwPstate(2, 0): fHwPstate = 3 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 2. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 2 from 3, ControlID = 18. SW occupancy updated.

AGPM: updateGPUHwPstate(3, 0): fHwPstate = 2 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 3. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 3 from 2, ControlID = 18. SW occupancy updated.

AGPM: updateGPUHwPstate(2, 0): fHwPstate = 3 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 2. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 2 from 3, ControlID = 18. SW occupancy updated.

AGPM: updateGPUHwPstate(3, 0): fHwPstate = 2 fFB = 0xffffff8012bc4800

AGPM: updateGPUHwPstate(): state = 3. Calling fFB->setAggressiveness()...

AGPM: GPU = display G-state set to 3 from 2, ControlID = 18. SW occupancy updated.

 

 

AGPM seems to work correctly. But after some period HW Monitor report only state 0 frequency (higher). Could be a problem of FakeSMC?

I see that temp is much higher.. so why AGPM switch off the GPU and the GPU stays at full powa?

Driver BUG??

×
×
  • Create New...