I have now installed driver for gtx 1060 on high sierra 10.13.1 (17B48) and everything works fine. But I do not have the option to change the resolution, hanging in 1080P and there are no options for changing the resolution in display system preferences. Dec 20, 2017 - The trick to building CUDA apps on macOS 10.13 is having Xcode 8.2. I have a fork of Tensorflow in branch v1-4-1-high-sierra-cuda with the.
Good evening. It is not an issue with the CUDA drivers. It is an issue with the embedded Apple nVidia drivers which are faulty. Please use the latest nVidia web drivers from nvidia.com. It will also eliminate the issue of slow UI in High Sierra. I tested this setup and it worked perfectly on a Late 2013 15' MacbookPro. Please be advised that you must upgrade the nVidia drivers every time you upgrade the OS.
Every release of nVidia web drivers works ONLY with the macOS version it was designed for. MacOS 10.13.1 macOS 10.13.0 By the way, I tested the nVidia web drivers on a mid 2010 13' MacbookPro with GeForce 320M and it worked like a charm. Of course, no CUDA support for this video card.
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. 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='nvdisable=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 OSXGPUFamily1 v2'.
I have no idea what that means; hopefully it's good. 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,15,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. Just got this from Nvidia tech support: “ Response By Email (Rajath) ( 12:33 PM) Hello Paul, 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.”. 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 8.0.9.0 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 hurry to upgrade my whole system thats working perfect:). 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. 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. Specs: 2009 4,1 flashed to 5,1 GTX 1080 Sandisk SATA SSD. 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':). To disable SIP and install the Nvidia web drivers I did the following: 1 - Used the uninstall option from the Nvidia system preferences. 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:).