Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
Updated the the script in Post 461 to now remove any existing OCSP blocks in the hosts file.

So if previously using the procedure on Page 4 and the issue returns or it has been tried without success, all that is needed is to run the Post 461 script and it will set everything to the improved process as needed; including removing the hosts file blocks.

Obviously stick with what you have if currently working and don't change for the sake of changing.
 
Last edited:

kingAndy

macrumors newbie
Jun 8, 2022
4
1
Updated the the script in Post 461 to now remove any existing OCSP blocks in the hosts file.

So if previously using the procedure on Page 4 and the issue returns or it has been tried without success, all that is needed is to run the Post 461 script and it will set everything to the improved process as needed; including removing the hosts file blocks.

Obviously stick with what you have if currently working and don't change for the sake of changing.
Thank you very much for all the work you did!
 

MacKing3000

macrumors newbie
Jun 8, 2022
29
4
I added a a little Script to patch the Cuda Driver as well, the CUDADriver.pkg has to be in Downloads.

If someone can provide a link to download it directly via curl I can add downloading the .pkg file.

View attachment 2017027


View attachment 2017028

the package is in #456





Is it possible to add this to it.. It downloads as .dmg file not PKG - I tried running your script from #456 but its giving an error because the CUDA is not there. Thanks in advance for all your amazing work on this.. making a lot of people happy and getting things working again.. myself included!

link to the CUDA DRIVER below

 

NJFraser

macrumors newbie
Jun 9, 2022
2
1
You want to press the easy button and not spend any time reading.

try Dayo’s solution on page 4, eierfrucht’s on page 10, or Dayo’s latest, which he just posted only a couple posts above yours.
You've proven my larger point which is the solution(s) are complex and densely intertwined amongst 20 pages of back and forth between multiple users. And when I said I've been following, that means I've been reading this closely for days but find that thicket of info too convoluted to feel safe to try some of the things on my machine. I didn't ask for anything to be easy-easy would be buying a new video card or new computer. I just asked for a consolidation based on the latest best attempts by folks clearly trying to solve the problem and share that with their fellow users. Snide responses ain't helpful for anyone.
 

MacKing3000

macrumors newbie
Jun 8, 2022
29
4
Yes, just copy the CUDADriver.pkg to your Downloads folder.
Awesome I got CUDA + Drivers working.. just one last thing now though..

Both Cuda + GPU are showing up in Cinema 4DXL .. but now I'm getting constant errors when I try preview via Live Viewer ( as in GPU Preview ). I know it's unrelated to getting the OS - CUDA + Drivers working.. but I'm feeling maybe the blocks in the scripts might be affecting OCTANE functions.. not sure if anyone else is experiencing something similar - attached the error log.
 

Attachments

  • Screen Shot 2022-06-11 at 1.03.10 am.png
    Screen Shot 2022-06-11 at 1.03.10 am.png
    66.5 KB · Views: 81

DTRX

macrumors member
Jun 9, 2022
35
29
Awesome I got CUDA + Drivers working.. just one last thing now though..

Both Cuda + GPU are showing up in Cinema 4DXL .. but now I'm getting constant errors when I try preview via Live Viewer ( as in GPU Preview ). I know it's unrelated to getting the OS - CUDA + Drivers working.. but I'm feeling maybe the blocks in the scripts might be affecting OCTANE functions.. not sure if anyone else is experiencing anything similar - attached the error code
Seems like a specific CUDA-related error to me. I am sorry, but I did not particularly test the GPGPU functionality. GPU though works for my usage scenario. IDK if this even has some relation to the here discussed trustd blacklisting issue of NVIDIA's development certificate.
 
  • Like
Reactions: MacKing3000

MacKing3000

macrumors newbie
Jun 8, 2022
29
4
Seems like a specific CUDA-related error to me. I am sorry, but I did not particularly test the GPGPU functionality. GPU though works for my usage scenario. IDK if this even has some relation to the here discussed trustd blacklisting issue of NVIDIA's development certificate.
Damn! Seems nuts that this is happening.. feels like all the effort will be in vein for some of us if the GPU’s can’t be put to work w 3D applications. It’s mostly the reason we’ve held on to the trusty 5,1 beasts!
 

startergo

macrumors 603
Sep 20, 2018
5,021
2,283
You've proven my larger point which is the solution(s) are complex and densely intertwined amongst 20 pages of back and forth between multiple users. And when I said I've been following, that means I've been reading this closely for days but find that thicket of info too convoluted to feel safe to try some of the things on my machine. I didn't ask for anything to be easy-easy would be buying a new video card or new computer. I just asked for a consolidation based on the latest best attempts by folks clearly trying to solve the problem and share that with their fellow users. Snide responses ain't helpful for anyone.
Have you tried this:
Post in thread 'Cannot install or use Nvidia Webdrivers anymore!' https://forums.macrumors.com/thread...idia-webdrivers-anymore.2346445/post-31159821
It does not involve modifying system folders/files.
 

DTRX

macrumors member
Jun 9, 2022
35
29
You've proven my larger point which is the solution(s) are complex and densely intertwined amongst 20 pages of back and forth between multiple users. And when I said I've been following, that means I've been reading this closely for days but find that thicket of info too convoluted to feel safe to try some of the things on my machine. I didn't ask for anything to be easy-easy would be buying a new video card or new computer. I just asked for a consolidation based on the latest best attempts by folks clearly trying to solve the problem and share that with their fellow users. Snide responses ain't helpful for anyone.
As already discussed, I nailed down a working solution on page 17 (post 412). Most people here were initially sceptical about if it would work and be helpful with lifting the driver ban. Others found deleting files in the root shell too risky for typical users. This is why the solution was tested for general functionality by several users (posts 429, 436, 449). In addition Macschrauber and Dayo decided to start developing scripts to help others (posts 456 and 461) applying the solution to their own machines.

As I have already written before, I did not find any positive outcome from blocking hosts either via Little Snitch or the hosts file as it was originally suggested on all those pages before 17. The only temporary fix that was reachable for me turned out to be booting into safe mode (if you combine that scenario with simultaneously disabling access to internet). This approach clears out cache files and therefore leads to a temporarily working driver after rebooting. If you reactivate your internet connection (which you will certainly do in most situations), trustd will rebuild its caches and eventually block the NVIDIA driver after few reboots - this was reported by many users before we started locking the cache folders.

To sum it up, just give the latest script (post 461) a try and forget about the rest.
 
Last edited:

DTRX

macrumors member
Jun 9, 2022
35
29
Have you tried this:
Post in thread 'Cannot install or use Nvidia Webdrivers anymore!' https://forums.macrumors.com/thread...idia-webdrivers-anymore.2346445/post-31159821
It does not involve modifying system folders/files.
This code signing solution leads to heavy modification of the driver itself. I also tested that way. It does actually help with reactivating the blocked driver preferences panel. The driver itself will stay non-functional. So it's a nice idea, not more.
 

DTRX

macrumors member
Jun 9, 2022
35
29
Damn! Seems nuts that this is happening.. feels like all the effort will be in vein for some of us if the GPU’s can’t be put to work w 3D applications. It’s mostly the reason we’ve held on to the trusty 5,1 beasts!
Well, my application for machine learning works.

OctaneRender can be picky about GPU driver versions, if you take a look at https://render.otoy.com/forum/viewtopic.php?f=7&t=70578

Maybe you need to downgrade?
 

harrymac20

macrumors newbie
Jun 2, 2022
5
4
Followed advice posted and worked for me after having major problems with Macpro not wanting to boot into safe mode (sorted by repeatedly pressing Shift key and not continually pressing the shift key when restarted) then was unnable to save the Hosts file when editted (Solved via using CTRL O and not CMD O then Y for yes)

My heavily modified Macpro is now back up and running as should and can use the WebDriver from Nvidia and also CUDA for video card rendering in Cycles as I use Blender daily.

Many thanks eirfrucht for the successful post. #230

I think I will be forever stuck on 10.13.6 though.
 

Fullerfun

macrumors member
Jun 5, 2022
33
29
As already discussed, I nailed down a working solution on page 17 (post 412). Most people here were initially sceptical about if it would work and be helpful with lifting the driver ban. Others found deleting files in the root shell too risky for typical users. This is why the solution was tested for general functionality by several users (posts 429, 436, 449). In addition Macschrauber and Dayo decided to start developing scripts to help others (posts 456 and 461) applying the solution to their own machines.

As I have already written before, I did not find any positive outcome from blocking hosts either via Little Snitch or the hosts file as it was originally suggested on all those pages before 17. The only temporary fix that was reachable for me turned out to be booting into safe mode (if you combine that scenario with simultaneously disabling access to internet). This approach clears out cache files and therefore leads to a temporarily working driver after rebooting. If you reactivate your internet connection (which you will certainly do in most situations), trustd will rebuild its caches and eventually block the NVIDIA driver after few reboots - this was reported by many users before we started locking the cache folders.

To sum it up, just give the latest script (post 461) a try and forget about the rest.
I’ve rebooted hundreds of times since Monday, so far trustd has not rebuilt the cache. I know I’m not the only one. I did discover on a system that didn’t have the latest security updates, that blocking only temporarily worked as you described,...and I’m fairly sure that’s because Apple changed up where trustd gets it’s caches from in each security update.

Your method is simpler and works well. I simply prefer/feel more secure about my system, to just block Apple‘s servers rather than shutting down trustd completely. It’s all a matter of choice/opinion.

I will post on here the second my blocking no longer works.

in meantime, if the 2 users who reported getting an updated driver directly from NVidia were legit, I’d imagine we will all have a solution from NVidia soon...and we can all go back to being angry at Apple/NVidia for dropping support beyond 10.13. I have contacted NVidia asking them to post the driver publicly or send it to me. Will post when/if I hear back from them.
 

DTRX

macrumors member
Jun 9, 2022
35
29
I’ve rebooted hundreds of times since Monday, so far trustd has not rebuilt the cache. I know I’m not the only one. I did discover on a system that didn’t have the latest security updates, that blocking only temporarily worked as you described,...and I’m fairly sure that’s because Apple changed up where trustd gets it’s caches from in each security update.

Your method is simpler and works well. I simply prefer/feel more secure about my system, to just block Apple‘s servers rather than shutting down trustd completely. It’s all a matter of choice/opinion.

I will post on here the second my blocking no longer works.

in meantime, if the 2 users who reported getting an updated driver directly from NVidia were legit, I’d imagine we will all have a solution from NVidia soon...and we can all go back to being angry at Apple/NVidia for dropping support beyond 10.13. I have contacted NVidia asking them to post the driver publicly or send it to me. Will post when/if I hear back from them.
Just consider the side effects of blocking Apple's servers. It will for sure affect more than just the trustd service. But, of course, it's your choice. I prefer to save some time.

If NVIDIA releases a new driver (still doubt that), this is for sure the best option to go with in the end for all 10.13.6 installations with unsupported NVIDIA GPUs.
 

mirko.meschini

macrumors regular
Feb 13, 2011
116
5
Italy
So I unbricked all affected machines with DTRX method and they are all still working. Thank you a lot guys for your work, that saved mine and my customers one too!!! We'll see on the next days if this solution is solid!
 

Fullerfun

macrumors member
Jun 5, 2022
33
29
Just consider the side effects of blocking Apple's servers. It will for sure affect more than just the trustd service. But, of course, it's your choice. I prefer to save some time.

If NVIDIA releases a new driver (still doubt that), this is for sure the best option to go with in the end for all 10.13.6 installations with unsupported NVIDIA GPUs.
my preferred method is to use little snitch to only block trustd from connecting to those specific severs...not the hosts file. So actually, no, only thing blocked is any future certificates that get revoked at Apple‘s severs...not other certificates from other websites trustd uses....assuming that Apple dosen’t start sending them through some other server/service as many have suggested....if that happens I will adjust the blocking. Your method completely disables trustd. No doubt, your method is fast and simple.
 
  • Like
Reactions: Ashok.Vardhan

Fullerfun

macrumors member
Jun 5, 2022
33
29
So I unbricked all affected machines with DTRX method and they are all still working. Thank you a lot guys for your work, that saved mine and my customers one too!!! We'll see on the next days if this solution is solid!
That solution is solid, trustd is completely disabled. It will prevent this specific problem from coming again.
 
  • Like
Reactions: mirko.meschini

sv1cec

macrumors newbie
Apr 16, 2009
25
1
Can someone PLEASE post a new thread, clearly explaining what we should do, to overcome the problem caused by the NVidia drivers no longer working? I went through 20 or something pages, and apart from the headache, I am still not sure what to do. I've saved the script from post 461, but I am still indoubt if that's what I should do (or even how I run it). A new thread with concise instructions would be more than welcome.
 

fulcrum99

macrumors newbie
Jun 10, 2022
2
0
Hello all, I just registered to share my experience with this apparent problem. I have a 1050 ti on a hackintosh, fully upgraded to high sierra. I'd been logging on successfully until yesterday when the mac would hang after 75% (after the screen flashes when it loads the nvidia drivers, I'm assuming). I've been able to run things in safe mode and following this thread, was waiting for the new drivers to release before I took any chances with a script, but thought I'd try letting it start up normally today and it started up as usual and ran without problem. So perhaps things have been sorted out? I saw someone mention running in safe mode and then returning after a while to normal, so maybe that is a fix as well?
 

TedsterTheSecond

macrumors newbie
Jun 6, 2022
21
5
This whole thing just fills me with terror. Can't NVidia just pull their finger out? I've spoken to help and begged them on social media so far nothing. Not even a reply.

I'd rather not run scripts, all credit to Macschrauber, but I'm not that techy and still don't know what I'm doing.

I was trying to boot my mac from internet recovery with Command option R and use an earlier back up and block trustd with little snitch, but it's not playing ball, and certainly not rendering one.
 

DTRX

macrumors member
Jun 9, 2022
35
29
Hello all, I just registered to share my experience with this apparent problem. I have a 1050 ti on a hackintosh, fully upgraded to high sierra. I'd been logging on successfully until yesterday when the mac would hang after 75% (after the screen flashes when it loads the nvidia drivers, I'm assuming). I've been able to run things in safe mode and following this thread, was waiting for the new drivers to release before I took any chances with a script, but thought I'd try letting it start up normally today and it started up as usual and ran without problem. So perhaps things have been sorted out? I saw someone mention running in safe mode and then returning after a while to normal, so maybe that is a fix as well?
Booting in safe mode clears out cache files and therefore leads to a temporarily working driver after rebooting. After some time trustd will rebuild its caches and eventually block the NVIDIA driver after few reboots - this was reported by many users before we started locking the cache folders.
 
  • Like
Reactions: fulcrum99

DTRX

macrumors member
Jun 9, 2022
35
29
This whole thing just fills me with terror. Can't NVidia just pull their finger out? I've spoken to help and begged them on social media so far nothing. Not even a reply.

I'd rather not run scripts, all credit to Macschrauber, but I'm not that techy and still don't know what I'm doing.

I was trying to boot my mac from internet recovery with Command option R and use an earlier back up and block trustd with little snitch, but it's not playing ball, and certainly not rendering one.
Just save yourself some time and use the script.
 
  • Like
Reactions: TedsterTheSecond
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.