Jump to content
fantomas1

Nvidia Web Driver updates for macOS Sierra (UPDATE May 15, 2019)

1,060 posts in this topic

Recommended Posts

Many upcoming games will require Sierra or later due to a significant update of metal API, so it depends on what you are doing especially while deciding the value of OS itself.

 

Yeah, of course YMMV, but gaming on macOS? Horrible imho. Much better to use dual boot.

 

Actually, while it's true that the frontend Console app is now pretty horrible, you can still find pretty much any info you want (and I'd say have even more control over it) by using the "log" command, once you understand how to use it properly.

 

I know, but it is much more cumbersome to do that this way. I really don't get why they did not retain this functionality. Frankly, I am more and more concerned where macOS is heading to in general. The lack of quality control, and their efforts to dumb down everything until it is not usable anymore makes me really worry.

Share this post


Link to post
Share on other sites
Advertisement

Hopefully yes.

 

In the meantime, you can edit NVDAStartupWeb.kext > NVDARequiredOS to match 16D32 build number (or just 16D). It works fine !

oh thx ;)

Share this post


Link to post
Share on other sites

Hopefully yes.

 

In the meantime, you can edit NVDAStartupWeb.kext > NVDARequiredOS to match 16D32 build number (or just 16D). It works fine !

 i try to edit the plist with txt editor but it doesn't work , i need an plist editor ?

Share this post


Link to post
Share on other sites

Its worked.

NVDAStartupWeb.kext

16C67 to 16D32

Share this post


Link to post
Share on other sites

Updated drivers no issue.

attachicon.gifScreen Shot 2017-01-25 at 9.01.05 am.png

 

What version are you using ? With latest 367.15.10.35f01 and NVDAStartupWeb.kext edit, I have this when I rebuild kernel cache :

 

 

rebuilding //System/Library/PrelinkedKernels/prelinkedkernel
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext NVDAStartupWeb.kext
kext file:///System/Library/Extensions/EnergyDriver.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
Invalid signature -67030 for kext <OSKext 0x7ff158f236d0 [0x7fffa1462da0]> { URL = "NVDAStartupWeb.kext/ -- file:///System/Library/Extensions/", ID = "com.nvidia.NVDAStartupWeb" }
kxld[com.nvidia.web.GeForceWeb]: The vtable 'vtable for nvDisplayPipeTransaction' is malformed. Make sure your kext has been built against the correct headers.
kxld[com.nvidia.web.GeForceWeb]: The vtable 'vtable for nvDisplayPipeTransaction' is malformed. Make sure your kext has been built against the correct headers.
kxld[com.nvidia.web.GeForceWeb]: The vtable 'vtable for nvDisplayPipeTransaction' is malformed. Make sure your kext has been built against the correct headers.
Link failed (error code 5).
Prelink failed for com.nvidia.web.GeForceWeb; omitting from prelinked kernel.
KernelCache ID: 5D7B164959B191F9419B863DAE41A36E
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>
kextcache updated critical boot files, requesting launchd reboot
logout

Share this post


Link to post
Share on other sites

 

What version are you using ? With latest 367.15.10.35f01 and NVDAStartupWeb.kext edit, I have this when I rebuild kernel cache :

rebuilding //System/Library/PrelinkedKernels/prelinkedkernel
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext NVDAStartupWeb.kext
kext file:///System/Library/Extensions/EnergyDriver.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
Invalid signature -67030 for kext <OSKext 0x7ff158f236d0 [0x7fffa1462da0]> { URL = "NVDAStartupWeb.kext/ -- file:///System/Library/Extensions/", ID = "com.nvidia.NVDAStartupWeb" }
kxld[com.nvidia.web.GeForceWeb]: The vtable 'vtable for nvDisplayPipeTransaction' is malformed. Make sure your kext has been built against the correct headers.
kxld[com.nvidia.web.GeForceWeb]: The vtable 'vtable for nvDisplayPipeTransaction' is malformed. Make sure your kext has been built against the correct headers.
kxld[com.nvidia.web.GeForceWeb]: The vtable 'vtable for nvDisplayPipeTransaction' is malformed. Make sure your kext has been built against the correct headers.
Link failed (error code 5).
Prelink failed for com.nvidia.web.GeForceWeb; omitting from prelinked kernel.
KernelCache ID: 5D7B164959B191F9419B863DAE41A36E
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>
kextcache updated critical boot files, requesting launchd reboot
logout

Hope this helps.

post-1083558-0-94519500-1485303806_thumb.png

post-1083558-0-06715600-1485303810_thumb.png

Share this post


Link to post
Share on other sites

Did 10.12.3 change anything regarding the iBook / Instruments Issue? Or regarding the various graphical glitches for example after fast user switching? (Also happens with "real" macs using macOS drivers)

Share this post


Link to post
Share on other sites

Oh I'm sorry ! I just realized you were talking about 10.12.3.

 

I'm now on 10.12.4 beta 16E144f and webdrivers are broken. Even with edited NVDAStartupWeb.kext :(.

What gfx card are you using? (Using phone so can't see)

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Fortunately, it's a GTX 650 Ti which doesn't need webdrivers at all ;).

I'll let you know how I go. Just made a backup and installing beta now.

 

Sent from my SM-G930F using Tapatalk

I seem to be having the same? issues. Installed latest Nvidia driver then the 10.12.4 beta 1, applied NVDAStartupWeb.kext patch 16E, fixed audio and patched ADGP.

OSX says that my GFX card is detected and it is, including 4Gb ram apposed to 7mb but my screen is glitchy, no transparency. Typing this post makes the screen flicker with every keystroke.

post-1083558-0-45590000-1485325550_thumb.png

post-1083558-0-20733900-1485325552_thumb.png

Hopefully this can be resolved soon or ill just go back to my backup :-)

Share this post


Link to post
Share on other sites

Did 10.12.3 change anything regarding the iBook / Instruments Issue? Or regarding the various graphical glitches for example after fast user switching? (Also happens with "real" macs using macOS drivers)

Same problems.  :thumbsdown_anim:

Share this post


Link to post
Share on other sites

Same problems.  :thumbsdown_anim:

 

Too bad. Think my decision to roll back to El Capitan (something I never did before!) was the right one.

 

Sierra = boooo. Apple, get your stuff fixed!

Share this post


Link to post
Share on other sites

Just installed 10.12.4 Beta (16E144f) and changed NVDAStartupWeb.kext:

<key>NVDARequiredOS</key>
<string>16E144f</string>

It works somehow. But not as it should. There is no hardware acceleration for now. Any Idea what to try to get it work properly?

Share this post


Link to post
Share on other sites

Just installed 10.12.4 Beta (16E144f) and changed NVDAStartupWeb.kext:

<key>NVDARequiredOS</key>
<string>16E144f</string>

It works somehow. But not as it should. There is no hardware acceleration for now. Any Idea what to try to get it work properly?

No ideas. Waiting xxx.xx.xx.xx.xxb01 (beta) driver special for 10.12.4.

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 glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By fantomas1
      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.128 --> build 17G7024 (thanks to flowrider) New!
      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 fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
    • By fantomas1
      This update:
      • Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
      • Adds the ability to follow a magazine from the Apple News+ catalog browsing view
      • Includes support for the Reiwa (令和) era of the Japanese calendar
      • Improves audio latency on MacBook Pro models introduced in 2018
      • Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
       
      Update
      Combo

      View full article
    • By fantomas1
      This update:
      • Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
      • Adds the ability to follow a magazine from the Apple News+ catalog browsing view
      • Includes support for the Reiwa (令和) era of the Japanese calendar
      • Improves audio latency on MacBook Pro models introduced in 2018
      • Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
       
      Update
      Combo
×