Jump to content
fantomas1

NVIDIA Web Driver Updater [UPDATE: 07/18/2016]

122 posts in this topic

Recommended Posts

Advertisement

Is it really necessary to use this application considering the latest web drivers are working on iMacs (MacBook and MacPro) ?

it automatically remove the hardware restriction from the package.... of course for the installation!

Share this post


Link to post
Share on other sites

I meant : Nvidia officially provides these drivers for iMacs so it installs on iMacs hardware, what kind of other hardware restriction does it remove ?

Share this post


Link to post
Share on other sites

I meant : Nvidia officially provides these drivers for iMacs so it installs on iMacs hardware, what kind of other hardware restriction does it remove ?

Who say that?

This depend by NVDIA, some build of Web Drivers (not all) limit the installation to only specific hardware:

var system_models = ["MacPro3,1", "MacPro4,1", "MacPro5,1"]; 

not oly iMacs.

the app remove that check...but leave the one for the OS version...

Share this post


Link to post
Share on other sites

Is it really necessary to use this application considering the latest web drivers are working on iMacs (MacBook and MacPro) ?

 

hi

 

please, read well:

 

application for downloading Retail & Beta!!! Nvidia Web Driver versions

 

 

you'll never have a beta web driver from Nvidia Driver Manager... unless the things change now that this application was born.   :P

Share this post


Link to post
Share on other sites

Who say that?

If you mean "who said it is now working for iMacs and Macbook ?" then Nvidia said so : 

 

BETA support is for iMac 14,2 / 14,3 (2013), iMac 13,1 / 13,2 (2012) and MacBook Pro 11,3 (2013), MacBook Pro 10,1 (2012), and MacBook Pro 9,1 (2012) users.

 

Here or there.

 

not oly iMacs.

the app remove that check...but leave the one for the OS version...

Is there something else than iMacs and MacPro used for Hackintosh ?  :)

The iMac support is pretty new so I though this application was made without knowing about it and I was wondering if it was still useful now.

 

 

you'll never have a beta web driver from Nvidia Driver Manager... unless the things change now that this application was born.    :P

Right, thanks for this clarification !

Out of curiosity, how does the application knows about these beta web drivers, do you (by you I mean fantoms1 who created the app) update it manually or does it directly get the information from an Nvidia server ?

 

You should maybe add the possibility to patch the kext after installation for OS X beta. I think it would be a nice and interesting feature for beta testers out there.

 

Anyway, thanks for this application, I did not mean to say it was "useless", I was just trying to understand what it was offering.  :)

Share this post


Link to post
Share on other sites

If you mean "who said it is now working for iMacs and Macbook ?" then Nvidia said so : 

 

 

Here or there.

 

Is there something else than iMacs and MacPro used for Hackintosh ?  :)

The iMac support is pretty new so I though this application was made without knowing about it and I was wondering if it was still useful now.

 

Sir from Here:

 

Includes BETA support for iMac and MacBook Pro systems with NVIDIA graphics

supported hardware is

 

 

GeForce 600 Series:

GeForce GTX 680

GeForce 200 Series:

GeForce GTX 285

GeForce 100 Series:

GeForce GT 120

GeForce 8 Series:

GeForce 8800 GT

Quadro Series:

Quadro K5000 for Mac, Quadro 4000 for Mac

Quadro FX Series:

Quadro FX 4800, Quadro FX 5600

 

so you mean that NVIDIA strictly support the real Mac described and only the supported graphics card?

I guess this is nothing new. You need to buy a Mac then! :whistle:

 

Anyway that package has no hardware restriction, only software (require your OS build begin with '15A')

 

EDIT

how the app works is our secret :P, but let see when new updates comes out

Share this post


Link to post
Share on other sites

@lgda

 

please, when you quote a message, quote the right part   ^_^

 

Micky1979 didn't say the latest driver will NOT support iMac, MacBook... more, it says BETA support for these platforms, which means that it's something pretty new, since 10.10.4 to be more exact.

 

Previous versions only support Mac Pro 5.1 (2010), Mac Pro 4.1 (2009) et Mac Pro 3.1 (2008). 

 

So it's why Micky1979 said:

 

This depend by NVDIA, some build of Web Drivers (not all) limit the installation to only specific hardware:

 


 

You should maybe add the possibility to patch the kext after installation for OS X beta. I think it would be a nice and interesting feature for beta testers out there.

 

even if we do that, there's no guarantee that it will work... I mean the patched kext

Share this post


Link to post
Share on other sites

fantomas, I was joking. :P

but the fact is  that the an Hackintosh surely does not respect the NVIDIA specs...no?

The app respect the OS version build installed... to download the latest right pkg..


 

even if we do that, there's no guarantee that it will work... I mean the patched kext

kexts can be patched, only implement that with some criteria (actual graphics card installed?)

Share this post


Link to post
Share on other sites

@Micky1979

 

I meant that even if the app patches the kext, there's no guarantee that this patched kext will work for a specific release, and I think he's more talking about a os x beta update release.

Share this post


Link to post
Share on other sites

Sure:

 

msg-674334-0-99078500-1444421048.png

 

user decide to install, that's all!

if need to patch their installed kexts after the install he know what to do as always. Or can request something new in this Topic for a new functionality. 

Edited by fantomas1

Share this post


Link to post
Share on other sites

Per question 25 in this thread, the latest NVIDIA drivers no longer have a system check that matches the MacPro3,1 - MacPro5,1 or a non-EFI NVIDIA GPU (which covered most Hackintoshes already).  You'll still need to remove the hardware check from older drivers, but yeah, NVIDIA has officially flipped the switch and lets their driver be installed on any system, including laptops and iMacs.

Share this post


Link to post
Share on other sites

Per question 25 in this thread, the latest NVIDIA drivers no longer have a system check that matches the MacPro3,1 - MacPro5,1 or a non-EFI NVIDIA GPU (which covered most Hackintoshes already).  You'll still need to remove the hardware check from older drivers, but yeah, NVIDIA has officially flipped the switch and lets their driver be installed on any system, including laptops and iMacs.

On final release NVIDIA do that, but for future betas who can say?

Share this post


Link to post
Share on other sites

Per question 25 in this thread, the latest NVIDIA drivers no longer have a system check that matches the MacPro3,1 - MacPro5,1 or a non-EFI NVIDIA GPU (which covered most Hackintoshes already).  You'll still need to remove the hardware check from older drivers, but yeah, NVIDIA has officially flipped the switch and lets their driver be installed on any system, including laptops and iMacs.

 

false

 

Capture d’écran 2015-10-10 à 16.24.57.png

 

system check is still present

 

but maybe no more in the near futur

Share this post


Link to post
Share on other sites

On final release NVIDIA do that, but for future betas who can say?

 

Given that they've publicly acknowledged the fact they're supporting laptops and iMacs (via the driver download page and their blog post), I have little doubt that they'll continue to do this.  It's very clear that NVIDIA is invested in their web driver as a way of enabling newer GPUs and providing better support for existing official products as well.

false

 

attachicon.gifCapture d’écran 2015-10-10 à 16.24.57.png

 

system check is still present

 

but maybe no more in the near futur

 

That's an OS version mismatch, not a hardware check failure.  What OS version are you on?  Non-beta releases are locked to one specific OS version as before, it's just that the driver installer package will now work on any NVIDIA system, not just the Classic MacPro.

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 rioredstone
      if a web driver is NOT installed, what happens??
       
      I used AMD RX560 in Sierra, but it is very unstable. usually gpu crash or window server crash occurred.
      so now I attached nvidea Quadro FX1700 to my Sierra. I know FX1700 works well in High Sierra, but I haven't tried it in Mojave yet.
      FX1700 works well without any additional kext, even nvidia web driver.
       
      I plan to buy a nividia card. I would like to know if a nvidia card, especially kepler, maxwell, pascal, works without web driver.
      just curious.
       
       
    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file, will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issues DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs
       
      This is what I needed for my NVIDIA rig and the MSI motherboard in the signature. Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from eGPU to iGPU and vice-versa.
       
      Cheers!
    • By crazybirdy
      Base on ASentientBot's great job.
      If you want to use latest version kexts all from 10.13.6, you can patch it by yourself.
      GeForceTesla.kext/Contents/MacOS/GeForceTesla
       
      Old Method : GeforceTesla.kext from post#2125.
      Find 554889e553504889fb83bb38030000007426488b03488bb3e80000004889dfff90c8050000488b03488bb3e80000004889dfff907806000031c04883c4085b5d Replace 6666666666662e0f1f8400000000006666666666662e0f1f8400000000006666666666662e0f1f8400000000006666666666662e0f1f8400000000000f1f4000 or perl patch code.
      perl -pi -e 's|\x55\x48\x89\xe5\x53\x50\x48\x89\xfb\x83\xbb\x38\x03\x00\x00\x00\x74\x26\x48\x8b\x03\x48\x8b\xb3\xe8\x00\x00\x00\x48\x89\xdf\xff\x90\xc8\x05\x00\x00\x48\x8b\x03\x48\x8b\xb3\xe8\x00\x00\x00\x48\x89\xdf\xff\x90\x78\x06\x00\x00\x31\xc0\x48\x83\xc4\x08\x5b\x5d|\x66\x66\x66\x66\x66\x66\x2e\x0f\x1f\x84\x00\x00\x00\x00\x00\x66\x66\x66\x66\x66\x66\x2e\x0f\x1f\x84\x00\x00\x00\x00\x00\x66\x66\x66\x66\x66\x66\x2e\x0f\x1f\x84\x00\x00\x00\x00\x00\x66\x66\x66\x66\x66\x66\x2e\x0f\x1f\x84\x00\x00\x00\x00\x00\x0f\x1f\x40\x00|g' GeForceTesla.kext/Contents/MacOS/GeForceTesla New Method : GeforceTesla.kext from post#2529 .
      Find 488b07ff90c0000000 Replace 488b07660f1f440000 or perl patch code.
      perl -pi -e 's|\x48\x8b\x07\xff\x90\xc0\x00\x00\x00|\x48\x8b\x07\x66\x0f\x1f\x44\x00\x00|g' GeForceTesla.kext/Contents/MacOS/GeForceTesla the patch code is the same as ASentientBot provided 10.13.4 patched GeforceTesla.kext.
      You need only one method between Old Method and New Method, each of them works fine here.
       
      10.13.6 kexts works fine as below,
      GeForceGA.bundle
      GeForceTesla.kext ..... (patched)
      GeForceTeslaGLDriver.bundle
      GeForceTeslaVADriver.bundle
      NVDANV50HalTesla.kext
      NVDAResmanTesla.kext
      IOGraphicsFamily.kext
      IONDRVSupport.kext
       
      or
       
      You can try to use NDRVShim.kext instead of replacing IONDRVSupport and IOGraphicsFamily post#1875, get NDRVShim.kext from post#1865, at /Volumes/macOS Mojave Patcher/macOS Mojave Patcher.app/Contents/Resources/macOS Post Install.app/Contents/Resources/legacynvidia/NDRVShim.kext
       
      And need to edit NVDAResmanTesla.kext/Contents/Info.plist to add the following string.
              <key>com.parrotgeek.NDRVShim</key>
              <string>1</string>
      <dict> <key>com.apple.iokit.IOGraphicsFamily</key> <string>1.5</string> <key>com.parrotgeek.NDRVShim</key> <string>1</string> <key>com.apple.iokit.IONDRVSupport</key> <string>1.5</string> <key>com.apple.iokit.IOPCIFamily</key> <string>2.4</string> <key>com.apple.kpi.bsd</key> <string>9.0.0</string> <key>com.apple.kpi.iokit</key> <string>9.0.0</string> <key>com.apple.kpi.libkern</key> <string>9.0.0</string> <key>com.apple.kpi.mach</key> <string>9.0.0</string> </dict> 10.13.6 kexts works fine as below,
      GeForceTesla.kext ..... (patched)
      GeForceTeslaGLDriver.bundle
      GeForceTeslaVADriver.bundle
      NVDANV50HalTesla.kext
      NVDAResmanTesla.kext ..... (edit Info.plist)
      NDRVShim.kext ..... (added)
       
      If you still have troube, try the following 10.13.6 kexts too.
      IOAccelerator2D.plugin
      IOAcceleratorFamily2.kext
      Refer to /Volumes/macOS Mojave Patcher/macOS Mojave Patcher.app/Contents/Resources/macOS Post Install.app/Contents/Resources/legacyGPUPatch.sh
      credits to: ASentientBot, parrotgeek1, dosdude1.
       
      And My nVidia 9300GE always need to fix reboot error with NVDAStartup.kext.310.42.25f01.zip from nawcom since 10.12.
       
      Download all the patche kexts here. All works fine here too.
      It's better to use Kext Utility.app to install kexts.
       

       
    • By Discount_Mac
      Hello everyone,
       
      I was able to install macOS Sierra 10.12.6 a few months ago successfully with working audio, internet, etc.
       
      But now I want to upgrade to High Sierra and am not sure whether or not it will be compatible with my system. (Tried to do it using a High Sierra USB. Wouldn't boot into installer, showed "+++++++++++++" or something.)
       
      My specs are:
      Dell Optiplex 3010
      Intel Core i3-3240 @ 3.40GHz (HD2500 Integrated Graphics)
      4GB of RAM
      NVIDIA Quadro FX1800 (Want to use this GPU, have an extra Radeon HD7470 somewhere that I can also use in this if needed)
      Conexant CX20641 Audio
      Realtek RTL8111E Ethernet
       
      So, can I upgrade to High Sierra? Please let me know.
       
      EDIT: I kept getting this error: (See attached image)
       
      Thanks
      -Discount_Mac

×