High Sierra and The Nvidia Web Driver

[Spacedust]

For unflashed cards, just remove NVIDIA card after removing the kext and the system is about to restart. Then put flashed card and finish the installation, then install new web driver, shutdown the system, install non-flashed card and boot normally

[Asgorath]

I just went through the 17A405 update, confirmed that I'm seeing the panic as well.  Booting into safe mode and nuking the StartupWeb kext allowed me to boot as expected, and then I was able to install the new web driver.

[Rominator]

Maybe someone could post this simple fix at Tony's board

24 pages of hand wringing and reformatting and rm-ing every GeForce kext ever written

They're using a shotgun to kill a cockroach

[mysticalos]

I told em how more than once, it gets buried by them continuing to make it difficult.

Plus they mod their kexts to hell and back with lilu and other injectors injecting into into driver to fix things that should be fixed with hot patching/ssdt/DSDT, which completely hoses libval and window server which is why they need even more fixes like nvidialibvalfix on 10.13 even though unmoddied drivers no longer need it.

what really gets me is how many of them keep spreading false info that you need to turn SIP back on just to install or upgrade drivers then turn it off again after. Such nonsense. The only thing turning SIP on is replacingthe "unknown error" with a permission prompt to authorize driver install. clicking continue with SIP off to skip the unknown error works just as well without all that fumbling.

[vgermax]

Blindly (stupidly) updated.

Tried recovery mode, "safe mode", etc. with no luck
Yanked card
Booted headless
SSH in
Deleted .kext
Updated to R117

[lowrider]

New Web Driver:

https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.15.120.pkg

Still no Cuda Driver.

Lou

[mysticalos]

People at tony mac still using shotguns on cockroaches. Turning SIP on just to install update, then turning it back off. Why? to fix a COSMETIC error where installer complains with unknown error if SIP is off (even though hitting continue everything works just fine).

I do wish nvidia would just add check to install though and if sip is disabled and gatekeeper is anywhere, don't request permissions or whatever that throws the cosmetic error. It truly is inconsequential though and certainly doesn't need completely unnecessary work arounds.

[mysticalos]

Users have noticed that system profiler has changed with todays update

Under Graphics/Display it used to say
  Metal:   Supported

But now says
  Metal:   Supported, feature set OSX_GPUFamily1 v2

OSX_GPUFamily1 v2 means Metal 1.2 feature set support (not Metal 2 with is v3)


Of course maybe that's always been there and people only noticing now.

I know it's there with stock driver. just don't know if it was V2 with previous web drivers

[eVasilis]

This may be of interest: https://forums.developer.apple.com/thread/88150, where it is mentioned that the reporting of OSX_GPUFamily1 v2 in High Sierra is a bug as all macs which support metal support OSX_GPUFamily1 v3 features.

[vgermax]

Haven't updated yet and System Profiler still says

Metal:   Supported, feature set OSX_GPUFamily1 v2

[mysticalos]

Ok so as other poster said that's an odd apple bug

[lowrider]

Yea!!!!!  Cuda Driver finally here:

http://www.nvidia.com/object/macosx-cuda-9.0.214-driver.html

Lou

[Asgorath]

New driver for 17A405 is out:

https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.15.121.pkg

[lowrider]

^^^^Another one???  That's the third Web Driver for that Build?  Thanks for there post!

Lou

[mysticalos]

I wondered what could be so important to push yet another update out after last one (update 2 was pushed to fix a serious metal regressions that caused severe flickering that was quite bad for epilepsy or other sensitive conditions).

So what was left for yet another update to fix?
The Panic in nvidiastartupweb if it loads on an unsupported OS version. By changing OS build number for sake of testing, it seems 221 now correctly passes control over to stock driver without exploding the whole system.

This means that if you are on 10.13.0, install this update now, so that when 10.13.1 comes out, you shouldn't have dick around with removing the old driver before updating. it should correctly handle things now, making the upgrade procedure go back to normal.

Of course, one should still always have good backups, and I hope anyone who got caught in reboot loop last time with pants down has learned from that