Jump to content
fantomas

Nvidia Web Driver updates for El Capitan (UPDATE 07/11/2018)

724 posts in this topic

Recommended Posts

SIP disabled ?

No, I'm using OZMOSIS don't need to disable SIP.

 

I will try to repair permissions from Recover, probably is that.

 

Thank you!

Share this post


Link to post
Share on other sites
Advertisement

No, I'm using OZMOSIS don't need to disable SIP.

 

I will try to repair permissions from Recover, probably is that.

 

Thank you!

 

If you want to modify anything in System folder, you have to disable SIP, no matter what you're using !

Share this post


Link to post
Share on other sites

 

Thank you, but no. :(

 

I had a lot of ERROR and after reboot with NVDA_DRV=1 reboot again.

...
ERROR repairing Permission for file:/System/Library/Extensions/Sandbox.kext/Contents/MacOS/Sandbox
ERROR repairing Permission for file:/System/Library/Extensions/SMARTLib.plugin/Contents/MacOS/SMARTLib
ERROR repairing Permission for file:/System/Library/Extensions/smbfs.kext/Contents/MacOS/smbfs
ERROR repairing Permission for file:/System/Library/Extensions/SMCMotionSensor.kext/Contents/MacOS/SMCMotionSensor
ERROR repairing Permission for file:/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext/BSDKernel
ERROR repairing Permission for file:/System/Library/Extensions/System.kext/PlugIns/IOKit.kext/IOKit
ERROR repairing Permission for file:/System/Library/Extensions/System.kext/PlugIns/Libkern.kext/Libkern
ERROR repairing Permission for file:/System/Library/Extensions/System.kext/PlugIns/MACFramework.kext/MACFramework
ERROR repairing Permission for file:/System/Library/Extensions/System.kext/PlugIns/Mach.kext/Mach
ERROR repairing Permission for file:/System/Library/Extensions/System.kext/PlugIns/Private.kext/Private
ERROR repairing Permission for file:/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext/Unsupported
ERROR repairing Permission for file:/System/Library/Extensions/TMSafetyNet.kext/Contents/Helpers/bypass
ERROR repairing Permission for file:/System/Library/Extensions/TMSafetyNet.kext/Contents/MacOS/TMSafetyNet
ERROR repairing Permission for file:/System/Library/Extensions/triggers.kext/Contents/MacOS/triggers
ERROR repairing Permission for file:/System/Library/Extensions/udf.kext/Contents/MacOS/udf
ERROR repairing Permission for file:/System/Library/Extensions/vecLib.kext/Contents/MacOS/vecLib
ERROR repairing Permission for file:/System/Library/Extensions/webcontentfilter.kext/Contents/MacOS/webcontentfilter
ERROR repairing Permission for file:/System/Library/Extensions/webdav_fs.kext/Contents/MacOS/webdav_fs
ERROR repairing Permission for file:/System/Library/Extensions/webdav_fs.kext/Contents/Resources/webdavfs_agent
Access time for /System/Library/Extensions updated successfully!
Access time for /Library/Extensions updated successfully!
Repair Process completed with errors!

Now we understad why.

Set CsrActiveConfig= 3 in the org.chameleon.Boot.plist (if you are using Enoch) or in RtVariables --> CsrActiveConfig= 0x03 in the config.plist in case of Clover. Reboot and retry ;)

No, I'm using OZMOSIS don't need to disable SIP.

 

I will try to repair permissions from Recover, probably is that.

 

Thank you!

Sorry I was writing.. Using Ozmosis you can boot the Recovery HD and disable SIP from there, otherwise you can't repair nothing if System Integrity protection is enabled, and Disk Utility no longer have that option

Share this post


Link to post
Share on other sites

Now we understad why.

Set CsrActiveConfig= 3 in the org.chameleon.Boot.plist (if you are using Enoch) or in RtVariables --> CsrActiveConfig= 0x03 in the config.plist in case of Clover. Reboot and retry ;)

 

Sorry I was writing.. Using Ozmosis you can boot the Recovery HD and disable SIP from there, otherwise you can't repair nothing if System Integrity protection is enabled, and Disk Utility no longer have that option

Thank you @polyzargone and @Micky1979 now worked! ;)

 

But I had to do a few steps.

  1. reboot in Recovery Mode
  2. disable SIP (csrutil disable)
  3. reboot to EL Capitan because in recovery mode I didn't have SUDO to run ./InsanelyRepairPermission
  4. In El Capitan sudo ./InsanelyRepairPermission -rt /
  5. reboot to Recory Mode
  6. reenable SIP (csrutil enable) and reboot again to El Capitan
  7. in El Capitan reeanable Nvidia in Ozmosis (nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args="nvda_drv=1")
  8. reboot for the last time.

Thank you guys!

Share this post


Link to post
Share on other sites

But I had to do a few steps.

 

3. reboot to EL Capitan because in recovery mode I didn't have SUDO to run ./InsanelyRepairPermission

You don't need to use sudo when you're in the Recovery HD. You are already logged as root ;). Just run this :

 

./InsanelyRepairPermission -rt /

6. reenable SIP (csrutil enable) and reboot again to El Capitan

Or leave it as disabled forever :). I know one could consider this is a major security break but it's a Hackintosh after all and we all used kext-dev-mode=1 in Yosemite so… Just to say.

 

I mean, having SIP constantly enabled is that important ?

Share this post


Link to post
Share on other sites

mean, having SIP constantly enabled is that important ?

IMHO yes. Consider the OS became vulnerably like Windows w/o antivirus.

Enoch and Clover can manipulate csr values with their configuration plist(s) but a value grater than 1 or at least 3 (ie file system protection + load of untrusted kexts) are not recommended.

Share this post


Link to post
Share on other sites

Enoch and Clover can manipulate csr values with their configuration plist(s) but a value grater than 1 or at least 3 (ie file system protection + load of untrusted kexts) are not recommended.

 

Agreed !

 

When I talked about disabling SIP forever, I was actually thinking of using 1 or 3 too :P.

 

I'm not sure anything greater than that is useful for most users.

Share this post


Link to post
Share on other sites

You don't need to use sudo when you're in the Recovery HD. You are already logged as root ;). Just run this :

 

./InsanelyRepairPermission -rt /

I tried this way but doesn't worked, give me a lot of error msgs like I'm not running with sudo.

 

And now from time to time lost video configuration and I need to do all the steps again to reenable, very weird. I hope Nvidia release a update driver soon.

Share this post


Link to post
Share on other sites

So, I installed the latest driver before upgrading to 10.11.4. Tried patching NVDAStartupWeb and no luck. Uninstalled driver, installed with Pacifist and manually patched it… still nothing! Tried rebooting with no caches to no avail…

 

:(

Share this post


Link to post
Share on other sites

So, I installed the latest driver before upgrading to 10.11.4. Tried patching NVDAStartupWeb and no luck. Uninstalled driver, installed with Pacifist and manually patched it… still nothing! Tried rebooting with no caches to no avail…

 

:(

Need more details about "no luck/still nothing" and your SMBios too.

Share this post


Link to post
Share on other sites

Need more details about "no luck/still nothing" and your SMBios too.

 

 

Not really sure what else to tell you. I was using MacPro6,1 in 10.11.3. I re-ran the AGDPfix (after the update, after restarting with nv_disable=1). I've reinstalled the drivers with Pacifist. I've manually patched NVDAStartupWeb's Info.plist to allow 15E and I've used "NVIDIA WebDriver Updater" utility as well. I've changed the SMBIOS to MacPro5,1 and tried reinstalling the drivers, etc, with no luck. Here's my boot.log: https://gist.github.com/levifig/6bc86b61794dff28ce98

 

FWIW, I have 2 graphics cards. My primary one (BIOS doesn't let me pick so it's the one in PCIe 16x #1) is a Radeon HD4850. My main card is on the 3rd slot and is a GTX970. I was running OS X just fine in 10.11.3: the Radeon wasn't accelerated and created a screen I didn't use (1 monitor, 2 inputs, one from each card). This problem seems to be unrelated with my setup, especially considering it worked in 10.11.3, but I thought it'd be better to share this bit!

 

Thank you for any help! :)

 

UPDATE: Not exactly sure how but it's working now. I know I changed my SMBIOS back to MacPro6,1, re-ran AGDPfix, re-ran Pacifist to install the drivers, re-patched the drivers, rebooted, hung before login screen, rebooted this time without caches and… voila: it's working! No idea what I did different… I guess I just retraced my steps and did something I could've missed the last time around. I'll keep this post here for posterity… ;)

Share this post


Link to post
Share on other sites

Not really sure what else to tell you. I was using MacPro6,1 in 10.11.3. I re-ran the AGDPfix (after the update, after restarting with nv_disable=1). I've reinstalled the drivers with Pacifist. I've manually patched NVDAStartupWeb's Info.plist to allow 15E and I've used "NVIDIA WebDriver Updater" utility as well. I've changed the SMBIOS to MacPro5,1 and tried reinstalling the drivers, etc, with no luck. Here's my boot.log: https://gist.github.com/levifig/6bc86b61794dff28ce98

 

FWIW, I have 2 graphics cards. My primary one (BIOS doesn't let me pick so it's the one in PCIe 16x #1) is a Radeon HD4850. My main card is on the 3rd slot and is a GTX970. I was running OS X just fine in 10.11.3: the Radeon wasn't accelerated and created a screen I didn't use (1 monitor, 2 inputs, one from each card). This problem seems to be unrelated with my setup, especially considering it worked in 10.11.3, but I thought it'd be better to share this bit!

 

Thank you for any help! :)

 

UPDATE: Not exactly sure how but it's working now. I know I changed my SMBIOS back to MacPro6,1, re-ran AGDPfix, re-ran Pacifist to install the drivers, re-patched the drivers, rebooted, hung before login screen, rebooted this time without caches and… voila: it's working! No idea what I did different… I guess I just retraced my steps and did something I could've missed the last time around. I'll keep this post here for posterity… ;)

It's about permission or kextcache problem. Re-Run InsanelyMac Permission Tool should fix the problem. :)

Share this post


Link to post
Share on other sites

Thank you again Micky for creating this:

http://www.insanelymac.com/forum/files/file/432-insanelyrepairpermission/

 

I was stuck in boot loop hell for the longest time after downloading the latest nVidia drivers and tried many things that didn't seem to work, but this script fixed it for me.  Updating my version of Citrix Receiver also had me in a boot loop earlier this week, but running this script again in Safe Mode fixed that for me also.

 

I bow down to you!  If anyone else is in a similar situation, I'd highly recommend this.

Share this post


Link to post
Share on other sites

New WebDriver - 346.03.06b01 for build 15E is out!

 

Very cool. Anyone know if they working better than the current 10.11 ones? I am wondering if they will fix Final Cut Pro X crashes!

Share this post


Link to post
Share on other sites

So I take it everyone else is also having the FCPX Transitions crash the program?

 

I'm up to the latest 10.11.4 beta (this morning) and these brand new 06b01 NVIDIA drivers....same problem still.

 

 

Come on NVIDIA fix this! we know you read this!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By NikTheNoob
      Hi,
       
      I'm rather new to Hackintosh and trying my first build with OpenCore on AMD, but I run into issues causing OpenCore to crash before even loading the macOS installer. As I'm not sure which one is causing the crash, I'm trying to resolve all of them and one of the error messages has to do with WhateverGreen, which I was able to see in this slow-mo loading video. Basically I'm getting an error that I'm running an unsupported processor, even though I think I was following this guide by the step.
      What could be causing this and what do I need to do to resolve it?
       
      CPU: AMD Ryzen 2700X
      MB: Gigabyte Aorus X470 Ultra Gaming
      Memory: 4x8 GB HyperX Predator, 3000 MHz Cl15
      Storage: Samsung Evo 970 Nvme 512 GB, Crucial MX500 500GB SATA
      GPU: MSI Radeon RX580 GamingX 8GB
    • By fantomas
      Hi InsanelyMacaliens    
       
      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS High Sierra.
       
      10.13.6
       
      Nvidia Web Driver - 387.10.10.10.40.134 --> build 17G11023 (thanks to TimeLord04) New!
      Nvidia Web Driver - 387.10.10.10.40.133 --> build 17G10021 (thanks to phi777)
      Nvidia Web Driver - 387.10.10.10.40.132 --> build 17G9016 (thanks to iCanaro)
      Nvidia Web Driver - 387.10.10.10.40.131 --> build 17G8037 (thanks to phi777)
      Nvidia Web Driver - 387.10.10.10.40.130 --> build 17G8030 (thanks to fabiosun)
      Nvidia Web Driver - 387.10.10.10.40.129 --> build 17G8029 (thanks to TimeLord04)
      Nvidia Web Driver - 387.10.10.10.40.128 --> build 17G7024 (thanks to flowrider)
      Nvidia Web Driver - 387.10.10.10.40.127 --> build 17G6030 (thanks to Extreme™) 
      Nvidia Web Driver - 387.10.10.10.40.124 --> build 17G6030 (thanks to flowrider) 
      Nvidia Web Driver - 387.10.10.10.40.123 --> build 17G6029 (thanks to Badruzeus) 
      Nvidia Web Driver - 387.10.10.10.40.122 --> build 17G5019 (thanks to TimeLord04) 
      Nvidia Web Driver - 387.10.10.10.40.118 --> build 17G5019 (thanks to ReddestDream)
      Nvidia Web Driver - 387.10.10.10.40.113 --> build 17G4015 (thanks to flowrider)
      Nvidia Web Driver - 387.10.10.10.40.108 --> build 17G3025 (check here)
      Nvidia Web Driver - 387.10.10.15.15.108 --> build 17G2307 (thanks to marcozardi)
      Nvidia Web Driver - 387.10.10.10.40.105 --> build 17G65 (thanks to sl0wtarget)
       
      10.13.5
      Nvidia Web Driver - 387.10.10.10.35.106 --> build 17F77 (check here)
       
      10.13.4
      Nvidia Web Driver - 387.10.10.10.30.107 --> build 17E202 (check here)
      Nvidia Web Driver - 387.10.10.10.30.106 --> build 17E199 (thanks to BreBo)
      Nvidia Web Driver - 387.10.10.10.30.103 --> build 17E199 (thanks to ricoc90)
       
       
      10.13.3
      Nvidia Web Driver - 387.10.10.10.25.161 --> build 17D102 (thanks to Cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.160 --> build 17D2102 (thanks to Cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.159 --> build 17D2012 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.158 --> build 17D102 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.157 --> build 17D2047 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.156 --> build 17D47 (thanks to darthsian) 
       
       
      10.13.2
      Nvidia Web Driver - 378.10.10.10.25.106 --> build 17C2205 (thanks to KGP-X99)
      Nvidia Web Driver - 378.10.10.10.25.105 --> build 17C2120 (see this post)
      Nvidia Web Driver - 378.10.10.10.25.104 --> build 17C205 (thanks to ReddestDream)
      Nvidia Web Driver - 378.10.10.10.25.103 --> build 17C89 (thanks to Il Francy MacPc) 
      Nvidia Web Driver - 378.10.10.10.25.102 --> build 17C88 (thanks to piiggggg)
       
       
      10.13.1
      Nvidia Web Driver - 378.10.10.10.20.109 --> build 17B1003 (see this post)
      Nvidia Web Driver - 378.10.10.10.20.108 --> build 17B1002 (thanks to BreBo)
      Nvidia Web Driver -378.10.10.10.20.107 --> build 17B48 (thanks to piiggggg) 
       
       
      10.13.0
      Nvidia Web Driver - 378.10.10.10.15.121 --> build 17A405 (thanks to Asgorath)
      Nvidia Web Driver - 378.10.10.10.15.120 --> build 17A405 (thanks to phi777)
      Nvidia Web Driver - 378.10.10.10.15.117 --> build 17A405 (thanks to phi777)
      Nvidia Web Driver - 378.10.10.10.15.114 --> build 17A365 (thanks to Asgorath).
    • By Kaku
      Greetings!
       
      So I managed to get a Catalina 10.15 vm up and running in ESXi 6.7u2.
      When I try to install Catalina updates, however, it goes to the Apple logo, status bar moving ever so slightly, reboots again and this time hangs on the Apple logo.  To fix this, I either remove or disable "Mac OS" as an option in the bootloader. Is there a way to get these updates to install? 
       
      In the meantime...
       
      I instead of restarting Catalina after choosing to update it, I shutdown the guest.  After a restart it SEEMED to update with the time duration countdown.
       
      Prior to this I did run disk utility and checked Untitled and Untitled-Data for errors (I don't think it found any).
       
      So I just logged back onto the VM and the version is still 10.15 and NOT 10.15.2 as hoped. So weird.
       
      Any ideas?
       
    • By fusion71au
      Clover r5101 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5101 for VMware.zip". Mount Clover-v2.5k-5101-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×