MP All Models FAQ - Nvidia Web Drivers

[h9826790]

CUDA is an application library and toolkit - not a driver. It's loosely coupled to the version of the web driver in use, in that CUDA won't use new GPU features if the web driver doesn't support them.

CUDA Toolkit - Free Tools and Training

Get access to SDKs, trainings, and connect with developers.

developer.nvidia.com

Interesting, because Nvidia officially call it "CUDA Driver"

NVIDIA CUDA 418.163 for macOS release

Download English (US) , , ,

www.nvidia.com

 

[AidenShaw]

Interesting, because Nvidia officially call it "CUDA Driver"

Maybe my bad, maybe just semantics. Thanks for the clarification.

For Windows and Linux the standard driver from Nvidia supports the CUDA toolkit - there is no separate CUDA driver, the standard driver supports the APIs that the CUDA toolkit needs.

 

[Speedstar]

does anyone here use 387.10.10.10.40.131 drivers with more then one GPU in McP5.1 with Luxmark OpenCL supported on all devices ?

 

[AidenShaw]

does anyone here use 387.10.10.10.40.131 drivers with more then one GPU in McP5.1 with Luxmark OpenCL supported on all devices ?

The current Nvidia driver version on Windows is 441.12, and 440.31 on Linux. Is 387.10 really the current Apple OSX version?

 

[flyproductions]

I really suggest to stay at 387.10.10.15.15.108,...

Is this still the case today?

I just recently purchased some NV-card, an INNO3D GTX 1070, which i am planning to install in my 5,1, running 10.13.6 with the latest security pack. And now i am wondering which driver to install best. All the latest from NV's website, which is 387.10.10.10.40.132 at the moment. Or the mentioned above 387.10.10.15.15.108.

Thanks for your suggestions.

 

[h9826790]

Is this still the case today?

I just recently purchased some NV-card, an INNO3D GTX 1070, which i am planning to install in my 5,1, running 10.13.6 with the latest security pack. And now i am wondering which driver to install best. All the latest from NV's website, which is 387.10.10.10.40.132 at the moment. Or the mentioned above 387.10.10.15.15.108.

Thanks for your suggestions.

My 1080Ti still working with 387.10.10.15.15.108 today.

 

[flyproductions]

My 1080Ti still working with 387.10.10.15.15.108 today.

Thanks for your reply!

Meanwhile i installed 387.10.10.10.40.132 along with the cuda driver updated to 418.163 and everything seems to work fine so far. Do you think there could be any advantage in going back to 387.10.10.15.15.108?

 

[bsbeamer]

Only advantage is driver doesn’t “break” with OS updates. If you’re on latest CUDA with latest toolkit, you need to be on .132 for 100% compatibility. If you’re not using toolkit, either will work.

FYI, the next iteration of toolkit will not be macOS compatible. Believe development on macOS stops with 10.1.

 

[flyproductions]

Only advantage is driver doesn’t “break” with OS updates. If you’re on latest CUDA with latest toolkit, you need to be on .132 for 100% compatibility.

So as i'm not using the toolkit and not intending to do so, i think i will get along fine with what i have now.

Thanks for your help!

 

[bsbeamer]

So as i'm not using the toolkit and not intending to do so, i think i will get along fine with what i have now.

Thanks for your help!

Make SURE you pay attention to any and all future security updates. If this is true, your driver will "break" with each update and require a new download. Generally speaking anywhere from 1-7 days after release before it's available from NVIDIA.

i installed 387.10.10.10.40.132

 

[flyproductions]

Make SURE you pay attention to any and all future security updates. If this is true, your driver will "break" with each update and require a new download.

So this could well be a reason to use the 15.15.108-driver if every security update stops the "regular" one from working. So question the other way around: can it do any harm to use 387.10.10.15.15.108 and why did NV pull it and strongly recommends not to use it?

 

[bsbeamer]

can it do any harm to use 387.10.10.15.15.108

Define harm. Many people are using this driver. It works and does not break. Added VOLTA support. It does NOT work with the latest CUDA and toolkit properly. The majority of users will never run into those issues, but it does create problems when trying to utilize CUDA rendering on some video applications when used with the latest CUDA driver. Make sure you stick with the CUDA driver(s) and/or toolkit released at the same time as this .108 driver was originally released.

why did NV pull it and strongly recommends not to use it?

A popular conspiracy theory says Apple requested/demanded its removal. The VOLTA support it added may have been part of that reason. We'll never REALLY know the real answers.

NVIDIA's reason for saying not to use is simple - because it is not compatible with the latest CUDA driver and toolkit. Again, use the older CUDA driver(s) released at the time if/when you run into issues and it "shouldn't" become a problem.

Will add - generally speaking, NVIDIA and CUDA on macOS is barely clinging onto life support at this point. If you're looking to holdout for legacy purposes, turn off all updates and just use the stuff as it is. The CPUs in MP5,1 are already EOL'd by Intel. Move to METAL on macOS or switch to another OS platform. CUDA might as well be labeled as EOL'd by NVIDIA for macOS.

If you're on macOS and trying to stay even remotely current, move onto other options (AMD GPUs) and/or at least have a working AMD GPU (certified for the OS) available if you run into issues.

The NVIDIA driver reissues are just for OS build compatibility with OS updates, nothing more, no additional GPU support, no additional functionality, no bug fixes. These OS updates will likely stop around September 2020 if past patterns hold.

 

[flowrider]

Nvidia dropping Mac Support for CUDA:

https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-CUDA-10.2-Released

Lou

 

[bsbeamer]

Surprised they’re even releasing 10.2 for macOS, but at least there is one final update for the holdouts. Should make it easier for archive purposes too.

 

[flyproductions]

Does anybody know if the recently released HS security update 7 will stop the current 132 web driver from working again? I do not dare to update right now.

 

[flowrider]

^^^^Yes it will. But, Nvidia released a new 133 driver this morning:

https://www.nvidia.com/Download/driverResults.aspx/156143/en-us

Lou

 

[flyproductions]

^^^^Yes it will. But, Nvidia released a new 133 driver this morning:

https://www.nvidia.com/Download/driverResults.aspx/156143/en-us

Lou

Thanks! Didn't see this and my 132-driver's control panel still claiming "no update available".

Anyway, i just downloaded. But as i am updating for the first time, i'm a bit confused how to proceed now: First run the security update and then update the driver? In this case a non NV card hast to be used for the process, as the mac autoreboots after the security update, resulting in a blackscreen if the driver is not updated and the NV card is used. Or is there any way to avoid this?

 

[flowrider]

^^^^Run the OS update and once installed and on the desktop, run the Nvidia web driver. The Nvidia card will allow you to reach the desktop, but you won't have acceleration until you update the driver.

Lou

 

[flyproductions]

Thanks again for your reply!

Sadly i could not even finish the update. I keep getting error 119.

...whatever this may be.

 

[flowrider]

^^^^

http://www.macfixguides.com/fix-error-119-on-mac.html

Lou

 

[flyproductions]

^^^^

http://www.macfixguides.com/fix-error-119-on-mac.html

Lou

Yes! This was nearly the only thing i was able to find for error 119 too. But did you take a closer look at it? I don't find it very helpfull. It's an all general/default troubleshooting "guide" which could fit to almost any error one can come across on a mac. Reads a bit like the phrase "error 119" was auto-inserted in all the locations it appears. It is just not mentioned anywhere what this particular error really means. Also the language sounds a bit strange to me.

In all it looks to me like some sort of ad for the mentioned "utility" MacSavior...which from the screenshot looks alot like MacKeeper.

 

[flyproductions]

http://www.macfixguides.com/fix-error-119-on-mac.html

Exactly what i was suspecting: This very same text comes up with whatever error you google for inserted. Presenting "MacSavior" as a solution at the very end. You can try a few numbers yourself.

I'm quite sure, sadly the only thing to be learned from mac"fixguides" is that the "utility" MacSavior - just like MacKeeper - should be avoided by any means.

 

[kasuja00]

Today i installed the security update 2019-008, software info is macOS 10.13.6 (17G11008)

Nvidia driver manager can't find new drivers compatible. Need i wait for news?

 

[bsbeamer]

Believe 17G10021 is the latest available, or install the .108 driver in the first post.

 

[flowrider]

I don't see that Security uUpdate 2019-008 has been issued? So, I'm assuming it's a Public Beta. Nvidia never issues drivers for OS's that are in Beta. At this point your only options are:

1. Go back to Security update 2019-007.

2. Use the 387.10.10.15.15.108 Web Driver as suggested above.

Lou