Jump to content

Graphics - No GPU Power Management


  • Please log in to reply
242 replies to this topic

#1
chevalier433

chevalier433

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

Hello,my hardware is p8z77-m,3570k,gtx 660,igpu disabled.I recently update from mountain lion to mavericks GM using my hack3.2 all work exceptionally well except GPU when i run some apps stay at full power not throttle down even when i close them and i need a restart for throttle down to work.If anyone has a solution i am glad to hear it!Thanks in advance.



#2
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 1,820 posts
  • Gender:Male

Known issue since DP3. 



#3
chevalier433

chevalier433

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

Known issue since DP3. 

Any known solutions?



#4
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 1,820 posts
  • Gender:Male

Any known solutions?

Known issue since DP3.  That means there is not solution or the issue would not exist. 



#5
chevalier433

chevalier433

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

Known issue since DP3.  That means there is not solution or the issue would not exist. 

ok thanks mate probably i will return to ML 



#6
jamiethemorris

jamiethemorris

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 216 posts
  • Gender:Male
Is this a problem specific to that card or is graphics power management broken in Mavericks?

#7
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 1,820 posts
  • Gender:Male

Is this a problem specific to that card or is graphics power management broken in Mavericks?

 

Broken in 10.9. Retail drivers should fix this once released. 

 

Before DP4 it worked until after sleep when it stopped working. 



#8
yokonunz

yokonunz

    InsanelyMac Protégé

  • Members
  • Pip
  • 42 posts

Thank you so much @Rampage Dev for poiting out the issue.

 

We are talking about the problem here: http://www.insanelym...2-gpu-voltages/

and here: http://www.insanelym...her-than-ml-10/

 

Do you unify threads?

 

Is a solution for you using NVIDIA Kexts from DP2??

 

Thanks!



#9
mcdougal33

mcdougal33

    InsanelyMac Protégé

  • Members
  • PipPip
  • 56 posts
  • Gender:Male

I'm having no gpu power management issues with my GTX560ti after editing the AGPM kext.  Before the edit it would get stuck in state 0 after sleep.  It was the exact same way in mountain lion too.

 

Here are my settings for iMac11,3.  If you're using a macpro profile then the control-id needs to be 18.  

 

<key>iMac11,3</key>
<dict>
<key>Vendor10deDevice1200</key>
<dict>
<key>Heuristic</key>
<dict>
<key>ID</key>
<integer>0</integer>
<key>IdleInterval</key>
<integer>250</integer>
<key>SensorOption</key>
<integer>1</integer>
<key>SensorSampleRate</key>
<integer>4</integer>
<key>TargetCount</key>
<integer>5</integer>
<key>Threshold_High</key>
<array>
<integer>55</integer>
<integer>40</integer>
<integer>60</integer>
<integer>100</integer>
</array>
<key>Threshold_Low</key>
<array>
<integer>0</integer>
<integer>75</integer>
<integer>90</integer>
<integer>100</integer>
</array>
</dict>
<key>LogControl</key>
<integer>1</integer>
<key>control-id</key>
<integer>17</integer>
</dict>
</dict>


#10
joseracer

joseracer

    InsanelyMac Protégé

  • Donators
  • 7 posts

Any chance this is caused by some particular 3rd party software install?

I´m pretty sure I did not had this before installing Photoshop CS6 trial, might go back to a Superduper image later on the day to test this. 

 

I even ran Ungine Heaven benchmarks, saw the clocks go to turboboost mode and then go back to the lower 135mhz state in my GF760gtx, and messed a bit with switching rapidly between spaces with the trackpad to look it climb back to the 675mhz zone and after 10/15 seconds of idle time go back gradually to 130ish or so (whatever the lowest speed is). I would say 90% sure and not 100% cause it was all during a troubleshooting / fine-tuning stage of my mavericks installation, since i was learning how to make a vanilla install without relying on scripts and installers that messed with the extra and system folders without me knowing what was going on, so my hack uptime was rarely more than 4 to 5 hours or so, and now it´s usually on for days straight, but so it was before the PS trial install and i can't remember the GPU being stuck as it is now.

 

I´m going to report back to this thread if i manage to make the time to go back to my previous installation and it works.

 

Bye!



#11
chevalier433

chevalier433

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

This issue happens with specific apps as i remember for me: VLC,Aperture,Transimission,Adobe CS6 Applications.I running vanilla myself i removed my hack.kext and my hack extra folder i only installed some drivers from multibieast for my esata raid external drive,trim support,usb3,network and chameleon bootloader with ML everything work out of the box same thing with MAV i only have this drive me nuts issue even my overclock to 4.5 and audiophile 2496 work flawless.



#12
yokonunz

yokonunz

    InsanelyMac Protégé

  • Members
  • Pip
  • 42 posts

Too much variables to debug... Apple needs to solve by it's self.. 

 

 

Does this affects real Macs?? I think so...



#13
ksaad

ksaad

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts

 

I'm having no gpu power management issues with my GTX560ti after editing the AGPM kext.  Before the edit it would get stuck in state 0 after sleep.  It was the exact same way in mountain lion too.

 

Here are my settings for iMac11,3.  If you're using a macpro profile then the control-id needs to be 18.  

<key>iMac11,3</key>
<dict>
<key>Vendor10deDevice1200</key>
<dict>
<key>Heuristic</key>
<dict>
<key>ID</key>
<integer>0</integer>
<key>IdleInterval</key>
<integer>250</integer>
<key>SensorOption</key>
<integer>1</integer>
<key>SensorSampleRate</key>
<integer>4</integer>
<key>TargetCount</key>
<integer>5</integer>
<key>Threshold_High</key>
<array>
<integer>55</integer>
<integer>40</integer>
<integer>60</integer>
<integer>100</integer>
</array>
<key>Threshold_Low</key>
<array>
<integer>0</integer>
<integer>75</integer>
<integer>90</integer>
<integer>100</integer>
</array>
</dict>
<key>LogControl</key>
<integer>1</integer>
<key>control-id</key>
<integer>17</integer>
</dict>
</dict>

Couldn't thank you enough for sharing such a straightforward solution for my 560Ti. I've been suffering slightly annoying performance levels playing Diablo III. And it was the only reason that made me boot into Windows. Thanks a lot, man.



#14
joseracer

joseracer

    InsanelyMac Protégé

  • Donators
  • 7 posts

Ok guys, just a brief (but intense) testing, on retail for about 30 minutes or so, opened photoshop trial, parallels windows VM, Maps, itunes, messed with Spaces fast switching, loved off and reloged in, etc etc. all of the stuff that under Mavericks GM managed to get my GF 760 GTX stuck at 979mhz every single time, and it is scaling back to 135mhz every single time, no problems spotted so far, hope this is permanent, but need to go for longer system uptime to be 100% sure, going to report back here tomorrow after a good night of sleep.

 

Bye!



#15
chevalier433

chevalier433

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

Hey dude take your time and if this final tell me about your configuration .



#16
chevalier433

chevalier433

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

Mavericks is officially out and we are stuck with this {censored} problem



#17
yokonunz

yokonunz

    InsanelyMac Protégé

  • Members
  • Pip
  • 42 posts

Yes. This still a bug on the official release.

 

Mavericks = power efficency?? Yes SURE! +10 degrees of GPU!



#18
joseracer

joseracer

    InsanelyMac Protégé

  • Donators
  • 7 posts

@ chevalier: updating here, after system sleep and wawe up clocks were stepping back to 135mhz again with Full screen youtube 1080p videos, Photoshop CS6, etc etc and then I reread your post and launched transmission as my final test to post back, and that one busted it, stuck at 979mhz now  :( . Seems to me that it´s  something that needs to be fixed at the .app end of thing ( just a small mavericks compatibility upgrade patch maybe? ) , and not Mavericks own fault anyways, yet on the other hand maybe Nvidia web drivers help fixing this.



#19
kokopellix

kokopellix

    InsanelyMac Protégé

  • Members
  • Pip
  • 10 posts
  • Gender:Male

..it really depends on the apps you´re running, same problems here.

Any Solution? Except don´t use the apps.



#20
Riley Freeman

Riley Freeman

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 717 posts
  • Gender:Male
  • Location:The Streets

I haven't tried the final 10.9 release on my Z68 because I read that the Kepler PM is still broken.

 

On my X79 with GT210 I have a AGPM edit to kick the card up from the lowest power state on boot. In 10.6.8 this leaves it running at 405MHz core, 810MHz shaders. However in 10.9 the core and shaders both run at 405MHz. Removing the LegacyAGPM shows both core and shader clocks running at similar speeds when stepping up and down.







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   Web hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy