Jump to content
fantomas1

Nvidia Web Driver updates for macOS Sierra (UPDATE May 15, 2019)

1,060 posts in this topic

Recommended Posts

Hello guys,

 

Anyone managed to get this to work on a GTX 950? I'm getting a black screen on when loading second stage boot. And...nothing else.

I suppose it's an issue with the driver? Is there a known solution to this? Or should we just wait for the next deriver update?

 

I had this same problem on my system with a GTX 980Ti.

 

What is your monitor setup?

 

I fixed it by moving both my monitors to DP (2x1440p).

 

My secondary monitor is dual-link DVI only, but I luckily had a dual-link dvi to DP cable.

 

If you have more than one monitor and one of them support DP, try disconnecting all other monitors and see if you get signal.

 

Also if you use iMac15; iMac17 or MacPro6 I guess you have already patched the AppleGraphicsDevicePolicy.kext? (Or renamed your Nvidia to GFX1) If not do that first.

 

post-211454-0-19533500-1466595577_thumb.png

Screenshot is from 10.11.5, but should give you an idea about how I connected my monitors.

Share this post


Link to post
Share on other sites
Advertisement

I had this same problem on my system with a GTX 980Ti.

 

What is your monitor setup?

 

I fixed it by moving both my monitors to DP (2x1440p).

 

My secondary monitor is dual-link DVI only, but I luckily had a dual-link dvi to DP cable.

 

If you have more than one monitor and one of them support DP, try disconnecting all other monitors and see if you get signal.

 

Also if you use iMac15; iMac17 or MacPro6 I guess you have already patched the AppleGraphicsDevicePolicy.kext? (Or renamed your Nvidia to GFX1) If not do that first.

 

ok, let's take them one by one.

 

I'm using a dual-monitor setup. One monitor connected via DVI, the other one via HDMI. I will try to disconnect one monitor and see if that makes any difference. I don't have DP on either monitor.

 

I'm using iMac 14,2 system definition. And by patching AGDP.kext you mean setting those devices to none? Does that even make any difference? I did that in El Capitan. But...I don't think that actually made any difference whatsoever.

 

How do I rename to GFX1? Is there a way to do it from Clover (kexts to patch section)? That would be really useful.

 

UDPATE:

 

Well Hooray! It does boot with a single monitor (I kept the DVI one).

 

Now, how do I get it to work with both monitors? :D

 

UPDATE 2:

 

Well, that's fixed as well. By moving the DVI display to, well, the other DVI port. :)) Are you kidding me? THAT fixed it?

 

Anyway, thanks a lot for the tips and fast reply.

Share this post


Link to post
Share on other sites

Yeah seems like there is something weird going on with the driver?

 

I'm not sure what the problem is but we are now on 2 out of 2, who had the problem and fixed it by just moving screens around.

 

And no you should not need the AGDP.kext edit when using 1Mac 14,2. :-)

Share this post


Link to post
Share on other sites

Has any one a solution for CUDA? 8.x from SDK requires update 7.5.29 is for all Programms invisible? CUDA-Z does not see anythink either ...

NO SUPPORT OF CUDA in SIERRA FOR NOW !

 

 

--- Update----

 

7.5.30 Update offered via preference.pane installs well but...

 

Does not work either CUDA-Z -quits Adobe 2015.3 CC blind no acceleration...

Share this post


Link to post
Share on other sites

Hi there,

I'm using a Mac Pro 2009 upgraded to 2012 CPUs with 5.1 and a GTX 980ti (EFI flashed).

 

I installed the latest web-driver from here, but if I try to boot the Cinema Display turns black (after boot-logo) and it crashed on the half way and restarts. It's also not possible to boot in VGA-Mode.

 

Is this a problem with the beta-driver? Is there anything I can do?

Share this post


Link to post
Share on other sites

I'm guessing you only need the driver with the 900 series cards?

 

I'm running a 780Ti and all 3 of my monitors worked perfectly during installation and, now, post installation. It was only after I installed the beta web driver, that I encountered the black screen after boot issue. I guess Sierra has 700 series support baked in now?

 

I'm just using the fakesmc I used with El Capitan and even the same exact clover config file and I have no issues running without the web driver, unlike 10.11...

Share this post


Link to post
Share on other sites
I guess Sierra has 700 series support baked in now?

 

I'm just using the fakesmc I used with El Capitan and even the same exact clover config file and I have no issues running without the web driver, unlike 10.11...

 

Looks like you're right.

 

I got a GT 730 that absolutely needs webdrivers in El Capitan and below but runs just fine in Sierra without them.

Share this post


Link to post
Share on other sites

Webdrivers works with DB2 by editing NVDAStartupWeb.kext :

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

Change NVDARequiredOS to this :

<key>NVDARequiredOS</key>

 <string>16A</string>

 

 

8yPms4A.png

yKbaBrw.png

 

 

Share this post


Link to post
Share on other sites

 

<key>NVDARequiredOS</key>

 

 <string>16A</string>

 

Works!

 

Unfortunately, there are then graphics errors in Safari and the App Store. The presentation in Magic Window 4K is also faulty. But I can live with that. After all, my system boots up again with full resolution.

 

Thank you very much.

Share this post


Link to post
Share on other sites

I find all the programs that need to access to internet, the screen will crash. Safari, Mail, App store, Map all have screen crash issue.

I can only access to internet through Chrome instead. Even though make changes to the NVDARequiredOS won't help this.

May be we need to wait the new Nvidia Web driver for Beta 2.

Share this post


Link to post
Share on other sites

Good to know that Chrome also works. Firefox Developer runs without a fault, too. Airmail as an email client also has no indication of failure. For system updates visit the Command Line instead of App Store.

 

There are always ways :-)

softwareupdate --list
sudo softwareupdate -vi "-->Package Name<--"

NVIDIA will not let us wait too long for an update.

 

Will Apple probably bring us native support for the NVIDIA Maxwell chipset under macOS 10.12 Final Release?

Share this post


Link to post
Share on other sites

There seems to be an updated driver, I just ran the updater app and found 367.05.10.05b07

 

post-1535873-0-95247300-1468002593_thumb.png

Hello guys,
 
Anyone managed to get this to work on a GTX 950? I'm getting a black screen when loading second stage boot. And...nothing else.
I suppose it's an issue with the driver? Is there a known solution to this? Or should we just wait for the next driver update?

 

Try running

sudo kextcache -system-prelinked-kernel

Worked for me with my 970

 

Edit: scratch that, it worked for 2 reboots now I'm back to black screens without nv_disable :\

edit2: well, after running the command a few more times it does seem to have worked. I think there might be a kernel cache issue in the public beta and dev preview 2

Edited by Faun

Share this post


Link to post
Share on other sites

I had a completely working system and had the web driver working in DP2 from the posts above. Once I installed the new b07 build today, I get a endless reboot loop after initial restart. Can only boot with nv_disable=1 - can't boot with -x, -f, or -F and "-v debug=yes" gives me no useful information. It stops at different places every time, no panic, nothing I can read that indicates what is causing the reboot. There does seem to be a lot of entires containing 80211, not sure if that is normal or not, even if it isn't what would that have to do with the Nvidia web drivers?

 

Anyone have any ideas? I would post the output of verbose but my first attempt to do so didn't work correctly so if that would help, let me know and I can keep trying (a few tips on getting that text would be helpful too).

 

Thanks!

 

i7-6700K

Gigabyte-Z170MX-Gaming 5

GTX 980

64 GB 2400 RAM

480GB SSD

Clover (latest build) with dual boot windows 10 on a separate SSD

Share this post


Link to post
Share on other sites

I had a completely working system and had the web driver working in DP2 from the posts above. Once I installed the new b07 build today, I get a endless reboot loop after initial restart. Can only boot with nv_disable=1 - can't boot with -x, -f, or -F and "-v debug=yes" gives me no useful information. It stops at different places every time, no panic, nothing I can read that indicates what is causing the reboot. There does seem to be a lot of entires containing 80211, not sure if that is normal or not, even if it isn't what would that have to do with the Nvidia web drivers?

 

Anyone have any ideas? I would post the output of verbose but my first attempt to do so didn't work correctly so if that would help, let me know and I can keep trying (a few tips on getting that text would be helpful too).

 

Thanks!

 

i7-6700K

Gigabyte-Z170MX-Gaming 5

GTX 980

64 GB 2400 RAM

480GB SSD

Clover (latest build) with dual boot windows 10 on a separate SSD

Same prob i have on eVGA GTX 970 and X99 chipset. looks like GPU pm problem.

Share this post


Link to post
Share on other sites

Hi,

 

same problem as above, it seems like the problem is that the web driver is not being loaded, NVDAStartupWeb:official is shown during boot. I'm using nvda_drv=1 as boot argument (this works fine for El Capitan) but for some reason it's being ignored in Sierra. Any suggestion to force web driver load?

 

Similar configuration that jsimpson746, but with 750Ti

 

 

Cheers

 

 

Sorted, I had to set manually nvda_drv=1 in the nvram, hope it helps.

Share this post


Link to post
Share on other sites

I have exactly the same problem can not load the web driver under sierra, would anyone a solution. Even with the latest Clover 3590 it does not work.

Share this post


Link to post
Share on other sites

There seems to be an updated driver, I just ran the updater app and found 367.05.10.05b07

 

attachicon.gifScreen Shot 2016-07-08 at 19.29.37.png

 

Try running

sudo kextcache -system-prelinked-kernel

Worked for me with my 970

 

Edit: scratch that, it worked for 2 reboots now I'm back to black screens without nv_disable :\

edit2: well, after running the command a few more times it does seem to have worked. I think there might be a kernel cache issue in the public beta and dev preview 2

^try. it took a few attempts but it boots up fine every time now

GTX 970

Share this post


Link to post
Share on other sites

Same prob i have on eVGA GTX 970 and X99 chipset. looks like GPU pm problem.

Οκ guys i found my solution

instal clover from here > http://www.insanelymac.com/forum/files/getdownload/18258-clover-v23k-special-edition-v3/

and chose two consecutive times (with restart) to use webdrivers from nVidia driver manager.

 

post-783357-0-23332800-1468078451_thumb.jpg

 

Update

and patching for Macpro 6.1 works nice too.

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 t0mmenhansen
      I havent used my hackintosh in a while. I wanted to boot to my mac drive. This error comes up when i try to boot. Ive tryed using explorer++ and update the lilu kext and whatevergreen kext, no luck yet. Any ideas?
       
      9700k
      16GB corsair
      1080 nvidia card
      z370-f mobo
      mac drive is an SSD from kingston
      Display port outpoot
       
    • By fantomas1
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au))
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

    • By fusion71au
      Clover r4961 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4961 for VMware.zip". Mount Clover-v2.4k-4961-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.
×