MP 1,1-5,1 Cannot install or use Nvidia Webdrivers anymore!

[The Buggman]

Can you please do a step by step tutorial?

I simply used this information found within the thread:

To disable checks globally run in Terminal:
sudo spctl --master-disable

- Disconnect all internet connections ... don't forget WiFi or anything else that might kick in automatically
- Reboot into Recovery and run date -u 060200002021 && reboot

You can boot into Recovery by restarting and holding Command+R until you see the progress bar.
Once in Recovery, use the tool bar at the top of the screen to access the Terminal and enter the command line.

Next, I rebooted into safe mode (restart and hold the shift key until you see the apple logo and progress bar).
Finally, I was able to reinstall the webdriver and CUDA packages.

Remember to download the packages you need prior to starting these tasks.
When you install them, it'll ask you if you want to keep or remove them – you might want to choose to "keep," of course.

Edit –
According to flyproductions:

Just one thing can be excluded: As long as internet is disconnected, earlier or actual date does not make any difference.

Edit #2 –
According to DJenkins:

For anyone on hackintosh getting black screens on boot because the drivers won't load, punch in the boot flag:
nv_disable=1

 

[garibaldo]

Same problem here, on two cMP running High Sierra with Dosdude patch, both with nVidia cards, none with "boot screen" so Safe Boot or Recovery are impossible. After first Mac start with the exact same problems, i started the second, it was turned off for months, and as soon I plugged the ethernet cable the window trails showed, and drivers went off...

 

[Nermal]

and as soon I plugged the ethernet cable the window trails showed, and drivers went off...

Well, that confirms - as suspected - that it's a server somewhere that's doing it, rather than an expiration built into the drivers. It should therefore be possible to roll back whatever's changed... if someone can figure out what that was.

 

[ndruha]

Well, that confirms - as suspected - that it's a server somewhere that's doing it, rather than an expiration built into the drivers. It should therefore be possible to roll back whatever's changed... if someone can figure out what that was.

Can somebody who has Little Snitch Firewall installed do the same steps that fix it, and then plug the ethernet cable in, so that he could see where it tries to connect? Then this location/port can be blocked.

 

[The Buggman]

Can somebody who has Little Snitch Firewall installed do the same steps that fix it, and then plug the ethernet cable in, so that he could see where it tries to connect? Then this location/port can be blocked.

I've had my computer connected to the internet for several hours after completing the steps and, so far, nothing has relapsed.

Edit: My suspicion had been that it would relapse after I restarted, but I'm not in the position to take that risk just yet.

 

[flyproductions]

Yes, everything is running exactly as it did before the purge. Fully operational.

Yes, i can verify that!

Made a safeboot, both, gatekeeper and SIP disabled and internet unplugged and sat date back to 2018. Installed Webdriver, in my case 387.10.10.15.15.108, and cuda without any issues and rebooted. Everything worked perfectly fine. I was able to perform a complete benchmark with Unigine Valley, delivering result as expected for a GTX 1080. Both, driver manager and cuda pref panels opened as normal. Not even setting the date back to the actual made any difference.

But after the first reboot with internet connection the mess began again. Card is still accellerated and 3D apps are running. But cuda is already gone again and driver manager refuses to open. And i’d bet after the next reboot everything is trashed again.

Even so i was hoping to have found and blocked some possible culprit with little snitch:

trustd seems to perform the certificate validation. So i at least unchecked "Allow any outgoing connection". Further modification like "block all..." was not possible as it is a protected system rule. But there must be some other thig happenig which LS doesn't notice. If only we knew what exactly to block, problem would be solved.

 

[flyproductions]

Can somebody who has Little Snitch Firewall installed do the same steps that fix it, and then plug the ethernet cable in, so that he could see where it tries to connect? Then this location/port can be blocked.

Must be some domain that is already trusted by LS or a system rule which cannot be changed. See my last comment.

I also blocked any outgoing connection to nvidia.com, which coul not prevent the inet connection from killin cuda again.

 

[flyproductions]

Just as expected! One mor reboot wit inet plugged in and everything is fu**ed again! ?

But at least we have a repeatable offline-fix now!

 

[mateo14]

I hope that MacVidCards.Eu and MACVIDCARDS know about this issue, and they have a solution. These two companies can't ignore these problems if they want to make more money.

Sadly, I can say the same thing about Apple and Nvidia.

 

[paulcons]

Just came on this thread... my cMP is working OK right now, not sure I want to open anything. Are we speculating that the bastards in Cupertino have figured out a way to brick our machines just because they had a hissy fit w/nVidia years ago?

 

[drifeppelin]

You can boot into Recovery by restarting and holding Command+R until you see the progress bar.
Once in Recovery, use the tool bar at the top of the screen to access the Terminal and enter the command line.

Next, I rebooted into safe mode (restart and hold the shift key until you see the apple logo and progress bar).
Finally, I was able to reinstall the webdriver and CUDA packages.

Remember to download the packages you need prior to starting these tasks.
When you install them, it'll ask you if you want to keep or remove them – you might want to choose to "keep," of course.

Confirming this worked for me. My computer wouldn't boot at all since I don't have an iGPU as back up, but it still let me access recovery mode. Once in recovery mode I unplugged my internet, opened terminal and entered the commands (disabled checks, set the date), rebooted into safe mode, installed drivers, reboot again, and I'm back in.

I have Radio Silence which is similar to Little Snitch. The moment I plugged my ethernet back in it connected to lots of places. I'm not sure if this will be of any help but this is what Radio Silence detected made a connection: trustd, findmydeviced, nsurlsessiond, sharingd, IMRemoteURLConnectionAgent, cloudd, syncdefaultsd, CalendarAgent, keyboardservicesd, come.apple.geod, AddressBookSourceSync
(Excluding connections made by apps I have installed like Discord & Google Drive).

 

[flyproductions]

So here is what Little Snitch comes up with as soon as the cable is plugged:

I managed to get trustd blocked for all outgoing connections. Meanwhile i also blocked identityservicesd for outgoing. But all this couldn't prevent cuda and driver manager from getting fu**ed again with the next reboot. And i dont't have to try to know that the next will mess up everything again. I'm a bit short of ideas right now. Does anybody see any other suspect in the list?

Just one thing can be excluded: As long as inet is diconnected, earlier or actual date does not make any difference.

 

[MisterAndrew]

It’s been a long time since Nvidia support in macOS has been deprecated. That’s a really old driver and may not be safe to use. It should be replaced with an AMD GPU.

 

[drifeppelin]

I have Radio Silence which is similar to Little Snitch. The moment I plugged my ethernet back in it connected to lots of places. I'm not sure if this will be of any help but this is what Radio Silence detected made a connection: trustd, findmydeviced, nsurlsessiond, sharingd, IMRemoteURLConnectionAgent, cloudd, syncdefaultsd, CalendarAgent, keyboardservicesd, come.apple.geod, AddressBookSourceSync
(Excluding connections made by apps I have installed like Discord & Google Drive).

Well, I just tried blocking ALL of the connections I mentioned seeing pop up in Radio Silence, and I've successfully restarted my computer three times with them blocked. So far, my hackintosh is booting normally, internet on, and there are no glitches like before. I booted up a random game on Steam and it seems to be running as expected for my GTX 1080.

I don't know if I'm just getting lucky or something, and it's just gonna break again soon, but I wanted to report this back to everyone.

I guess I'll try unblocking them one at a time, and restarting twice each time, and see if/when it breaks.

EDIT: Weirdly it's still working after unblocking each connection. So the fact my system is still working right now may not be because of blocking anything...

 

[flyproductions]

Well, I just tried blocking ALL of the connections I mentioned seeing pop up in Radio Silence,...

As you can see, i tried a similar thing:

Not blocking all of them, but all of the (in my opinion) suspects.

The others i could not imagin doing any harm.

LS gives some detail of what they do:

cloudd:
CloudKit Daemon is part of Apple's iCloud syncing. CloudKit connects to Apple and iCloud domains to sync your data as defined in System Preferences > iCloud. For example cloudd is responsible for syncing Safari Browsing History, iCloud Tabs and more

CalendarAgent:
CalendarAgent is a macOS system process that syncs calendars for the Calendar app and Reminders app to iCloud and other servers. Little Snitch ships with a rule group named “iCloud Services” containing rules for connections to iCloud.

apsd:
The Apple Push Service Daemon is responsible for receiving Push Notifications in macOS, including notifications that appear in Notification Center or iMessages in the Messages app.

syncdefaultsd:
The “Defaults Synchronization Daemon” is part of the iCloud integration of macOS and synchronizes preferences for apps between your devices and iCloud.

timed:
The time synchronization daemon is part of macOS and maintains system clock accuracy by synchronizing the clock with reference clocks via technologies like NTP.

com.apple.geod.xpc:
The Geo Daemon is a system process that loads map data on behalf of other apps.


Really don't know what any of them could have to deal with the NV-drivers or certificates. Everything else is blocked. And incoming connections are zero.

But whenever i reboot, CUDA and the driver manager are gone, and with the next reboot everything else too.

Which leads to the next conclusion: Even internet connection (at least for my experience) does not do any harm "on the fly". As i’m writing this online, i have full normal driver support and can open the prefpanes just fine.

But this doesn't help much. There must be something flying right below Little Snitch's radar. ?

 

[flyproductions]

It’s been a long time since Nvidia support in macOS has been deprecated. That’s a really old driver and may not be safe to use. It should be replaced with an AMD GPU.

If you don't have anything helpful to say, do just that: Don't say anything!

 

[tonidrbn]

Guys, I've restarted my computer 3 times since I did this trick and the drivers still work (with internet of course and no firewall). Am I just lucky?

I simply used this information found within the thread:




You can boot into Recovery by restarting and holding Command+R until you see the progress bar.
Once in Recovery, use the tool bar at the top of the screen to access the Terminal and enter the command line.

Next, I rebooted into safe mode (restart and hold the shift key until you see the apple logo and progress bar).
Finally, I was able to reinstall the webdriver and CUDA packages.

Remember to download the packages you need prior to starting these tasks.
When you install them, it'll ask you if you want to keep or remove them – you might want to choose to "keep," of course.

 

[drifeppelin]

As you can see, i tried a similar thing:

I've just finished unblocking all of the connections I blocked, one at a time, and my computer is still working. So yeah... I don't know if any of my blocking actually made a difference, something else may be keeping my computer from breaking right now...

Guys, I've restarted my computer 3 times since I did this trick and the drivers still work (with internet of course and no firewall). Am I just lucky?

If yours is working after following those steps, without blocking anything, that could just be what's happening to me too and I falsely attributed it to me blocking everything.

I suppose I'll see if things are still working tomorrow.

 

[adriandegar]

I simply used this information found within the thread:




You can boot into Recovery by restarting and holding Command+R until you see the progress bar.
Once in Recovery, use the tool bar at the top of the screen to access the Terminal and enter the command line.

Next, I rebooted into safe mode (restart and hold the shift key until you see the apple logo and progress bar).
Finally, I was able to reinstall the webdriver and CUDA packages.

Remember to download the packages you need prior to starting these tasks.
When you install them, it'll ask you if you want to keep or remove them – you might want to choose to "keep," of course.

I followed your steps but I am not able to open the original driver pkg; I’m getting the prompt like the first post in this thread to delete the pkg due to the certificate revocation.

I’m assuming you’re installing the same pkg file that was previously giving you an issue? I’m unclear at which step the computers knowledge of the package certificate revocation is getting reset?

 

[garibaldo]

I just unplugged cMP from Internet, set calendar to two year ago, and clone the HD, the cloned HD boot without problems in nVidia drivers... According to @tsialex the webdrivers certificates expired:

https://forums.macrumors.com/threads/an-explicit-definition-of-boot-screen-and-its-implications.2176959/post-31142232

 

[adriandegar]

So I’m disconnected from the internet. I checked the console and looks like trustd is retrieving information about signature revocation associated with this pkg from somewhere locally. Does anyone know how to remove the locally stored record of this pkg signature revocation?

 

[The Buggman]

I followed your steps but I am not able to open the original driver pkg; I’m getting the prompt like the first post in this thread to delete the pkg due to the certificate revocation.

I’m assuming you’re installing the same pkg file that was previously giving you an issue?

Are you also making sure your internet is off prior to booting into safe mode? Furthermore, when you're in safe mode you should see "Safe Mode" in the menu bar at the top of the screen just to be sure on that front as well.

You should be installing whatever driver pkg you normally would be for your machine according to your OS X build number. I was able to install the exact same ones that were giving me trouble originally.

 

[dutchyonabike]

Same problem for me. I turned on my 2012 MacPro 5,1 (10.13.6) today (running a GTX980) and now every thing flickers. I have tried all the different ports on the card and nothing has worked. I get the same message in sytem preferences that people have mentioned, a loop of "To use the “NVIDIA Driver Manager” preferences pane, System Preferences must quit and reopen." I'm done with Apple. Luckily my work machine is a custom PC.

 

[flyproductions]

So I’m disconnected from the internet. I checked the console and looks like trustd is retrieving information about signature revocation associated with this pkg from somewhere locally. Does anyone know how to remove the locally stored record of this pkg signature revocation?

Did you click on "Details" (blue in the lower left corner of your pic)?

Also you are trying a very old version of the package. Most recent ones are 387.10.10.10.40.140 or 387.10.10.15.15.108 (works with any security update) and CUDA 418.163 for the first and 10.2.89 for the second one.

 

[Ammok]

I have Sierra 10.12.4 installed on other hard drive. It works without problem with Nvidia!