Jump to content

Nvidia Web Driver updates for macOS Sierra (UPDATE Sept 27, 2019)

fantomas

By fantomas,
in New Releases and Updates

 Share
1,025 posts in this topic

Recommended Posts

jsimpson746
jsimpson746
Posted
Posted

When trying to 

 

 

set manually nvda_drv=1 in the nvram

I used 'sudo nvram boot-args="nvda_drv=1"' and the response I get is "nvram: Error setting variable - 'boot-args': (iokit/common) general error"

 

I have tested the nvram and confirmed values, even boot arguments I write like "-v", are retained after reboot. Though, when I rebooted it did not boot in verbose mode. So I am not sure even finding a way to add nada_drv=1 to my nvram is going to help if it is ignoring it. 

 

Why all of a sudden is the nvda flag in clover not enough for macOS? Is there a different flag I can try to force it to use the web drivers? 

Link to comment
Share on other sites
jsimpson746
jsimpson746
Posted
Posted

Ok I was able to get it to work. First thing I had to do was uninstall "EmuVariableUefi" in clover. After reboot, I was able to see the hidden file "NVRAM.plist" in the root OS directory, duplicate, edit, delete original, and replace with edited plist to include boot-arg "nvda_drv=1". Once I switched back my SMBIOS to iMac 17,1 booted up fine with the web drivers working!! Had to double check that my board id was still set to none in the graphic policy kext as well, but it was.

 

Also, I uninstalled the web drivers in the system preference pane and reinstalled during this process so that also could have helped. 

 

So now I am booting without any bootflags in clover, everything seems fine even without "dart=0" and the web driver utility is actually telling me it is using web drivers (check box next to it) which it never had done that before, so that made me happy.....haha

 

Thanks everyone for your posts as it all helped me tremdously in finally finding this solution.

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Guys, I'm getting reboots when trying to boot with the Nvidia driver on a GTX 950.

 

It used to work with DP1. Then I updated to DP2, I thought it's the driver. So now I also updated the driver, and I got the same issue: reboot on second stage boot, when booting with nvda_drv=1. The only way I can boot right now, is with nv_disable=1. But, of course, that denies the purpose of having the Nvidia driver installed in the first place.

 

Any idea what's wrong here? Am I missing something?

Link to comment
Share on other sites
@ROBASEFR
@ROBASEFR
Posted
Posted

Guys, I'm getting reboots when trying to boot with the Nvidia driver on a GTX 950.

 

It used to work with DP1. Then I updated to DP2, I thought it's the driver. So now I also updated the driver, and I got the same issue: reboot on second stage boot, when booting with nvda_drv=1. The only way I can boot right now, is with nv_disable=1. But, of course, that denies the purpose of having the Nvidia driver installed in the first place.

 

Any idea what's wrong here? Am I missing something?

I had the same problem, but now with latest Nvidia Web Driver - 367.05.10.05b07 it is Ok.

and Activate manually the Webdriver usage in Configuration panel

 

Hope this helps

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

I had the same problem, but now with latest Nvidia Web Driver - 367.05.10.05b07 it is Ok.

and Activate manually the Webdriver usage in Configuration panel

 

Hope this helps

Well, I do have that driver version. And that's exactly what I can't seem to be able to do: activate it.

 

I mean, I do activate it, it requires restart, and after restart, it goes into restart again (the issue described in my previous post). I think the driver doesn't get activated, for some reason. Just can't pin point the reason.

Link to comment
Share on other sites
dvil
dvil
Posted
Posted

Well, I do have that driver version. And that's exactly what I can't seem to be able to do: activate it.

 

I mean, I do activate it, it requires restart, and after restart, it goes into restart again (the issue described in my previous post). I think the driver doesn't get activated, for some reason. Just can't pin point the reason.

 

Do you have the variable nvda_drv 1 defined in your nvram? It seems like the bootarg option is no longer recognised by the web driver. Type sudo nvram nvda_drv=1 in the console and check that the line nvda_drv 1 appears in you nvram (sudo nvram -p) and that it is persistent between boots. boot-args nvda_drv=1 seems like it is being ignored by the web driver.

 

Hope this helps.

 

Cheers,

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Do you have the variable nvda_drv 1 defined in your nvram? It seems like the bootarg option is no longer recognised by the web driver. Type sudo nvram nvda_drv=1 in the console and check that the line nvda_drv 1 appears in you nvram (sudo nvram -p) and that it is persistent between boots. boot-args nvda_drv=1 seems like it is being ignored by the web driver.

 

Hope this helps.

 

Cheers,

 

Thanks, I'll check that tomorrow. And yes, I was using it as boot argument. In case it's not in nvram, how exactly should I go from there?

Link to comment
Share on other sites
dvil
dvil
Posted
Posted

Hi arsradu,

 

Assuming that you are using clover in UEFI only mode you need the EmuVariableUefi driver, the RC scripts and the clover control panel to be installed, if you have this options already install proceed as below, otherwise install these option and restart you machine.

 

Now, in the clover control panel go to the NVRAM variables tab and from the dropbox "Save NVRAM variables to disk" select "Always", I'm not sure if this is necessary but in my case only started to work after this.

 

Now set the nvda_drv variable to 1 in the NVRAM, type in the console sudo nvram nvda_drv=1 and press enter, check that the variable has been set to 1, type nvram -p and look for the line "nvda_drv      1", no "=" should appear. Restart you machine and hope for the best, this worked for me but as you can see in the posts above is much hit or miss with the Sierra beta 2.

 

Good luck!

Link to comment
Share on other sites
Badeendje
Badeendje
Posted
Posted

Had these troubles too with Sierra, not with El Cap before. Anyways on a hunch I also saved the nvram to the disk and now it seems to work right... but surprised by it but whatever works works...

So far have restarted 20'ish times just to make sure, both restart + cold start, and no black screens anymore =).

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Hi arsradu,

 

Assuming that you are using clover in UEFI only mode you need the EmuVariableUefi driver, the RC scripts and the clover control panel to be installed, if you have this options already install proceed as below, otherwise install these option and restart you machine.

 

Now, in the clover control panel go to the NVRAM variables tab and from the dropbox "Save NVRAM variables to disk" select "Always", I'm not sure if this is necessary but in my case only started to work after this.

 

Now set the nvda_drv variable to 1 in the NVRAM, type in the console sudo nvram nvda_drv=1 and press enter, check that the variable has been set to 1, type nvram -p and look for the line "nvda_drv      1", no "=" should appear. Restart you machine and hope for the best, this worked for me but as you can see in the posts above is much hit or miss with the Sierra beta 2.

 

Good luck!

EmuVariableUefi driver - checked

RC Scripts - checked

Save NVRAM variables to disk - set to Always, but it changes back to Auto after restart.

 

Also, setting the nvda_drv=1 in nvram is not persistent after reboot. I think I'm gonna reinstall, and start with the PB1 maybe. Hope that works.

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted
Save NVRAM variables to disk - set to Always, but it changes back to Auto after restart.

 

Do you have an existing nvram.plist at the root of your disk ? If so, try to delete it then recheck Clover prefpane on next startup.

  • Like 1
Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Do you have an existing nvram.plist at the root of your disk ? If so, try to delete it then recheck Clover prefpane on next startup/

Finally, fixed! :)

 

I think there was a bit of failure on my side, as well, since I was booting from the El Capitan SSD, instead of Sierra HDD. And even though they both have the exact same EFI content, same Clover version, I was calling for a nvram.plist that was not located on the HDD I was trying to boot from. :D So..yeah... My bad on that part.

 

Maybe my failures can help others learn so that they can avoid issues like these in the future. :)

 

By the way, now there is no nvda_drv=1 boot argument in my config anymore. And...so far so good.

 

Thank you guys so much!

  • Like 1
Link to comment
Share on other sites
Phil511
Phil511
Posted
Posted

@fantomas1,

 

Thank you for your Webdriver for Sierra public beta. It worked. 

I have GeForce GTX 960 4GB OC and I am running macOS Sierra Public Beta. 3 days in a row, when I played you tube video through Safari, after 3-4 songs, both montior screens suddenly turned black, then the disk icons reappeared while screen remaied black. Then the system crashed (unresponsive). Had to restart with restart button. Then, last night, I installed Chrome browser and played the same you tube videos, i did not experience black screens, freezes or system crashes even after 10 songs, It appeared this may be a Safari browser issue. Anybody has similar experience like me?  

  • Like 1
Link to comment
Share on other sites
ergot
ergot
Posted
Posted

Hi Guys,

I have updated to DP3 with the latest web drivers but cannot boot up, only with nv_disable flag.

I used nvram patch and checked nvram -p looks OK.

Any other idea?

I don't know if my GFX supported under 10.2..

Link to comment
Share on other sites
@ROBASEFR
@ROBASEFR
Posted
Posted

Hi, seems I have the same a strange problem as Arsradu in post 69 here when using Sierra DP2  (Clover r3652) and Clover configurator 4.31

Even if I change the bootargument from nvda_drv=1 to nv_disable=1

On booting the both are remaining ! look on image below ( -> blackscreen)

 

So I have to modifiy it manually everytime at bootscreen and then boot is OK.

 

Never saw this before !

 

I have tried to nvram -c    but it comes back everytime ...

 

Seems it picks up nvram.plist parameters from my original bootdisk (Sierra DP2) from where I newely installed Sierra-SSD (PB2)

 

Is there a thing to change in Clover configurator preferencepane concerning NVRAM ? ( Auto save or never ?)

How usefull is NVRAM on hackintosh ? ( Tidbits releaved that resetting NVRAM desactivated localisation )

 

Thanks for your lights !

 

post-305243-0-75803000-1469373931_thumb.jpg

Link to comment
Share on other sites
ergot
ergot
Posted
Posted

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.

for me no web drivers will boot with no gfx support, i have 750 TI

maybe my nvram related, how to clear nvram?

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted

for me no web drivers will boot with no gfx support, i have 750 TI

maybe my nvram related, how to clear nvram?

 

Not sure but I think it's :

 

 

sudo nvram -d

 

But I have to say that my 730 is supposed to be a Kepler. For an unknown reason, it never worked with OS X stock kexts in previous versions. Sierra fixed it but it doesn't necessarily mean that Maxwell support (i.e. for 750 Ti models) has been added…

Link to comment
Share on other sites
@ROBASEFR
@ROBASEFR
Posted
Posted

Not sure but I think it's :

sudo nvram -d

But I have to say that my 730 is supposed to be a Kepler. For an unknown reason, it never worked with OS X stock kexts in previous versions. Sierra fixed it but it doesn't necessarily mean that Maxwell support (i.e. for 750 Ti models) has been added…

no

 

sudo nvram -c

 

 

% nvram --help

nvram: (usage: no such option as --)

nvram [-x] [-p] [-f filename] [-d name] [-c] name[=value] ...

-x use XML format for printing or reading variables

(must appear before -p or -f)

-p print all firmware variables

-f set firmware variables from a text file

-d delete the named variable

-c delete all variables

name=value set named variable

name print variable

Note that arguments and options are executed in order.

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...