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

Phil511 · July 30, 2016

@Faun, thanks to your Nvidia web driver for PB1 as it works perfectly with my system. Any chance you will have Nvidia web driver for Public Beta 2 soon?

oraton · July 30, 2016

For those having success with latest web driver and PB1, does this include Pascal support? Anyone having success with the 10xx series cards?

ergot · July 31, 2016

Hi ergot

No, no NVIDA inject in EFI/CLOVER/config.plist

Did you use bootflag nv_disable=1 until Webdrivers where installed ?

I suppose you did an Webdriver install before using nvda_drv=1 ? latest is here

This app.can update and search new drivers and download and then install them automaticaly !

Understand that a clean Sierra PB2 install contains already Nvidia drivers but your card is not natively recognized !

The alternative Webdrivers you need are beta

My Clover folder doesn't help you beacause we have very different hardware and the Webdriver are not in EFI/CLOVER !

Good luck

Thanks

I have the latest web drivers, i did not used nvda flag until installing web drivers...nothing helped...

Brumbaer · July 31, 2016

@ergot I haven't read all of the thread, so this might be a repeat.

For one there is/was a problem with nvda_drv in config.plist. It has to be in the nvram and you might need the nvram emulation efi driver to get it working.

Second. I use my GTX970 since 10.11.3 with the corresponding Webdrivers. I alway uses DP to connect.

With DP3 and the latest Webdriver, It doesn't work anymore - but it does if I use HDMI.

Probably one or the other might help.

@ROBASEFR · August 2, 2016

Updated to PB3 16A270f) but no support for my GC card (yet)

patience for new webdriver beta....

TheRacerMaster · August 4, 2016

New Web Driver is out, ~~presumably~~ for 10.12 DB4 (PB3?).

August 4, 2016

...and still no support for Pascal. :blush:

(I mean, no GP100.kext inside)

jsl · August 5, 2016

New Web Driver is out, ~~presumably~~ for 10.12 DB4 (PB3?).

This new Nvidia Web Driver not working for GTX-980 display card yet in my hackintosh.

Anyone got it working for GTX-980 or GTX-970 in 10.12 beta 2 to beta 4 ?

Dontview · August 5, 2016

This new Nvidia Web Driver not working for GTX-980 display card yet in my hackintosh.

Anyone got it working for GTX-980 or GTX-970 in 10.12 beta 2 to beta 4 ?

GTX 970 here. New driver working fine in DP 4. I use the display port.

Brumbaer · August 5, 2016

Indeed σomething strange is happening to these drivers.

On DispalyPort and just updating have "negative" colors.

i change on HDMI and working nice again.

DP 4 ~ GTX 960 X99 chipset

There seems a change in the underlying data structure, but the already saved values of the screen preferences are not updated to that data structure.

Change resolution or orientation of the monitor in question forth and back.

It will rewrite the values and the display will be ok again.

asdesoso · August 5, 2016

Anyone that has GT610 working on Sierra DP4? It doesn´t work since DP1 on Sierra, only "works" if I put nv_disable=1 on Clover, but it doesn´t have QE/CI.

I tried with InjectNvidia and with Web drivers, but it stucks in a black screen.

Best regards.

drowsyhaze · August 6, 2016

Just upgraded over an existing 10.11.6 installation yesterday to PB3 but can't get these kexts to load with my GTX 970, with or without nvda_drv=1. Any reason this might be?

The only change I made to Clover was an update from 3333 to 3676 and SMBIOS from MacPro3,1 to imac11,2, imac11,3, imac14,2, and macpro5,1, but no luck with any of them.

ergot · August 6, 2016

update to PB3 with the latest web drivers i still cannot get full acceleration with my GPU...in boot i use nada_drv=1 but even if i don't use this boot flag i still can boot the system...

Is there a place where i need to "clean" boot arguments or something like this?

nvram -xp don't show nvda_drv , even when adding one sudo nvram nvda_drv=1 i still cannot boot properly

any suggestion will be appreciated

thanks

Gurqn · August 6, 2016

update to PB3 with the latest web drivers i still cannot get full acceleration with my GPU...in boot i use nada_drv=1 but even if i don't use this boot flag i still can boot the system...

Is there a place where i need to "clean" boot arguments or something like this?

nvram -xp don't show nvda_drv , even when adding one sudo nvram nvda_drv=1 i still cannot boot properly

any suggestion will be appreciated

thanks

i think nvidia webdriver no longer expose nvda_drv=1. I noticed that when upgraded today. So just added that to clover boot arguments, that's all. Everything works properly for now.

Pavo · August 6, 2016

i think nvidia webdriver no longer expose nvda_drv=1. I noticed that when upgraded today. So just added that to clover boot arguments, that's all. Everything works properly for now.

Sure it does, running GTX 970 on MacPro 5,1 right now with macOS 10.12 DP4 with web drivers and working fine

drowsyhaze · August 6, 2016

Sure it does, running GTX 970 on MacPro 5,1 right now with macOS 10.12 DP4 with web drivers and working fine

Incidentally, I'm not able to assign boot arguments to the nvram, which seemed like it might be the solution, and get this error:

claes2:~ claes$ sudo nvram boot-args="nvda_drv=1"
nvram: Error setting variable - 'boot-args': (iokit/common) general error

Any reason this might be?

P.S. On legacy PBR, here are my nvram parameters according to terminal:

bootercfg	(%00
fmm-computer-name	claes
prev-lang:kbd	en:0
security-mode	none
Clover.KeepBackupLimit	0
SystemAudioVolumeDB	%f2
SystemAudioVolume	0
LocationServicesEnabled	%01
csr-active-config	%03%00%00%00
Clover.NVRamDisk	Yes

CSR Status (does this even matter?):

System Integrity Protection status: enabled (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: enabled
	DTrace Restrictions: enabled
	NVRAM Protections: enabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Any thoughts on why my installation won't load the web drivers?

Here's my boot.plist if it helps:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<false/>
			<key>Fixes</key>
			<dict>
				<key>AddDTGP_0001</key>
				<true/>
				<key>FixHDA_8000</key>
				<true/>
				<key>FixHPET_0010</key>
				<true/>
				<key>FixIPIC_0040</key>
				<true/>
				<key>FixUSB_1000</key>
				<true/>
			</dict>
			<key>Name</key>
			<string>DSDT.aml</string>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>PatchAPIC</key>
		<true/>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>Generate</key>
			<false/>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>dart=0 nvda_drv=1</string>
		<key>Debug</key>
		<true/>
		<key>DefaultVolume</key>
		<string>osx</string>
		<key>Legacy</key>
		<string>PBR</string>
		<key>Secure</key>
		<false/>
		<key>Timeout</key>
		<integer>2</integer>
		<key>XMPDetection</key>
		<string>Yes</string>
	</dict>
	<key>CPU</key>
	<dict>
		<key>UseARTFrequency</key>
		<false/>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>Inject</key>
			<string>1</string>
		</dict>
		<key>FakeID</key>
		<dict>
			<key>IMEI</key>
			<string>0x0</string>
			<key>LAN</key>
			<string>0x0</string>
			<key>NVidia</key>
			<string>0x0</string>
			<key>SATA</key>
			<string>0x0</string>
			<key>WIFI</key>
			<string>0x0</string>
			<key>XHCI</key>
			<string>0x0</string>
		</dict>
		<key>USB</key>
		<dict>
			<key>FixOwnership</key>
			<false/>
			<key>Inject</key>
			<false/>
		</dict>
	</dict>
	<key>DisableDrivers</key>
	<array>
		<string>Nothing</string>
	</array>
	<key>GUI</key>
	<dict>
		<key>CustomIcons</key>
		<true/>
		<key>Hide</key>
		<array>
			<string>henrietta</string>
			<string>EXTRA</string>
			<string>frederick</string>
			<string>Windows</string>
			<string>\EFI\BOOT\BOOTX64.EFI</string>
		</array>
		<key>Language</key>
		<string>en:0</string>
		<key>Mouse</key>
		<dict>
			<key>DoubleClick</key>
			<integer>500</integer>
			<key>Enabled</key>
			<true/>
			<key>Mirror</key>
			<false/>
			<key>Speed</key>
			<integer>8</integer>
		</dict>
		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Kernel</key>
			<string>All</string>
			<key>Legacy</key>
			<string>First</string>
			<key>Linux</key>
			<false/>
			<key>Tool</key>
			<true/>
		</dict>
		<key>ScreenResolution</key>
		<string>1920x1080</string>
		<key>Theme</key>
		<string>mac</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>NvidiaSingle</key>
		<false/>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>Debug</key>
		<false/>
		<key>KernelCpu</key>
		<false/>
		<key>KernelHaswellE</key>
		<false/>
		<key>KernelLapic</key>
		<false/>
		<key>KernelPm</key>
		<true/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>t1-AppleHDA/Resources/xml>zml</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				eG1sLnps
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				em1sLnps
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>t1-10.12-AppleHDA/Realtek ALC...</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				ihnUEQ==
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				AAAAAA==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>t1-10.9-10.12-AppleHDA/Realtek ALC889</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				ixnUEQ==
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				iQjsEA==
				</data>
			</dict>
		</array>
	</dict>
	<key>RtVariables</key>
	<dict>
		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x3</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>BiosReleaseDate</key>
		<string>10/07/10</string>
		<key>BiosVendor</key>
		<string>Apple Inc.</string>
		<key>BiosVersion</key>
		<string>MP51.88Z.007F.B03.1010071432</string>
		<key>Board-ID</key>
		<string>Mac-F221BEC8</string>
		<key>BoardManufacturer</key>
		<string>Apple Inc.</string>
		<key>BoardType</key>
		<integer>11</integer>
		<key>ChassisAssetTag</key>
		<string>Pro-Enclosure</string>
		<key>ChassisManufacturer</key>
		<string>Apple Inc.</string>
		<key>ChassisType</key>
		<string>06</string>
		<key>Family</key>
		<string>Mac Pro</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>Mobile</key>
		<false/>
		<key>ProductName</key>
		<string>MacPro5,1</string>
		<key>SerialNumber</key>
		<string>XB20274SEUH</string>
		<key>Trust</key>
		<false/>
		<key>Version</key>
		<string>1.0</string>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>Detect</string>
		<key>InjectSystemID</key>
		<true/>
	</dict>
</dict>
</plist>

Original post:

Just upgraded over an existing 10.11.6 installation yesterday to PB3 but can't get these kexts to load with my GTX 970, with or without nvda_drv=1. Any reason this might be?

The only change I made to Clover was an update from 3333 to 3676 and SMBIOS from MacPro3,1 to imac11,2, imac11,3, imac14,2, and macpro5,1, but no luck with any of them.

Pavo · August 6, 2016

System Integrity Protection status: enabled (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: enabled
	DTrace Restrictions: enabled
	NVRAM Protections: enabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Well since you have NVRAM Protections: enabled then I would say yes it matters

drowsyhaze · August 6, 2016

Thank you - I think I have found a solution! Hopefully it works for others!

First, I changed my the Rt Variable "CsrActiveConfig" from 0x03 to 0x67 in Clover, as per these instructions (useful resource as SIP management is more nuanced now than it was). This allowed me to add boot arguments to the nvram:

sudo nvram boot-args="nvda_drv=1"

Checked with nvram -p and the change had been committed! So, I reboot, but still no Nvidia kexts!

Then, I used this command, as per a forum post that can not be named:

sudo nvram nvda_drv

Which produced these results with nvram -p:

boot-args	dart=0 nvda_drv=1
bootercfg	(%00
Clover.KeepBackupLimit	0
nvda_drv	1
prev-lang:kbd	en:0
SystemAudioVolumeDB	%02
security-mode	none
Clover.NVRamDisk	Yes
fmm-computer-name	claes
csr-active-config	g%00%00%00
SystemAudioVolume	%01
LocationServicesEnabled	%01

Rebooted and the kext has loaded! Thanks for all of the help!

ergot · August 7, 2016

nothing helped me...i think the boot arg nvda_drv is not saved or clear in reboot in plist file.

anyone know how to edit this file manually?

UPDATE

Make it work! bcuz nvram did not saved my string I installed EMU driver in clover folder and script by clover, used nvram boot-args='nvda_drv=1' and after boot I had black screen..good so far meaning its working but since I am using SMBIOS macpro6,1 I used AGDPfix and now I have full acceleration with web drivers

Gurqn · August 7, 2016

Sure it does, running GTX 970 on MacPro 5,1 right now with macOS 10.12 DP4 with web drivers and working fine

So you didn't manually add this argument and nvidia web driver automatically added that when you installed correct ? It was a case with El Capitan, however same behaviour cannot be seen for Sierra. It's strange, argument also appears in my nvram right now but it's because of clover i think.

@drowsyhaze

Also thank you for detailed instructions.

Pavo · August 7, 2016

So you didn't manually add this argument and nvidia web driver automatically added that when you installed correct ? It was a case with El Capitan, however same behaviour cannot be seen for Sierra. It's strange, argument also appears in my nvram right now but it's because of clover i think.

No I did not manually add this argument, and yes I am using macOS Sierra 10.12 DP4, all I did was install the web drivers but you also have to remember I do not use a hack, using a real Mac Pro 5,1. Since thats the case and seems like a lot of people are having issues maybe Clover is having issues adding arguments to nvram.

Gurqn · August 7, 2016

No I did not manually add this argument, and yes I am using macOS Sierra 10.12 DP4, all I did was install the web drivers but you also have to remember I do not use a hack, using a real Mac Pro 5,1. Since thats the case and seems like a lot of people are having issues maybe Clover is having issues adding arguments to nvram.

Ah i see now, thank you for that, I wasn't know that you are using real 5.1. As you guessed, it's probably related to clover i think. Let's see how it will end up, I'm using hack as 6.1.

Thanks again.

ergot · August 8, 2016

Any news with CUDA support?

fantomas · August 9, 2016

Nvidia Web Driver 367.10.10.05b01 has been updated to support the last macOS Sierra beta 5 (16A286a)

Check the first page, #1.

Regards

Gurqn · August 9, 2016

Nvidia Web Driver 367.10.10.05b01 has been updated to support the last macOS Sierra beta 5 (16A286a)

Check the first page, #1.

Regards

Little bit confused here, is there any change when comparing with current driver, it's just recently released ? Nvidia panel indicate that there are no update yet, so is that modified same blob for DP5 ? Thanks

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

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites