netkas.org forum

General Category => OSX and Graphics Cards => Topic started by: Rominator on September 27, 2017, 08:18:58 AM



Title: High Sierra and The Nvidia Web Driver
Post by: Rominator on September 27, 2017, 08:18:58 AM
How's it working', folks?


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on September 27, 2017, 08:24:12 AM
The metal hitching is gone finally. the first non broken 378 driver. the last good performance metal driver was 367, which means this is first pascal supporting driver that should actually feel good in metal games.

It no longer breaks ibooks/little snitch etc because they refactored driver to not break those apps with library injection, well that or they got apple to finally allow them to do it. But it is clear the driver had some serious refactoring, for example half of it is now installed in system/library/extensions and other half in library/extensions instead of all in one place.

The installer does seem to be broken though. it errors out during install, but if you tell it to ignore error and continue anyways it still works, for most users. Although some users on hackintosh forums are reporting that upon reboot the drivers are hosed for them, so it's possible depending on when installer errors or what causes it, some users get the install to still work and others do not?. nvidia will have to fix package installer at some point. if you're not sure you got full package can always triple check all files made it to where they should be with pacifist then manually kextcache rebuild for good measure.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on September 27, 2017, 03:21:41 PM
Works fine for me.  However, the Cuda Driver. now 9.0.197 does NOT work in High Sierra, but does work in Sierra.

Lou


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Spacedust on September 27, 2017, 07:07:39 PM
It was made for 10.12, not 10.13, so we need to wait for proper CUDA driver.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on September 28, 2017, 12:27:59 AM
^^^^This morning it was linked to High Sierra.  They then Nvidia unlinked it and put a message that another Cuda Driver was coming.  So, YES, I know that!

Lou


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Asgorath on September 28, 2017, 12:38:53 AM
Just finished the upgrade, everything went smoothly.  I ignored the error message during the installer, and forced a kext cache rebuild before rebooting just to be safe.  I left NVWebDriverLibValFix in /Library/Extensions, as the WindowServer appears to have LV enabled:

Code:
~> codesign -d -v  /System/Library/PrivateFrameworks/SkyLight.framework/Resources/WindowServer
Executable=/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier=com.apple.WindowServer
Format=Mach-O thin (x86_64)
CodeDirectory v=20100 size=391 flags=0x2000(library-validation) hashes=5+5 location=embedded
Platform identifier=4
Signature size=4485
Info.plist entries=4
TeamIdentifier=not set
Sealed Resources=none
Internal requirements count=1 size=72

I have SIP disabled since I'm running a Hackintosh, and so the LV fix seems to be required.  I don't have access to an unmodified/official Apple system to test what would happen if SIP was left enabled.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on September 28, 2017, 12:45:20 AM
What's interesting, I had sip disabled entire time on my hack, and i can use drivers witout issue and without lvfix as well. in fact little snitch and ibooks etc also had full windows without libvalfix. ultimately I decided to add the fix anyways anyways just in case.

One thing I did notice, no one could boot without libvalfix if they were using Lilu or whatever it is for audio instead of toledo's patch, so maybe Lilu itself just dirty's up kext environment enough to need libval to fix it? who knows.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Asgorath on September 28, 2017, 01:00:30 AM
What's interesting, I had sip disabled entire time on my hack, and i can use drivers witout issue and without lvfix as well. in fact little snitch and ibooks etc also had full windows without libvalfix. ultimately I decided to add the fix anyways anyways just in case.

One thing I did notice, no one could boot without libvalfix if they were using Lilu or whatever it is for audio instead of toledo's patch, so maybe Lilu itself just dirty's up kext environment enough to need libval to fix it? who knows.

Right, those things modify the binaries and those will absolutely be rejected unless you have LV disabled.  I might try booting without the LV fix since I'm not using Lilu or anything like that.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Rominator on September 28, 2017, 01:25:48 AM
Well, I can tell you this.

One HS issue with new driver is that the dock is solid with Titan-X Maxwell, yet 2 displays work and Uningine Valley seemed to run at 1/2 speed.

Anyhow, I tossed in a GTX680 and with Web Driver it had the solid Dock

Turned off Web Driver and the Dock went translucent, as it is meant to be.

With Web Driver off the 680 2GB ndid a 37 FPS in Uningine. The Titan-X did 25 FPS.

So, seems like it isn't quite done being baked.Hopefully they issue a fix shortly.

If Nvidia needs testing done on real Macs and a variety of their cards, I'd be the best person to talk to. I've pretty much got at least one of everything.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: chromafile on September 28, 2017, 02:19:41 AM
For High Sierra :D

https://www.nvidia.com/download/driverResults.aspx/125379/en-us
https://www.nvidia.com/object/macosx-cuda-9.0.197-driver.html


Title: Re: High Sierra and The Nvidia Web Driver
Post by: macfriedchikkin on September 28, 2017, 02:34:10 AM
For High Sierra :D

https://www.nvidia.com/download/driverResults.aspx/125379/en-us
https://www.nvidia.com/object/macosx-cuda-9.0.197-driver.html
The first one, yes, the second, no.


Hey, Rom, are those your results trying to use 2 monitors? I'm getting the same results under HS as I did under Sierra for Unigine; exactly 58.5


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on September 28, 2017, 02:49:41 AM
For High Sierra :D

https://www.nvidia.com/download/driverResults.aspx/125379/en-us
https://www.nvidia.com/object/macosx-cuda-9.0.197-driver.html

Did you not read my third post down on this very page ???  The Cuda Driver you linked (9.0.197)  DOES NOT work with High Sierra!

Lou


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on September 28, 2017, 02:53:21 AM
Rominator:

I just ran Heaven and Valley.  My results are much like Sierra was.

No issues with my dock.

Lou


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Rominator on September 28, 2017, 03:02:42 AM
I'm out and won't be able to fiddle with it anymore for a few hours.

This just popped up on my blog :

    
Hi David,
Andy D has just posted a comment on your blog post, New High Sierra drivers out:
All working with a GTX 1080 Ti here now. The trick I had is that Gatekeeper wants to block loading of the kernel extension. I got a pop-up message while installing. Once installation of the driver is complete, don't reboot - load System Preferences, head to Security and Privacy and click 'Allow' next to the 'NVIDIA Corporation' notification. Then, force-quit the installer and run it again. This time, no message from Gatekeeper. Reboot and the driver is spot on.

The CUDA driver v9.0.197 (installed using the same Gatekeeper method) does complain that an update is required, but it did that occasionally in the last version too, so I'm not going to worry about that.

In System Information the Metal status reports 'Supported, feature set OSX_GPUFamily1 v2'. I have no idea what that means; hopefully it's good.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on September 28, 2017, 06:24:44 AM
^^^^Goodness - Cuda Driver 9.0.197 DOES NOT work in High Sierra, works fine in Sierra!!!!!  Nvidia has posted the attached on it's Web Site when searching for the High Sierra Web Driver.

Lou


Title: Re: High Sierra and The Nvidia Web Driver
Post by: jeanlain on September 28, 2017, 07:08:31 AM
Rominator:

I just ran Heaven and Valley.  My results are much like Sierra was.

No issues with my dock.

Lou
Unigine doesn't use Metal, so it's not surprising that performance hasn't improved.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on September 28, 2017, 07:27:37 AM
I tested performance in WoW and fornite (both use metal). wow is much better but has a new water reflections bug that causes pretty erratic flickering, but easily avoided by turning water to "fair". across board performance is better in WoWs metal engine

fortnite performance is about same as before, i didn't notice any improvement. the game still has shotty code in a few places, like a hard freeze when opening map for first time in any new game. still super playable though with good performance minus the little freezes when first loading assets.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Zodi on September 28, 2017, 02:01:11 PM
Doesn't work for me!
I tested on one of my MacPro's without success...

I installed 10.13 on a new hard disk partition, the installation works fine
but after after the installation of NVIDIA Web-driver and reboot I saw only the grey error screen :-(
Also after PR-reset...

(addition)
If I boot with pressed shift-key without extensions (also nvidia) the Mac boots,
but with a terrible speed..



Modellname:   Mac Pro
  Modell-Identifizierung:   MacPro5,1
  Prozessortyp:   6-Core Intel Xeon
  Prozessorgeschwindigkeit:   2,66 GHz
  Anzahl der Prozessoren:   2
  Gesamtanzahl der Kerne:   12
  L2-Cache (pro Kern):   256 KB
  L3-Cache (pro Prozessor):   12 MB
  Speicher:   48 GB
  Geschwindigkeit für Prozessorverbindungstyp:   6,4 GT/s
  Boot-ROM-Version:   MP51.0084.B00
  SMC-Version (System):   1.39f11
  SMC-Version (Prozessormodul):   1.39f11



Title: Re: High Sierra and The Nvidia Web Driver
Post by: Spacedust on September 28, 2017, 03:59:25 PM
What is your GPU?


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Spacedust on September 28, 2017, 04:03:30 PM
What really makes me annoyed right now is the lack of APFS support in Windows. Now I'm unable to reboot to macOS with an unflashed card, because it cannot see the APFS partition. I have to put EFI GPU, then press ALT at boot to choose macOS drive manually.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Zodi on September 29, 2017, 07:14:43 AM
What is your GPU?

GTX970, standard PC card, unflashed bios!
NVIDIA GeForce GTX 970:

  Chipsatz-Modell:   NVIDIA GeForce GTX 970
  Typ:   GPU
  Bus:   PCIe
  Steckplatz:   Slot-1
  PCIe-Lane-Breite:   x16
  VRAM (gesamt):   4095 MB
  Hersteller:   NVIDIA (0x10de)
  Geräte-ID:   0x13c2
  Versions-ID:   0x00a1
  ROM-Version:   VBIOS 84.04.36.00.6e
  Metal:   Unterstützt


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Rominator on September 29, 2017, 12:18:41 PM
Yes, this driver and its interaction with High Sierra and APFS...something didn't get finished before it got rushed out.

Let's hope the .1 version is fully functional.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Asgorath on September 29, 2017, 03:01:29 PM
How is APFS related exactly?

To everyone who is having problems: please check your system logs for errors, and post them here.  That includes panic logs or crash logs for things like the WindowServer.  Really hard to figure out what's going wrong without more information.  The vast majority of issues I've seen across a number of forums all boil down to the driver binaries not loading, because Apple changed the way they're using Library Validation.  The most obvious fix for that is to use the LV hack kext, but there are other workarounds as well.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on September 29, 2017, 03:14:57 PM
Could I post the related (I think) part of the log here?


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Asgorath on September 29, 2017, 03:21:06 PM
Sure.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on September 29, 2017, 03:29:19 PM
Sep 29 10:41:06 localhost bootlog[0]: BOOT_TIME 1506670866 0
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.cdscheduler" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.install" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.family.asl" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.callhistory.asl.conf" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.contacts.ContactsUICore" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.authd" sharing output destination "/var/log/asl" with ASL Module "com.apple.asl".
   Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
   Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.authd" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.eventmonitor" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.secinitd" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.mail" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.coreaudio" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.performance" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.iokit.power" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.icloud.fmfd" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:33 --- last message repeated 2 times ---
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.contacts.ContactsAutocomplete" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.mkb" sharing output destination "/private/var/log/keybagd.log" with ASL Module "com.apple.mkb.internal".
   Output parameters from ASL Module "com.apple.mkb.internal" override any specified in ASL Module "com.apple.mkb".
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.mkb" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.CoreDuetAdmissionControl" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.MessageTracer" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.networking.boringssl" sharing output destination "/Library/Logs/CrashReporter" with ASL Module "com.apple.networking.networkextension".
   Output parameters from ASL Module "com.apple.networking.networkextension" override any specified in ASL Module "com.apple.networking.boringssl".
Sep 29 10:41:28 localhost syslogd[38]: Configuration Notice:
   ASL Module "com.apple.clouddocs" claims selected messages.
   Those messages may not appear in standard system log files or in the ASL database.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1]: Early boot complete. Continuing system boot.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system): Could not import service from caller: path = /System/Library/LaunchDaemons/com.apple.platform.ptmd.plist, caller = launchd.1, error = 138: Service cannot be loaded on this hardware
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.cmio.AVCAssistant): ThrottleInterval set to zero. You're not that important. Ignoring.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.diskmanagementd): ThrottleInterval set to zero. You're not that important. Ignoring.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.diskmanagementd): The TimeOut key is no longer respected. It never did anything anyway.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system): com.apple.CoreRAID (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.multiversed): Unknown key for dictionary: DEFAULT-OPTIONS
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.syslogd): The HopefullyExitsLast key is no longer respected. Please remove it.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.syslogd): Please switch away from OnDemand to KeepAlive.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system): com.apple.opendirectoryd (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.opendirectoryd): This service is defined to be constantly running and is inherently inefficient.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (org.cups.cupsd): Service has increased maximum shutdown time to 60 seconds. This will create a poor experience for the user.
Sep 29 10:41:25 localhost com.apple.xpc.launchd[1] (com.apple.mobile.keybagd): This key does not do anything: OnDemand
Sep 29 10:41:28 localhost syslogd[38]: ASL Sender Statistics
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSPerAppTokenMap is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3ce70) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363b600). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSPerAppTokenMapEntry is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3ce98) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363b628). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSCertificateStorage is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3cd30) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363b830). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSPreferences is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3cec0) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363bb50). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSSystemUser is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3cee8) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363bce0). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSMultiUserMode is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3ce20) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363c230). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSIncomingMessage is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3cd80) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363c348). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSLog is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3cda8) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363c398). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSMessage is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3cdd0) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363c410). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSMultiUserFS is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3cdf8) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363c460). One of the two will be used. Which one is undefined.
Sep 29 10:41:29 localhost apsd[76]: objc[76]: Class APSOutgoingMessage is implemented in both /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService (0x7fff89c3ce48) and /System/Library/PrivateFrameworks/ApplePushService.framework/apsd (0x10363c4d8). One of the two will be used. Which one is undefined.
Sep 29 10:41:30 localhost Installer Progress[67]: Progress UI App Starting
Sep 29 10:41:30 localhost com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.system): Service "com.apple.ManagedClient.startup" tried to hijack endpoint "com.apple.ManagedClient.agent" from owner: com.apple.ManagedClient
Sep 29 10:41:30 localhost systemstats[49]: assertion failed: 17A365: systemstats + 179634 [FB138264-8F86-3462-9C53-FC084690A767]: 0x0


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on September 29, 2017, 03:30:03 PM
This at the time of the failed startup


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Asgorath on September 29, 2017, 06:42:31 PM
This at the time of the failed startup

Okay, there's nothing related to the NVIDIA drivers or WindowServer there, so not sure what's going wrong.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on September 29, 2017, 09:39:11 PM
I don't know what this means, but Cuda Driver 8.0.90 works in High Seurra!

Lou


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Rominator on September 30, 2017, 10:47:21 AM
How is APFS related exactly?



Last night I finally had my SATA SSD take the Web Driver Without giving me the error message. It is an OCZ Agility 512 GB SATA SSD.

I waited excitedly for the reboot and to finally see Web Driver working in HS.

Instead I got a constant grey screen.

Somehow, on THAT BOOT, the SSD has gone dead. It (by definition) just got APFS "update" format.

The Web Driver wasn't working.

I PRAM reset and reinstalled HS and Web Driver.

Now the drive is locked up and dead. If it is on the SATA bus at boot, the machine hangs until I remove it.

If I use a SATA to USB3 adapter, it is invisible.

There are well documented APFS issues like this. May be 100% Apple APFS.

But fact that it was on a Web Driver reboot makes me unhappy.

I solved Nvidia Web Driver issues with m,ultiple PRAM resets and reinstalls. There is some issue here that nobody wants to own.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on September 30, 2017, 11:50:08 AM
Okay, there's nothing related to the NVIDIA drivers or WindowServer there, so not sure what's going wrong.

Thanks, Asgorath! I noticed that both times when that happened, I had an external drive switched on. This is a dump drive where everything downloaded is temporarily stored there. This particular drive has been converted to APFS and has trouble loading. Before HS, with hfs+, the drive was readily available, with its icon appearing on the desktop, once the boot up of my mac was complete. This is not the case any more and it takes quite some time for it to become available. Could this be related? Mind you, the drive, a 1 TB WD Red, sits inside an oldish USB 2 enclosure.

Thanks


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Asgorath on September 30, 2017, 02:41:00 PM
Right, I skipped the APFS upgrade using the instructions from Rehabman, and haven't seen anything like those problems.  The High Sierra web driver just worked for me on the first reboot.

I've heard lots of reports of APFS performing much worse than HFS+, particularly on mechanical hard drives.  If you're using APFS on a WD Red, that could definitely be the problem.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on September 30, 2017, 03:16:25 PM
At least I can live with that, for the time being...

Thanks


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on September 30, 2017, 04:21:14 PM
Hmm, I've been running High Sierra on my SM951 since the release of the Web Driver.  No issues, except some startup items are not starting up.  I need to activate them manually.  And as I previously posted Cuda Driver 9 does not work, but the latest Cuda Driver 8 does?  Otherwise no issues.  Only my SM951 has been converted to APFS, I've left my other drives alone for now.  And, BTW, TRIM is still turned on.  My GPU is an MVC flashed Gigabyte GTX 1080 Gaming.  The two FW updates also went well on my cMP 5,1 with the flashed card.

Lou  


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Spacedust on October 01, 2017, 12:50:42 PM
I've switched back to HFS+ just by doing backup from HDD to SSD with Carbon Copy Cleaner, then again from HDD to SSD and all works well as before. Drive is visible under Windows and I can switch OS'es without any trouble.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on October 01, 2017, 09:32:45 PM
With the exception of my boot disk which is only 500 GB, the rest in my mac pro are 4TB blacks, two of which in raid 0. Getting a 500 GB SSD to replace my boot disk is feasible; the rest, there is no way in hell I can afford the premium... It sucks.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on October 01, 2017, 10:14:04 PM
not sure how this thread got off of topic of HFS vs APFS and HDDs, but this is nvidia driver thread.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on October 01, 2017, 11:56:30 PM
I'm out and won't be able to fiddle with it anymore for a few hours.

This just popped up on my blog :

    
Hi David,
Andy D has just posted a comment on your blog post, New High Sierra drivers out:
All working with a GTX 1080 Ti here now. The trick I had is that Gatekeeper wants to block loading of the kernel extension. I got a pop-up message while installing. Once installation of the driver is complete, don't reboot - load System Preferences, head to Security and Privacy and click 'Allow' next to the 'NVIDIA Corporation' notification. Then, force-quit the installer and run it again. This time, no message from Gatekeeper. Reboot and the driver is spot on.

The CUDA driver v9.0.197 (installed using the same Gatekeeper method) does complain that an update is required, but it did that occasionally in the last version too, so I'm not going to worry about that.

In System Information the Metal status reports 'Supported, feature set OSX_GPUFamily1 v2'. I have no idea what that means; hopefully it's good.


See Post #24 here:

https://forums.macrumors.com/threads/new-nvidia-web-driver-has-my-1080-tis-working-in-hs-10-13-sort-of.2073935/#post-25156726

Lou


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on October 05, 2017, 09:36:37 PM
Goes without saying but todays security update breaks web driver.

However for first time ever, it doesn't just break it, it REALLY breaks it, even if it's disabled.

I figured per usual driver would compare to OS build number, refuse to load and fall back to reg driver on boot. nope. it goes into a kernel panic loop until you boot off a diff volume, and remove it. like it coudln't even be present on system post update.

EDIT
but the usual hacks to force them to load, still work. so the drivers panic if they try not to load, but work if they do..hmm

that's quite ironic really. the very check in driver designed to prevent instability by refusing to load, is actual cause of panic. FORCING driver to load anyways by editing that build number resolves that panic. ha. I think nvidia at very least should look into why it's not peacefully handing off to stock driver without causing a panic.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on October 06, 2017, 09:55:54 PM
I guess there won't be an updated driver until 10.13.1


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Rominator on October 06, 2017, 10:05:04 PM
https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.15.117.pkg

But working on the procedure

Courtesy of Mysticalos hint, simply removing the NVDAStartupWeb.kext from Library/Extensions and rebooting lets you get to desktop with flashed cards (and likely Hackintosh too)

Please note, this is not System/Library/Extensions but just Library/Extensions


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Asgorath on October 06, 2017, 11:17:47 PM
I guess there won't be an updated driver until 10.13.1

What makes you say that?  As usual, there was a new web driver within 24 hours of the security update going live.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Rominator on October 06, 2017, 11:20:37 PM
Full procedure at macvidcards.com in the Blog.

Works on EFI cards that need Web Driver

Can't speak for other configs.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Spacedust on October 06, 2017, 11:23:32 PM
What about unflashed cards?


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on October 07, 2017, 01:51:27 AM
https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.15.117.pkg

But working on the procedure

Courtesy of Mysticalos hint, simply removing the NVDAStartupWeb.kext from Library/Extensions and rebooting lets you get to desktop with flashed cards (and likely Hackintosh too)

Please note, this is not System/Library/Extensions but just Library/Extensions
Yeah the problem was definitely in startupweb. removing it, or convincing it to load web driver, both resolved issue in my tests. But panic ensued if it was present an build number didn't match. Most interesting was panic backtrace would be the apple nvidia drivers not web drivers, like it was some kind of bad/dirty handoff. I'm confident nvidia will fix this oversight but i also think it's a safe bet for safety measures when next security or point release comes out, to be safe we should def avoid startupweb doing any driver handoff until we're sure it's safe.

users who are already stuck in panic loop, who don't have access to emergency/backup boot volumes, have found that simply pulling any nvidia card will allow you to reach desktop too to delete kext. then shut down reinsert nvidia card. boot back up and get new driver and good to go. this of course requires access to an IGP or an AMD card on hand to power display.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on October 07, 2017, 07:18:19 AM
I guess there won't be an updated driver until 10.13.1

What makes you say that?  As usual, there was a new web driver within 24 hours of the security update going live.

Just a very wrong prediction. I thought that with 10.13.1 being near, it would made sense for nvidia to wait for it. I am glad I was wrong!


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Spacedust on October 07, 2017, 03:00:59 PM
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 ;)


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Asgorath on October 07, 2017, 04:50:21 PM
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.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: Rominator on October 07, 2017, 07:41:54 PM
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


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on October 07, 2017, 11:57:12 PM
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.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: vgermax on October 10, 2017, 08:00:52 PM
Blindly (stupidly) updated.

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



Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on October 16, 2017, 11:56:04 PM
New Web Driver:

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

Still no Cuda Driver.

Lou


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on October 17, 2017, 01:01:12 AM
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.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on October 17, 2017, 01:08:37 AM
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


Title: Re: High Sierra and The Nvidia Web Driver
Post by: eVasilis on October 17, 2017, 09:41:13 AM
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.


Title: Re: High Sierra and The Nvidia Web Driver
Post by: vgermax on October 17, 2017, 07:02:44 PM
Haven't updated yet and System Profiler still says

Metal:   Supported, feature set OSX_GPUFamily1 v2


Title: Re: High Sierra and The Nvidia Web Driver
Post by: mysticalos on October 18, 2017, 12:29:23 AM
Ok so as other poster said that's an odd apple bug


Title: Re: High Sierra and The Nvidia Web Driver
Post by: lowrider on October 18, 2017, 07:06:34 PM
Yea!!!!!  Cuda Driver finally here:

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

Lou