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

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

 of  199
  RSS

Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 3 years ago
 

I think I have this working (partially).

2017 15" MBP (internal GPU - Radeon Pro 560 and Intel 630)

Sonnet eGPU (550)

EVGA GeForce 1070, latest driver linked earlier in the thread seemed to install but I had to dismiss a warning that I think was related to SIP. Also had to dismiss a Nvidia Device Manager warning (could not load).

Booted Recovery, disabled kext for SIP via Terminal.

Rebooted, ran the package installer version of the app noted on Page 1. Seemed to go OK but I got the Nvidia Device Manager warning again and dismissed it. Odd but if I go directly into Preferences I can open it, change settings, check for driver updates, etc. Seems to work, just not loading when I first boot up.

Turned on GPU, connected TB3 cable (2m active), logged out and back in, my System Report DOES show the correct Nvidia card as being installed and the CudaZ app does show active performance scores updating in background. However I cannot get this card to drive a third party display via DP cable. System recognizes two displays and lets me change aspects of the arrangement but the external screen just stays blank. Expected?

Also in After Effects testing, even though AE sees the card and I set experimental support for CUDA to be active, I don't think it's actually accelerating the layer transforms in my comp (as an example of something that now supports GPU acceleration in cc 2018).

What do you guys think?

Thunderbolt 3 Macs, Sonnet and OWC eGPUs, 4K Displays, etc


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 

CUDA-Z detects my card, but again, apps dont... hmmm...

Screen Shot 2017 10 25 at 18.58.13

PS not detecting/using it either...

Screen Shot 2017 10 25 at 19.05.16
Screen Shot 2017 10 25 at 19.07.03

 

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix

 
2017 13" MacBook Pro [7th,2C,U] + RX 560 @ 32Gbps-TB3 (AKiTiO Node Lite) + macOS 10.15.4 & Win10 [build link]  


ReplyQuote
yifanlu
(@yifanlu)
Eminent Member
Joined: 3 years ago
 
Posted by: Chippy McChipset

I think I have this working (partially).

2017 15" MBP (internal GPU - Radeon Pro 560 and Intel 630)

Sonnet eGPU (550)

EVGA GeForce 1070, latest driver linked earlier in the thread seemed to install but I had to dismiss a warning that I think was related to SIP. Also had to dismiss a Nvidia Device Manager warning (could not load).

Booted Recovery, disabled kext for SIP via Terminal.

Rebooted, ran the package installer version of the app noted on Page 1. Seemed to go OK but I got the Nvidia Device Manager warning again and dismissed it. Odd but if I go directly into Preferences I can open it, change settings, check for driver updates, etc. Seems to work, just not loading when I first boot up.

Turned on GPU, connected TB3 cable (2m active), logged out and back in, my System Report DOES show the correct Nvidia card as being installed and the CudaZ app does show active performance scores updating in background. However I cannot get this card to drive a third party display via DP cable. System recognizes two displays and lets me change aspects of the arrangement but the external screen just stays blank. Expected?

Also in After Effects testing, even though AE sees the card and I set experimental support for CUDA to be active, I don't think it's actually accelerating the layer transforms in my comp (as an example of something that now supports GPU acceleration in cc 2018).

What do you guys think?

"System recognizes two displays and lets me change aspects of the arrangement but the external screen just stays blank."

That was the exact problem I had until I switched to another display. May I ask if your setup worked fine in Sierra? I'm trying to pinpoint the issue to either OSX or my monitor.

NVIDIAEGPUSupport - Nvidia eGPU support for macOS High Sierra
Clover-DSDT+apple_set_os.efi - Macbook Pro Windows error 12 & iGPU fixed Bootloader
---
late-2016 13" MacBook Pro Touchbar + [email protected] (HP OMEN Accelerator) + macOS10.13 & Win10

 
2016 13" MacBook Pro [6th,2C,U] + GTX 1060 @ 16Gbps-TB3 (HP OMEN Accelerator) + macOS 10.13 & Win10 [build link]  


ReplyQuote
krak3nn
(@krak3nn)
Active Member
Joined: 3 years ago
 
Posted by: geaguirre80

I can confirm the hotplug-logout-login trick with my MBP 15" 2016 + 980ti + Akitio Node, sadly my hdmi cable has a couple of small cuts and only output signal in bootcamp but internal screen and CUDA works perfect.

I can also confirm this method works with my Akitio Node tested with a GTX980 and GTX1080 Ti.

Full procedure is:
1. Leave eGPU disconnected.
2. Boot into OS.
3. Plug eGPU in. You can confirm in System Information if your NVIDIA GPU is seen.
4. Log out.
5. Log back in and the GPU should initialized along with the external monitor if you have one attached.

EDIT: Display out is working fine but applications like the Adobe CC suite does not detect the GPU.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 

I get the feeling I can’t drive my LG Display as the display needs to be connected to the GPU. 

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix

 
2017 13" MacBook Pro [7th,2C,U] + RX 560 @ 32Gbps-TB3 (AKiTiO Node Lite) + macOS 10.15.4 & Win10 [build link]  


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 3 years ago
 
Posted by: yifanlu
Posted by: Chippy McChipset

I think I have this working (partially).

2017 15" MBP (internal GPU - Radeon Pro 560 and Intel 630)

Sonnet eGPU (550)

EVGA GeForce 1070, latest driver linked earlier in the thread seemed to install but I had to dismiss a warning that I think was related to SIP. Also had to dismiss a Nvidia Device Manager warning (could not load).

Booted Recovery, disabled kext for SIP via Terminal.

Rebooted, ran the package installer version of the app noted on Page 1. Seemed to go OK but I got the Nvidia Device Manager warning again and dismissed it. Odd but if I go directly into Preferences I can open it, change settings, check for driver updates, etc. Seems to work, just not loading when I first boot up.

Turned on GPU, connected TB3 cable (2m active), logged out and back in, my System Report DOES show the correct Nvidia card as being installed and the CudaZ app does show active performance scores updating in background. However I cannot get this card to drive a third party display via DP cable. System recognizes two displays and lets me change aspects of the arrangement but the external screen just stays blank. Expected?

Also in After Effects testing, even though AE sees the card and I set experimental support for CUDA to be active, I don't think it's actually accelerating the layer transforms in my comp (as an example of something that now supports GPU acceleration in cc 2018).

What do you guys think?

"System recognizes two displays and lets me change aspects of the arrangement but the external screen just stays blank."

That was the exact problem I had until I switched to another display. May I ask if your setup worked fine in Sierra? I'm trying to pinpoint the issue to either OSX or my monitor.

Actually never attempted on 10.12.x. Both the host computer and the card are new. However to Eightarmedpet's comment, it is an LG display that is not running properly. I can add that it doesn't matter whether the connection is HDMI or DP — neither works.

If others have a 2017 15" MBP + Sonnet box + GeForce 10x0 series that both runs CUDA on a host-display-only setup and can run a third party display if needed, would be curious to know the brand of display and connection type.

Thunderbolt 3 Macs, Sonnet and OWC eGPUs, 4K Displays, etc


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 3 years ago
 
Posted by: krak3nn
Posted by: geaguirre80

I can confirm the hotplug-logout-login trick with my MBP 15" 2016 + 980ti + Akitio Node, sadly my hdmi cable has a couple of small cuts and only output signal in bootcamp but internal screen and CUDA works perfect.

I can also confirm this method works with my Akitio Node tested with a GTX980 and GTX1080 Ti.

Full procedure is:
1. Leave eGPU disconnected.
2. Boot into OS.
3. Plug eGPU in. You can confirm in System Information if your NVIDIA GPU is seen.
4. Log out.
5. Log back in and the GPU should initialized along with the external monitor if you have one attached.

Going to try this next. I tried something similar during the first series of tests but worth a shot. 

Thunderbolt 3 Macs, Sonnet and OWC eGPUs, 4K Displays, etc


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: Eightarmedpet

I get the feeling I can’t drive my LG Display as the display needs to be connected to the GPU. 

That's the rule number one with all eGPU setups, for now. You also have to set the eGPU display as the primary in system preferences/displays.

There is no system wide eGPU selection logic as with Windows. The app developer has made a decision which GPU to use.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
Excubitoro
(@excubitoro)
Trusted Member
Joined: 3 years ago
 

Macbook pro 2016 15" + Gaming box 1070

Did all the steps and can see monitor and nvidia driver correctly, but the external monitor is black. I'm using a DP for the output, could that be it. Doesn't it work with Display Port?

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 3 years ago
 

Here's what I can confirm with the 2017 15" MBP (AMD and Intel graphics), Sonnet 550W eGPU, EVGA GTX 1070 + the latest drivers and app from this thread:

Driving third party displays does not work regardless of connection type or whether you do an extra logout+login session.

Tested on: LG display, Asus 4K, HP Envy 4K via both DP and HDMI.

What happens with this setup depends on which display is set as the primary system display:

If set to the Mac's display, the third party screen simply remains blank and goes to sleep after a minute. It's strange because in the System Report, if I highlight the GTX 1070, it *shows* the connected display by name, its resolution etc. And the display's OSD will show that it sees which connector is being used... but it's basically like there's an acknowledgement of connection but a lack of signal.

If the third party display is set as the primary, then something different happens, very similar to what is shown in some of the other posts. The laptop display stays active but becomes blurred, while the connected display remains blank. Then at that point you're stuck because no more menus are available. When you power down or disconnect the eGPU the system freezes and restarts.

So basically the only thing I could get working was direct-to-host CUDA-Z driver reports and live benchmark scores, and in some cases third party apps like AE (in addition to the system report) recognize the specific card that is present, how much VRAM it has, etc. So we're almost there but not quite. Smile

Thunderbolt 3 Macs, Sonnet and OWC eGPUs, 4K Displays, etc


ReplyQuote
 of  199