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 fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • 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)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
    • 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
×