Jump to content
Rampage Dev

New Nvidia Retail Driver Install Solution

98 posts in this topic

Recommended Posts

New Nvidia Retail Driver Install Solution

Posted on May 16, 2013by rampagedev

about:

New Nvidia Retail drivers have been released today. It introduces a new Preference Pane under System Preferences that allows you to enable the Nvidia Web Driver or OS X Default Driver The new drivers require information to be written to the NVram. Without this you will not be able to Meklort, who developed the NVram Module that we currently use, assisted me in understanding why the NVram information showed up on some systems and not others. If you are using my Recovery Partition And Enable All Features Of iCloud and iMessages fix you must remove nvram.log from /var/log/ before you can begin.

If you plan to enable ECC, for a Nvidia card that support this feature, you must add the slot identification edit in your DSDT or the option to enable ECC on that card will not be available.

Accreditation:

Meklort for NVram Module and boot.plist Flag

Originally posted here

Guide:

Part 1: Install

1. Download Mac OS X Driver Release 313.01.01 here

2. Install the drivers

3. Install the latest Bootloader found here

4. In your Extra folder if not present already create a folder called modules:



screen-shot-2013-05-15-at-10-36-58-pm.pn


5. From i386/modules folder copy FileNVRAM.dylib into Extra/modules:


screen-shot-2013-05-15-at-10-37-31-pm.pn


6. Continue to Part 2


Part 2: Fusion Drive Installs or Systems Without FileNVRAM


1. In your Extra folder open org.chameleon.Boot.plist:


screen-shot-2013-05-15-at-10-39-15-pm.pn


2. Under Kernel Flags add nvda_drv=1:


screen-shot-2013-05-15-at-10-41-25-pm.pn


3. Continue to Part 3


Part 3: Enabling


1. Go to System Preferences:


screen-shot-2012-11-23-at-7-45-43-pm.png


2. Go to Nvidia Driver Manager:


screen-shot-2013-05-15-at-10-43-46-pm.pn


3. In the Preference Pane change the settings to match the following:


screen-shot-2013-05-15-at-10-45-11-pm.pn


4. Restart


5. The new kexts should now be loaded:


screen-shot-2013-05-15-at-10-47-27-pm.pn


6. If you are using my Recovery Partition And Enable All Features Of iCloud and iMessages fix please redo Parts 4-7 here

Share this post


Link to post
Share on other sites
Advertisement

it seems that following your guide these new drivers works fine on the first pc in signature...

if i'll report something strange i'll tell you. :)

cheers

 

p.s. thank you!

Share this post


Link to post
Share on other sites

After installing the driver for the 560 TI (which isn't supported according to http://www.nvidia.co...f03-driver.html), turning it on from system prefs doesn't stick after a reboot. Though turning it on and then running LuxMark resulted in a lock up (confirmed kexts were loaded via 3rd party system info app).

 

Cosmetic bug:

 

post-810930-0-83759400-1368747116_thumb.png

 

There is a way to force it but its not a good idea since it is cosmetic.

Share this post


Link to post
Share on other sites

After installing the driver for the 560 TI (which isn't supported according to http://www.nvidia.co...f03-driver.html), turning it on from system prefs doesn't stick after a reboot. Though turning it on and then running LuxMark resulted in a lock up (confirmed kexts were loaded via 3rd party system info app).

 

can you check your log looking for the lock up was caused by the well know NVDA Channel Exception??

 

Thanks, and good luck

Share this post


Link to post
Share on other sites

Cosmetic bug:

 

post-810930-0-83759400-1368747116_thumb.png

 

There is a way to force it but its not a good idea since it is cosmetic.

 

I am facing same problem

Share this post


Link to post
Share on other sites

I am facing same problem

 

Do you not see that the drivers are loaded in my pic? There is no issue just cosmetic. If you add the boot flag you can guarantee the drivers are loaded.

Share this post


Link to post
Share on other sites

Hi,. excuse me for the silly questions....

I am trying unsuccessfully -for several days :wallbash: -to get a GTX titan to work on my desktop...this is a real MacPro5,1 2xQuad-Core Intel Xeon, 96 GB RAM...with extra power supply.

I read somewhere that with 10.8.4 the titan was supported....but got a blank screen with the latest version. I was able to boot and login after I moved NVDA*.kext.

Now I see my two cards in System information, one is a Qadro 4000, the other ( Vendor: NVIDIA (0x10de) Device ID: 0x1005 Revision ID: 0x00a1 Kernel Extension Info: No Kext Loaded ). If I rebuild the cache and reboot it hangs, I tried installing NVidia drivers but they not compatible with 10.8.4.... I have no real clue if I should revert to 10.8.3 and use new nvidia drivers, change these kext things, any suggestions would be greatly apreciated.

 

S>

Share this post


Link to post
Share on other sites

Hi,. excuse me for the silly questions....

I am trying unsuccessfully -for several days :wallbash: -to get a GTX titan to work on my desktop...this is a real MacPro5,1 2xQuad-Core Intel Xeon, 96 GB RAM...with extra power supply.

I read somewhere that with 10.8.4 the titan was supported....but got a blank screen with the latest version. I was able to boot and login after I moved NVDA*.kext.

Now I see my two cards in System information, one is a Qadro 4000, the other ( Vendor: NVIDIA (0x10de) Device ID: 0x1005 Revision ID: 0x00a1 Kernel Extension Info: No Kext Loaded ). If I rebuild the cache and reboot it hangs, I tried installing NVidia drivers but they not compatible with 10.8.4.... I have no real clue if I should revert to 10.8.3 and use new nvidia drivers, change these kext things, any suggestions would be greatly apreciated.

 

S>

 

I have 4 users using the Titan in 10.8.4 with no issues with the latest beta. Start with Beta 12E36 and up.

Share this post


Link to post
Share on other sites

Mine Works simply from change within system prefs, without modifying org.chameleon or something.

I'm using Screen%20Shot%202013-05-18%20at%2010.27.46%20AM.png

 

Just to be sure the driver is loaded properly check CUDA prefpane from system pref

 

Screen%20Shot%202013-05-18%20at%2010.30.28%20AM.png

Share this post


Link to post
Share on other sites

Mine Works simply from change within system prefs, without modifying org.chameleon or something.

I'm using Screen%20Shot%202013-05-18%20at%2010.27.46%20AM.png

 

Please read the guide. It says only for fusion installs and or not having Nvram needs the flag. Thank you.

Share this post


Link to post
Share on other sites

How about a clover based installation ?

Tried to use the prefpane to switch to web drivers with clover 1654 and it didn't worked (not a cosmetic issue !) :wallbash:

It works with nvda_drv=1 in boot args.

Is there a way to make it work with the nvidia nvram prefpane with clover ?

Share this post


Link to post
Share on other sites

How about a clover based installation ?

Tried to use the prefpane to switch to web drivers with clover 1654 and it didn't worked (not a cosmetic issue !) :wallbash:

It works with nvda_drv=1 in boot args.

Is there a way to make it work with the nvidia nvram prefpane with clover ?

 

Did you check system info? Otherwise go ask Slice.

Share this post


Link to post
Share on other sites

Yes I checked the system info. Apple driver is loaded.

Nvidia driver can't be loaded unless I use the nvda_drv=1 boot arg.

Will ask Slice.

Thank you.

Share this post


Link to post
Share on other sites

Yes I checked the system info. Apple driver is loaded.

Nvidia driver can't be loaded unless I use the nvda_drv=1 boot arg.

Will ask Slice.

Thank you.

 

Thanks for the feed back. Let us know what slice says.

Share this post


Link to post
Share on other sites

 

5. From i386/modules folder copy FileNVRAM.dylib into Extra/modules:

screen-shot-2013-05-15-at-10-37-31-pm.png?w=640

 

I can't find this file.. (might be a noob thing sorry)

Share this post


Link to post
Share on other sites

[/center]

 

I can't find this file.. (might be a noob thing sorry)

 

Its in the folder of the complied binaries of the boot loader.

Share this post


Link to post
Share on other sites

Hey there,

 

I couldn't find it so I went ahead and tried the reboot without moving that file. It looks like my resolution problem has been fixed. :D

 

Here is a screenshot of the inside of my i386 folder... No modules folder, and no .dylib file. What does it do when you move the file? Should I bother pursuing it?

 

image.jpg

Share this post


Link to post
Share on other sites

Hey there,

 

I couldn't find it so I went ahead and tried the reboot without moving that file. It looks like my resolution problem has been fixed. :D

 

Here is a screenshot of the inside of my i386 folder... No modules folder, and no .dylib file. What does it do when you move the file? Should I bother pursuing it?

 

image.jpg

 

This is because you failed to follow the instructions on the guide on where to get the bootloader.

Share this post


Link to post
Share on other sites

I have 4 users using the Titan in 10.8.4 with no issues with the latest beta. Start with Beta 12E36 and up.

 

Thanks for the suggestion, but I can't seem to be able to locate anything older than 12E52..., maybe I 'll try again with 10.8.3, new drivers enabled, nvda_drv=1, and enabling the latest nvidia version, etc... I think I tried that already,...it seems to be something to do with the "Kernel Extension Info: No Kext Loaded"

is there another way to load this kext, I tried downloading some kext files, but osx86tool does not like to open those files, somehow hardware detection in osX86tools doesn't work, and I get errors when I try to setup a custom geforce card with over 5GB using GFX string creator.... any suggestion?

Thanks, S>

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 Coddyx
      Hi,
       
      I followed the AMD OSX Vanilla Guide and managed to successfully build my first hackingtosh.
      Everything works great EXCEPT for my MSI - Radeon RX 580 8 GB GAMING X.
      I ran some benchmarks (and tried World of Warcraft) and I am getting ~50% of the performance I am usually getting in Windows 10.
      Unigine Heaven reports ~950 vs 1750 in Windows and World of Warcraft runs @ 30 fps lowest settings vs 60 fps ultra settings in Windows.
       
      Here are the kexts I am using:
      AppleALC Lilu NullCPUPowerManagement RealtekRTL811 VirtualSMC WhateverGreen  
      I should mention that this is an AMD hackingtosh running on Ryzen 5 1600 3.2 GHz 6-Core Processor.
       
      I read and I completely understand that I should not expect 100% performance. But I believe a 50% drop is out of the ordinary.
       
      If anyone has ideas on what I could try to up the performance it would be greatly appreciated.
       
      Thank you!
       
       
    • 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 issue 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.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
       
      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.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      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 dGPU to iGPU and vice-versa.
       
      Cheers!
    • By Coke2g
      I've been happily using macOS Sierra 10.12.6 (16G29) successfully for more than a year (all things working), but now I replaced my old Asus GTX 750 Ti card with a new Zotac GTX 1060 6GB, and it get stuck on boot just before going to the login screen (verbose boot screen attached).
       
      I've updated Clover with all its kexts, and reinstalled the Nvidia Web Drivers (using nvidia-update script), but it's still stuck in the same part. I can only enter using nv_disable=1
       
      My current Hackintosh specs:
      Motherboard MSI H110M Gaming (MS-7994) (LGA 1151/Intel H110/DDR4/SATA 3 & USB 3.1) CPU Intel Core i5-6600 6M Skylake Quad-Core 3.3 GHz LGA 1151 65W RAM HyperX FURY 16GB (2 x 8GB) DDR4 2133 (PC4-17000) HX421C14FBK2/16 Video Zotac GTX 1060 6GB SSD Samsung SSD 850 EVO 250GB HDD Western Digital Black 1TB (32MB Cache) (WDC WD1001FALS-00J7B1)  
      I've read that maybe it can be fixed patching the DSDT, but I don't know how to do it.
       
      My RunMe.app generated zip file and verbose boot screen are attached.
       
      Any kind of help is appreciated. Thanks.
      Send me Coke-iMac.zip

    • By Pericles
      I've been trying to boot MacOS Mojave (10.14.4) after installation on a system I've built.
       
      I was able to successfully install Mojave through my USB, it seemed like the installer recognised my gpu and was working with it in the installation screen as it looked like it was outputting video at 4k resolution. When the computer restarted I then booted into the "Preboot" option on clover twice (the first time I tried the progress bar got to a certain point and then the system restarted) and on the second attempt the progress bar filled up completelly and the mac installer counted down to a restart (which I took as meaning that it had successfully finished the installer). After restarting however I tried to boot into MacOS from the SSD I installed it on, the apple logo showed up with a progress bar that filled up completelly before the screen turned black, then grey with a cursor over the grey screen. Also, it's probably worth noting that the GPU's fans continue to spin from turning the system on, up to the point where the screen turns grey after which they stop spinning.
       
      My system specs are as follows:
      CPU: i5 3470
      GPU: RX 570
      RAM: 16GB DDR3 1600MHz 
      MB: Asrock B75m r2
      SSD: Samsung 850 Evo 250gb
      WiFi/BT: Fenvi FV-T919 PCIE Card
       
      I am thinking that it's probably a gpu related issue as everything about the installation process has gone pretty smoothly up to the point where it's displaying a grey screen at bootup (and not going further). I have attached a photo of the output from rebooting with the verbose bootflag (it's missing one line at the bottom "busy timeout[1], (240s): 'AppleACPICPU'"), after the verbose output stays on the screen for a few minutes the screen then turns grey with the cursor and hangs there.

    • By AppleVegas
      Hello! I was trying to install hackintosh a while ago and today I decided to install it today.
      I am able to boot it, I installed OS but have problems with iGPU. It has only 4mb vram.
      I did almost everything, I installed whatevergreen, used special clover config, but nothing. I've only got it to recognize my igpu.
       
      I have a laptop with this specs:
      Laptop brand name: Lenovo G50-80
      iGPU: Intel HD Graphics 5500 -- Only shows 4mb of vram
      CPU: Intel Core i5-5200U 2.20GHz
      dGPU: AMD Radeon R5 M230 or AMD Radeon HD 8500m (it has two brand names lol) -- will be really glad if you tell me how to launch it in High Sierra with my iGPU, now I can't even load OS when I have discrete GPU enabled
      RAM: 6GB ddr3
      Bluetooth: Qualcomm Atheros QCA61x4 -- On the way to enable it
      Wi-Fi: Qualcomm Atheros AR956x -- Managed to enable it
       
      P.S: In the windows I can see that my iGPU has Dedicated Video Memory: 128MB
       
      Any help? I think you are only my savers

×