Seems to have some problems. Encounter a "Driver encountered a problem" message while installing on Mac Pro 5,1, and continuing gets it 'working', but it's slow and there's some graphical glitchiness (not quite like using the OS X CPU driver, but similar).
I also have TWO Nvidia driver managers in my task bar, so that's weird. And CUDA is the latest (9.0.197 as of this writing), but it still claims that I need an update.
Would sure appreciate some insight...
Same here running on a patched 3.1 Mac Pro with GTX 1080. Windows do not update when moving or resizeing.
So i'm holding of updating my main boot drive.
I'm also waiting for the new Cuda driver. The latest version 9.0.197 is not compatible with High Sierra "Supported MAC OS X 10.12.x". High Sierra is 10.13. My MacPro 5.1 (with Geforce GTX 980Ti) works fine, but all the apps that require Cuda switched to OpenCL.
Installing this driver put my 5,1 mac pro into endless start up boot. Upon installing it did the same thing as above, 2 driver managers in top task bar. Unable to get system to boot properly, now doing a complete restore from last night and I guess will try a different approach. Make sure you have a backup before installing :)
You need an original card that came with your Mac first I had your same problem. I installed the gt 120 video card downloaded the drivers first then your Mac will boot up fine, take out the gt 120 and install the video card you want problem solved. I have a gtx 980ti and 64gb of ram on two 2010 Mac Pro 5.1. macvidcards thank you you saved my behind
I had the same issues as Dan. Got an error during installation, and after reboot the Finder/Dock is slow and glitchy. I opened the installer .pkg and checked that files had been installed in the correct place, but clearly something isn't right. The Nvidia Driver Manager preference pane on my system seems to be an old version, so perhaps that's the item that didn't get installed correctly. I tried to manually run the 'NVPrefPane.pkg' item I extracted from the full installer and it wouldn't run. CUDA is also complaining.
Updated my 2012 5,1 w/ Macvidcards flashed GTX980 and everything seems to work fine. No hiccups except the CUDA preferences is telling me there is an update required despite running the latest 9.0.197. Saw small bumps in Lexmark, Cinebench and Geekbench as well. So far so good.
Doubt it makes a difference, but I had first installed the new CUDA driver before the update to High Sierra. After I installed High Sierra I then went to the Nvidia preferences panel and checked for updates, then let it download and install the update itself from within system preferences -- rather than installing it myself from the .pkg manually.
I have a MacPro5,1 with NVIDIA GeForce GTX 980 4 GB and came across the same issue, however, in my case, I can't run Octane Renderer. I get an error message "There is no CUDA device which is supported by Octane Render.."
I had a similar issue with Iray for Cinema 4D and Mac OS 10.12 until the drivers got an update. I think we just have to wait and hope.
Tried it on my CMP 5,1 12-core for my flashed Titan X. Accepted the driver offered from the Nvidia Prefs pane. First reboot "stalled" on the grey apple screen with the thermometer barely creeping forward; after about an hour of nothing I did a hard power-down and restart. Endless boot looping ensued. Tried Single User mode with [sudo nvram boot-args="nv_disable=1"] switch but no love. Resored from last Time Machine backup and am running again using native OS X driver (not special).
I think Nvidia may have rushed and screwed the pooch. Hope they fix it soon.
All working with a GTX 1080 Ti here now. The trick I had is that Gatekeeper wants to block loading of the kernel extension. I got a pop-up message while installing. Once installation of the driver is complete, don't reboot - load System Preferences, head to Security and Privacy and click 'Allow' next to the 'NVIDIA Corporation' notification. Then, force-quit the installer and run it again. This time, no message from Gatekeeper. Reboot and the driver is spot on.
The CUDA driver v9.0.197 (installed using the same Gatekeeper method) does complain that an update is required, but it did that occasionally in the last version too, so I'm not going to worry about that.
In System Information the Metal status reports 'Supported, feature set OSX_GPUFamily1 v2'. I have no idea what that means; hopefully it's good.
I wasn't getting any warnings from GateKeeper so couldn't do this. According to the system profiler the GeForceWeb extension is being loaded and I have Metal v2 support, but performance is pretty bad.
Paul, can you see through the Dock or is it solid white?
The dock is solid white, not transparent as usual. I thought this meant the system was using the default drivers but these don't support the Titan X. Previously the system wouldn't boot unless I installed the Nvidia web drivers.
Yeah, you've got same problem I do.
Nvidia's got some 'splainin to do.
First install was a build up from the developer builds. 2nd time I started with fresh 365 build, then Web Driver.Same white dock. Same poor performance, yet not as poor as "no driver loaded"
I've submitted a support request to Nvidia. It was quite tricky because the graphics driver problems mean Safari can't render their website properly. I had to use the element inspector to find the submit button!
So, it appears that, at the very least, the CUDA drivers are broken - not, in my opinion, should be something that breaks the actual display drivers so badly - but Nvidia have promised better CUDA at a later date.
Fortunately, the actual firmware update on a 4,1>5,1 doesn't seem to have broken anything, so macOS Sierra chugs along quite beautifully.
Not that I expected any differently, but let's be honest - a firmware update for an eight-year-old machine that's already been hacked to make it think it's a seven-year-old machine is rolling the dice.
poor performance, non-transparent dock... after next restart: endless boot-cycle... how to fix that?
I think the worst part is that, with the change from HFS+ to APFS, reverting back to a previous OS is no longer a painless procedure.
I think I'll wait a month or two for the bugs to get squashed, then try again.
Just got this from Nvidia tech support:
Response By Email (Rajath) (09/29/2017 12:33 PM)
Thank you for contacting NVIDIA Customer Care.
Your case is being escalated to our L2 Support group. The technician from the L2 Support will review the case notes and may attempt to recreate the issue, find a solution, or a workaround if possible. As this process may take some time we ask that you be patient and a L2 tech will contact you as soon they can to assist or point you in the right direction. You will be updated through email.”
FYI on the driver on the Nvida download page about the Cuda driver.
This could be what’s causing the problem but I didn’t get any kind of alert in the security settings. Just a more vague ‘the installer had an error message’.
Very slow cinebench scores. I have a Mac Pro 5,1 12 core @ 3.46 ghz 64 gigs ram, Nvidia 980 TI
Cinebench OpenGL Windows 10 (85 fp/s)
Cinebench OpenGL Elcapitan 10.11.6 (58.15 fp/s)
Cinexench OpenGL High Sierrs 10.13 (24 fps)
Windows on High Sierra draw traces, unusable until you cliclk anywhere but that window on the screen, then it re-draws itself, and the Cuda 9.0 needs update?
Elcapitan still happy with Cuda 188.8.131.52
New driver please, glad High Sierra is on it's own personal 180 gig Intel SSD in the DVD Bay. El Capitan safe on a PCI flash Samsung 500 gig, with a CCC clone up on a 500 gig spin drive... no worries. no hurry to upgrade my whole system thats working perfect :)
Everyone should report the issues to NVIDIA tech support. The more information they have the quicker they can fix the drivers.
Hey, So, on the good news front I finally got HS Web Driver to work.
I reinstalled the driver after a PRAM reset.
I did briefly see 2 Nvidia icons in top right.
On bad news front, I have bricked an SSD (SATA int) that I was restarting after Nvidia Driver install. It was foirst one to not report the error, on reboot it is DEAD. Probably an APple APFS issue along with PRAM reset along with 10.13 along with WEbdriver. Don
't know who to pint finger at but at least the other drive is finally A-OK. The working one is PCIE SSD.
Thank you, Dave, this worked for me as well (thankfully *without* bricking my PCIe SSD boot drive).
I used the Nvidia Driver Manager in System Prefs to uninstall the old driver (CUDA Preferences Applet remained). Redownloaded the web driver from Nvidia, shut down the system (and unplugged it for a minute), restarted with Option-Command-p-r (PRAM reset) boot option, then ran the driver package install from the download folder.
No warnings from the installer or from High Sierra.
Restarted and... all is well! :)
Geekebench 4 OpenCL score went down (from 132526 to 130546) but CUDA score went up a little (from 139844 to 140301)
HTH and good luck everybody!
I can confirm this worked for me as well. Specifically following Thomas's process. Should note that the first time I threw the nvidia card back in I got a black screen, and wound up swapping back to my 4870 thinking I'd borked it. Didnt bother with a second PRAM reset on restart, and got OS right away, still with nvidia web drivers selected. Might just have been taking a really long time before. Swapped back to 1080 and tried again, and it came right up after a couple minutes. Full transparency, no tearing.
Everything seems to be running fine now. I seem to have accidentally thrown out my previous Heaven scores, but will give that a go in a bit too.
2009 4,1 flashed to 5,1
Sandisk SATA SSD
I installed the High Sierra update onto my 2011 Imac 27 which has a 2GB Nvidia GeForce GTX 765M which I transplanted from a Sager laptop. After I installed the Nvidia web drivers, I also get the Cuda Preferences message saying that an update is required. I deleted the preferences pane and downloaded the CUDA drivers from the Nvidia website (184.108.40.20606). I still get the same nagging message upon startup but everything else is running very smoothly including a translucent dock.
Uninstalling the web drivers, restarting with a PRAM reset, then re-installing the web drivers worked for me too. I had to replace the Titan X with an older card for this operation so I'd have something that could boot using the drivers included with Mac OS, but I afterwards I was able to put it back in place. CUDA is still complaining, but I remember this from previous upgrades. Hopefully the next CUDA update will sort it out.
Uninstalling the drivers, resetting PRAM, then re-installing will work for a Hackintosh, but you'll have to temporarily re-enable SIP.
Thats good news for some, but I'm not dealing with resetting PRAM then having to slightly disable SIP I have lots of software that will not work correctly with SIP on.
I'm still happy with El Capitan on my 2012 Mac Pro 12 core, 64 gigs of ram, Nvidia 980 TI, and a 500 gig PCI Samsung boot drive. As I said in last post, Cinebench preforms better in Windows 10 on my Mac Pro. Glad I am not a gamer, macOS is like 30 fps less on the OpenGL
I only had to re-enable SIP for the installation of the Nvidia web drivers. Once that was done I could disable SIP.
Just been told a CUDA update for Mac OS 10.13 will be out soon.
Thanks for that piece of news Paul. But I don't think SIP has anything to do with it. Seems it would be refused by macOS and not just get the "Seems to have some problems. Encounter a "Driver encountered a problem" message while installing on Mac Pro 5,1. I'm in no big hurry anyways, my mac smokes on El Capitan... I have the Refind boot loader because I run Windows 10 and varieties of Linux occasionally. After clicking on my usual choice "El Capitan" Both monitors are on and all booting activity finishes ready to rock in like 4-5 seconds... Even if I choose Windows 10, maybe 10-15 seconds as that ssd is in a drive bay. El Capitan is on a Samsuncg PCI Flash 500 gig.
I'll wait as I really do not need a desktop Siri, that why I skipped Sierra... My crappy Amazon Fire phone is all good just saying "OK Google" :)
If you could post updated instructions to disable the web drivers (so that one can the access the recovery mode) and then enable them (so that you can boot normally), that'd be much appreciated. Have managed to disable the driver, disable SIP but have been unable to re-enable the Nvidia driver under High Sierra. Thx so much & keep up the good work!
To disable SIP and install the Nvidia web drivers I did the following:
1 - Used the uninstall option from the Nvidia system preferences. Shut down.
2 - Started up using the recovery partition. (Hold down 'r' when starting up. You could also create a startup disk using the Mac OS 10.13 installer and a USB flash drive.)
3 - Launched terminal, re-enabled SIP.
4 - Restarted normally and re-installed the Nvidia web drivers. This time I got the expected security alert and was able to allow loading of the appropriate system extensions.
5 - Restarted with recovery partition.
6 - Launched terminal and disabled SIP.
7 - Restarted normally. Now running the Nvidia web drivers.
SIP was definitely the issue for me, but that's expected because I'm running Mac OS 10.13 on an unsupported Mac.
I'll give that a shot Paul after work... SIP is not a big deal, it is all the PRAM settings I chooses not to mess with because of the bootloader and my sound prefs, using toslink digiital out to my Denon receiver with a pair of B&W speakers.... I can rock the neighborhood.
I too have an unsupported 2007 Mac Pro hacked to run 10.11.6 like a champ... Just a extra render box for stuff like Cinema 4d network Render helper. Not messing with that box at all, my emergency backup. Was a quad core 2.66 ghz xeon, For $50.00 I bought 2 qaud core 3.0 ghz xeons from eBay. The surgery took about 45 minutes, and the machine hums at more than twice the GeekBench score than machine when new. So twin towers side by side :)
Don't update to the 10.13 Supplemental Update!
It will bork your machine, mine wouldn't start at all unless I put in my old Mac edition GTX 285. It's appears to be an incompatibility with the Nvidia web driver but it's beyond a normal incompatibility where it will still start up w/ the default OS X driver -- in this case it's a boot loop.
John is right, I saw that they had the new display driver for the Supplemental Update... Borked High Sierra as he said, endless boot loop. Fortunately I have El Capitan on it's own PCI SSD, I just held the option key after forced shit-down and rebooted to 10.11.6 Then I borked High Sierra, Disk Utility... gone for a long time. Centos 7.2 liked that HD Intel 180 gig SSD to keep Windows 10 Enterprise company beside it :)
I DID NOT have to remove the 980 TI
See the blog post above this.
Easy way to do the supplemental update