Jump to content
fantomas1

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

1,060 posts in this topic

Recommended Posts

Have you tried it, any pascal promises? :D

That's something I would like too.

I can't find the download link, but it's just 59MB in size, so....

Share this post


Link to post
Share on other sites
Advertisement

I'm running the Sierra GM but I can't install the newest Nvidia driver. It tells me:

 

 

Mac OS X version 10.12 (16A323) is required for this update. Please update your OS version and try again.

 

Any thoughts?

Share this post


Link to post
Share on other sites

Redownload from Appstore. That build is newest release of GM and is the official one that got released yesterday.

Previous versions, downloaded with the public beta code, are older builds.

Share this post


Link to post
Share on other sites

Unable to get graphics card working  it says " version no compatible"  GPU is an Nvidia  750Ti 

post-377047-0-94980700-1474507813_thumb.png

Edited by fantomas1

Share this post


Link to post
Share on other sites

Unable to get graphics card working  it says " version no compatible"  GPU is an Nvidia  750Ti 

 

As usual :

sudo nano /System/Library/Extensions/NVDAStartupWeb.kext/Contents/info.plist

Then change NVDARequiredOS to this (assuming you're indeed on 16B2327e) :

<key>NVDARequiredOS</key>
<string>16B</string>

Repair permissions, rebuild kernel cache and reboot.

 

 

 

 

 

kiqJuBN.png

 

 

 

Edited by fantomas1

Share this post


Link to post
Share on other sites

Back on topic then
I'm still getting random flickering screen. It's so weird it happens from now and then and suddenly there seen to be nothing wrong with graphics again.

Anybody else running into this?

Share this post


Link to post
Share on other sites

Off Topic:
Too bad that I’m not a good programmer. Would be a fun project taking/reversing the maxwell driver and writing/patching a kext to support pascal. Linux support is here, the framebuffer mode is already working on OSX, FreeBSD drivers are downloadable from nvidia.
Looking at the sizes of the kexts is interesting. Nvidias kexts are small, compared to AMDs...
Maybe we have to buy a GTX1080 for Slice :lol:

This are the binary drivers from FreeBSD, even some source code is included:
NVIDIA-FreeBSD-x86_64-367.44 $ find .
<...parts ommited...>
./obj
./obj/.DS_Store
./obj/libEGL.so.1
./obj/libGL.so.1
./obj/libGLESv1_CM.so.1
./obj/libGLESv2.so.2
./obj/libglx.so.1
./obj/libnvidia-cfg.so.1
./obj/libnvidia-eglcore.so.1
./obj/libnvidia-glcore.so.1
./obj/libnvidia-glsi.so.1
./obj/libnvidia-gtk2.so.367.44
./obj/libnvidia-ml.so.1
./obj/libnvidia-tls.so.1
./obj/libvdpau_nvidia.so.1
./obj/linux
./obj/linux/libcuda.so.367.44
./obj/linux/libEGL.so.1
./obj/linux/libEGL_nvidia.so.367.44
./obj/linux/libGL.so.367.44
./obj/linux/libGLdispatch.so.0
./obj/linux/libGLESv1_CM.so.1
./obj/linux/libGLESv1_CM_nvidia.so.367.44
./obj/linux/libGLESv2.so.2
./obj/linux/libGLESv2_nvidia.so.367.44
./obj/linux/libnvidia-cfg.so.367.44
./obj/linux/libnvidia-eglcore.so.367.44
./obj/linux/libnvidia-fatbinaryloader.so.367.44
./obj/linux/libnvidia-glcore.so.367.44
./obj/linux/libnvidia-glsi.so.367.44
./obj/linux/libnvidia-ptxjitcompiler.so.367.44
./obj/linux/libnvidia-tls.so.367.44
./obj/linux/libOpenGL.so.0
./obj/linux/libvdpau_nvidia.so.367.44
./obj/linux/tls
./obj/linux/tls/libnvidia-tls.so.367.44
./obj/linux/tls/tls_test
./obj/linux/tls/tls_test_dso.so[/b]
./scripts
./scripts/linux.sh
./scripts/setup.sh
./src
./src/common
./src/common/inc
./src/common/inc/cpuopsys.h
./src/common/inc/nv-gpu-info.h
./src/common/inc/nv-modeset-interface.h
./src/common/inc/nvCpuUuid.h
./src/common/inc/nvstatus.h
./src/common/inc/nvstatuscodes.h
./src/common/inc/nvtypes.h
./src/common/inc/xapi-sdk.h
./src/Makefile
./src/nvidia
./src/nvidia/ebridge_export.h
./src/nvidia/ebridge_freebsd.c
./src/nvidia/ibmnpu_export.h
./src/nvidia/ibmnpu_freebsd.c
./src/nvidia/Makefile
./src/nvidia/nv-freebsd.h
./src/nvidia/nv-kernel.o
./src/nvidia/nv-misc.h
./src/nvidia/nv-reg.h
./src/nvidia/nv.h
./src/nvidia/nvidia-sources.mk
./src/nvidia/nvidia_acpi.c
./src/nvidia/nvidia_ctl.c
./src/nvidia/nvidia_dev.c
./src/nvidia/nvidia_i2c.c
./src/nvidia/nvidia_linux.c
./src/nvidia/nvidia_modeset_interface.c
./src/nvidia/nvidia_os.c
./src/nvidia/nvidia_os_pci.c
./src/nvidia/nvidia_os_registry.c
./src/nvidia/nvidia_pci.c
./src/nvidia/nvidia_subr.c
./src/nvidia/nvidia_sysctl.c
./src/nvidia/nvlink_common.h
./src/nvidia/nvlink_freebsd.c
./src/nvidia/os-interface.h
./src/nvidia-modeset
./src/nvidia-modeset/Makefile
./src/nvidia-modeset/nv-modeset-kernel.o
./src/nvidia-modeset/nvidia-modeset-freebsd.c
./src/nvidia-modeset/nvidia-modeset-os-interface.h
./src/nvidia-modeset/nvkms-api-types.h
./src/nvidia-modeset/nvkms-ioctl.h
./src/nvidia-modeset/nvkms-kapi.h
./src/nvidia-modeset/nvkms.h
<...parts ommited...>

from the maxwell mac kext:
Output from "nm NVDAGM100HalWeb" kext  (lots of similarity if compared to NVDAGK100HalWeb kext)

                 U _ADDRLIST_FBMEM_ONLY
                 U _ADDRLIST_FBMEM_PREFERRED
                 U _ADDRLIST_SYSMEM_ONLY
                 U _ADDRLIST_SYSMEM_PREFERRED
                 U _CliAddDeviceMemory
                 U _CliCheckAdmin
                 U _CliDelDeviceMemory
                 U _CliDestroyDeviceMemoryMemDesc
                 U _CliDispGetDispChannelInfo
                 U _CliFindDeviceMemoryInfo
                 U _CliFindDispChannelInfo
                 U _CliFindDmaMappingInfoInClient
                 U _CliFindVASpace
                 U _CliGetChannelClassInfo
<... lot's ommited ...>
                 U _vpGetBinResInfoSigDbg_STUB
                 U _vpGetBinResInfoSigProd_STUB
                 U _vpGetBinResInfoUcodeHeader_STUB
                 U _vpGetBinResInfoUcodeImage_STUB
                 U _vpGetBinResInfoUcodePatchLocation_STUB
                 U _vpGetBinResInfoUcodePatchSignature_STUB
                 U _vpGetConfig_STUB
                 U _vpGetExternalConfig_STUB
                 U _vpGetUcodeImage_STUB
                 U _vpHalIfacesSetup_VGPUSTUB
                 U _vpIdle_STUB
                 U _vpPatchUcodeSig_STUB
                 U _vpProbeEnginePresence_STUB
                 U _vpService_STUB
                 U _vpSetBlockLevelClockGating_STUB
                 U _vpStateDestroy_STUB
                 U _vpStateLoadHal_STUB
                 U _vpStateUnload_STUB
                 U _vrrmgrCheckVrrReleaseAndSchedPolling
                 U _wborConstruct_STUB
                 U _wborDetermineCapabilities_STUB
                 U _wborInitCapabilities_STUB
                 U _wborReadCaps_STUB
                 U _wborSetPropertiesList_STUB
                 U _wborWriteCaps_STUB
                 U _wbor_iGrp_ipVersions_getInfo_STUB
                 U _windowConstruct_STUB
                 U _windowDetermineCapabilities_STUB
                 U _windowInitCapabilities_STUB
                 U _windowReadCaps_STUB
                 U _windowSetPropertiesList_STUB
                 U _windowWriteCaps_STUB
                 U _window_iGrp_ipVersions_getInfo_STUB

post-1175328-0-63204000-1474560331_thumb.png

Share this post


Link to post
Share on other sites

Apple has released 10.12.1 for devs.

Do not install! The current Nvidia driver (...F01) is NOT WORKING!

 

I have a flashed GTX960 and the flickering is terrible :-) So wait for Nvidia to catch up with Apple.

 

Cheers,

 

Marc

Share this post


Link to post
Share on other sites

Apple has released 10.12.1 for devs.

Do not install! The current Nvidia driver (...F01) is NOT WORKING!

 

I have a flashed GTX960 and the flickering is terrible :-) So wait for Nvidia to catch up with Apple.

 

Cheers,

 

Marc

 

Hi,

 

It's not the first time... read post #390

Share this post


Link to post
Share on other sites

I have GTX 980 and X99 platform. nvidia drivers working well dont use boot arg nvda_drv=1 on Mac OS Sierra . slice autor of clover write about that here http://www.insanelymac.com/forum/topic/304530-clover-change-explanations/page-2 last time when clover has been updated  "

Rev 3733

It was my mistake setting nvda_drv=1 flag as boot-args. No! It is NVRAM variable nvda_drv that can have a value "1".

So I make new config value"

 

    <key>SystemParameters</key>

    <dict>

        <key>NvidiaWeb</key>

        <true/>

    </dict>

 

thats all guys everything works :)

 

 

Hi, ony solution for CHAMELEON users to get the old  nvda_drv=1 work in SIERRA again?

I cant get (like in older OS X) the drivers loaded /used anymore :(

 

I have luck, because my gou GT 640 also works with Apple drivers but want to use Nvidia Web drivers.

Share this post


Link to post
Share on other sites

I updated to 10.12.1 Beta. 

 

Followed polyzargone's instructions, and everything works again. 

Be sure you select the Nvidia driver again from the top menu to activate it.  

 

Thanks!

Share this post


Link to post
Share on other sites

Hi, ony solution for CHAMELEON users to get the old  nvda_drv=1 work in SIERRA again?

I cant get (like in older OS X) the drivers loaded /used anymore :(

 

I have luck, because my gou GT 640 also works with Apple drivers but want to use Nvidia Web drivers.

 

I'm using Clover 3763 (latest from the website at the time of writing) and the normal nvda_drv=1 boot arg works fine for me.

Share this post


Link to post
Share on other sites

Yep, Clover devs found an way to get  nvda_drv=1 working again. (Has to do that web driver not more using kernel flag , insted reading nvram value = chameleon hasnt nvram anymore).

Share this post


Link to post
Share on other sites

I have these graphics issues...

does anyone know how to fix?

 

@GTX 750Ti with web driver

I have gotten the same transparency graphics issues with my GT730. Even with the latest f01 update of Nvidia web driver for Sierra. How did you managed to fix yours mate? Surprisingly, the previous Nvidia 10.11.6 update for El Capitan works wonders. The graphics glitches happened after I updated through system preferences pane of Nvidia web driver to the latest f01. Any idea of how do I roll back to the El Capitan nvidia web driver? I tried installing it but there's an error saying the software cannot be installed on 10.12 machines. Cheers.

Share this post


Link to post
Share on other sites

Just wanted to tell, Cinebench R15 has the error "Strings not found" on startup for me, clicking the Icon, but works well in Sierra if started from terminal:

Downloads/CINEBENCH_R15/CINEBENCH\ OSX.app/Contents/MacOS/CINEBENCH\ OSX 

Just FYI

PS: (on Nvidia GTX970: Geekbench 4.0.1 exits on OpenCL Benchmark (just Nvidia related??) and CUDA-Z can't be started because of missing cuda (7.5.30 is installed) ??).

Share this post


Link to post
Share on other sites

Just wanted to tell, Cinebench R15 has the error "Strings not found" on startup for me, clicking the Icon, but works well in Sierra if started from terminal:

Downloads/CINEBENCH_R15/CINEBENCH\ OSX.app/Contents/MacOS/CINEBENCH\ OSX 

Just FYI

PS: (on Nvidia GTX970: Geekbench 4.0.1 exits on OpenCL Benchmark (just Nvidia related??) and CUDA-Z can't be started because of missing cuda (7.5.30 is installed) ??).

 

Your Cuda version doesn't support macOS Sierra. The next update should fix this.

I have OpenCL problems with Adobe CC programs (no OpenCL preview or rendering). Don't know if its Adobe or Nvidia related...

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 fantomas1
      This update:
      • Makes downloaded issues available in the My Magazines section of Apple News+, both online and offline
      • Adds all publications in Apple News+, including newspapers, to the catalog at the top of the News+ feed
      • Adds the ability to clear downloaded magazine issues in Apple News+ by selecting History > Clear > Clear All
      • Addresses an issue which prevents creation of a new Boot Camp partition on iMac and Mac mini with Fusion Drive
      • Resolves an issue that may cause a hang during a restart
      • Resolves a graphics issue that may occur when waking from sleep
      • Fixes an issue that may cause fullscreen video to appear black on Mac mini
      • Improves file sharing reliability over SMB
       
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo

      View full article
    • By fantomas1
      This update:
      • Makes downloaded issues available in the My Magazines section of Apple News+, both online and offline
      • Adds all publications in Apple News+, including newspapers, to the catalog at the top of the News+ feed
      • Adds the ability to clear downloaded magazine issues in Apple News+ by selecting History > Clear > Clear All
      • Addresses an issue which prevents creation of a new Boot Camp partition on iMac and Mac mini with Fusion Drive
      • Resolves an issue that may cause a hang during a restart
      • Resolves a graphics issue that may occur when waking from sleep
      • Fixes an issue that may cause fullscreen video to appear black on Mac mini
      • Improves file sharing reliability over SMB
       
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo
    • By fantomas1
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo
    • By eliot6001
      I don't know whether my LAN device will work on MAC and Which version of mac but i still want to run MAC on my PC, Also i checked my CPU-GPU and it turned out that i can Run MAX High sierra but i realized that some people have trouble with Sound and Internet connection so Here's the NAME of my LAN device:
       
      PCI\VEN_10EC&DEV_8136&SUBSYS_012310EC&REV_05\4&45F2A70&0&00E1 as (LAN DEVICE took the name from device manager in  windows). 
      also from compatibleIds i got this:
      PCI\VEN_10EC&DEV_8136&REV_05
       
      Is it Supported on any version of macOS ?
    • By Aldaro
      I have been running macOS Mojave on my system for 3 months and everything was working pretty well.  After taking an update for clover, my entire system got wrecked, and I cannot even boot to an installation environment anymore (which I really need to do since I am starting back at square one).  I still have the old EFI folder backed up, but I know it'll only be a matter of time before Apple introduces an update that requires me to update Clover in order to work correctly.  I have tried all the available memory fixes, but none of them seem to work.  I was previously using the original osxaptiofix; so, I gave v2, and v3 a try, but to no success.  I read somewhere on the main discussion board for clover that AptioMemoryFix was no longer going to be supported and I therefor decided to skip over it (not to mention it isn't even available in newer clover installation packages).
       
      System specs:
      Motherboard: GIGABYTE Z390 M GAMING
      CPU Intel core i5 9600k @ stock 3.7GHz
      RAM 32GB DDR4 2667MHz
      GPU AMD Radeon RX 580 with 8GB of GDDR5
      SSD Intel 660p 512GB NVME
      NIC: Intel i210 10/100/1000 as it is natively supported in macOS
       
      I have been using the iMac 19,1 SMBIOs as I built this machine to match it as close as humanly possible.  As for my UEFI settings, I did the usual:
      Disabled Windows specific features and secure boot
      Enabled XHCI hand off
      Enabled Above 4G decoding
      Disabled onboard NIC since it is made irrelevant by my intel i210
       
      --INJECT KEXTS--
      FakeSMC
      Lilu
      WhateverGreen
      AppleALC
      USBInjectAll -- WITH PATCHED SSDT in /EFI/CLOVER/ACPI/patched
      Below are images of the errors I am receiving when trying to boot the macOS Mojave installer.
       
      with original osxaptiomemoryfix

       
      osxaptiofixv2

       
      osxaptiofixv3

       
      Anyway, if somebody can help me figure out what's going on, that'd be greatly appreciated.  My ultimate goal is to get an install with minimal clover patches as to be better prepared when the winds of change from Apple come roaring.
       
      p.s: I have also attached a copy of my EFI folder
       
       
      EFI.zip
×