Contribute
Register

NVIDIA Releases Alternate Graphics Drivers for macOS High Sierra 10.13.4 (387.10.10.10.30)

pastrychef

Moderator
Joined
May 29, 2013
Messages
13,314
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Radeon VII
Mac
MacBook, Mac Pro
Classic Mac
iBook, Power Mac, PowerBook
Mobile Phone
iOS
Ok, here it goes:

I'm reaching out to all of the great, amazing people in this community for your help. This is my first Hackintosh build (wife and I have named her Ripley - from the Alien series). She had been working pretty well with a few exceptions. The ultimate goal is to get full acceleration and the best rendering speeds in FCPX/Motion (which I use primarily) and Adobe AE and some other apps.

When it was working at it's best, I would have artifacts appear in the preview of some of the generators and plugins in FCPX (mostly motionVFX plugins) and normal video footage. I've uninstalled and reinstalled them to no avail. I'm aware it has to do with something in my setup. I've read through most of the comments in this post to try and find the best way to resolve this and here's where I'm at:

1. Do I try to fix what I currently have by changing a number of settings?
2. Do I erase it all and start from scratch? (really don't want to do this)

I've included a zip file with everything I can think would be needed to make an assessment (config.plst file, screen shots of S/L/E folder and L/E folder, etc.) and some additional screen shots. My current SYMBIOS is iMac 14.2 (thinking this should be changed), I'm using Clover Configurator 4.60.3.4, and my specs are:

Gigabyte-Z170X-UD3
Intel Core i7 6700K (Skylake)
32GB RAM (2x16gb BallistiX Sport)
EVGA GeForce GTX 1060 6GB SSC GAMING ACX 3.0

I thank you all in advance for your help, wisdom and advice.
=)

Rodney
I took a look at the files you posted. Some of the settings in your config.plist seem uncommon. I don't know if you used them because they are actually needed or if you misunderstood someone's instructions or followed a bad guide.

Here are the things that seemed "uncommon" to me in your config.plist:
  • In ACPI section, you have FixLAN enabled. Is this needed?
  • In ACPI section, you have Drop OEM_DSM for IntelGFX. Is this needed?
  • In Graphics section, you have ig-platform-id set correctly for Skylake, but I see in your profile that you have a GTX 1060. If you wish to use the HD 530 for Quick Sync, AirPlay, etc, you should set ig-platform-id to 19120001 and Inject Intel should be enabled.
  • In Kernel and Kext Patches section, you have the 15 port limit patch twice. You just need it once.
  • In SMBIOS section, you are using iMac14,2 system definition. iMac17,1 fits your hardware more closely.
  • In SMBIOS section, you have not completed setting up Serial, UUID, or Board Serial.
  • In SMBIOS section, you should disable Mobile and enable Trust.

I saw that you have your hackintosh kexts installed in both /EFI/CLOVER/kexts/Other/ and /Library/Extensions/. People far smarter, knowledgable, and experienced than myself recommend installing kexts in to /Library/Extensions/ with the exception of FakeSMC.kext which should be in /EFI/CLOVER/kexts/Other/.

That being said, I have adapted the approach of keeping all my hackintosh related kexts in /EFI/CLOVER/kexts/Other/ for convenience and have not experienced any problems. This is just my personal experience and YMMV. I do not want to start any debates about this subject. I'm just telling you what works for me.

I didn't look at what you have in /System/Library/Extensions/. There's just too much there. I'm just going to say that on a desktop, I don't know of any hackintosh related kexts that should be installed there.

Regarding your kexts:
  • You have XHCI-200-series-injector.kext installed. You are running a 100 series motherboard, so this is not needed.
  • FakeSMC.kext (and it's sensors) should be in /EFI/CLOVER/kexts/Other/.
  • Lilu.kext and its plugins work better in /EFI/CLOVER/kexts/Other/ for me. It's up to you if you want to install them in /EFI/CLOVER/kexts/Other or /Library/Extensions/. If you decide to install in /Library/Extensions/, it's advisable to also install LiluFriend.kext.
  • If/when you install kexts to /Library/Extensions/, you should use an app like KextBeast to install them.
  • If/when you install kexts to /EFI/CLOVER/kexts/Other/, you can just copy them over.

Lastly, I'm not a FCPX user, but based on what I've read, if you use FCPX a lot, it's strongly advised to go with an AMD video card. It just works better than Nvidia in FCPX. Period.

Recent releases of Nvidia web drivers have had some pretty serious issues with lag on many hackintoshes running on Skylake or newer hardware. If you do a search, you will easily find hundreds of posts on the topic. NvidiaGraphicsFixup.kext version 1.2.5 incorporates workarounds (not fixes) that may circumvent the lag issues. Apparently, this works for some users but not all. You will have to test yourself to see if you are affected by the lag and if NvidiaGraphicsFixup.kext works for you. I have not found any common denominators that give definitive indications on which systems are affect or which systems the NvidiaGraphicsFixup.kext workarounds work.
 
Joined
Jan 12, 2018
Messages
22
Motherboard
MSI Z370-A PRO
CPU
i7-8700K
Graphics
RX 580
@izo1, I now appreciate the detailed explanation of your experience regarding the graphic cards. “Plug and play” graphic cards definitely saves time and you don’t have to spend time figuring out what’s wrong with Nvidia graphics and the lag issues.

I understand your point and I agree that I asked the impossible question. Every computer is unique and there is no universal guide that ensures a working Hackintonish, its on the Hackintoshers to figure out the correct configuration.

If I persistently experience issues with Nvidia, I’m not gonna waste time and just buy AMD card (Likely RX570 as you suggested). I will then compare, and sell/return the other card.

And yes, I shouldn’t be fooled by labels, just focus on specs, performance reports, and capability with certain software that I would actually use. Thank you izo1!
 
Joined
Dec 5, 2013
Messages
57
Motherboard
ASUS ROG Maximus IX Hero
CPU
I7-7700K
Graphics
RX 580
Mac
iMac, MacBook Air
Mobile Phone
iOS
Click on "releases" and download "1.2.4.RELEASE.zip"

https://github.com/lvs1974/NvidiaGraphicsFixup/releases
Please do not spread wrong information. Everyone here is talking about the newest version of the kexts (Lilu 1.2.3 and NvidiaGraphicsFixup 1.2.5). Downloading and installing kexts from the releases won't include the workaround patch for the lags. The kext must be compiled since there is no official release on the repositories yet or downloaded if someone shares a compiled version of it.

It's very easy to compile both kexts on your own:
- Install Xcode 9.3
- Download the whole Lilu repository as a zip
- Unzip it
- Start the Xcode project (if there is an `.xcworkspace` then open this one instead of `.xcproj`)
- Compile the project by clicking on the play button (the kext target should be selected if not already)
- (I don't remember this) If it will ask you for a code sign identity you have to provide your personal dev. account (Apple ID)
- Open the `Products` group in the project navigator and find the kext there
- Right click on the kext and then click on `Show in finder`
- Profit from the kext

You can compile the NvidiaGraphicsFixup kext the same away except that it depends on the Lilu.kext, which you have to copy into the project folder of NvidiaGraphicsFixup before compiling.

To be fair those steps are fairly trivial and shouldn't require any complex pre-setup and work out of the box. You can then copy your compiled kexts into clover.
 
Joined
Aug 13, 2013
Messages
12
Mac
MacBook Pro
Classic Mac
Power Mac
Mobile Phone
iOS
I took a look at the files you posted. Some of the settings in your config.plist seem uncommon. I don't know if you used them because they are actually needed or if you misunderstood someone's instructions or followed a bad guide.

Here are the things that seemed "uncommon" to me in your config.plist:
  • In ACPI section, you have FixLAN enabled. Is this needed?
  • In ACPI section, you have Drop OEM_DSM for IntelGFX. Is this needed?
  • In Graphics section, you have ig-platform-id set correctly for Skylake, but I see in your profile that you have a GTX 1060. If you wish to use the HD 530 for Quick Sync, AirPlay, etc, you should set ig-platform-id to 19120001 and Inject Intel should be enabled.
  • In Kernel and Kext Patches section, you have the 15 port limit patch twice. You just need it once.
  • In SMBIOS section, you are using iMac14,2 system definition. iMac17,1 fits your hardware more closely.
  • In SMBIOS section, you have not completed setting up Serial, UUID, or Board Serial.
  • In SMBIOS section, you should disable Mobile and enable Trust.

I saw that you have your hackintosh kexts installed in both /EFI/CLOVER/kexts/Other/ and /Library/Extensions/. People far smarter, knowledgable, and experienced than myself recommend installing kexts in to /Library/Extensions/ with the exception of FakeSMC.kext which should be in /EFI/CLOVER/kexts/Other/.

That being said, I have adapted the approach of keeping all my hackintosh related kexts in /EFI/CLOVER/kexts/Other/ for convenience and have not experienced any problems. This is just my personal experience and YMMV. I do not want to start any debates about this subject. I'm just telling you what works for me.

I didn't look at what you have in /System/Library/Extensions/. There's just too much there. I'm just going to say that on a desktop, I don't know of any hackintosh related kexts that should be installed there.

Regarding your kexts:
  • You have XHCI-200-series-injector.kext installed. You are running a 100 series motherboard, so this is not needed.
  • FakeSMC.kext (and it's sensors) should be in /EFI/CLOVER/kexts/Other/.
  • Lilu.kext and its plugins work better in /EFI/CLOVER/kexts/Other/ for me. It's up to you if you want to install them in /EFI/CLOVER/kexts/Other or /Library/Extensions/. If you decide to install in /Library/Extensions/, it's advisable to also install LiluFriend.kext.
  • If/when you install kexts to /Library/Extensions/, you should use an app like KextBeast to install them.
  • If/when you install kexts to /EFI/CLOVER/kexts/Other/, you can just copy them over.

Lastly, I'm not a FCPX user, but based on what I've read, if you use FCPX a lot, it's strongly advised to go with an AMD video card. It just works better than Nvidia in FCPX. Period.

Recent releases of Nvidia web drivers have had some pretty serious issues with lag on many hackintoshes running on Skylake or newer hardware. If you do a search, you will easily find hundreds of posts on the topic. NvidiaGraphicsFixup.kext version 1.2.5 incorporates workarounds (not fixes) that may circumvent the lag issues. Apparently, this works for some users but not all. You will have to test yourself to see if you are affected by the lag and if NvidiaGraphicsFixup.kext works for you. I have not found any common denominators that give definitive indications on which systems are affect or which systems the NvidiaGraphicsFixup.kext workarounds work.
Thank you for this. Ironically, this post gave me some insight into my own problems with Intel QuickSync (Skylake w/ Nvidia GPU). I was sure I tried that platformID before, but this time around it worked flawlessly. I also installed IntelGraphicsFixup because I seem to remember that being a requirement in other threads. I wonder if the workarounds in the latest NvidiaGraphicsFixup also alleviate the known issues using a discrete GPU w/ QuickSync on Skylake.

EDIT: UGH! I forgot about the iTunes segfaults!
 
Last edited:

pastrychef

Moderator
Joined
May 29, 2013
Messages
13,314
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Radeon VII
Mac
MacBook, Mac Pro
Classic Mac
iBook, Power Mac, PowerBook
Mobile Phone
iOS
Thank you for this. Ironically, this post gave me some insight into my own problems with Intel QuickSync (Skylake w/ Nvidia GPU). I was sure I tried that platformID before, but this time around it worked flawlessly. I also installed IntelGraphicsFixup because I seem to remember that being a requirement in other threads. I wonder if the workarounds in the latest NvidiaGraphicsFixup also alleviate the known issues using a discrete GPU w/ QuickSync on Skylake.

EDIT: UGH! I forgot about the iTunes segfaults!
I don't think there are any issues with using IGPU for Quick Sync.

Use Shiki.kext to fix iTunes crashes.
 

aol

Joined
Apr 14, 2011
Messages
513
Motherboard
GA-Z370-HD3P
CPU
i7-8700K
Graphics
RX570
Mac
MacBook Pro, Mac Pro
Mobile Phone
iOS
...

It's very easy to compile both kexts on your own:
- Install Xcode 9.3
- Download the whole Lilu repository as a zip
- Unzip it
- Start the Xcode project (if there is an `.xcworkspace` then open this one instead of `.xcproj`)
- Compile the project by clicking on the play button (the kext target should be selected if not already)
- (I don't remember this) If it will ask you for a code sign identity you have to provide your personal dev. account (Apple ID)
- Open the `Products` group in the project navigator and find the kext there
- Right click on the kext and then click on `Show in finder`
- Profit from the kext

You can compile the NvidiaGraphicsFixup kext the same away except that it depends on the Lilu.kext, which you have to copy into the project folder of NvidiaGraphicsFixup before compiling.
...
Would appreciate if anyone can clarify this. I'm confused about the different versions of lilu, the release and debug version, and which version should be used for your system, and which version should be used when compiling lilu plugins, and which compiled plugin version (release or debug) you should use in your system. The dev in me says you should use release version for everything: lilu release in your system, lilu release when compiling other plugins, release version of other plugins; and that debug can only run slower and produce more debug output. But the docs suggest you should use the debug version in various places. Thanks for any clarity.
 
Joined
Sep 21, 2013
Messages
23
Motherboard
Asus Sabertooth X99
CPU
i7-5820K
Graphics
RX Vega 56
Mac
MacBook Pro, Mac mini, Mac Pro
Classic Mac
iBook, iMac, Performa, Power Mac, PowerBook, Xserve
Mobile Phone
iOS
I tried the new NvidiaFixUp (compiled from source and updated Lilu) and it gives me black screens. I am sick of tired of nVidia. In short, I simply went and buy a used AMD RX 580 8GB that is slightly above MSRP. It's a downgrade from a GTX 1070, but it will give me less hassles with macOS, which I spend most of my time on compared to Windows. Also, it will give me better Final Cut Pro X performance.

Also, the new drivers causes glitches in Adobe Photoshop CC. Also, I don't see using the old nVidia drivers as a long term solution. Maybe it's best for people who want to build a Hackintosh to stick with Apple sanctioned AMD cards, even if they are expensive thanks those cryptominers.
 
Joined
Dec 5, 2013
Messages
57
Motherboard
ASUS ROG Maximus IX Hero
CPU
I7-7700K
Graphics
RX 580
Mac
iMac, MacBook Air
Mobile Phone
iOS
Would appreciate if anyone can clarify this. I'm confused about the different versions of lilu, the release and debug version, and which version should be used for your system, and which version should be used when compiling lilu plugins, and which compiled plugin version (release or debug) you should use in your system. The dev in me says you should use release version for everything: lilu release in your system, lilu release when compiling other plugins, release version of other plugins; and that debug can only run slower and produce more debug output. But the docs suggest you should use the debug version in various places. Thanks for any clarity.
Here is the commit that includes the workaround:

https://github.com/lvs1974/NvidiaGraphicsFixup/commit/2548a94bce9fe38e855ca17f19bea05978938cd7

You can read through the comments bellow. The one you've asked for in particular is this:
  1. Download Lilu source code and compile https://github.com/vit9696/Lilu (by default it will be compiled as Debug, which is what you need).
  2. Download NvidiaGraphicsFixup source code.
  3. Place the compiled Debug Lilu.kext at the root of your NvidiaGraphicsFixup source folder.
  4. Build NvidiaGraphicsFixup.
  5. Profit.
 
Joined
Feb 24, 2013
Messages
2,308
Motherboard
ASUS WS X299 SAGE/10G
CPU
i9-9980XE
Graphics
Radeon VII
Mac
MacBook Pro
Mobile Phone
iOS
Please do not spread wrong information. Everyone here is talking about the newest version of the kexts (Lilu 1.2.3 and NvidiaGraphicsFixup 1.2.5). Downloading and installing kexts from the releases won't include the workaround patch for the lags. The kext must be compiled since there is no official release on the repositories yet or downloaded if someone shares a compiled version of it.

It's very easy to compile both kexts on your own:
- Install Xcode 9.3
- Download the whole Lilu repository as a zip
- Unzip it
- Start the Xcode project (if there is an `.xcworkspace` then open this one instead of `.xcproj`)
- Compile the project by clicking on the play button (the kext target should be selected if not already)
- (I don't remember this) If it will ask you for a code sign identity you have to provide your personal dev. account (Apple ID)
- Open the `Products` group in the project navigator and find the kext there
- Right click on the kext and then click on `Show in finder`
- Profit from the kext

You can compile the NvidiaGraphicsFixup kext the same away except that it depends on the Lilu.kext, which you have to copy into the project folder of NvidiaGraphicsFixup before compiling.

To be fair those steps are fairly trivial and shouldn't require any complex pre-setup and work out of the box. You can then copy your compiled kexts into clover.
You can relax. No one is spreading false information. I’m sure the compiled version will be posted on Github soon.

Compiling is easy, I’m away from my computer but someone should compile it and attach it here.
 
Top