Jump to content

OpenCL fix for non-GF100/GF110 cards (aka CC/SM 2.1+)

cmf

By cmf,
in nVidia

 Share
138 posts in this topic

Recommended Posts

tamorgen
tamorgen
Posted
Posted

@cmf,

I did the edits to the GeForceGLDriver and

libclh.dylib. From you description, it sounds like I DO NOT need to do the

echo

"export CL_ENABLE_SM2_DEVICE=1"

>>

~/.

profile, correct?

 

Also, are you getting even remotely the same benchmarks as you did in 10.7.2?

I've done all the correct manual edits to AGPM.kext, NVDAGF100Hal, and GeForceGLDriver, but after the update to 10.7.3, my score dropped from 45.22 to 35.67. My Luxmark 1.0 Score dropped from 7115 to 4550. Also, with LuxMark 2.0, it does not show my clock speed (it actually shows 0 MHz), and I get a whopping 133 score for the Room Scene.

 

I know it's comparing apples and oranges (or Apples & Windows), but my GTX 570 HD gets a 55.70 Cinebench score in Win 7 x64. 45 wasn't great, but it was at least in the ballpark. 35 is barely above half of the Windows score.

Link to comment
Share on other sites
cmf
cmf
Posted
  • Author
Posted

@cmf,

I did the edits to the GeForceGLDriver and

libclh.dylib. From you description, it sounds like I DO NOT need to do the

echo

"export CL_ENABLE_SM2_DEVICE=1"

>>

~/.

profile, correct?

yep, not necessary for now.

 

Also, are you getting even remotely the same benchmarks as you did in 10.7.2?

I've done all the correct manual edits to AGPM.kext, NVDAGF100Hal, and GeForceGLDriver, but after the update to 10.7.3, my score dropped from 45.22 to 35.67. My Luxmark 1.0 Score dropped from 7115 to 4550. Also, with LuxMark 2.0, it does not show my clock speed (it actually shows 0 MHz), and I get a whopping 133 score for the Room Scene.

 

I know it's comparing apples and oranges (or Apples & Windows), but my GTX 570 HD gets a 55.70 Cinebench score in Win 7 x64. 45 wasn't great, but it was at least in the ballpark. 35 is barely above half of the Windows score.

uhm, hard to say, at least for the opencl part. i'd say it's about the same and depending on what you're doing apples opencl implementation can be faster or slower than nvidias implementation.

for the opengl part, well, opengl performance on os x has always sucked and nvidias opengl drivers on windows/linux/... are far superior (including shader compiler optimizations at which apple should actually be good at ...).

and concerning benchmarks: they are not everything. things can easily go wrong on both sides. and i'd like to think that apple has better tests/indicators than some benchmark to tell if their implementations performance has dropped by 50% or whatever.

 

and correct clock speed (+cache sizes) display has sadly never worked for fermi gpus on 10.7.

Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

@cmf,

 

Thanks very much for the explanation. SO basically the echo command sets a user configuration file which I ran anyhow even though I did all the necessary hex edits for 10.7.3. SHould I remove that lined of script from the the user profile since its not needed or use leave things alone?

 

Thanks for your great thread!!!!

Link to comment
Share on other sites
cmf
cmf
Posted
  • Author
Posted

@cmf,

 

Thanks very much for the explanation. SO basically the echo command sets a user configuration file which I ran anyhow even though I did all the necessary hex edits for 10.7.3. SHould I remove that lined of script from the the user profile since its not needed or use leave things alone?

 

Thanks for your great thread!!!!

it doesn't hurt you if you keep it in and it might be beneficial (for a while) when 10.7.4 comes along ;)

Link to comment
Share on other sites
cmf
cmf
Posted
  • Author
Posted

small 10.8 update (with a disclaimer that i haven't tested anything of this yet):

apple did in fact shuffle some code around and the GeForceGLDriver code that had to be patched to get opencl working is now located in libclh.dylib. however, it seems like the patch is _not_ required any more (as does the other libclh.dylib patch, although it would still be valid), b/c either opencl is fully supported on fermi gpus now (most likely) or they moved the check someplace else that i haven't found yet.

 

some other interesting tidbits (for which i should probably start a new and highly speculative thread ;)):

* there are some references to opengl 4 and opengl es 2 support (since i couldn't test it on my hackintosh yet, i'm not sure if an opengl 4 context can be created ... i however failed to create an opengl 3.3 context on my oldish mbp, which could either mean opengl 3.3 won't be supported at all or apple is still working on it - hoping for the latter and full opengl 4.0+ support of course)

* there are some very interesting kepler related functions/strings in libclh and geforcegldriver (which could mean three things: 1) those are simply remains of nvidias driver code, 2) apple is heavily testing kepler gpus, but nothing is certain yet, 3) next-gen mbps will indeed have a kepler gpu ;)))

* gl drivers are based on R295 which is the most current nvidia driver version for windows/linux/etc. (hoping for better performance and stability)

* opencl version is still 1.1

Link to comment
Share on other sites
  • 2 months later...
cmf
cmf
Posted
  • Author
Posted

patch /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDriver does not work for ML DP3.

any ideas?

GeForceGLDriver doesn't need to be patched with 10.8 any more.

libclh.dylib however does (if you don't have gf100/gf110 card) and the fix mentioned in the first post still works.

 

 

and ftr: dp3 and dp3 update 1 were kinda borked. dp3 update 2 seems to have fixed everything and works really nice so far :)

 

edit: interestingly, the size of libclh.dylib has increased by 2 mb in dp3. since there is no opencl 1.2 support for nvidia cards yet, i'm guessing kepler support (there are lots of kepler functions in there ...).

  • Like 1
Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

@cmf,

 

 

Do we need to hex patch the GeoForceGLDriver binary file after 10.7.4 update? I see you do not need to do it for 10.8 is why I ask.

 

If we do not need to Hex edit it for 10.7.4 should we still run the script below?

 

 

 

echo "export CL_ENABLE_SM2_DEVICE=1" >> ~/.profile

 

 

I do understand we still need to patch libclh.dylib as noted in your first post that was edited recently making notes for 10.7.4 and 10.8.

Link to comment
Share on other sites
cmf
cmf
Posted
  • Author
Posted

Do we need to hex patch the GeoForceGLDriver binary file after 10.7.4 update? I see you do not need to do it for 10.8 is why I ask.

yes, the 10.7.2/10.7.3 fix still works.

 

If we do not need to Hex edit it for 10.7.4 should we still run the script below?

 

 

 

echo "export CL_ENABLE_SM2_DEVICE=1" >> ~/.profile

not necessarily. as long as the GeForceGLDriver binary fix is working, you don't need it.

Link to comment
Share on other sites
  • 4 weeks later...
FecsoMAC
FecsoMAC
Posted
Posted

I have Quadro 4000 MAC card on Lion 10.7.4. I installed the new nvidia driver(Retail_270.00.00f06.dmg), and I can't enable openCL.

I modified GeForceGLDriver and libclh.dylib. After restart I get slow motion in system.

 

I modified these files in apple driver, and everything was good, I could use OpenCL, but now with nvidia, it isn't working.

(In the new nvidia driver I didn't find in info.plist of NVDAGF100Hal.kext the IOPCIPrimaryMatch)

 

Any idea?

Thx

Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

Here it is. http://ge.tt/5RPfQGJ/v/0?c

 

It's the whole GeForceGLDriver.bundle just in case you didn't keep a backup of the original file before editing. The libclh.dylib is patched.

 

I also included the script I use to patch the file. I just double-click it and it puts a backup copy of libclh.dylib on my desktop and then patches the original file.

  • Like 1
Link to comment
Share on other sites
  • 4 weeks later...
subxero
subxero
Posted
Posted

That's just wrong...re-read the text and watch for "ML" "mountain lion" "ML GM" etc. ;)

 

From the Netkas site:

 

Enabling OpenCL on 10.7.5/mbp2012 drivers and ML GM

 

July 11th 2012 Posted to Apple,Lion,Mountain Lion,Nvidia

 

10.7.5/mbp2012 drivers run opencl on Fermi just fine out of box, no more need to enable it binpatching, but..

If you have a card with more than 2 gb of video memory, opencl suddenly gets disabled, wtf?

Here is why: (warning, assembler skills needed for the pic)

H7DPd.png

basicaly, if your video ram amount > 2GB by at least 1 byte, then you are screwed.

Funny Apple, they decided to control it themselves instead of putting check in the nvidia driver.

But, we can just disable the check and enjoy. End Quote!

 

Exactly what I said. This is a patch to enable cards that COULD normally have OpenCL support, but don't Because they have memory greater than 2GB. This is not a generic OpenCL patch.

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...