Jump to content
fantomas1

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

1,060 posts in this topic

Recommended Posts

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

Share this post


Link to post
Share on other sites
Advertisement

@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? 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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...

Share this post


Link to post
Share on other sites

@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.

Share this post


Link to post
Share on other sites

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

d38QtMk.png

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 ?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

There seems a change in the underlying data structure, but not 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.

u have right bro.. fixed.

Thanks

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

 

PIOXz15.png

Share this post


Link to post
Share on other sites

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.

 

 

 

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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 :)

post-474300-9372_thumb.png

Share this post


Link to post
Share on other sites

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.

 

 

2016_08_07_15_07_47.png

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.
×