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

If I turn off "Windows 8/10 features" by selecting "Other OS" The CSM settings disappear but the system uses whatever CSM setting they were set to. Of course CSM Disabled works fine if only 1 display is connected.
Previously CSM brought low-res boot screens mirrored on both monitors and then the same blank screens before login. So i just used the UEFI GOP and a push button HDMI switch hanging below one of the monitors to save the cable pins.
 
New 121 driver and CUDA driver out. All good it seems and doesn't require sip. Just ENTER and ignore error, before reboot fix permissions and caches just in case!

https://images.nvidi...0.10.15.121.pkg

Yes!! Confirmed works like before. Just update ignore error and hit continue and restart. Was getting annoying having to enabling sip and all that stuff before and after every Nvidia update
 
Screen Shot 2017-10-26 at 10.47.35 PM.png


NVIDIA Alternate Graphics Drivers for macOS 10.13.0 (17A405) (LATEST)
https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.15.121.pkg (LATEST)

Updated top post with the newly released drivers. :thumbup:
 
Last edited:
Hey guys,

I've any thing in my Hackintosh working, just there are some micro lags in the apps (safari to start and tabs, dashboard open, etc..) and this is really bored. Any fix?

ylQyvBm.jpg
 
I turned on screen sharing and file sharing. But this time, I decided to change the General Security settings so auto login was allowed and no password prompt from sleep. Installed the iTunes 12.7 update. Rebooted a couple of times without changing anything else - then I installed the .120 drivers. I got the error during install and rebooted. Blank non initialized monitors but after a while they initialized but were blank. No problem, I'll just VNC in. WRONG. Just a black screen. I rebooted twice trying to VNC in each time. Same thing VNC showed a black rectangle and sometimes the connection would drop.
I turned off auto login and tried to log into my maintenance account to update something unrelated, last used installing the .114 web driver apparently. Result, blank screen and kicked back to login window after a few seconds. Could speculate that auto login creates a constant blank screen while the login retries/fails. Logged into my regular account and found removing ~/Library/ByHost/com.apple.windowserver* for the problem account resolved the issue and i was able to login. Working .121 web drivers were incompatible with the previous version of that file. The last 'blast from the past' concerning the web drivers on 10.13 on this machine i hope.
 
What new/fixed with 121? Like to see change log
 
I turned off auto login and tried to log into my maintenance account to update something unrelated, last used installing the .114 web driver apparently. Result, blank screen and kicked back to login window after a few seconds. Could speculate that auto login creates a constant blank screen while the login retries/fails. Logged into my regular account and found removing ~/Library/ByHost/com.apple.windowserver* for the problem account resolved the issue and i was able to login. Working .121 web drivers were incompatible with the previous version of that file. The last 'blast from the past' concerning the web drivers on 10.13 on this machine i hope.

I am going to remember that file in case it happens again.

I just got through experiencing some more janky-ness with HS. The install that does not need Library validation to boot with dual display -

I booted into it so I could change CSRActive Config to 0x0 and install .121. While I was changing CSRActive Config, Nvidia popped up telling me about the new driver. I said no. Changed CsrActiveConfig to 0x0, then rebooted and was greeted with the boot loop.

I know that means "library borked" and I need a "validation kext". But I don't understand how changing from 0x67 to 0x0 would cause that. I think when Nvidia notified me of the update, that is when something got borked. So just for the heck of it, I changed back to 0x67 and tried to get back in. Nope boot loop. SIGH. Dropped in NVWebDriverLibValFix.kext and was able to get back in. To avoid more drama, I rebooted 0x0, installed web drivers then rebooted 0x67 - all good
 
Last edited:
YMMV but .121 appears to be a solid improvement for me with a GTX1060. I've only tested a bit, but my graphics performance is back to what it was in Sierra. I had a lot of lag since upgrading and it's quite snappy now.
 
Status
Not open for further replies.
Back
Top