I know that many of you are excited about El Cap coming in 2 days. I need to remind you that all newer Nvidia cards require delicate planning whenever there is an OS update.
The good news is that our EFI cards make this easier then for the poor souls with unflashed cards. They end up staring at a black screen as their Mac endlessly reboots.
So, if you have one of the following cards you need to think before hitting that "update" button:
GTX Titan Black
All of those cards have been left out of OS X since 10.8.5. Will Apple ever include drivers for them? Hard to say, but until the iPad Pro comes with a 980, maybe not.
So, again, please come here or read at Macrumours Mac Pro section or Netkas.org to see what the news is on the 30th. We are on the West Coast so lunchtime for you may be breakfast for us, we may not have the first posts.
Currently the GM build has numbers that match the linked driver from our driver page. If Apple changes the build number for Final Release, expect Nvidia to have an update. Unfortunately, if Apple springs the change on Nvidia at the last moment, it may take a day or two to be issued. If there is a work around, we will post it here. It is also possible that Apple will keep the GM build version and all will be well. The current Nvidia driver has a "b" in the version number, that means "Beta". Expect a release with an "F" in the Final one.
Again, please think before you hit "update", if there isn't an Nvidia driver yet you will be really mad at yourself.
UPDATE: Not only was the Beta driver compatible with 15A284, but Nvidia has already issued a Final driver for 10.11 Build 15A284. Please see the driver download page.
For those running Yosemite on an EFI card from us that requires Web Drivers, you will need to do the nv_disable step to install El Capitan, then turn the drivers back on via terminal. See the instructions here:
Please note that the nv_disable terminal command does not have to be done from single user mode, it can be done whilst running a previous version of OS X before you run the installer.
We are proud to offer the only video cards that give a true 4K SST boot screen on the cMP. I have noticed that if you are using the Dell UP2715K 5K display that in order to see the 4K boot screen you need to pay attention to the order of the DP plugs.
On the 980Ti and Titan-X, the Main 5K cable goes to the bottom port, with the secondary cable going to the next one up.
On the 970 and 980 I have found that the reverse is true. You need to put the secondary cable on bottom port with the main cable on next port up.
To be clear, the "bottom" port to me is the one on right if you are looking at the card installed in Mac Pro. So, the one closest to the Logicboard. Another way to think of this is if you stood the card up with the gold PCIE fingers pointing down, the bottom port would be...on the bottom.
Some oddball cards may have these reversed, so if you aren't seeing boot screens on your 5K display, try switching around until you do.
Happy Fall to everyone.
I would like to share a quick little fix that may help some of you. Currently, if you do a PRAM/NVRAM reset you will be booted from the OS X Default Driver, which will cause issues with Maxwell cards.
There is a way to keep the Web Drivers as the default driver, even after NVRAM resets.
1. Go to /Library/Preferences/SystemConfiguration/com.apple.Boot.plist (make a backup copy)
2. Open this file in X-Code or a plist or text editor. You will see a line that says "Kernel Flags", under this will be <string></string>
3. Insert "nvda_drv=1" between them, end result being <string>nvda_drv=1</string>
5. Repair Permissions
To test, turn off the Nvidia Web Driver via the Preference Pane and reboot. The preference pane and the Nvidia Icon will say that you are using OS X Default Driver, but if you look in the "extensions" section of System Profiler you will see that the Web Drivers are loaded.
Note: if you don't have X-Code and use a text editor you may have issues saving or replacing the file, I did it in X-Code and it was very easy.
Anyhow, with this little fix you don't have to worry about accidentally turning off the driver. This will also make it possible to create a disc image that contains a working web driver that therefore does NOT require an initial boot to set the NVRAM setting.
Do note that I doubt very much that this will "force" the web driver to load and let you use it in an "unauthorized" OS.
BTW, to disable SIP you need to use Recovery partition, open Terminal and type "csrutil disable"