Jump to content
fantomas

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

716 posts in this topic

Recommended Posts

Advertisement

bb1045 made it first :D few posts above... But this time I will wait, spent several hours figuring out what was the culprit. Plist edit, reboot (verbose) filled with mdworker sandboxed out of everything and temps jumping to some 70 °C instead of baseline 50 °C (mmkay, baseline used to be 70 °C but I reapplied Arctic Ceramique...) After second reboot with un/installed f05 it was clear path to uninstall and not re. Waiting for feedback this time :D

Share this post


Link to post
Share on other sites

I'm not certain about the drivers from OP but I'm hoping somehow I can get imovie working inside of osx or vm osx with my system.

 

I have

MSI ge70 20e laptop with i7 4700 and Nvidia Gt 860m

Bios has no option to shut off Gt 860.

 

Is there any hope to getting imovie to work for me?

Share this post


Link to post
Share on other sites

Just to let you know: latest update from Apple, "Security Update 2016-003 Supplemental Update" breaks NVidia Web Drivers totally, machine just does not start. Had to uninstall the drivers totally to boot up properly. And yeah, not on a hackintosh, but an Early 2009 Mini.

Yep, thats "normal", always because Nvidia use that stupid OS version check (inNVStartupWeb, as fixed .plist entry) which make taht kind of trouble - even the "old" driver would run perfekt.

For me, which can also use Apple Drivers (with Kepler GT 740) it is bad, that after updating system (OS version changes) it does NOT use the Apple drivers, the OS try to use the Web drivers,

they fail and an endless loop of blackscreen with the running apple wheel , short before the desktop would come up, starts.

 

The way how Nvidia implemented the drivers in case of not fitting system version is not intelligent - better would be if the driver "sees" wrong OS version, it boots up in safe mode.

So the user can change or update something insted of black screen/ bootloop.

Share this post


Link to post
Share on other sites

Apple killed NVIDIA.

 

Yep, thats "normal", always because Nvidia use that stupid OS version check (inNVStartupWeb, as fixed .plist entry) which make taht kind of trouble - even the "old" driver would run perfekt.

For me, which can also use Apple Drivers (with Kepler GT 740) it is bad, that after updating system (OS version changes) it does NOT use the Apple drivers, the OS try to use the Web drivers,

they fail and an endless loop of blackscreen with the running apple wheel , short before the desktop would come up, starts.

 

The way how Nvidia implemented the drivers in case of not fitting system version is not intelligent - better would be if the driver "sees" wrong OS version, it boots up in safe mode.

So the user can change or update something insted of black screen/ bootloop.

Share this post


Link to post
Share on other sites

Can you test this instead of editing the kext?

does this kext work in /L/E ?

And no patching is needed in the original apple kext?

Share this post


Link to post
Share on other sites

The issue I'm having with latest drivers is that it doesn't stick.. Upon every boot, it's on the OS X default graphics driver. Can't get it to stick even though nvda_drv=1 in config.plist and so is Nvidiaweb is ticked under system parameters. How do i get it to stick on WebDrivers upon every boot?

Share this post


Link to post
Share on other sites

First check if which driver is really loaded/used. Using nvda_drv=1 with newest chameleon (features Webdriver usage like Clover) works.

But Nvidia Prefpane always shows OS X drivers used, even Nivida Web drivers are in use!

My WebDriverCheck tool shows what is really used - Web oder Apple driver.

http://www.insanelymac.com/forum/files/file/695-webdrivercheck/

 

Also try to update prelinked kernel - sometimes thats the problem.

Share this post


Link to post
Share on other sites

Did you try EmuUEFIvariable.efi?

 

The issue I'm having with latest drivers is that it doesn't stick.. Upon every boot, it's on the OS X default graphics driver. Can't get it to stick even though nvda_drv=1 in config.plist and so is Nvidiaweb is ticked under system parameters. How do i get it to stick on WebDrivers upon every boot?

Share this post


Link to post
Share on other sites

Security update 2017-001 bumps the build to 15G1421.  I've updated /System/Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist with this new build, but I still can't get the web driver to load.  I've also repaired the permissions.

Any other tricks?  Mad that I installed the security update without checking if there was a new web driver available.  Now I have non-accelerated graphics, making everything unusable 

Share this post


Link to post
Share on other sites

I've updated /System/Library/Extensions/NVDAStartupWeb.kext/Contents/Info.plist with this new build

 

 

How ? Have you try to just set 15G instead of full build number ?

Share this post


Link to post
Share on other sites

Are there  additional steps beyond modifying the plist and restarting?  

I am trying http://www.insanelymac.com/forum/files/file/474-nvidia®-webdriver-updaterapp/now

 

Beside repairing permissions and rebuilding kernel cache, no.

 

The app you're talking about will do the necessary steps :).

 

Anyway, I can confirm webdrivers works fine on 10.11.6 (15G1421).

Share this post


Link to post
Share on other sites

Even after running the app I still can't get the Web Drivers recognized.  

I have GeForce GTX 970 in a Mac Pro 2010, and I only get full resolution and no graphics acceleration (lots of tearing and other bad artifacts, slow finder animations, etc).

Web Driver is checked in the Driver Manager.

In CUDA Preferences it says No GPU Detected

Share this post


Link to post
Share on other sites

 

Is SIP disabled?

 

Check it :

csrutil status

 

 

No, it is not.  Unfortunately, I tried to reset my PRAM, and not I am in a boot loader loop.  Unclear if this was the cause, or if something else was lurking all long,

Share this post


Link to post
Share on other sites

It can't work without disabling SIP because the NVDAStartupWeb.kext is now considered as "untrusted" by the system.

 

Booting the Recovery HD, disabling SIP and rebuild kextcache should do the trick. You may need to boot in single user mode to do the later.

/sbin/ mount -uw /
touch /System/Library/Extensions
reboot

Share this post


Link to post
Share on other sites

 

It can't work without disabling SIP because the NVDAStartupWeb.kext is now considered as "untrusted" by the system.

 

Booting the Recovery HD, disabling SIP and rebuild kextcache should do the trick. You may need to boot in single user mode to do the later.

/sbin/ mount -uw /
touch /System/Library/Extensions
reboot

Thank you - disabling SIP was the missing link.  I guess most users here are hackintosh, so already have it disabled. It was new for me, as I'm on a stock Mac Pro, just with the GTX 970.

Share this post


Link to post
Share on other sites

@DMCrimson

You can prevent problem like that by faking build version to just 15G instead of full build number.

The trick applies to any OS X/macOS version BTW :).

Share this post


Link to post
Share on other sites

@DMCrimson

 

You can prevent problem like that by faking build version to just 15G instead of full build number.

 

The trick applies to any OS X/macOS version BTW :).

I know, I've been doing that constantly :D For some reason the WebDriver updater doesn't work for me anymore, so I need to rely on MacKextLight to edit the build version and KextUtility to rebuild caches (which also removes some bootargs despite it's config)

Share this post


Link to post
Share on other sites

That's just what I was referring to. It downloads all right, but patching the driver results in spinning beachball... MKL lets one to edit plist easily inside the kext and makes sure the permissions are set correctly.

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.

Announcements

  • Similar Content

    • By tlefko
      Site
      checkout our official site! https://twortech.wixsite.com/pcmac Version Info
      This build is compatible up to Big Sur Beta
      Now Compatible with macOS 11 Please leave feedback with issues or w/o Comitted to Updating up to OS 11 Latest Release Notes
      Fixed Bluetooth and Wifi Stability Issues Improved Preformance and Power Managements Can Provide Files for Display Overrides Additional Patches for 4K Display updated for Big Sur if using unsupported wifi card disable it in bios use config.plist FIXED SLEEP WAKE BUG Exact same functionality as Catalina What Works / Does Not
      Everything works minus in-built mic Some displays may be detected as 40hz (working on fix) Notes
      Never tested USB C over Display Output, everything else works flawlessly USB devices eject on sleep (not really an issue) POST
      run sudo pmset -a hibernatemode 0 If no mouse, install all voodoo kexts using Kext Utility Description
      This esentially an ultra-simplistic version that is stable without the use of a deploy or complicated file installations and copies. You can easily view all the SSDT patches along with configuration files for the bootloader as they are all documented clearly in the files. This does include a copy of Clover, which of course I do not contribute to and am only responsible for the provided files, patches, and kext placements This guide provides a working setup with little knowledge of the topic and without "optimization" (because often they can break things). But, it is fully functional and preforms properly and is stable Make sure you are using DW1560 for wifi or else KP. If not using remove BRCM kexts from CLOVER>kexts>other. BIOS Setup
      Disable Secure Boot INSTALL (VERY IMPORTANT)
      Due to structural changes in the setup of apple's Big sur, this EFI cannot boot the installer it can only boot into a system / device that has already been created and setup. To do this, you need to install Big Sur to a virtual machine (lots of guides online) and then create an dmg of that system, and restore it onto your HDD using the 'dd' command There are various guides online how to get this virtual machine setup complete. You can then use the attached EFI folder to boot and use macOS big Sur You can use this video to show you how to get your macOS pre-installed onto your hard drive https://www.youtube.com/watch?v=HMU3nhcbWHw Boot Entry Setup
      Due to the fact this BIOS is locked down pretty heavily, reccomended to use Windows to find a free tool to add UEFI boot entries Messages and Facetime
      Gnerate your own Serials, Board Numbers, MLB There are various guides online to do this and as default they're set to essentially Null (Fakeserial) This is fairly straightforward and there is lots of external recourses, or you can contact me for support. Headphones and Audio
      All audio from speakers should work perfectly along with Bluetooth and USB audio no internal mic Credits
      MaLd0n for DSDT Patches (HUGE SHOUTOUT) Original Kext Authors Clover Team Finished!
      Congratulations, there really aren't any more steps that are required. Feel free to contact me with any questions. Donations
      Send me a coffee/beer lefkotyler@gmail.com  
       
      *check GitHub for latest releases and faster support https://github.com/tlefko/HP-Envy-13-Big-Sur
      EFI.zip
    • 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.138 --> build 17G14019 (thanks to TimeLord04) New!
      Nvidia Web Driver - 387.10.10.10.40.137 --> build 17G13035 (thanks to fabiosun)
      Nvidia Web Driver - 387.10.10.10.40.136 --> build 17G13033 (thanks to iCanaro)
      Nvidia Web Driver - 387.10.10.10.40.135 --> build 17G12034 (thanks to iCanaro)
      Nvidia Web Driver - 387.10.10.10.40.134 --> build 17G11023 (thanks to TimeLord04)
      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 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 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?
       
×