[APP] NVIDIA eGPU support for High Sierra (NVIDIAEGPUSupport)  

@Arthy, no, it does not work at all when the external monitor is unplugged, and only works intermittently on the external monitor when it IS plugged in. This hack may work for some, but it doesn't work with this hardware combination.

@fr34k

ok thanks. It did not work 100% but at least a bit better. The external screen stayed black and only the cursor worked... also boot was incredibly slow. I try to downgrade if possible....

Hi, @soulwash, I will also try to downgrade... Do you know the steps of downgrading, I can not find the "macos high sierra 10.13.3 installer"... only find some updates of 10.13.3.

I've to say that I've not played with Nvidia cards for several months because being in the endless patching loop is not very fruitful. Glad to see that a few people still have strong motivation in exploring these hacks, and my clue about AppleGPUWrangler as the culprit turned out to be true.

As to eGPU screen output, my first attempt also failed. Don't stop there. Try again, different cables and monitors. Do not use any other display adapters except Apple's TB3/TB2 if you happen to have a TB2 Mac.

After rebuilding caches using the method from my old automate-eGPU.sh, a couple of restarts, it is close to perfect on macOS 10.13.4. Just keep the eGPU plugged in from the beginning. If you happen to have the notorious 2015 13" that rejects newer Nvidia cards on startup, hot-plug during the early boot process. If the Apple logo shows up on the eGPU monitor, it is a sign that macOS is set to run eGPU monitor as the primary. If not, the internal screen is the primary display. This setting can be also changed programmatically, in C/C++. Maybe in Swift as well. Some years ago I made an app that switched the white bar location. Not possible by the script AFAIK.

I tested with two different TB2 MBPs, all display interfaces (HDMI, DP, DVI) worked, two different monitors, including 4K. Of course, no eGPU surprise removal support with Nvidia even though it shows a list of processes that need to be closed.

The remaining symptoms are caused by the older AppleGPUWrangler from 10.13.3 which results in
1) slower startup process
2) inability to change AMD dGPU (M370X in my case) to drive the internal display (automatic graphics switching always turns on, and if you try to uncheck, and logout, the internal screen goes black). Iris Pro is always active. However, apps like Valley correctly attach to M370X (iGPU+dGPU combo, no eGPU attached) and you can verify it in Activity Monitor > Window > GPU History.

No other issues. OpenCL, OpenGL work fine. Haven't tested any TB3 Mac yet.

Good job @fr34k 🙂

@goalque
Nice, comprehensive and detailed report!
So rebuilding caches (like in your old script) helps with the external monitor problem? If so I could add those 2 additional lines (+ tests) to the script.

Posted by: goalque

 

If you happen to have the notorious 2016 13" that rejects newer Nvidia cards on startup, hot-plug during the early boot process.

Early or late 2016? I guess you meant the TB2 one?
I have tried this on my late 2016 TB3, doesn't solve the issue. The display tab in About indicates the iGPU is attached to the internal display. Is there any way to switch manually or force the eGPU to the internal display?

Posted by: Arthy

Posted by: goalque

 

If you happen to have the notorious 2016 13" that rejects newer Nvidia cards on startup, hot-plug during the early boot process.

Early or late 2016? I guess you meant the TB2 one?
I have tried this on my late 2016 TB3, doesn't solve the issue. The display tab in About indicates the iGPU is attached to the internal display. Is there any way to switch manually or force the eGPU to the internal display?

Early 2015. It was a typo, just corrected.

Ignore "About > Displays", that info is not always up to date. Set the eGPU monitor as the primary (white bar on top). Go to Graphics/Displays > click on the video card and press Command+R === more reliable result which GPU runs which display.

Posted by: fr34k

@goalque
Nice, comprehensive and detailed report!
So rebuilding caches (like in your old script) helps with the external monitor problem? If so I could add those 2 additional lines (+ tests) to the script.

Thanks! Not sure yet. See RebuildCaches() function:

 echo "Rebuilding caches..."

 if [[ $(test -f /System/Library/PrelinkedKernels/prelinkedkernel && echo 1) ]]

 then

 rm /System/Library/PrelinkedKernels/prelinkedkernel 2>/dev/null

 fi

 if [[ $(test -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && echo 1) ]]

 then

 rm /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache 2>/dev/null

 fi

 touch /System/Library/Extensions

 kextcache -q -update-volume /

 touch /System/Library/Extensions

 kextcache -system-caches

The eGPU display was black first, but after a few tries no issues anymore. Just very slow startup, with both MBPs.

@goalque
the last four lines I have in my script it's only the first two rms that I don't have implemented.

Posted by: fr34k

@goalque
the last four lines I have in my script it's only the first two rms that I don't have implemented.

Those rms were important when I rebuilt AMD eGPU kext caches. Verify that paths still exists in macOS 10.13.4, and macOS regenerates these files. Sometimes a double reboot was necessary.

Kext-swapping method is nice when it works, but just like the TB1/2 patch - it may just suddenly not work on later versions of macOS. So in summary we have (pls correct if wrong - my testing has too many variables (750M, TB2) to make precise deductions):

• NVDAEGPUSupport + 10.13.4 AppleGPUWrangler (Patched or not) = Incompatible
• NVDAEGPUSupport + 10.13.3 AppleGPUWrangler = Works
• Different versions of NVDAEGPUSupport needed per OS version -> automation across updates possible - same kext can be managed with a binary and its OS version and driver references fixed on update

 

So should we:

• Invest time in creating a very stable script for NVDA support on 10.13.4+ while automating NVDAEGPUSupport install (could add to wrangler patcher) based on this replacement strategy <- Doable
• Invest time in creating a new NVDAEGPUSupport compatible with the new OS <- Hard
• Invest time in reverse-engineering macOS <- Hard af

 

Reversing really requires more man-hours and luck vs. scripting...

Posted by: goalque

Those rms were important when I rebuilt AMD eGPU kext caches. Verify that paths still exists in macOS 10.13.4, and macOS regenerates these files. Sometimes a double reboot was necessary.

Double reboot typically happens if before first reboot caches were not built/were incompletely built. Kextcache commands should technically suffice in my opinion, but yea, as I've said multiple times - the kextcache command is kind of messed up on HS (reported as well).

@mac_editor
In theory we could do Apple's and NVIDIA's work and create stable drivers and optimal eGPU support but I guess this will require tens of thousands of work hours if it even suffices.
Since we're all doing this not as a full time job, it won't be feasible, unless all of a sudden a bunch of developers come our way and want to do a lot of work for basically nothing. (building kexts, drivers etc.)

As far as I can see into the future: 10.13.14 will bring a shtld of changes we cannot completely foresee. That's why I'd suggest focusing on the wrangler and see what's the exact problem there. Maybe we have some luck. I wouldn't invest too much time though, as I can almost guarantee that in June, all hell breaks loose (aka nothing works anymore) once the first betas come out.

I'll complete my plans for a new automation script anyways. And since I try to make it as flexible as possible, I think it can serve as the automation most people can go with. My goal there is to combine all efforts made regarding eGPU into one simple and convenient solution. As you may also have noticed, the eGPU situation as gotten pretty complex (especially for newbies!) and so I try to make it as easy, secure and future poof as possible. The temporary workaround does not have any checks about the system, that's why I required people to read the full post before they do anything. But this will not install anything your system does not need (unless you explicitly tell it to). As long as a solution can be packed into an archive of arbitrary type and can be found in the internet under a static URL (or predictably dynamic) it can be implemented. That's essentially why I'm doing this.

Also: there is the slim chance Apple might finally recognize that NVIDIA might be worth a cooperation and the eGPU situation will resolve itself. (Ah, dreams can be so beautiful)
Although I guess they would still block TB1/2.

Conclusively, I think we should do what we can to try fixing 10.13.4, but due to security updates I would not create a version with maximum stability for one macOS version in specific as it will require loads and loads of more work, which in the end might all be for naught with 10.14

You sir, are a complete star. Thanks for your and everyone else's hard work at the bleeding edge…

@fr34k Valid points. 10.14 = workaround resets probably. If Apple natively supports NVIDIA, then only a TB1/2 patch will be needed. I suppose then that our end goal should be a stable NVIDIA support for 10.13.6 at best for now - and see what we can do with 10.14 later.

Thank you for your comprehensive response @fr34k - much appreciated.

Hi, by any chance does this work with GTX 1050ti for macOS High Sierra? What are the supported nVIDIA graphics cards for macOS?

I could not get this to work on a mid-2015 Macbook Pro 15" on 10.13.4 + Node + 1080TI using the automated script.

When I plug in the eGPU, it shows "Disconnect Null", but the NVDA driver manager doesn't see the card.

But if mac is booted up with the eGPU connected, the NVDA driver manager would see the card, but the disconnect button still shows "null", and it still doesn't do anything. When I try to disconnect "null" it would just show me the forever spinning colour wheel.

It doesn't appear to be operational when it's connected 🙁

@airoscar What exactly did not appear to work? As said hot-plugging is not fully supported (no eGPU screen output but OpenCL does work), and surprise removal does not work at all. You have to keep eGPU connected during the boot process if you're aiming to get eGPU screen output. Null signifies that you just don't have eGPU display output. However, in OpenCL, CUDA and Metal calculation it should work when hot plugged. I have the same 2015 15" MBP. Is it the Iris Pro only model or with the dGPU?

@oiwio Hi,

It is possible to use a time machine backup... I think there is no other way to do. Maybe purge your system and reinstall os x. After that manually install the 10.13.3 update

Good day all, I have an issue with black screen in external monitor connected to egpu

I have a 2015 15" macbookpro with amd gpu,TB2->3, devil eGPU w/ 970, external monitor connected to 970
what i have done so far is as below:
I am on 10.13.3 [17D47], followed the instruction in this thread to install web drivers and nvidia-egpu-v6.zip

I am unable to boot with eGPU attached
I tried the below and it still didnt work.

1. Logging in without the eGPU attached
2. Plugging in the eGPU (check in system profiler that it is detected) [When i plug in, external and internal screen is black]
3. Logging out and logging in again [unable to do this]

However, I notice that hotplugging shows nvidea chipset so I decided to test if i can hot plug eGPU while the mac is booting. (inspiration from how to get win10 to work with egpu) I set verbose boot on onyx, after the first flash of text i hot plug the egpu and it actually boots up with 970 detected. It also managed to detect my external monitor. However, the external monitor is still black. 

Windows10 with eGPU works perfectly though!

Anyone here has this issue and could possibly guide me?

 

 

 

@lancetan36
technically all are supported (Pascal and Maxwell for sure)
For 10.13.4 the workaround is still just not good. 10.13.3 is (mostly) stable

@fr34k firstly thank you so much for your incredible work.  I used your method to the letter, and had no trouble with the script working.  However, after reboot, I am unsure of the steps with connecting the eGPU, I have tried plugging in first, then booting, which brings me to just a black screen (internal - I am not using an external display).  If I wait for boot to finish and log in, then log out and hot plug, the screen again goes dark (internal).

Could you assist me?  Very willing to pay for your assistance.  Many thanks 

2017 15" MBP + 10.13.4 + Akitio Node Pro + Zoltac Geforce 1080 Ti

@glenn_aitken

First:
A general test if it works is: login, hot plug and see in the System Information if
a) your Node Pro is recognized (Hardware - >Thunderbolt)
b) Your graphics card is recognized (Hardware -> Graphics)

Second:
Try the hot plug immediately after the display is lit (backlight on, no logo yet)

Report if it works.

If you have dGPU equipped MBP, you should ensure that iGPU is set to run the internal display (gmux EFI setting). gfxCardStatus app may help. At least "automatic graphics switching" turned on. Otherwise, the internal screen goes black.

Posted by: soulwash

@oiwio Hi,

It is possible to use a time machine backup... I think there is no other way to do. Maybe purge your system and reinstall os x. After that manually install the 10.13.3 update

A time machine backup is possibly the only official way to go back to 10.13.3. Apple skips all earlier High Sierra builds, only the latest 10.13.4 is available under the App Store's updates tab.

Hi @fr34k, I tested the GTX 1050 with my eGFX breakaway box on my 13" touchbar MBP, and it didn't even react when I plugged it in. (I have already installed nvidia drivers using goalque's script). It just said in System Report>PCI that it was a display controller and did not even recognize it as the GTX 1050. Please help

@fr34k thanks for your reply.  I have curiously got it working perfectly.  Although my method is not the same as with others.  After your wonderful script install, I merely have to log in with the eGPU disconnected (normal boot)  and then simply turn the eGPU on, go to the NVIDIA driver manager (where the card doesn't show up), and unlock the padlock (enter system password) ...  and then when launching any program that I use, such as Premiere Pro CC or After Effects or Da Vinci Resolve it comes up listed in the GPU section and can be accessed and used.  

The one thing that is strange is that it DOESNT show up under the NVIDIA Graphics Driver manager ... however what made it kick into life (and work with the mentioned programs) was simply "unlocking" the padlock in the NVIDIA driver manager, inputting my password, and I heard the Graphics card "click" in the Node Pro

First:
A general test if it works is: login, hot plug and see in the System Information if 
a) your Node Pro is recognized (Hardware - >Thunderbolt)  YES

Node Pro:

  Vendor Name: AKiTiO

 Device Name: Node Pro

  Vendor ID: 0x41

  Device ID: 0x30C

  Device Revision: 0x1

  UID: 0x00418A0E990A5100

  Route String: 3

  Firmware Version: 23.1

  Port (Upstream):

  Status: Device connected

  Link Status: 0x2

  Speed: Up to 40 Gb/s x1

  Current Link Width: 0x2

  Link Controller Firmware Version: 0.26.0

  Port:

  Status: No device connected

  Link Status: 0x7

  Speed: Up to 40 Gb/s x1

  Current Link Width: 0x1

  Link Controller Firmware Version: 0.26.0

b) Your graphics card is recognized (Hardware -> Graphics)  YES

NVIDIA GeForce GTX 1080 Ti

  Chipset Model: NVIDIA GeForce GTX 1080 Ti

  Type: External GPU

  Bus: PCIe

  PCIe Lane Width: x4

  VRAM (Dynamic, Max): 11263 MB

  Vendor: NVIDIA (0x10de)

  Device ID: 0x1b06

  Revision ID: 0x00a1

  ROM Revision: VBIOS 86.02.39.00.2e

  Automatic Graphics Switching: Supported

  gMux Version: 4.0.29 [3.2.8]

  Metal: Supported, feature set macOS GPUFamily1 v3

Second:
Try the hot plug immediately after the display is lit (backlight on, no logo yet)

HAVEN'T tried yet as seems to be working perfectly - unless I am doing something wrong.  I just stacked and edited 15 (!) 4k streams and viewed in FULL resolution in premiere pro with no skipping at all.  Unreal.   Also shows on Geekbench 4 and is testable, although only on OPENCL as I got the trial version.Thoughts?  Thanks again in advance

@glenn_aitken
Wow, what an awkward workaround. But nice that you got it working.

@lancetan36
what you you mean, you used @goalque's script. the automate-eGPU.sh is for Sierra only not for High Sierra. The .kext is for legacy AMD GPU
Which script exactly?

Ohhhhh now I see my mistake. I used goalque's script for the 1050 when I am running on High Sierra. Is there another script for High Sierra (for nVIDIA GPUs)?

Side question: does .kext support Rx 560 as well for high sierra? 

@fr34k

@lancetan36
first: before you continue use the uninstall parameter in @goalque's script
second: yes there are 2, one for ≤10.13.3 and a temporary for 10.13.4 (which one do you have)
third: yes the kext does support the 560

Tell me which version of macOS you're on and I will assist you further,

@fr34k, what is your Paypal address? can you PM me cheers

@fr34k, yes please do. I need your help. 

Okay so, I am running on High Sierra 10.13.3, RX 560. How do I uninstall Goalque's script?

@lancetan36
superb! 10.13.3 is perfect:

Download @goalque's script
curl -o ~/Downloads/automate-eGPU.sh "https://raw.githubusercontent.com/goalque/automate-eGPU/master/automate-eGPU.sh"
Go into downloads folder:
cd ~/Downloads/
Make script executable:
sudo chmod +x automate-eGPU.sh
Execute:
sudo ./automate-eGPU.sh -uninstall
Remove script again:
rm automate-eGPU.sh
Reboot:
sudo reboot

While you do that, I'll compile the rest

Do you want the NVIDIA or the AMD to run?

I have the AMD M370x in my MacBook. Does the automatic graphics switching in the OS power settings affect anything? Should it be turned off?

Im not running an external monitor. Sometimes the NVDA driver manager sees the eGPU sometimes it doesn’t and it goes black screen kind of often. I think I’m gonna just go back to an earlier version of Mac for now. What would be the most reliable Mac version to roll back to?

@airoscar
For me it does not affect anything, some people report not properly working apps and monitors. Definitely worth a try, BUT NOT on 10.13.4. There it forces the internal monitor go black.
10.13.3 or 10.13.3 SU are both fine