Jump to content
fantomas

Nvidia Web Driver updates for El Capitan (UPDATE 07/11/2018)

724 posts in this topic

Recommended Posts

Advertisement

@chanhan: "Updated El Capitan to 10.11.6 (15G1212) and now nvidia web drivers are not working."

 

You could install the beta drivers until NVIDIA updates the OS X El Capitan drivers.

NVIDIA Alternate Graphics Drivers for OS X 10.11.6 (15G12a Beta)
http://us.download.nvidia.com/wanl9YNPeTLf4ztbBsDkiMXsE4tbtMGp/WebDriver-346.03.15b01.pkg

 

It worked for me

Share this post


Link to post
Share on other sites

Just installed the 'supplemental' Security Update 2016-003 from today, getting the default OS driver after rebooting. Anyone know if there's a new web driver to address this update?

Share this post


Link to post
Share on other sites

Quick question related to the tool: does the tool do anything more than changing the file:

/System/Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist

altering the lines:

<key>NVDARequiredOS</key>
<string>15G1212</string>

to the new string 15G1217? Then I can do it manually, after the update gets installed and before I hit the "Reboot" button...

Share this post


Link to post
Share on other sites

Quick question related to the tool: does the tool do anything more than changing the file:

/System/Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist

altering the lines:

<key>NVDARequiredOS</key>
<string>15G1212</string>

to the new string 15G1217? Then I can do it manually, after the update gets installed and before I hit the "Reboot" button...

 

No, the tool doesn't do anything more.

 

You could also run this before or after downloading and installing the update (but before hitting Reboot :P) :

 

 

sudo nano /System/Library/Extensions/NVDAStartupWeb.kext/Contents/info.plist

 

Then manually edit the NVDARequiredOS. Don't forget to fix permissions and rebuild kernel cache using another great tool :

 

 

sudo InsanelyRepairPermission -rt /

 

You'll just need to know the relevant build number in advance :).

Share this post


Link to post
Share on other sites

Guys, use this : http://www.insanelymac.com/forum/files/file/474-nvidia%C2%AE-webdriver-updaterapp/ to patch the NVDAStartupWeb.kext so it matches 15G1217 build number ;).

Could you please explain to me, how to use this?

 

I downloaded the file, started it and typed "15G1217" into the text field. Then I hit "patch immediately" without checking the box "patch after installation". I can see now that inside the relevant Info.plist the string has been changed to "15G1217". But what would be my next step now??? I have no clue....

Thanks for your help!

Share this post


Link to post
Share on other sites

Could you please explain to me, how to use this?

 

I downloaded the file, started it and typed "15G1217" into the text field. Then I hit "patch immediately" without checking the box "patch after installation". I can see now that inside the relevant Info.plist the string has been changed to "15G1217". But what would be my next step now??? I have no clue....

Thanks for your help!

repair permissions and rebuild the cache by kext wizard or other programm

Share this post


Link to post
Share on other sites

Found the kext wizard....are these the boxes I have to check?

Sorry, it's in German but I think it's pretty clear what is meant.

post-1955331-0-34424600-1484820373_thumb.jpeg

Share this post


Link to post
Share on other sites

Yes this checked are correct.

BUT! before sou use that, please check date/time of the /System/Library/PrelinkedKernels/prelinkedkernel

and check the date/time of that after you use the kext wizard with repair permissions / Systemcache new.

I say that, because sometimes the tool does not refresh the cache = prelinkedkernel = fault will not be gone!

It it worked the date/time of /System/Library/PrelinkedKernels/prelinkedkernel is new.

 

You can also repair permission (if you change an .plist of an kext ) by

start terminal

sudo chown -R root:wheel (drag & drop the whole kext you want to repair in permissions from /S/L/E into the terminal OR write the whole path here, like /System/Library/Extensions/NVDAStartupWeb.kext )

sudo touch /System/Library/Extensions

 

The second command refreshes the cache=prelinkedkernel - you will see that by changed = newer date/time of the /System/Library/PrelinkedKernels/prelinkedkernel.

This takes some time (up to 1 Minute) so be patient.

Share this post


Link to post
Share on other sites

The app thake the step to edit the Info.plist, repair permissions and "touch" /System/Library/Extensions" causing the prelinkedkernel to be rebuilted. No other operations needed IMHO, unless you have other problems.

Share this post


Link to post
Share on other sites

A plist edited in place by sudo has no effect on permissions. sudo touch /System/Library/Extensions will update the kernel cache to reflect the change. A reboot will be required before the Web Driver can be selected again.

Share this post


Link to post
Share on other sites

Hey everyone, I've followed the steps to change build number and repair permissions and I see web driver is selected through vnc but I still get no signal on the monitor. Any help?

Share this post


Link to post
Share on other sites

A plist edited in place by sudo has no effect on permissions. sudo touch /System/Library/Extensions will update the kernel cache to reflect the change. A reboot will be required before the Web Driver can be selected again.

sudo is not used by NVIDIA Web Drivers Updater.app. It use a UNIX socket through an XPC connection, and the OS trust the app because is code signed granting its helper tool to execute privileged tasks as root.

Share this post


Link to post
Share on other sites

I have a 2009 Mac Pro I have installed a modified Nvidia 960 GTX card in, and I installed the Security Update, which of course broke the Nvidia driver.  I tried running both the linked to Nvidia WebDriver Updater as well as the repair permissions, and while I can now select the Nvidia driver, it is still using the OS X driver (slow graphics effects & only 1 screen).  Does anyone have any suggestions for how to make it actually use the Nvidia driver?  Thanks!

Share this post


Link to post
Share on other sites

I have a Geforce GTX 980 installed in my MacPro 5.1 (2010). I did all the steps mentioned above. Right after that I checked the "prelinkedkernel". It showed date/time just a minute ago. So that looked fine to me. 

Now I could pick the NViDIA Web Driver, rebooted... but my monitor stayed dark. I checked the webdriver preferences and under EEC my GPU is not listed. 

Also very strange: my CUDA wants to be updated. I checked with the NVIDIA website: I'm using the latest version.

 

Any idea? I'm really desperate, I need my Mac to do my work tomorrow.... thanks!

 

 

Share this post


Link to post
Share on other sites

For me, after installing the newest Sec update, and changed the .plist to 15G1217, rebuild prelinked kernel, my GT 740 works as before (Macpro 2008 + chameleon bootloader)

Perhaps GTX 960/980 is more an "diva" - make more trouble than other gpus - and something other, beside changing .plist for Web driver, is needed?

Share this post


Link to post
Share on other sites

Fun times!

@matde - can you try to plug your monitor into another port?  The one monitor I have that is working is in the HDMI port.

@mitch_de - why do you use chameleon bootloader with your MacPro?

I looked up how to clear out my kext caches build a new prelinked kernel, but when I run the command

kextcache -prelinked-kernel System/Library/Caches/com.apple.kext.caches/Startup/kernelcache -K System/Library/Kernels/kernel System/Library/Extensions

kextcache -prelinked-kernel

I get the following error:

NVDAStartupWeb.kext has invalid signature; omitting.

It also mentions: Untrusted kexts are not allowed

So, maybe that's why you're using the chameleon bootloader so you can use unsigned kexts?
 
This is so frustrating - this is why I spent the extra money to buy a real mac, so I wouldn't have to deal with downtime of my workstation :-/  And here are hackintoshes that are being more reliable! :-)
Granted, Apple never intended me to put a GTX 960 in it, but they haven't released a decent graphics card for them in 239852935 billion years.
The downfall of Apple is well under way. :-P

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By NikTheNoob
      Hi,
       
      I'm rather new to Hackintosh and trying my first build with OpenCore on AMD, but I run into issues causing OpenCore to crash before even loading the macOS installer. As I'm not sure which one is causing the crash, I'm trying to resolve all of them and one of the error messages has to do with WhateverGreen, which I was able to see in this slow-mo loading video. Basically I'm getting an error that I'm running an unsupported processor, even though I think I was following this guide by the step.
      What could be causing this and what do I need to do to resolve it?
       
      CPU: AMD Ryzen 2700X
      MB: Gigabyte Aorus X470 Ultra Gaming
      Memory: 4x8 GB HyperX Predator, 3000 MHz Cl15
      Storage: Samsung Evo 970 Nvme 512 GB, Crucial MX500 500GB SATA
      GPU: MSI Radeon RX580 GamingX 8GB
    • By fantomas
      Hi InsanelyMacaliens    
       
      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS High Sierra.
       
      10.13.6
       
      Nvidia Web Driver - 387.10.10.10.40.134 --> build 17G11023 (thanks to TimeLord04) New!
      Nvidia Web Driver - 387.10.10.10.40.133 --> build 17G10021 (thanks to phi777)
      Nvidia Web Driver - 387.10.10.10.40.132 --> build 17G9016 (thanks to iCanaro)
      Nvidia Web Driver - 387.10.10.10.40.131 --> build 17G8037 (thanks to phi777)
      Nvidia Web Driver - 387.10.10.10.40.130 --> build 17G8030 (thanks to fabiosun)
      Nvidia Web Driver - 387.10.10.10.40.129 --> build 17G8029 (thanks to TimeLord04)
      Nvidia Web Driver - 387.10.10.10.40.128 --> build 17G7024 (thanks to flowrider)
      Nvidia Web Driver - 387.10.10.10.40.127 --> build 17G6030 (thanks to Extreme™) 
      Nvidia Web Driver - 387.10.10.10.40.124 --> build 17G6030 (thanks to flowrider) 
      Nvidia Web Driver - 387.10.10.10.40.123 --> build 17G6029 (thanks to Badruzeus) 
      Nvidia Web Driver - 387.10.10.10.40.122 --> build 17G5019 (thanks to TimeLord04) 
      Nvidia Web Driver - 387.10.10.10.40.118 --> build 17G5019 (thanks to ReddestDream)
      Nvidia Web Driver - 387.10.10.10.40.113 --> build 17G4015 (thanks to flowrider)
      Nvidia Web Driver - 387.10.10.10.40.108 --> build 17G3025 (check here)
      Nvidia Web Driver - 387.10.10.15.15.108 --> build 17G2307 (thanks to marcozardi)
      Nvidia Web Driver - 387.10.10.10.40.105 --> build 17G65 (thanks to sl0wtarget)
       
      10.13.5
      Nvidia Web Driver - 387.10.10.10.35.106 --> build 17F77 (check here)
       
      10.13.4
      Nvidia Web Driver - 387.10.10.10.30.107 --> build 17E202 (check here)
      Nvidia Web Driver - 387.10.10.10.30.106 --> build 17E199 (thanks to BreBo)
      Nvidia Web Driver - 387.10.10.10.30.103 --> build 17E199 (thanks to ricoc90)
       
       
      10.13.3
      Nvidia Web Driver - 387.10.10.10.25.161 --> build 17D102 (thanks to Cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.160 --> build 17D2102 (thanks to Cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.159 --> build 17D2012 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.158 --> build 17D102 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.157 --> build 17D2047 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.156 --> build 17D47 (thanks to darthsian) 
       
       
      10.13.2
      Nvidia Web Driver - 378.10.10.10.25.106 --> build 17C2205 (thanks to KGP-X99)
      Nvidia Web Driver - 378.10.10.10.25.105 --> build 17C2120 (see this post)
      Nvidia Web Driver - 378.10.10.10.25.104 --> build 17C205 (thanks to ReddestDream)
      Nvidia Web Driver - 378.10.10.10.25.103 --> build 17C89 (thanks to Il Francy MacPc) 
      Nvidia Web Driver - 378.10.10.10.25.102 --> build 17C88 (thanks to piiggggg)
       
       
      10.13.1
      Nvidia Web Driver - 378.10.10.10.20.109 --> build 17B1003 (see this post)
      Nvidia Web Driver - 378.10.10.10.20.108 --> build 17B1002 (thanks to BreBo)
      Nvidia Web Driver -378.10.10.10.20.107 --> build 17B48 (thanks to piiggggg) 
       
       
      10.13.0
      Nvidia Web Driver - 378.10.10.10.15.121 --> build 17A405 (thanks to Asgorath)
      Nvidia Web Driver - 378.10.10.10.15.120 --> build 17A405 (thanks to phi777)
      Nvidia Web Driver - 378.10.10.10.15.117 --> build 17A405 (thanks to phi777)
      Nvidia Web Driver - 378.10.10.10.15.114 --> build 17A365 (thanks to Asgorath).
    • By Kaku
      Greetings!
       
      So I managed to get a Catalina 10.15 vm up and running in ESXi 6.7u2.
      When I try to install Catalina updates, however, it goes to the Apple logo, status bar moving ever so slightly, reboots again and this time hangs on the Apple logo.  To fix this, I either remove or disable "Mac OS" as an option in the bootloader. Is there a way to get these updates to install? 
       
      In the meantime...
       
      I instead of restarting Catalina after choosing to update it, I shutdown the guest.  After a restart it SEEMED to update with the time duration countdown.
       
      Prior to this I did run disk utility and checked Untitled and Untitled-Data for errors (I don't think it found any).
       
      So I just logged back onto the VM and the version is still 10.15 and NOT 10.15.2 as hoped. So weird.
       
      Any ideas?
       
    • By fusion71au
      Clover r5101 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5101 for VMware.zip". Mount Clover-v2.5k-5101-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By liljboi2
      Trying To Boot Mac OS X El Capitan On Surface Book 1 i5 128GB 
      Ive tried everything under the sun to try to get this to even load the installer
      ive had mixed experiences trying many different options and “combos” 
      i Can Offer Someone That Can Help A “Software Pack” Which Includes
      My EFI
      Kexts
      DSDT
      Readmes
       
      Pretty Much Everything I HaveTried And Researched
      Hopefully That Will Help As I’m Confident I Should Have All Required Files But Not So Confident On How They Should Be Coupled 
      There Is A Guide On This Platform That Goes Over Installing This But What Is Demoed Is MacOS Sierra 10.12 When My Target Is 10.11 El Capitan  Everyone In The Comments That Tried El Capitan Either Have Out Of The Gate Sucess Or Gave Up And Went To Sierra The Problem Is Besides The Guide Author Correcting A Few Mistakes There Is No Actual Diagnosis And Help Given 
       
      For A While I Was Getting Nothing But A Black Screen After Moving Files I Finally Got An Apple Logo Great!..Not Really Because that’s all it would do.
       
      i Tried EFI Folder From Guy Who Did Surface Pro 4 “Port” And after I While I Will Get Cross Where The Apple Logo Would Be So There’s Something Happening When Using His EFI ; Mines Will Just Hang At Apple Logo For As Long As I Let It 
       
      With Verbose Boot Or Boot Flag -v 
       
      I Get Errors Concerning OSXAptioFixDrv They Are Usually Different 
      If I Try OSXAptioFix2Drv I Get
       
      ...........................................
       
      if i try OSXAptioFixDrv I get 1 of 3 errors Typically Saying Similiar Things 
      About Relocating Memory 
       
      Will Try To Add Photos 
       
      This Is Not My First Hackintosh More Like 5th or 6th But Besides On HP Elitebook Revolve Where I Had Similar Issues Due To BIOS Settings 
      I simply CAN NOT Get It To Boot No Matter What I Do Or Edit Please Help Or Provide EFI Folder That Will Work For Me 
      For Now Looking To Upgrade BIOS as I think it has something to do with firmware being to old as this PC Is usually never connected to Wi-Fi unless I need to download something and I cannot stress I have done everything under the sun to get this to even boot the installer 
×