Contribute
Register

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

Status
Not open for further replies.
If anyone tries this new driver release with a 1060 card please report back. I'm still on Sierra due to the worse graphics glitching with High Sierra.
The drivers are good enough that my High Sierra system is on par or better than my Sierra system, using a 1060. My Sierra system will often crash after being put to sleep, my High Sierra system does not. The glitches show up quickly and are resolved cleanly on Sierra, but show up after a delay and require a bit more attention to resolve on High Sierra. It's a wash for me. They are not the reason I have not yet migrated my main system to HS.
 
I thought I'd see what happens with dual display, SIP, library validation and boot-loops with 10.13.1 installed from scratch

The usual EFI. All vanilla, both displays connected to the nVidia card (HDMI & DP), CSM enabled, CSRActive Config 0x67 all the way, and iGPU disabled. Fresh installer made with createinstallmedia.

The OSX install went fine.

Got to the desktop and installed the web drivers. No error message or Gatekeeper popup.

Rebooted.

Stuck at giOconsole users blah blah.

No boot loop though and the hack was ping-able. I didn't enable screen sharing.
I rebooted with just the display port display connected. All good. i was in.

I connected the 2nd display and set it up as a separate display. I enabled screen sharing just incase. Then I rebooted with both monitors connected all good.

So it's not perfect but getting better.

The latest (usual) kexts:

FakeSMC
XHCI-200-series-injector
USBInjectAll
VoodooHDA (kext only)
IntelMausiEthernet
NVWebDriverLibValFix

The latest Clover installed UEFI, Emuvarible, OsxAptioFix2Drv, and RC scripts on target volume.

An SSDT for USB port limit and one for CPUPM.

SMBIOS iMac 18,3
 
Last edited:
Hey guys,

I tried a fresh install of HS 10.13.1, but can't get past the IOConsoleUser: gIOScreenLock State 3 error during boot. This happens right after installing the nvidia web driver. I have the web driver checked, and its the correct web driver version (latest one).

During multibeast install, i used the 14,2 iMac model.

Not sure what other info i need to provide, much appreciated for the help!
 
can somebody attach EFI folder from working system? spend 2 days for continious testing and nothing helped.
 
Thanks for all the great tips in this thread.

I have a MacBook Pro (Retina, 15-inch, Late 2013), NVIDIA GeForce GT 750M 2 GB. Only found out that I could/should install NVIDIA web drivers _after_ I had installed the 10.13.2 BETA (I'm currently running 10.13.2 Beta (17C76a)).

Incidentally, I'm still seeing problems with Google Chrome in 10.13.2 which are triggered when the NVIDIA discrete graphics card is in use (https://bugs.chromium.org/p/chromium/issues/detail?id=773705 and other bugs)

Couple of questions:

1. Has anyone running 10.13.1 and equivalent hardware to mine had success with the webdrivers?
2. Is there a BETA version of the NVIDIA drivers available that I can install with 10.13.2?

Thanks
 
Big Note: With the 378.10.10.10.15.120 driver, you no longer need to change your SIP setting - just install normally. Update is accomplished in the same manner. However, you will get the error message shortly into the installing process; click continue to complete the installation and reboot. You're good to go. :thumbup:

Therefore, the below procedures are no long need. I'll leave them for a while as a possible method to debug.






Note: There are some problems installing the initial Nvidia drivers (378.10.10.10.15.114) for High Sierra (HS) 10.13.0. This was my solution to the kext install error and resulting black screen. In my initial HS installation, I used the System Definition iMac14,2, and I did not add/need any other graphics kexts (e.g. Lilu.kext, Shiki.kext, NVWebDriverLibValFix.kext, etc).

Note: If you have the black screen and can't get into your HS system, then boot into the Recovery system. Then, from the top menu: Utility > Terminal. In the Terminal, remove the Nvidia drivers with the following Terminal commands:
Code:
cd /Volumes/yourHSdiskname/System/Library/Extensions/
rm -R GeF*.*
cd /Volumes/yourHSdiskname/Library/Extensions/
rm -R GeF*.* NVDA*.*
cd /Volumes/yourHSdiskname/
sudo touch ./Library/Extensions/ ./System/Library/Extensions/
Reboot. For some reason, the above breaks audio. So, if you can get along without it while trying the below procedure, I'll tell you how to regain audio below.


Installation

Note: If you have install the first High Sierra 10.13.0 build and have the Nvidia drivers installed, see Post #518 for the short method to update with the 10.13.0 Supplemental update. I believe that method will also work with any HS 10.13.0 installer dated Oct 05, 2017 and newer.


I am testing High Sierra on my Gene system with a NVMe and (temporary) a GTX 1060 with the SysDef iMac14,2. HS was easy to install (over a GM installation), but when I went to install the Nvidia drivers...well, I experience the problems you all have had. So, benefiting from your efforts, I successfully installed the drivers doing the following:

:ch: Mount the HS drive's EFI partition and change the SIP setting (CsrActiveConfig) from MultiBeast's default 0x3 to 0x0 which turns on SIP and save;

:ch: Make sure that the Security and Privacy System Preference pane General tab setting for "Allow apps downloaded from:" is set to "App Store and identified developers";

:ch: Reboot;

:ch: Once back to the Desktop, open the Security and Privacy System Preference pane and make sure the General tab is showing;

:ch: Start the Nividia install process;

:ch: During the installation, a window with a message like "The [...] kext is not signed and, in the Security and Privacy System Preference pane, you can approve its installation" (or something like that);

:ch: Once you approved the installation of that kext, the installer will complete and ask to your click on the "Restart" button...Don't do it yet;

:ch: In the Terminal, "touch" the two major kext directories:
Code:
sudo touch /Library/Extensions/ /System/Library/Extensions/

:ch: Now, mount the EFI partition and change the SIP (CsrActiveConfig) setting back to 0x3 and NvidiaWeb setting to "true";

:ch: Reboot;

:ch: The update "breaks" audio, so download and run toleda's audio_cloverALC-130.sh script from: GitHub - toleda/audio_CloverALC: OS X Realtek ALC onboard audio with Clover;

:ch: Reboot again.

You should be good to go! :thumbup:

Unfortunately, the GTX 1060 has worst glitching upon wake up from sleep then it did in Sierra. As a result, this problem caused me to reboot since the usual fixes couldn't be tried. :mad:

Thanks. Problem solved.
 
The drivers are good enough that my High Sierra system is on par or better than my Sierra system, using a 1060. My Sierra system will often crash after being put to sleep, my High Sierra system does not. The glitches show up quickly and are resolved cleanly on Sierra, but show up after a delay and require a bit more attention to resolve on High Sierra. It's a wash for me. They are not the reason I have not yet migrated my main system to HS.

I took the plunge and updated to HS. Now I get a full on lockup when the drivers glitch out and have to hard reboot. No Kernel panic, and I cannot SSH or Remote desktop into the machine. I've disabled sleep and it is fine but I really wish it would sleep properly like it did in Sierra. I never should have updated.
 
I took the plunge and updated to HS. Now I get a full on lockup when the drivers glitch out and have to hard reboot. No Kernel panic, and I cannot SSH or Remote desktop into the machine. I've disabled sleep and it is fine but I really wish it would sleep properly like it did in Sierra. I never should have updated.

Did you use Multi-beast and other outdated methods that modify and install 3rd party kexts into the system? Upgrades are usually not a problem when you go vanilla and have a tight config.
 
Did you use Multi-beast and other outdated methods that modify and install 3rd party kexts into the system? Upgrades are usually not a problem when you go vanilla and have a tight config.

No it's just loading 4 or so kexts from the EFI partition with clover. This is not an upgrade issue, it's a problem with the Nvidia Web drivers. They are awful and they are 5x awful on HS.
 
I upgraded to HS thinking that I would be headed for a better life with my 1060 6GB. Turns out not to be so. Same issues and now the 'hot corner put display to sleep' fix no longer works. Considering just getting rid of the 1060 and replacing with something that works - any recommendations?
 
Status
Not open for further replies.
Back
Top