Contribute
Register

Solving NVIDIA Driver Install & Loading Problems

slim.jim said:
There is no support for Pascal GPUs in El Capitan. You must be running at least 10.12.4 with the 378.05.05.05f01 driver.
Click to expand...
Thanks for the quick response. Maybe you can help me with another issue ive had when trying to boot sierra on the same system specs. I would be able to boot from a usb just fine but once i tried to boot off of the hard drive after instillation I would get stuck on the apple loading screen for roughly 30 minutes before the monitor would shut off. I would restart the monitor and the system would have loaded or just reset to clover. Any idea why?

thanks again for the speedy response its much appreciated
 
Build 1
ROG MAXIMUS IX HERO |  i7 7700 |  GeForce GTX 1060 6GB SC
Jake4004 said:
Thanks for the quick response. Maybe you can help me with another issue ive had when trying to boot sierra on the same system specs. I would be able to boot from a usb just fine but once i tried to boot off of the hard drive after instillation I would get stuck on the apple loading screen for roughly 30 minutes before the monitor would shut off. I would restart the monitor and the system would have loaded or just reset to clover. Any idea why?

thanks again for the speedy response its much appreciated
Click to expand...

This is a topic for another thread in another section of the forum.
 
K3NS4N said:
I have same problem

I use Gigabyte ga-z270xp-sli and evga gtx 1070 SC
I tried so much solutiones but doesn't work.
We need help.
:(
Click to expand...

Don't know about Pascal series 10xx cards, but as in my post https://www.tonymacx86.com/threads/...loading-problems.161256/page-255#post-1592220 I was able to install drivers and working with a Gtx970oc.
The only problem is that it reset to OSX Drivers whenever I restart. But it' doesn't seem to make a difference on El capitan. Haven't installed any GPU becnchmarking on the Mac system yet.
 
Slim Jim,
Somehow I was offered a supplementary update to 10.12.6 that no one else has noted, or installed. It has changed my build number to 16G1023 from 16G29. This may be a Beta sup. and it was offered to me through the Apple store on 10/4/2017.

Kernel Version: Darwin 16.7.0
Boot Volume: SIERRA
Boot Mode: Normal
Computer Name: DASBOOTS iMac
User Name:
Secure Virtual Memory: Enabled
System Integrity Protection: Disabled
Time since boot: 21 minutes

Nvidia web driver version: 378.05.25F01 is installed
here is a screen print of the update on my machine:
BETA%20OS%20SUPPLIMENTARY%2016G1023_zpsrhzmdbwa.jpg

It states it is Security Update for Public Beta 2017-001 Version 10.12.6 Installed on 10/4/2017

This macOS Sierra 10.12.6 update improves security, stability and compatibility of your Mac, and is recommended for all users.
For more detailed information about this update, please visit https://support.apple.com/kb/HT20735
For more detailed information about the security content of this update, please visit: https://support.apple.com/kb/HT201222

Neither link shows info for this.
After editing the build number in the NVDAStartupWeb.kext Plist the following happened:

A message popped up stating the NVDAStartupWeb.kext could not load as it was not installed properly. Video rolls at login, then settles down. I would say kernel extension(s) for Nvidia are not loading, and this is confirmed in the extension list under system report “loaded NO”. all Nvidia kexts no say NO.
This the plist text for:NVDAStartup.kext for my machine currently (also current machine is using a GTX 1060)
< key>NVDAStartup</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.NVDAStartup</string>
<key>IOClass</key>
<string>NVDAStartup</string>
<key>IOMatchCategory</key>
<string>IOFramebuffer</string>
<key>IOPCIClassMatch</key>
<string>0x03000000&amp;0xff000000</string>
<key>IOPCIMatch</key>
<string>0x000010de&amp;0x0000ffff</string>
<key>IOProbeScore</key>
<integer>100000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>IOSourceVersion</key>
<string>10.17.5</string>
<key>NVDARequiredOS</key>
<string></string>
<key>NVDAType</key>
<string>Official</string>

This is the plist text for NVDAStartupweb.kext:
< key>NVDAStartup</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.nvidia.NVDAStartupWeb</string>
<key>IOClass</key>
<string>NVDAStartupWeb</string>
<key>IOMatchCategory</key>
<string>IOFramebuffer</string>
<key>IOPCIClassMatch</key>
<string>0x03000000&amp;0xff000000</string>
<key>IOPCIMatch</key>
<string>0x000010de&amp;0x0000ffff</string>
<key>IOProbeScore</key>
<integer>200000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>NVDARequiredOS</key>
<string>16G1023</string>
<key>NVDAType</key>
<string>Web</string>
</dict>
Does the NVDARequiredOS key have to have 16G1023 for both kexts or only the web? Obviously I have to unlock permissions to change Plist text(s) in either of these? You will note NVDAStartup.kext does not have an OS build number in the string line...
Further is there any editing required in my Clover Plist to allow the current Web driver to function again that was working perfectly before this beta fiasco? Drive show loaded now in NVida Control Panel in Mac menu bar. I have repaired permissions and rebuilt kext caches.
 
ginosse21 said:
Hello there, I have Sierra installed on my custom mac but ii will not work with my EVGA GTX 1060 6gb, when i install the web driver my system doesn't recognize the graphic card, some one can help me to solve this problem??
Thanks
Click to expand...
This answer is for everyone!!!! Basically it is not an answer. YOU MUST HAVE ALL THE COMPONENTS YOU ARE USING LISTED UNDER YOUR AVATAR ORRRRR IN THE QUESTION YOU ARE ASKING!
YOU MUST HAVE THE OS VERSION YOU ARE USING, 10.12.6 OR 10.13.X AND THE BUILD NUMBER. SIERRA HAS 7 VERSIONS 10.12.1 TO 10.12.6 AND ONE EXTRA BETA BUILD.
If your system information/graphics section does not show your card, the the Nvidia Web driver (correct version) is not loading.
Even if it shows loaded in the Nvida Control Panel.
If it is not loading for what ever reason you must have a specific boot flag for the web driver in you clover Plist. This can be accomplished by using Clover Configurator or editing you Plist manually. The instructions are in a sticky in the forum in the Graphics section for the manual edit. The web driver must be the proper version for the build you are using. You can uninstall any build from the Nvida control panel but it must be unlocked to accomplish this. I or the moderators cannot answer questions without the machine and OS info completed in some manner. The old Nvida boot flag to disable, WILL disable the new web driver as well it cannot be in the boot mix, as an added boot flag or in your current Clover Plist!!
 
dasboot5 said:
This answer is for everyone!!!! Basically it is not an answer. YOU MUST HAVE ALL THE COMPONENTS YOU ARE USING LISTED UNDER YOUR AVATAR ORRRRR IN THE QUESTION YOU ARE ASKING!
YOU MUST HAVE THE OS VERSION YOU ARE USING, 10.12.6 OR 10.13.X AND THE BUILD NUMBER. SIERRA HAS 7 VERSIONS 10.12.1 TO 10.12.6 AND ONE EXTRA BETA BUILD.
If your system information/graphics section does not show your card, the the Nvidia Web driver (correct version) is not loading.
Even if it shows loaded in the Nvida Control Panel.
If it is not loading for what ever reason you must have a specific boot flag for the web driver in you clover Plist. This can be accomplished by using Clover Configurator or editing you Plist manually. The instructions are in a sticky in the forum in the Graphics section for the manual edit. The web driver must be the proper version for the build you are using. You can uninstall any build from the Nvida control panel but it must be unlocked to accomplish this. I or the moderators cannot answer questions without the machine and OS info completed in some manner. The old Nvida boot flag to disable, WILL disable the new web driver as well it cannot be in the boot mix, as an added boot flag or in your current Clover Plist!!
Click to expand...

Sorry, i didn't update my signature, at the moment i don't have a OS version cause i can't finish my installation because of the graphic driver. I will check tomorrow again and i will tell you!! Thanks
 
Mac Pro
GA-Z97X-GAMING 3 |  i7 4790 |  GeForce GTX 1060 6GB Single Fan
dasboot5 said:
Slim Jim,
Somehow I was offered a supplementary update to 10.12.6 that no one else has noted, or installed. It has changed my build number to 16G1023 from 16G29. This may be a Beta sup. and it was offered to me through the Apple store on 10/4/2017.

Kernel Version: Darwin 16.7.0
Boot Volume: SIERRA
Boot Mode: Normal
Computer Name: DASBOOTS iMac
User Name:
Secure Virtual Memory: Enabled
System Integrity Protection: Disabled
Time since boot: 21 minutes

Nvidia web driver version: 378.05.25F01 is installed
here is a screen print of the update on my machine:
BETA%20OS%20SUPPLIMENTARY%2016G1023_zpsrhzmdbwa.jpg

It states it is Security Update for Public Beta 2017-001 Version 10.12.6 Installed on 10/4/2017

This macOS Sierra 10.12.6 update improves security, stability and compatibility of your Mac, and is recommended for all users.
For more detailed information about this update, please visit https://support.apple.com/kb/HT20735
For more detailed information about the security content of this update, please visit: https://support.apple.com/kb/HT201222

Neither link shows info for this.
After editing the build number in the NVDAStartupWeb.kext Plist the following happened:

A message popped up stating the NVDAStartupWeb.kext could not load as it was not installed properly. Video rolls at login, then settles down. I would say kernel extension(s) for Nvidia are not loading, and this is confirmed in the extension list under system report “loaded NO”. all Nvidia kexts no say NO.
This the plist text for:NVDAStartup.kext for my machine currently (also current machine is using a GTX 1060)
< key>NVDAStartup</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.NVDAStartup</string>
<key>IOClass</key>
<string>NVDAStartup</string>
<key>IOMatchCategory</key>
<string>IOFramebuffer</string>
<key>IOPCIClassMatch</key>
<string>0x03000000&amp;0xff000000</string>
<key>IOPCIMatch</key>
<string>0x000010de&amp;0x0000ffff</string>
<key>IOProbeScore</key>
<integer>100000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>IOSourceVersion</key>
<string>10.17.5</string>
<key>NVDARequiredOS</key>
<string></string>
<key>NVDAType</key>
<string>Official</string>

This is the plist text for NVDAStartupweb.kext:
< key>NVDAStartup</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.nvidia.NVDAStartupWeb</string>
<key>IOClass</key>
<string>NVDAStartupWeb</string>
<key>IOMatchCategory</key>
<string>IOFramebuffer</string>
<key>IOPCIClassMatch</key>
<string>0x03000000&amp;0xff000000</string>
<key>IOPCIMatch</key>
<string>0x000010de&amp;0x0000ffff</string>
<key>IOProbeScore</key>
<integer>200000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>NVDARequiredOS</key>
<string>16G1023</string>
<key>NVDAType</key>
<string>Web</string>
</dict>
Does the NVDARequiredOS key have to have 16G1023 for both kexts or only the web? Obviously I have to unlock permissions to change Plist text(s) in either of these? You will note NVDAStartup.kext does not have an OS build number in the string line...
Further is there any editing required in my Clover Plist to allow the current Web driver to function again that was working perfectly before this beta fiasco? Drive show loaded now in NVida Control Panel in Mac menu bar. I have repaired permissions and rebuilt kext caches.
Click to expand...

You should only need to change the web version of the kext. If you use terminal with the command sudo nano and then the path to the kext you do not need to unlock it or change any permissions to modify it. You will have to make sure SIP is fully disabled though because modifying the kext breaks the signature on it.
 
ginosse21 said:
Sorry, i didn't update my signature, at the moment i don't have a OS version cause i can't finish my installation because of the graphic driver. I will check tomorrow again and i will tell you!! Thanks
Click to expand...

We need more details about what is happening and what you have done so far.
 
slim.jim said:
You should only need to change the web version of the kext. If you use terminal with the command sudo nano and then the path to the kext you do not need to unlock it or change any permissions to modify it. You will have to make sure SIP is fully disabled though because modifying the kext breaks the signature on it.
Click to expand...

I modified the kext through terminal as instructed, rebuilt kext cache and kernel caches as instructed through terminal. The Web driver shows loaded in Nvidia control panel in menu bar but is not loading.This is what shows for the startup extension:
NVDAStartupWeb:

Version: 10.18.5
Last Modified: 7/20/17, 10:29 AM
Bundle ID: com.nvidia.NVDAStartupWeb
Loaded: No
Get Info String: NVDAStartupWeb 10.18.5 (378.05.05.25f01)
Obtained from: Unknown
Kind: Intel
Architectures: x86_64
64-Bit (Intel): Yes
Location: /System/Library/Extensions/NVDAStartupWeb.kext
Kext Version: 10.1.8
Loadable: No
Authentication Errors:
Authentication Failures:
File owner/permissions are incorrect (must be root:wheel, nonwritable by group/other): /System/Library/Extensions/NVDAStartupWeb.kext, Info.plist
Signature Validation Errors: Kext signature validation error code -67030
Dependencies: Satisfied
Signed by: Unknown

also this is the text info from the terminal command to rebuild kext cache:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext USBInjectAll.kext
TruStudioPCUSBAudioPlugin.kext does not appear in strict exception list for architecture: x86_64
kext-dev-mode allowing invalid signature -67007 0xFFFFFFFFFFFEFA41 for kext TruStudioPCUSBAudioPlugin.kext
SBUSBAudioDriver.kext does not appear in strict exception list for architecture: x86_64
kext-dev-mode allowing invalid signature -67007 0xFFFFFFFFFFFEFA41 for kext SBUSBAudioDriver.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_GPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_XHCIMux.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AtherosE2200Ethernet.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AHCI_3rdParty_SATA.kext
NVDAStartupWeb.kext has incorrect permissions; omitting.
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleHDA.kext
AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion.
AppleDataSetManagement.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
TruStudioPCUSBAudioPlugin.kext does not appear in strict exception list for architecture: x86_64
SBUSBAudioDriver.kext does not appear in strict exception list for architecture: x86_64
AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion.

Got it fixed, when I manually set permissions, in the kext, some items were read / write , had to change all, to write only, and rebuild cache and repair permissions, now working flawlessly.
 
Last edited:
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top