NVIDIA Releases Alternate Graphics Drivers for macOS High Sierra 10.13.0 (378.10.10.10.15)

[Clicky]

Interesting note: in the comments Pike R Alpha says he runs his system with SIP fully enabled and loads all unsigned kexts via the boot loader. I know this is pushing against years of inertia in this community and a bit like tilting at windmills, but it really seems like that's how things should be run in general. Guess I'm experimenting tonight...

Yeah fam, you should always load all the unsigned kexts you can from the boot-loader. Vanilla is the way to go.

 

[superic]

New driver update:

change Rt Var to 0x0, restart, update and change back to 0x67, restart.

Everything works fine, not sure if changing it back to 0x0 is necessary for updating driver, but I did it anyways.

 

[Franckd]

First of all, I'd like to thank the community of this forum for helping when we're lost. As I sure am right now.
Secondly, please, please, please be indulgent with my english. (I will try to do my best to be clear)

I'm working with a Mac Pro 5.1 mid 2012 (3,2 GHz Quad-Core Intel Xeon, ATI Radeon HD 5770 1 Go,
32 Go 1066 MHz DDR3)

I have installed High Sierra ( 10.13 17A405 ) and its latest patch.

To be honest, I'm a very dumb about about OS, drivers. But as a mainstream customer, I read that the latest Nvidia GPU (series 10) could work with Sierra . So I bought a new GPU :
ASUS GeForce GTX 1050 Ti - ROG STRIX-GTX1050TI-4G-GAMING

I have installed the latest beta drivers on nvidia website (even If i saw in the supported product list, that my GPU wasn't there). The drivers installation worked. But when I installed the new card, the screen stayed black (I have waited more than 15 mn, and tried it a few times)

When I put back my original ATI radeon card, the mac pro works.

My question : what did i do wrong. I tried to PRAM the machine (do we say that ?) and still nothing. I have tried for days, to understand, but it's a bit like reading chinese (no offense) to me. If you can help me, link me, advise me, it would be very very nice.

 

[driftwoodtv]

No. You have to involve SIP in CsrActiveConfig or you will get the usual Nvidia error saying there is a problem.

@Franckd What you did wrong was not follow the guides properly possibly. You should be able to get it working without problem. Follow that https://www.tonymacx86.com/threads/...er-on-high-sierra-black-screen-panics.234390/

 

[Franckd]

Thanks for the link Driftwoodtv !

 

[superic]

Updates:
I lost audio after updating to the latest driver. Just had to apply the audio sh again and everything works fine.

 

[driftwoodtv]

Interesting: True Metal 2 support which I don't remember seeing in the previous driver system report?

Metal: Supported, feature set OSX_GPUFamily1 v2

 

[MysticalOS]

I just don't get why everyone enables SIP to install it. the installer error if it's disabled is literally only cosmetic, you hit continue and business as usual.

 

[Clicky]

Thanks for the information. I've made a script that uninstalls previous web driver, downloads the driver package then tries to user-approve the kexts before installing and rebuilding the caches, hoping this might allow for clean installs without changing the SIP settings which is not really ideal. Credit to Pike R Alpha's for his documentation here.

Hey Vulgo,

Ok so I found a situation where I could use your script.

Not sure what number install this is but -

I install fresh again to an SSD. This time I used my same EFI but went through the Install with SIP Enabled 0x0.

Everything went fine, I turned on screen sharing and file sharing, then installed the latest web drivers (.120) and got the Gatekeeper warning. I allowed for that and rebooted.

No boot loop, my displays initialized but were blank. I was able to VNC in.
Everything looked good and after logging in my displays showed for a moment, long enough for me to set Use Separate Displays. They went blank again. Checked VNC yeah, it showed 2 displays there.

Thinking it may be something with booting with SIP enabled (0x0), i changed CSRActive Config to 0x67 -- same thing blank screens / VNC worked. I added NVWebDriverLibValFix.kext to kexts/other rebooted. Still those blank initialized displays. I rebooted a couple times going back and forth with 0x0 and 0x67 and ditched NVWebDriverLibValFix.kext. Then I rebooted again 0x67 same thing So, I ran your script sudo-ed (I noticed it downloaded .117) it said success - rebooted blank initialized screens.

Weird. This is practically the same way I installed before. The exception installing .120 from scratch and not having .117 on there first.

From VNC if I change my display settings to Mirrored - the displays activate. Then if I change to Separate the displays go blank and through VNC I go to a log in. I log in switch to Mirrored - displays activate. WTF. I think I am going to wipe and install again. Using the usual 0x67 then 0x0 to install web drivers. Maybe going with .117 first then .120. IDK fam.



UPDATE:

Ok so I installed fresh again with the same EFI using 0x67.

Then booted 0x0 to install .120 web drivers. So gatekeeper security warning and allowed. Continued with the install then changed back CSRActive Config and rebooted with 0x67 - initialized display but screens were blank.

I did not bother setting up screen sharing this time. I rebooted into a working Sierra and manually removed all the Nvidia Web drivers. That being anything in S/L/E L/E which had nvidia and or geforce with web references. Wow there were a lot. Two of the same ones. More than when installing .117.

Rebooted into High Sierra to make sure I could get in. I was in. Rebooted with 0x0. Installed Web drivers .117 (no Gatekeeper notification cause I already allowed them during the .120 install). Set CsrActive Config and rebooted with 0x67. All good displays were on but they were mirrored. Set to separate All good!

Something is up with the .120 drivers when installing fresh.


I rebooted again with 0x0, and used the Control Panel applet to install .120 rebooted with 0x67 . BOOM Displays for days!

 

[Clicky]

Hey guys, I got a strange thing going on. If I change the desktop wallpaper on my primary display, it reverts back to the original one after reboot. This behavior follows the default display only. And it only happens if I choose a picture for the wall paper. It will "remember" Solid Colors.

I saw some articles about the desktop.plist but I do not have that. I also saw some articles where this happens if the wall paper is located on another drive, but it is not. It is on the High Sierra drive. Sorry if this is newb.

EDIT: Never mind. I had to create a "new desktop" for my primary display in Mission Control, change the wallpaper on that, then close the "original desktop". WTF. High Sierra is janky AF!