maroder Posted January 29, 2014 Share Posted January 29, 2014 So far it's running well - love my GPU scaling up and down again. Also the small lag I had when using Quickview completely disappeared now. And if it does break something theres no harm done. If you make a backup from OpenCL you can easily revert to original. Link to comment Share on other sites More sharing options...
Hackmodford Posted January 29, 2014 Share Posted January 29, 2014 But like Gringo said. You can't use OpenCL at all now right? So it doesn't move it to the CPU but rather disables it entirely which is not a solution. Link to comment Share on other sites More sharing options...
zhuangzi23 Posted February 1, 2014 Share Posted February 1, 2014 The issued being discussed *still* exists in Beta (13C48). Haven't tried this workaround. Link to comment Share on other sites More sharing options...
frenchepaul Posted February 1, 2014 Share Posted February 1, 2014 But like Gringo said. You can't use OpenCL at all now right? So it doesn't move it to the CPU but rather disables it entirely which is not a solution. Depends on your usage really. I use my OSX partition for music production and media server. Really don't have a use for OpenCL. So in my case, that's a great compromise. But you're right, this is only a work around. Link to comment Share on other sites More sharing options...
Mull7965 Posted February 2, 2014 Share Posted February 2, 2014 But like Gringo said. You can't use OpenCL at all now right? So it doesn't move it to the CPU but rather disables it entirely which is not a solution. This is not how I understand the description of the patch. The author talks about three key function calls in the OpenCL framework: one to do basic initialisation, one to initialise CPU support, and a third call to initialise GPU support. Remember, OpenCL code can be run on either CPU or GPU. In some cases the CPU is faster, in other cases the GPU is. Either way, the patch simply stops the third call from happening. To me this implies that OS X will use the CPU for running all OpenCL code, because it doesn't think it has a GPU to run the code on. Link to comment Share on other sites More sharing options...
Hackmodford Posted February 2, 2014 Share Posted February 2, 2014 ...OS X will use the CPU for running all OpenCL code, because it doesn't think it has a GPU to run the code on. Can anyone confirm this is how it works? I just tried the it for the heck of it. It breaks preview for me. Link to comment Share on other sites More sharing options...
yokonunz Posted February 2, 2014 Share Posted February 2, 2014 Can anyone confirm this is how it works? I just tried the it for the heck of it. It breaks preview for me. Screen Shot 2014-02-02 at 11.03.56 AM.png You are doing something wrong in patching. Have you signed OpenCL? Do you have fixed permissions? Link to comment Share on other sites More sharing options...
Hackmodford Posted February 3, 2014 Share Posted February 3, 2014 I code signed it after making the change. I'm not aware of having fixed permissions. Should I have run a permission check afterwards? Link to comment Share on other sites More sharing options...
Hackmodford Posted February 3, 2014 Share Posted February 3, 2014 I tried it a second time. Same thing Update: Tried a third time created a new certificate, re codesigned, fixed permissions, restarted. Got the same issue Link to comment Share on other sites More sharing options...
Riley Freeman Posted February 3, 2014 Share Posted February 3, 2014 I decided to give this a try on 10.9.2 (13C44, haven't updated to 13C48 on this install yet). I got a "no identity found" error when I first tried to codesign it. I removed the quotes from the certificate name and then it worked. After patching and signing I just rebooted. Preview works fine, there's no corruption. I also took a closer look at Luxmark and saw that there's an option to run tests on just the CPU, so I did that: Update: I've updated to 13C48 now. Repatched the framework and everything is still running smooth. I can't see any lag or CPU hit from using the CPU for OpenCL at the system level (and with a i3 I'd notice if it was getting hit hard). I've launched the new apps like Maps and iBooks and everything seems fine. There's no OpenCL-related errors in the system log either. Obviously if you use anything OpenCL-intensive like Photoshop then it might not be a good idea switching to CPU rendering. But for me it's well worth it. I was expecting laggier performance but it's silky smooth. And I'd rather put a bit extra load onto my i3, knowing it will step down, than on my overclocked 670 which won't. Link to comment Share on other sites More sharing options...
Riley Freeman Posted February 3, 2014 Share Posted February 3, 2014 @ Hackmodford: Are you still running 10.91 there? I updated my 10.8.5 install to 10.9.1 and after patching I'm getting the same garbled display in Preview. Getting the update to 10.9.2 now so I'll patch that and see if it fixes things. Maybe it doesn't work right on 10.9.1 or maybe there's some cruft left from upgrading from 10.8.5. The other copy of 10.9.2 I tested this with earlier was a clean install. Actually, I don't think the patch worked because the card is locked at 1GHz again. Will update again once I've gotten 10.9.2 installed and patched. OK, running 13C48 now, patched and everything is working fine again. Something must have gone wrong with the patch on 10.9.1. Link to comment Share on other sites More sharing options...
Hackmodford Posted February 4, 2014 Share Posted February 4, 2014 @Riley Freeman Interesting... I too have upgraded from 10.8.5. Sure I've done a couple time machine restores. I've even done a fresh install then migrated from a time machine backup. Currently I'm back to my backup copy of openCL. I am going to try running a luxmark benchmark on the cpu instead of the gpu to see if I get any problems. Update 1: Wow! Apparently my CPU is no slouch when it comes to OpenCL Update 2: I get a similar score with the patch. And luxmark only sees my cpu as being available. So I wonder if it's more related to Preview than OpenCL? Maybe the smbios makes a difference? Link to comment Share on other sites More sharing options...
nomaj Posted February 4, 2014 Share Posted February 4, 2014 Update 2: I get a similar score with the patch. And luxmark only sees my cpu as being available. So I wonder if it's more related to Preview than OpenCL? Maybe the smbios makes a difference? I was wondering same thing... But Preview app calls QuickPreview framework - so maybe problem is there... maybe QP framework from ML will work??? Link to comment Share on other sites More sharing options...
Riley Freeman Posted February 4, 2014 Share Posted February 4, 2014 I updated to LuxMark 2.1 and got a score of 249. Bit better than my last one Although after some time I've noticed that my GPU is stuck at 1GHz again. Turns out it was a game that was getting it stuck (Modern Combat Domination). It must have been calling OpenCL it's own way. Ran a few other games and no problems. Link to comment Share on other sites More sharing options...
cahhee Posted February 6, 2014 Share Posted February 6, 2014 so for 10.9.2, replace 00F6C3057413 with 00F6C3007413 ? Link to comment Share on other sites More sharing options...
Riley Freeman Posted February 6, 2014 Share Posted February 6, 2014 Yep that's it. Link to comment Share on other sites More sharing options...
cahhee Posted February 8, 2014 Share Posted February 8, 2014 Thanks Riley its working - have not seen my gpu stay in its high clock. turbo boost up to 4 ghz Link to comment Share on other sites More sharing options...
yokonunz Posted February 12, 2014 Share Posted February 12, 2014 Good news for everyone here! NVIDIA is working on Web Drivers for 10.9.x wich fix all issues including OpenCL crash! This is the very beta version for 10.9.1 wich I don't suggest to install. http://us.download.nvidia.com/dMfCTEwWd5bvEIglG4b8ya6U4erhZeeC/WebDriver-331.01.01b07.pkg I hope they will release a stable version as soon 10.9.2 will be released!!! Urray! :) 1 Link to comment Share on other sites More sharing options...
Riley Freeman Posted February 12, 2014 Share Posted February 12, 2014 I hope so too. That beta still doesn't fix the power management bug. Link to comment Share on other sites More sharing options...
Melvin.FoX Posted February 12, 2014 Share Posted February 12, 2014 Hi guys! I'm crawling in a matter of configuring Hackintosh but I had the same issue and accidentally resolved it but updating HWSensors :C After almost everything configured properly I had to use [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] one more time and installed FakeSMC along with all the plugins and monitors and after booting I got 1.02 GHz whole the time. But I updated, as before HWSensors to 6.0.1082 http://sourceforge.net/projects/hwsensors/ and after update and running Unigine Heaven my GPU clock gets down to 324 MHz. I know that this sounds stupid but just try it Link to comment Share on other sites More sharing options...
Hackmodford Posted February 12, 2014 Share Posted February 12, 2014 So you're saying with version 6.0.1082 of FakeSMC you do not have any issues? Can you post the FakeSMC version? You can find this in S/L/E/FakeSMC.kext and check the info.plist inside for the version number. Link to comment Share on other sites More sharing options...
Melvin.FoX Posted February 12, 2014 Share Posted February 12, 2014 info.plist shows me 5.3.82 so it cames from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] that's weird but here are some screenshots with running Heaven and after (it's in my native language but I think you will know what's what ): Without HWSensors 6.0.1082 I had 1.02 GHz just after boot. Link to comment Share on other sites More sharing options...
Hackmodford Posted February 12, 2014 Share Posted February 12, 2014 To summarize FakeSMC 6.0.1082: GPU clocks down FakeSMC 5.3.82 : GPU stays up or is it the other way around? Also it is possible to have HWMonitor v6.0.1082 with FakeSMC v5.3.82 I've noticed that with the HWSensors installer you have to use customize and choose to install the latest version of FakeSMC and all the plugins if you want those updated. Otherwise it will only update HWMonitor. Link to comment Share on other sites More sharing options...
zhuangzi23 Posted February 12, 2014 Share Posted February 12, 2014 I'm running the brand-newest HMMonitor + FakeSMC along with Mavericks (13C53). Just now tried to open a .jpg in preview, GPU stuck at max frequencies. HWMonitor is not the solution we're looking for. Link to comment Share on other sites More sharing options...
Hackmodford Posted February 12, 2014 Share Posted February 12, 2014 I'm guessing he had the old version 5.3.82 of fakesmc with the newer 6.0.1082 version of HWMonitor. I'm also curious what version of gpu sensors he has. Maybe there's a special combination? Link to comment Share on other sites More sharing options...
Recommended Posts