MP 1,1-5,1 nvidia webdriver .132 issues with 17G9016 (10.13.6) and Titan X [urgent]

absente

macrumors member
Original poster
Feb 18, 2019
47
4
After the last security update to 17G9016 (which i run by mistake) I am having heavy problems making my titan x recognizable by the OS. Whatever I've tried it simply doesn't work. That never happened before on previous updates.

Right after installing the 17G9016 update I installed the 378.10.10.10.40.132 webdriver via remote screen.

- I've tried multiple times installing / uninstalling drivers
- Multiple times resetting nvram/pram (3 chimes)
- multiple times almost all procedures I could find on the forum

I have also a spare GT120 that I installed in slot two. When booting with the nvidia driver and going to system preferences -> PCI or system preferences -> graphics controllers the titan card is there, however not recognized. It just appears as "vga compatible controller".

When booting just with the titan and using screen sharing it is also not recognized by name in the system preferences. I know the card is fine, because it worked before the update.

I need quick help, I use this machine for work. I know there is always an option to create a backup and install an earlier version, but reinstalling all the applications and preferences would be a nightmare.

If it is important, I used the 387.10.10.10.40.105 driver before that update and it worked well.

MP2009 flashed to 5,1 , 141 bootrom
 

absente

macrumors member
Original poster
Feb 18, 2019
47
4
After waisting one more day i decided to roll back to 17G65, which was the original version everything worked on. I used dosdude's patcher and did a new install. However to my surprise it was now 17G66 - for which there are no webdrivers. After some researching I found out that this is the only version (officially) available anymore.

It took me quite over four hours find an authentic 17G65. I am currently doing an install and see if it switches to 17G66 - to be safe i'll disconnect the wifi and disallow automatic updates.

I'll use this thread to log my steps in case anyone else has the same problem at some point.
 

tsialex

macrumors 603
Jun 13, 2016
5,601
6,420
Brazil
After waisting one more day i decided to roll back to 17G65, which was the original version everything worked on. I used dosdude's patcher and did a new install. However to my surprise it was now 17G66 - for which there are no webdrivers. After some researching I found out that this is the only version (officially) available anymore.

It took me quite over four hours find an authentic 17G65. I am currently doing an install and see if it switches to 17G66 - to be safe i'll disconnect the wifi and disallow automatic updates.

I'll use this thread to log my steps in case anyone else has the same problem at some point.
You have a supported Mac, you shouldn't use dosdude installs. You are making an already complicated situation even worse, kept it simple as possible, use official Apple installers.

There is no working 17G65 anymore, signing certificates expired 10/29 and Apple only re-issued 17G66.
 
  • Like
Reactions: bsbeamer

bsbeamer

macrumors 68030
Sep 19, 2012
2,621
1,281
You should see this thread for driver options:
 

absente

macrumors member
Original poster
Feb 18, 2019
47
4
@tsialex i changed the system date via console before the install and the 17G65 can be installed. I can't believe apple "missed" that little "hole". I know it doesn't make sense, but reverting back to my original version was the only logical approach after days of issues.

I am now doing the web-driver installation, I hope I can finally fix my working mac after two days
 

absente

macrumors member
Original poster
Feb 18, 2019
47
4
For what it's worth:

- after reverting back to 17G65 and installing the x.105 drivers my titan x was recognized instantly

that leads me to assume that the 17G9016 security update in combination with the 378.10.10.10.40.132 nvidia webdriver might not be supported or needs to be fixed. I've already send out an email to nvidia about the issue.

In order to be sure, I've tried the same on another cmp and could replicate the problem.