Nvidia Driver For Mac El Capitan
Original story: OS X El Capitan includes a new graphics API called Metal, the same API the company included in iOS 8 last year. Metal is roughly analogous to technologies like DirectX 12 and the not-quite-finalized Vulkan, designed to improve performance by reducing driver overhead.
Nvidia Driver For Mac El Capitan
In iOS 8 and iOS 9, comparing the Metal version of GFXBench to the OpenGL ES version shows off near-universal improvements in the high-level tests with more mixed results in the low-level tests. This was generally the case in OS X, but the wider variety of hardware meant a wider variety of test results. Many tests showed OpenGL holding even, or even beating Metal, though tests that were limited specifically by driver overhead showed some nice gains.
Updated 04/03/19: When I wrote this guide, NVidia drivers were still being released for the current version of macOS, 10.12-10.13. Sadly, Apple and NVidia relations have seemed to have come to a head. NVidia states that it is actively being blocked from releasing drivers for its GeForce cards for 10.14.x+. I highly recommend AMD video cards over NVidia as this seems unlikely to change. My GPU section of the Definitive Mac Pro Upgrade Guide contains more info on this spat, as well as current information. For posterity, I've left the upgrade guide below largely intact with a few minor edits to help reflect more current information.
It's no secret that there's always been a gaming performance gap, macOS sadly scores quite poorly compared to its Windows counterpart, so it's only fair to compare Mac to Mac or Windows to Windows and not Mac to Windows when considering the gains. Rather than benchmarking Windows, which isn't my daily driver, I'm more interested in how the GPU affects macOS. Below are my Uniengine v4 benchmarks vs. when I ran them against my 2008 Mac Pro. Despite the low marks when compared to running Uniengine in Windows, The Mac Pro 2010 is twice as fast by the benchmarks as my previous setup of a 2008 Mac Pro running a GeForce 760. One of the more fascinating things I learned when trying my hand at a Hackintosh was that the 3rd generation 3770k i7 wasn't quite enough to completely best the over-engineered Mac Pro despite having a faster bus / CPU, but merely matched it. If/when I have more time, I may swap the GPUs to see if the scores are as GPU dependent as they seem.
It's a good idea for the first boot to keep around an EFI card, as you may have to enable the web drivers. Also, I encountered the error of Mac NVidia Web Drivers fail to update or cannot remove Kext files" when updating my OS recently; you'll want to follow the instructions I posted to deinstall the drivers if this happens to you.
Ever since NVidia has shipped it's web drivers, gone are the sketchy days of flashing a 6970 and using a rom creator. Installing off-the-shelf GPUs has gone from tribal knowledge to common knowledge for the Mac Pro user since I wrote my "how to" guide for the 760. Ironically, it wasn't until Apple killed upgradability that the dream of off-the-shelf GPUs could be bought without the infamous Apple-tax. I debated even not calling this article a "how to". The downside is despite the EFI compatible ROMs preloaded on the 700+ GeForce cards; they're not EFI boot screen compatible on OSX sadly. The only game in town is macvidcards.com which according to all accounts on MacRumors is a legit source, but I find the idea of hoarding an EFI hack a little irksome. It's hard to complain too much as NVidia has quietly kept the Mac Pro and Hackintosh community happy, self-included. There's no specialized knowledge needed to upgrade your GPU or abnormal risks of a bad firmware flash. The only caveat is you'll want to keep an EFI card around for major OS updates.
Based on the driver software developers have found so far, it looks like support is there for graphics cards from Nvidia, Intel, and AMD. Here's the unofficial requirements based on netkas.org research:
If from this you discover that your full PCI-ID is [14e4:432b], then the following advice applies to you: Do not waste time on the b43 driver. I have been fiddling with it for weeks, and switching to broadcom-wl made all the problems go away. broadcom-wl might make your device names funky, but that's easily fixed with the udev rule documented on Broadcom Wireless.
As of kernel version 3.17.1-2, Broadcom Wireless driver most likely will not work (ERROR @wl_cfg80211_scan :WLC_SCAN error (-22)). The only option seems to be loading the b43 driver in PIO mode. To enable PIO mode, install driver by following the guide at wireless.wiki.kernel.org, then load the b43 kernel module with pio=1 and qos=0 parameters. To make this happen at boot, create b43-firmware.conf file in /etc/modprobe.d/ and add the following lines:
Although using PIO should be much slower than using DMA, I have not noticed any performance drop. Further testing showed repetitive occurrences of noticable performance drops. Mostly expressed as rapid decrease of transfer speed, sometimes even dropped connections. It also seems that b43 driver has issues operating at 5Ghz.
Consult Nouveau for general info on the driver. Works out of the box, performance however is not that great and your system will get quite hot when running nouveau.Will cause issues in electron based applications! Fix by adding --disable-gpu to the .shortcut!
Running the drivers in efi-mode requires setting some PCI registers before the kernel modules get loaded, preferably using a udev hook or GRUB script. You can also use a efi shell script in REFind as stated here. Otherwise, the screen just remains black when X starts. Follow these instructions in order to find the appropriate PCI device IDs for which to set the registers. This approach has been confirmed to work and is still being actively discussed inside the above mentioned thread. Updated EFI Shell boot method here. The latest NVIDIA drivers are no longer supported for this MacBook's GPU you will instead need to use these ones nvidia-340xx-dkmsAUR! Once installed create a config by running the command:
The NVIDIA binary driver does not support either simple display configuration switching or automatic monitor/display configuration on hotplug events, but this can be achieved by using autorandr and autorandr_launcher. Install autorandr first, and manually save each configuration as a profile. autorandr_launcher can then be compiled and configured as a systemctl service.autorandrautorandr_launcher
Older versions of XFCE power manager will break backlight key handling if you select "handle display brightness keys" after installing nvidia driver (even after re-adding "RegistryDwords" "EnableBrightnessControl=1" to /usr/share/X11/xorg.conf.d/10-nvidia-brightness.conf)
Thank you so much for this solution!!!! My late 2015 model froze on reboot from installing Epson Printer drivers. Endless loop and wouldnt start, this fixed it.I have actually done a similar thing before when my older MacBooks GPU kicked it, thankfully they had dual graphics chips so in a similar fashion in Verbose mode i had to create a new folder manually and move GPU drivers to disable the faulty GPU on startup. Just like this script move the bad kexts. Fantastic, thank you so much! I thought i was going to have to bake my motherboard in the oven again.. lol ( actually a legit way to reflow dead GPUs ) but thankfully this wasnt hardware related.
Hi, I have a question or a problem with my 2015 Macbook pro, ive had it since present but once i updated my mac too el capitan the computer quit on me and stopped working, once i reinstalled el capitan it booted perfectly the laptop, but then if i try too login it takes super long with a circle processing logo on the cursor and it takes forever without no login boot. hope you can help me on this one havnt got too use my laptop for 1month
I have exhausted several searches online but nothing works. My MacBook was operating fine prior; I have el capitan installed been using for months now. I launched a new app, that I recently installed , and I got a blue screen, with no other option but to power off.
Hi Justin I have got a Problem with 10.11.5 el capitan ,mac boots in safe mode when i use shift key then restarts in normal mode ,but after i shut down it wont boot again,its hard to get in safe boot cos not always it works ,is there an easy way to fix that kext files in normal mode? or using program script ? i can only put into sleep mode my mac ? please help ?
Trawling around the web looking for possibly suspect .kext files I stumbled across thes following .kext files reported by other people:VirtualboxEvernoteEltimaSyncJMicronATALivescribeSmartpenSSuddrivVideoglideAirparrotdriverLogitechHIDDdDevicesLogimgrdriverLogitechunifyingEPSONUSBPrintclass