Hi am upgrading my video card Radeon 4870 from my Mac Pro 2009 OSX 10.8.2 to a EVGA GTX 680 4GB and I wanted to know if my Final Cut Pro X and Adobe Premiere/Effects will run faster with this card. Any luck installing this card? Thanks
From what I know CUDA is only support in Adobe products, Final Cut Pro X uses GPU in some other manner.
I am not sure if OS X can use more than 2GB of VRAM anyway, other might fill me in, it might be possible if you're on Mountain Lion.
Read through the many other recent threads here on the GTX 6XX cards and CUDA/OpenCL. CUDA is easy to enable, OpenCL not so much so. Whether you will realize a benefit is wholly dependent upon the application and how well GPU acceleration is implemented. Be careful with the 680. Very few of the many different models have dual six pin connectors.
You'll need to siphon energy from somewhere else in the system to power the GTX680. 6-pin and 8-pin is really pushing it.
This one looks like it has a 6-pin and an 8-pin, but it has the converter I think included...
http://www.newegg.com/Product/Product.aspx?Item=N82E16814130798
----------
I also found this link which it says 10.8.2 natively supports GTX 6XX series
http://www.tonymacx86.com/graphics/...orce-gtx-680-4gb-kepler-hackintosh-guide.html
I just wanted to know if anybody out there has tried it?
am just curious between this and Radeon 5870 which one is better in video/graphics app?
I think this is the one I need
http://www.newegg.com/Product/Product.aspx?Item=N82E16814127695
2 6pin they said...
I use that card and it runs cool and is stable. It has 6 pins so fits right in. It is faster than my 5770 but I am not sure I am getting the best out of Opencl yet. Hoping for updated drivers at some point. I don't get the boot screen for what it's worth... It shows all 4gb in system profiler.
C
Unless you've successfully made the mods required for cards with more than 2 gb vram, you are not getting opencl at all.
how do you do it?
no OpenCL at all?
Unless you've successfully made the mods required for cards with more than 2 gb vram, you are not getting opencl at all.
Good question. I am still waiting on someone to write a clear, concise, coherent, explicit, preferably screenshot illustrated step by step guide to enabling OpenCL on GTX > 2 GB cards. Numerous users have bricked their Pros trying to follow the instructions out there as they are, and those that fail to get it working are the ones who ALWAYS get blamed (i.e., operator error).
Search around the forum here. You'll find lots of posts about it. Also over at netkas there are a few too.
Numerous users have bricked their Pros trying to follow the instructions out there
"Bricked their Pros" ????????
Hyperbole much?
Here's the thing, anytime you drag the OpenCl folder someplace, it makes a copy of it.
So you make 2 copies, one you mod. The mod doesn't work....YOU HOLD THE SHIFT KEY, DO A SAFE BOOT, AND PUT THE UNMOLESTED COPY BACK IN. Repair Permissions and reboot. Back to square one in under 5 minutes.
Hardly worthy of the phrase "Brick" which is typically used to describe an item that is RUINED FOR ALL TIME by a bad flash.
http://www.urbandictionary.com/define.php?term=bricked
"To render your computer useless, as useless as a brick. Usually the result of tampering with the insides and doing irreversible damage."
So a 5 minute reboot fix is worthy of this phrase?
For every person who can't make this work there are at least 20 who did it first time and never thought about it again it was so easy.
It is people convincing themselves that this is difficult that MAKES it difficult for them.
Using the work "brick" is the exact sort of stress that leads them to believe this.
It is simple and easy. Follow the instructions and move on.
"Bricked their Pros" ????????
Hyperbole much?
Here's the thing, anytime you drag the OpenCl folder someplace, it makes a copy of it.
So you make 2 copies, one you mod. The mod doesn't work....YOU HOLD THE SHIFT KEY, DO A SAFE BOOT, AND PUT THE UNMOLESTED COPY BACK IN. Repair Permissions and reboot. Back to square one in under 5 minutes.
Hardly worthy of the phrase "Brick" which is typically used to describe an item that is RUINED FOR ALL TIME by a bad flash.
http://www.urbandictionary.com/define.php?term=bricked
"To render your computer useless, as useless as a brick. Usually the result of tampering with the insides and doing irreversible damage."
So a 5 minute reboot fix is worthy of this phrase?
For every person who can't make this work there are at least 20 who did it first time and never thought about it again it was so easy.
It is people convincing themselves that this is difficult that MAKES it difficult for them.
Using the work "brick" is the exact sort of stress that leads them to believe this.
It is simple and easy. Follow the instructions and move on.
It is NOT "irreversible damage" it is a (self) corrupted system file. Mac users have been fixing this sort of thing since we picked our printers in the "Chooser". Hysteria isn't helpful.
Anytime you have a bad system file, you just boot from another OS install, System disk, or JUST HOLD THE SHIFT KEY and fix it by copying an unmolested folder back over the one you screwed up and running a repair permissions. 5 minute fix and you are back at square one. I can not BEGIN to understand how this is "irreversible damage".
I have written clear instructions before, i'll go search them out and paste them here.
If someone wants to draw some illustrations, feel free. AT most there are 4 or 5 people who have issues doing this. I believe most of them tried again and did it right. They got to work and never bothered to do a forum follow up saying it was all a silly typo they made. You are trying to make this sound like there are hundreds of people brought to a standstill, staring in frustrated angst at their screen. That is not the case.
Convincing yourself that it is difficult is exactly how to make it be that way.
https://forums.macrumors.com/posts/15792770/
Info regarding 10.7.5 GM
Hey, wanted to confirm that 10.7.5 GM still works great with the EFI cards and the non-Efi Nvidia cards.
OpenCl still requires same exact fix as before
1. Drag the entire OpenCl.framework folder onto your desktop, this will make a copy and leave original in frameworks folder
2. Dig down to the listed file (follow path in Netkas post below, it is your roadmap)
The file you wanna patch is /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
Just do these two simple patches you can do with any hex editor and you are good to go:
1) for 32-bit part:
find 3d 01 00 00 80 73 e7
replace with 3d 01 00 00 80 90 90
2) for 64-bit part, for lion
find ff 50 68 48 39 d8 73 e5
replace with ff 50 68 48 39 d8 90 90
for mountain lion
find ff 50 68 4c 39 e0 73 e7
replace with ff 50 68 4c 39 e0 90 90
P.S. doesnt applies to gtx670/gtx680, they have a different problem
3. Drag file to hexedit
4. do the fixes per the above Netkas post, it is CRUCIAL that you only REPLACE the searched for text, do NOT just add, the easy way to be sure is to check the file length before starting and before saving. If it has changed so much as a single byte, you have messed it up and need to do it again.
5. save file back where it was
6. drag the unbuggered original into a folder somewhere in case you screw up, thus making a 2nd copy
7. delete original from frameworks folder
8. drag the fixed one into the frameworks folder
9. this final step is crucial----RUN "REPAIR PERMISSIONS" from disk utility, if you don't see it mention that exact folder, run it again.
10. Reboot
11. Enjoy OpenCl goodness
12. Donate $5 to Netkas for making your life easier and thwarting Apple's evil goals of kneecapping decent cards