I've worked with a few guys who love, I repeat, LOVE to modify their OSX systems and build hackintoshes... ...By ripping out the basic driver for the OSX gfx, they were able to build their own that worked. CUDA included. Seems to be a problem with the OSX graphics driver. It's not CUDA being broken, it's more like the apple driver needs to be accessed first, and it doesn't allow other drivers access through the standard GPU. Some data gets sent out, according to the benchmarks attached to the cards themselves, but most of the data is being sent to the OSX standard GPU or CPU-GP, which won't accept data from other graphics cards, and for some reason, has trouble passing data back to them or through them, regardless of whether or not the display is attached to onboard or discrete cards. One of them built a simple driver and ran it, with cuda and 3 Geforce cards with 4gb each. The main graphics started out slow and lowres, but selecting the new driver ups the res and allows the system to use the CUDA. A simple IF statement did the trick. If another graphics card existed on the system, it checked for which was selected as the main. With the main being another card, it always turned dumped the driver and kext from the active, and switched to the new gfx card after login. Another replaced the osx gfx driver with the webdriver, named it the same, gave it the same identifiers for the kexts and driver package, and ran the system. It worked fine. He installed CUDA, then ran Premiere Pro trial, and put in a few plugins. It ran fine at 4k, and all the cards were available for use. Took a very short time to render an hours worth of video with AE and still imports. He did have to open AE and set the renderer before they would show up, but it worked fine. Once done, he closed AE and as far as I know never had to do that again. THis points to the problem being APPLE. They like to lock down every function that can be modified so you pay somebody to modify it in specific fashion, and they like to keep tabs on the mods so they can later claim it was all a part of their plan. Ever since Steve left us, they've gone non-art, or, as I like to say, ANTI-PROFESSIONAL. Their driver works by their benchmark and works "enough" for the masses. But when it comes to specific capabilities that put more wear and tear on a system, they are completely against it. Not far from their earlier stance on such things, but they used to allow higher end hardware to be utilized at its maximum or just short, which included any specific hardware function. Unfortunately, there was a shift in their rendering pipelines, mainly with retina displays and iris functions. They felt it was better, and was a slight speed boost without stressing the hardware, and spreads that stress across the system (got that from the hackintosh guys). They are moving away from part specific stress and toward methods that use "More of the entire machine", but anything that is specific to a single piece of hardware is being discouraged. Remove the Apple provided drivers and things speed back up. You can replace the mac drivers. IT's just not recommended. If they allowed open access to their driver builds, I'm sure they could be modified to allow for CUDA or any other GFX pipelining structure, but they've locked it all down, and basically gave you all the finger, over and over again saying "It means howdy stranger", obviously not oblivious to the fact that we all know what it really means.
So there it is. If you know how to replace the standard OSX driver (removing it completely and putting in something else that looks like it to the system), you might be able to get this all working. But most people don't know what or how to modify. Until they get a specific request that forces their hand (put a gun to some guys crotch and he'll figure out the meaning of life for you), they're not going to help. An added bonus... ...Permissions are a problem. Occasional kernel panic \ flat out crash is common. The files have to be WRITTEN by the right process, and have the correct standard system permissions. Very much like Windows "Trusted Installer" problems. I see a pattern forming here....
680
Replies
AdChoices