Why? If it's because you want to roll back to HFS+. You can achieve that via clones, no need to perform any OS re-installation.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
{WARNING} 10.13.3 update may REQUIRE SIP enabled with Nvidia web driver
- Thread starter h9826790
- Start date
- Sort by reaction score
Why? If it's because you want to roll back to HFS+. You can achieve that via clones, no need to perform any OS re-installation.
For SIP enable or HFS+? Easier solutions for both. If HFS+, use Carbon Copy Cloner and make bootable clone on an HFS+ formatted drive.
As mentioned in a previous post, my issue pertains to Dosdude's SIP Disabler script. In order to enable SIP and install the most recent NVIDIA Web Driver, I will need to manually patch and reinstall High Sierra without using Dosdude's utility.
This is not a problem as such; it is simply bothersome.
This is not a problem as such; it is simply bothersome.
You actually can ENABLE SIP to install the web drivers w/ the Dosdude1 HS patcher -- I did it today. Whomever can share these steps wherever to let others know you can continue OS & Nvidia web driver updates if your machine is patched w/ Dosdude1:
1. With SIP initially DISABLED update your OS as per usual.
2. You must have access to your recovery partition in order to access terminal & ENABLE SIP. If you don't have the partition, boot from Dosdude1's HS Patcher bootable USB, access terminal, and use "csrutil enable" to ENABLE SIP. Instructions to create the bootable USB are here.
3. Restart from recovery holding SHIFT to enter safe mode. Install the corresponding Nvidia web drivers in safe mode.
4. Restart again into the recovery partition and now DISABLE SIP.
5. Restart normally into macOS.
6. At this point, I find that enabling SIP has killed the patcher's ability to allow you to install other updates thru App Store. Download Dosdude1's "Software Update Patch" (swupatch.sh.zip) manually at the bottom of the page here and unzip it. Open terminal, type "sh" plus a space, drag the file into terminal, hit enter, and follow the prompts. It'll restore normal updating ability.
This should be the new updating method to follow for anyone with a patched system.
Thanks for the sharing.
Does this method require a Mac EFI / OOTB graphic card?
I did it with a flashed EFI card. Although I'm uncertain about non-EFI cards, it can probably be done manually as per usual with these cards, but will be cumbersome with all the restarts. You'd probably have to remotely use the command line to manually boot in/out of recovery & safe mode. Alternately, if you keep one of the original Mac-supported cards on hand (recommended), it'd be easier to just pop that in to complete the updates. I keep my original GT 120 on hand just in case.
After installing the latest 10.13.3 Supplemental update and the latest Nvidia 387.10.10.10.25.158 web driver. My MacPro will not start up with the web driver active. I had the same issue last week with 10.13.3 plain and version version—-.156 web driver but was able to get it to work after reinstalling the driver several times. I spent about 1 hour chatting with NVIDIA tech yesterday and they think my (mac edition) GTX 680 is bad and needs replacing. It works fine with MAC OS build in drivers do I need the NVIDA stuff at all? Is my GPU even replaceable?? is my GTX 680 defective as tech support says? even thought it works with out Nvidia driver and passes the Tech Tools video test. See image.
And yes I tried reinstalling the drivers with SIP on and off. It just does not work.
And yes I tried reinstalling the drivers with SIP on and off. It just does not work.
Attachments
Last edited:
SIP needs to be enabled for the driver. Enable SIP. Shut down the machine. Start the machine, confirm SIP is enabled. Install the driver. Also check gatekeeper.
Just to confirm - is your GTX 680 an official Mac version (EVGA Mac Edition with Mac labels), or was it flashed to become a Mac version? Do you use CUDA at all?
Is your system drive formatted APFS or HFS+? Is it the same 840 EVO SSD in your signature? Are you booting on the Velocity Solo X2, or is that a media drive? Do you happen to know if the Velocity Solo X2 had a firmware upgrade?
Try removing the CalDigit PCIe card and reinstall to see if that helps. Believe that card required drivers vs. native?
Just to confirm - is your GTX 680 an official Mac version (EVGA Mac Edition with Mac labels), or was it flashed to become a Mac version? Do you use CUDA at all?
Is your system drive formatted APFS or HFS+? Is it the same 840 EVO SSD in your signature? Are you booting on the Velocity Solo X2, or is that a media drive? Do you happen to know if the Velocity Solo X2 had a firmware upgrade?
Try removing the CalDigit PCIe card and reinstall to see if that helps. Believe that card required drivers vs. native?
1. It’s an official EVGA Mac Edition GTX 680
2. System drive is the SSD on the velocity pci card. Yes the Velocity Solo was updated does not require drivers.
Note: I may have to pull solo solo and install the SSD in the drive bay. Used to have to do this for every update.
I forgot the installers lose there way when you put things where they don’t belong.
Thanks will try.
2. System drive is the SSD on the velocity pci card. Yes the Velocity Solo was updated does not require drivers.
Note: I may have to pull solo solo and install the SSD in the drive bay. Used to have to do this for every update.
I forgot the installers lose there way when you put things where they don’t belong.
Thanks will try.
Dear bsbeamer,
None of the above worked. BUT IT IS FIXED The answer: after all the restarts the one thing that fixed the problem is to set the LED Cinema Display system preference to (•) Default for Display. I am now up and running with my EVGA GTX 680 mac edition GPU is up and running.
Cuda is also loaded but I am not sure if I need it since I don't play games or edit movies.
Just the native system preferences. I was thinking of getting a Radeon RX 580 as a replacement but I have to say the information on the power connection and all the different flavors and brands is confusing. May be just wasting money on old tech.
I agree.
My mac is not a hobby I use my IPad to browse the web, my mac pro has to earn it's keep. I can't justify spending more money on equipment than I can bill. Also when a paying customer is waiting for a project they don't want to here about your Tech issues. This is not government work.
On a side note: I suspect this is why Apple likes closed boxes that consumers can't mess with. The apple care lines would be backed up for weeks with 3rd party tech issues.
As explained earlier, this was not possible under my installation.
I have since manually modified and reinstalled High Sierra.
Here's an odd one for you. We have two Mac Pro's, one a 5,1-flashed 2009 and the other a real 5,1 2010. SIP was disabled on both. On the 2009, I've had no trouble updating to 10.13.3 and the .158 NVidia drivers. On the 2010, I was getting the black screen with cursor, or a grey screen with a constant stopwatch icon.
I enabled SIP, deleted and reinstalled the NVidia drivers, and now the new card would work -- mostly. Games would recognize it and run, but things like the Finder were dog slow -- windows would leave artifacts and scrolling was painful.
Turned SIP off again, and now everything works great.
Remember, this is on a true Mac Pro, not a Hackintosh.
On my other Mac Pro, SIP has been disabled the whole time and everything is working properly.
No clue... but I guess it could be worse than if I have to enable/disable SIP every time I install a new version of the driver.
[RICHR]
I enabled SIP, deleted and reinstalled the NVidia drivers, and now the new card would work -- mostly. Games would recognize it and run, but things like the Finder were dog slow -- windows would leave artifacts and scrolling was painful.
Turned SIP off again, and now everything works great.
Remember, this is on a true Mac Pro, not a Hackintosh.
On my other Mac Pro, SIP has been disabled the whole time and everything is working properly.
No clue... but I guess it could be worse than if I have to enable/disable SIP every time I install a new version of the driver.
[RICHR]
Seems like a bug in the installer. They could probably fix it eventually. Their driver itself works without SIP.
This is an old post, but just to clarify...
All drivers in 10.13 from all developers must be authorized in this way. The messaging is the same for everyone. Gatekeeper settings are irrelevant. Unidentified developers will actually be completely blocked from installing extensions at all with SIP enabled.
This is an old post, but just to clarify...
All drivers in 10.13 from all developers must be authorized in this way. The messaging is the same for everyone. Gatekeeper settings are irrelevant. Unidentified developers will actually be completely blocked from installing extensions at all with SIP enabled.
NVIDIA themselves have confirmed that SIP is required to be enabled during the install. This was a change of practice after one of the 10.13.2 security updates for Meltdown/Spectre and will be this way moving forward. This change impacts all legitimate 2010-2012 MacPro 5,1 machines that have not messed around with their device IDs. These machines are not officially EOL'd.
If you have a 2008 3,1 or 2009 4,1 that was flashed/upgraded/hacked/changed to ID as a 5,1 or as an iMac/iMac Pro there is no official support or documentation being provided by NVIDIA. The nature of changing the machine ID to something else is basically "breaking" some of the built-in security within macOS to get around the limitations of installing 10.13. Would not be shocked that SIP being disabled on those machines makes a lot of difference. As mentioned by others, these machines are getting closer to Hackintosh builds and would be a good idea to keep an eye on those forums.
If you have a 2008 3,1 or 2009 4,1 that was flashed/upgraded/hacked/changed to ID as a 5,1 or as an iMac/iMac Pro there is no official support or documentation being provided by NVIDIA. The nature of changing the machine ID to something else is basically "breaking" some of the built-in security within macOS to get around the limitations of installing 10.13. Would not be shocked that SIP being disabled on those machines makes a lot of difference. As mentioned by others, these machines are getting closer to Hackintosh builds and would be a good idea to keep an eye on those forums.
In case 4,1 flashed to 5,1. The cMP will be natively supported MacOS 10.13. And can keep SIP enabled.
My concern is that I need to enable SIP to *install* the update, but disable it again to actually be able to RUN anything. That seems counterintuitive, especially for a real 5,1 machine.
Note that NVidia does support 3,1 and 4,1 machines with these drivers, so there is no real reason for them not to work on a flashed 4,1 given the hardware is absolutely identical (except possibly for a thermal sensor).
[RICHR]
Interesting, Nvidia web driver 387.10.10.10.25.158 really stated that both 4,1 and 3,1 are supported. But these two Mac do not officially supported for 10.13.3
It's the way the driver needs to be installed, contact NVIDIA if you have a problem with it. Their support is great, but this change is because of Apple. The fixes for Spectre and Meltdown required this change.
Personally happy they are continuing to update drivers for Mac users. This is a rather small issue once you know what needs to be done to install. When you have no indication that SIP needs to be enabled the first time and the install is halted and machine won't boot - that's more alarming.
I don't like requiring SIP to be disabled at all. As for contacting NVidia support, unless you know of a specific Mac person to talk to, it's worse than useless -- I am constantly told that they either don't support Macs, or only support specific models, and they can't help me. Last time I actually had to link their online blogs and documentation PROVING that they in fact do support the Mac before someone would even answer a question for me. I'm happy that I can use a GeForce instead of Radeon, but I sure hope their support improves.
[RICHR]
Like it or not, SIP is now what is required for the install. Complain to Apple about the way they implemented their "fixes" for Spectre and Meltdown - that is what caused this change. We're a bunch of users just trying to help out other users. Don't take your fight up with anyone here.
NVIDIA support has been pretty great for Mac in the past several years, especially if you have official Mac cards or Founders Edition products with NVIDIA branding. Personally have no complaints at all. If I could enable more video encoding/decoding through GPU/CUDA it would keep my machines running for several more years. Unfortunately, a lot of that has to do with software manufacturers.
NVIDIA support has been pretty great for Mac in the past several years, especially if you have official Mac cards or Founders Edition products with NVIDIA branding. Personally have no complaints at all. If I could enable more video encoding/decoding through GPU/CUDA it would keep my machines running for several more years. Unfortunately, a lot of that has to do with software manufacturers.
Not fighting with anyone here, just expressing frustration at the situation in general. And I think you're misunderstanding what I was saying -- I have no problem at all with SIP being enabled for the installation of the driver... what bothers me is having to disable it again to actually run anything. That seems a failing on NVidia's part, though it COULD be how Apple's applications interface with the video driver.
I currently have a 1070 Founder's Edition. That hasn't helped me any with support, though. I've gotten the same runaround as when I had a PNY 970 and tried to get help from either NVidia or PNY.
On the plus side, it is SO much easier to deal with multiple cards from multiple families on the Mac... when running Bootcamp, I need to pull my old factory card because Win7 throws a fit at having two different cards, even from the same manufacturer.
[RICHR]
I currently have a 1070 Founder's Edition. That hasn't helped me any with support, though. I've gotten the same runaround as when I had a PNY 970 and tried to get help from either NVidia or PNY.
On the plus side, it is SO much easier to deal with multiple cards from multiple families on the Mac... when running Bootcamp, I need to pull my old factory card because Win7 throws a fit at having two different cards, even from the same manufacturer.
[RICHR]