Jump to content

Graphics - No GPU Power Management


chevalier433
 Share

270 posts in this topic

Recommended Posts

It would be cool if there was a command we could use to restart the OpenCL framework... I'm also curious about the CPU usage.

 

This is interesting...

After opening preview my GPU clock gets locked at 1.08 GHZ

I then ran Luxmark and got this during the benchmark.

post-1106388-0-74948400-1390783198.png It actually ramped up to the Turbo state.

This is the benchmark score I got.

post-1106388-0-48986900-1390783227_thumb.png

After the benchmark it went back down to 1.08 GHZ

post-1106388-0-53558700-1390783246.png

Here is my lowest clock state.

post-1106388-0-35268200-1390783467.png

 

I get the same luxmark score when starting from a "non-stuck" state as I do from a "stuck" state.

Also the clock remains stuck at 1.08GHz after running luxmark. So I guess more confirmation it is OpenCL  -_-

 

In any case I guess my GPU is not stuck at its highest state because it can go a little higher...

Link to comment
Share on other sites

Mine (660 GTX) doesn't get stuck at its highest state either, it stays at the second highest I think (GPUSensors FakeSMC plugin says 992Mhz). Highest is 1.12GHz, so it does ramp down, just not all the way.

 

The clocks ramping up are clearly a consequence of OpenCL doing calculations on the GPU, but I still don't believe that OpenCL itself is to blame for the clocks not dropping again afterwards.

 

/EDIT

Screen Shot 2014-01-26 at 23.35.22.png

yay

  • Like 1
Link to comment
Share on other sites

It would be cool if there was a command we could use to restart the OpenCL framework... I'm also curious about the CPU usage.

 

This is interesting...

After opening preview my GPU clock gets locked at 1.08 GHZ

I then ran Luxmark and got this during the benchmark.

attachicon.gifScreen Shot 2014-01-26 at 7.36.32 PM.png It actually ramped up to the Turbo state.

This is the benchmark score I got.

attachicon.gifScreen Shot 2014-01-26 at 7.38.17 PM.png

After the benchmark it went back down to 1.08 GHZ

attachicon.gifScreen Shot 2014-01-26 at 7.38.23 PM.png

Here is my lowest clock state.

attachicon.gifScreen Shot 2014-01-26 at 7.43.39 PM.png

 

I get the same luxmark score when starting from a "non-stuck" state as I do from a "stuck" state.

Also the clock remains stuck at 1.08GHz after running luxmark. So I guess more confirmation it is OpenCL  -_-

 

In any case I guess my GPU is not stuck at its highest state because it can go a little higher...

 

With this patch LuxMark wont start.. because patch kills OpenCL ( read the first page of patch ).

 

What i find that for example Photoshop uses OpenCL - after patch PShop don't find OpenCL support at all - works with CPU.

 

This is not perfect solution... what i see nice about it - is that your gfx card wont be stuck at high frequency, less heat and power consumption.

For people who don't care about mentioned they just need to stop using quick-preview and instead Preview apk to use something like Xee or similar.

 

Hope that Apple or Nvidia will fix this annoying thing. I'm not sure that this bug can be found on real Mac-s.

Link to comment
Share on other sites

I just patched the framework in 10.8.5 and can confirm that neither LuxMark nor Oceanwave will run any benchmarks now that the GPU support is disabled.

 

It's a little easier on ML as there's no need to codesign the binary. I just used two terminal commands (one to backup and one to patch)

sudo cp /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL.bak
sudo perl -pi -e 's|\xE8\x52\xBE\x01\x00\xF6\xC3\x05\x74\x13|\xE8\x52\xBE\x01\x00\xF6\xC3\x00\x74\x13|' /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
  • Like 1
Link to comment
Share on other sites

No it isn't, look again!

 

If I look at both threads this is what I get with "Copy & Paste":

 

10.9.1: 00F6C3057413 to 00F6C3007413
10.9.2: 00F6C3057413 to 00F6C3007413
 
It's identical - but maybe I'm just blind ...  :geek:
Link to comment
Share on other sites

The original search string for 10.9 and 10.9.1 was E83DE10100F6C3057413.

 

I couldn't find this in 10.9.2 so nomaj said to search for 00F6C3057413 which is only half of the original string.

 

The second half of the string is the same for 10.8.5 and the various 10.9 builds. Only the first half varies.

  • Like 1
Link to comment
Share on other sites

The original search string for 10.9 and 10.9.1 was E83DE10100F6C3057413

 

I couldn't find this in 10.9.2 so nomaj said to search for 00F6C3057413 which is only half of the original string.

 

LOL Now I get it. Thank you for clearing things up  :)

Link to comment
Share on other sites

What is the exact string for 10.9.2 I cant get this to work at all :/

 

Ok maybe I search for 00F6C3057413 and replace it with 00F6C3007413 then save the file or sign it first then save it what is the exact steps for this patch.. 

 

Im having hard time to make it work.. either from not being able to repair permissions or booting back with missing-bluetooth-controller problem with my mavericks cleaned install…

 

btw i used myhack to make the usb but according to people i have to restart as soon my hack promote me to choose what extra folder kext i want to install or the bug my fix have changes IRQs of the installation etc..

 

maybe thats why I'm getting missing-bluetooth-controller problem.. maybe i need to complete the install.. make the usb install with another method..

 

anyway what is the exact steps for making this patch work with 10.9.2 thanks guys.. 

Link to comment
Share on other sites

sure its harmless but the problem is i cant boot to the desktop and the boot process hangs at that message..

 

that problem happens when i save the edited opencl file and boot back so the permission is change for opencl file and i have to repair the permission using the install usb/ Disk utility..

 

anyway what is the exact hex string for 10.9.2  ??

 

2. after i enter the string and replace it with what exactly and then save the file or not ??

 

3. should i signe the file and restart right away or repair permission before restarting..??

 

Dont know what exactly im doing wrong and everyone has already made the patch and done by now :P

 

maybe i first of all need a new clean install of mavericks with another method then myhack.. I cant get this patch to work what ever step I do or change..

Link to comment
Share on other sites

Totally agree. I thought OpenCL would just run on the CPU instead of the GPU and everything would be fine but if it breaks things then I'm not patching. So far we have only one person saying that though.

 

sure its harmless but the problem is i cant boot to the desktop and the boot process hangs at that message..

 

What I meant to say was, it might be the last message you see, but it's harmless and has nothing to do with why your hack hangs at that point.

Link to comment
Share on other sites

 Share

×
×
  • Create New...