Jump to content

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


fantomas
 Share

1,025 posts in this topic

Recommended Posts

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

If you are still not updated to PB4 or DP5 than you will not see any update, once you update the OS you will see the update.

I suggest to download first the update of web drivers than update OS and update web drivers.

I am going to try this now...

 

UPDATE

update to BP4 breaks my GPU...I have installed the latest drivers but i have many glitches on top of windows and top bar

 

P.s

the app will not show new drivers, I am downloading the latest build for the OS and check again...

Link to comment
Share on other sites

Question to those brave guys of you who are using it in a daily basis:
How many bug there are to be fixed and how does it affects you in your dally tasks? I'm asking that coz this hack im using is my daily driver and I don't wanna screw it all up although still wanna update.

 

My spects are on sign but im now running this 750TI I bought this week, works well.

Link to comment
Share on other sites

There might be hardware problems for you, I'm not quite sure that because of webdriver, I'm on DP5, still using same webdriver. There was problem with Airmail but it's also seems fixed with DP5, I can say pretty stable.

  • Like 1
Link to comment
Share on other sites

Odd, I just installed the Sierra PB and this is my build number; 16A284a. I'm getting a black screen on my 970, I had to swap in my 680 in the mean time. WebDriver Updater finds no drivers for my OS build.

 

EDIT: EVGA 970, black screen. With 680, perfect. Same results with HDMI, DVI-D or wiping kernel caches. Considering WebDriver Updater doesn't find a driver for my OS build I think the latest drivers might be for the DP5 only.

 

EDIT 2: Well, considering the NVIDIA Web Drivers are activated while using the 680 I'm guessing there's a bug with it working with my 970

Link to comment
Share on other sites

There might be hardware problems for you, I'm not quite sure that because of webdriver, I'm on DP5, still using same webdriver. There was problem with Airmail but it's also seems fixed with DP5, I can say pretty stable.

 

PB3 was working just fine,  i think its compatibility issue with my GPU 

  • Like 1
Link to comment
Share on other sites

Question to those brave guys of you who are using it in a daily basis:

How many bug there are to be fixed and how does it affects you in your dally tasks? I'm asking that coz this hack im using is my daily driver and I don't wanna screw it all up although still wanna update.

 

My spects are on sign but im now running this 750TI I bought this week, works well.

 

Then beta software is not for you. You should wait for the official version.

Link to comment
Share on other sites

Then beta software is not for you. You should wait for the official version.

Not such universal rule. I've seen and even tried pretty stable betas like Windows 10 previews, those were pretty stable. Usually, betas tend to come quite stable as release date comes around (not trying to be captain obvious here)

besides Apple historically not religiously release their final product in September "This fall" and that is around the corner already. But I understand where you came with this idea from and this is true most of the time.

Link to comment
Share on other sites

Not such universal rule. I've seen and even tried pretty stable betas like Windows 10 previews, those were pretty stable. Usually, betas tend to come quite stable as release date comes around (not trying to be captain obvious here)

besides Apple historically not religiously release their final product in September "This fall" and that is around the corner already. But I understand where you came with this idea from and this is true most of the time.

 

You seeked advice and I gave you mine, what you with it is your business. Surely, you will die if you don't upgrade now...just do it.

At least, be smart and install it on a different drive or partition to test it if you cannot afford your 'daily driver' to fail

Link to comment
Share on other sites

PB4 booted with PB3 drivers for me and my 970... no driver update and no issues as far as I can tell...

 

attachicon.gifpb4970proof.jpeg

That's the kind of answer I'm looking for. You didn't tell not to do it, you didn't say it's unsafe nor that should do this or that. Thanks mate, I asked for testimonials based on your experience and that's just about what you gave me ;)

Hats off.

Link to comment
Share on other sites

That's weird... I am using driver 367.10.10.05b01 (the latest, and the same driver released for PB3) on PB4 (16A286a) with no issue... I wonder why you guys are having issues and are seeing new drivers...

 

 

That's the kind of answer I'm looking for. You didn't tell not to do it, you didn't say it's unsafe nor that should do this or that. Thanks mate, I asked for testimonials based on your experience and that's just about what you gave me ;)
Hats off.

 

Sorry - I was responding to the rest of the conversation about driver problems... I would actually strongly discourage you from installing the beta on your main machine. There are issues (it is a beta, running on unsupported hardware with a community sponsored bootloader...), as evidenced by all of the users having issues with their GTX 970s in the past page, and the problems users have been having in general with unsupported GPUs...

 

Moreover, aside from being the wrong thread, you're not really going to have much luck answering this question unless a user has the exact same hardware that you do and a similar workflow. This isn't Windows, it's OS X, running in beta with known issues on real macintoshes, on hackintoshes... you're definitely going to run into some hiccups and may even have to do some reconfiguration, and, even then, it's still a beta. Heck, skylake support, that was added in 10.11.4, hasn't even made it into 10.12 (last I checked at least)...

 

But, you know - go for it if you want to! YMMV, there are always risks, et cetera - thus is the nature of both betas and hackintoshes.

  • Like 1
Link to comment
Share on other sites

I have a Gigabyte GTX970 WindForce OC running DP5 with latest webdrivers and....... no luck :no: 

I've tried booting with and without nvda_drv=1 and my card still isn't detected..........

Link to comment
Share on other sites

Have you tried this?

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

Have you tried this?

 

It doesn't work for me and my 750Ti :

 

$ sudo nvram boot-args

nvram: Error getting variable - 'boot-args': (iokit/common) data was not found

 

$ sudo nvram nvda_drv

nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found

Link to comment
Share on other sites

It doesn't work for me and my 750Ti :

 

$ sudo nvram boot-args

nvram: Error getting variable - 'boot-args': (iokit/common) data was not found

 

$ sudo nvram nvda_drv

nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found

 

you need to disable SIP , you can use clover config set variable to 0x67

by the way for 750ti on PB 4 you will have some glitches on screen, it totally related to the web drivers 

Link to comment
Share on other sites

you need to disable SIP , you can use clover config set variable to 0x67

by the way for 750ti on PB 4 you will have some glitches on screen, it totally related to the web drivers 

 

 

I already have 0x67 in my config.plist :

<key>BooterConfig</key><string>0x28</string>
<key>CsrActiveConfig</key>
<string>0x67</string>

But doesn't work :

nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found
Link to comment
Share on other sites

What's the "nvram -p" output?

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00
Link to comment
Share on other sites

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Why don't you just add required parameter to boot arguments ? BTW attaching my config without smb

config.plist.zip

Link to comment
Share on other sites

 

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Why don't you just add required parameter to boot arguments ? BTW attaching my config without smb

 

with your config i have the same result :

$ sudo nvram nvda_drv
nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found$ sudo nvram boot-args
nvram: Error getting variable - 'boot-args': (iokit/common) data was not found$ sudo csrutil status
System Integrity Protection status: disabled.

$ sudo nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00
Link to comment
Share on other sites

 

 

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Why don't you just add required parameter to boot arguments ? BTW attaching my config without smb

 

with your config i have the same result :

$ sudo nvram nvda_drv
nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found$ sudo nvram boot-args
nvram: Error getting variable - 'boot-args': (iokit/common) data was not found$ sudo csrutil status
System Integrity Protection status: disabled.

$ sudo nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

 

Can you post your Clover config because it seems to me you got some nvram issues thats not related to web drivers

  • Like 1
Link to comment
Share on other sites

 

 

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Why don't you just add required parameter to boot arguments ? BTW attaching my config without smb

 

with your config i have the same result :

$ sudo nvram nvda_drv
nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found$ sudo nvram boot-args
nvram: Error getting variable - 'boot-args': (iokit/common) data was not found$ sudo csrutil status
System Integrity Protection status: disabled.

$ sudo nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

 

I just posted config in order to demonstrate how argument should be added. BTW I don't use any efi driver beside of aptiofix. For example "EmuVariableUefi" I don't know if it's a causing that ? You should follow what Pavo recommends.

Link to comment
Share on other sites

 Share

×
×
  • Create New...