Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid
 
Notifications
Clear all

Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid  

 of  68
  RSS

psonice
(@psonice)
Estimable Member
Joined: 2 years ago
 

@goalque nearly but not quite working on iMac (2014 with Radeon 295x [edit: plus 1080ti in sonnet 550 over tb2]). Setup:

- held R on boot, restored macOS 10.13.5
- removed nvdaegpu kext (which was still in extensions)
- updated Nvidia drivers
- unplugged everything

i then installed your tools on an external USB drive with the GPU connected, disconnected after GPU detected. Installation went fine. Booted via EFI from then on. Results:

- Boot with eGPU connected: black internal display, severe lag

- attach EGPU after login, logout and back in: corrupt internal display with visible mouse, external display connected to eGPU working fine 

I tried variations with the DisplayPort cable attached later, no joy

Also tried setting skipdata in the plist, no difference  tried disabling forceIntegrated too as there’s no integrated GPU in this iMac, no difference.

Anything else you want me to try? And is it worth trying pure mode?

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

.

goalque liked
ReplyQuote
philw
(@philw)
Trusted Member
Joined: 3 years ago
 

@psonice similar result on my 2014 27" - black screens and basically no success with hybrid...

Given up on all my Macs...but successfully running: Gigabyte Designare Z390, Core i9-9900K, 64GB RAM, 2x Internal GTX 1080TI, 2x GTX 1070 eGPU (Sonnet eGFX)

 
2018 Gigabyte Z390 Designare (GTX1080TIx2) [9th,8C,K] + GTX 1070 @ 32Gbps-TB3 (Sonnet Breakaway 350) + Win10 [build link]  


goalque and psonice liked
ReplyQuote
itsage
(@itsage)
Illustrious Member Admin
Joined: 4 years ago
 

If you experience black screen, check your Login items. Check and remove some items the folders, "LaunchAgents" and "LaunchDaemons" in /Library as well as ~/Library.

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide

 
2020 13" MacBook Pro [10th,4C,G] + RX 5700 @ 32Gbps-TB3 (Prototype eGPU Enclosure) + macOS 10.15.4 & Win10 1903 [build link]  


psonice and goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 

Thanks for the first iMac reports. This was a bit expected. Does it have Intel iGPU at all? If not, then there is no workaround atm due to Nvidia eGPU & AMD dGPU framebuffer conflict. Furthermore, your dGPU may appear differently in ioreg than with MBPs. Pls type "ioreg -l > ~/Desktop/ioreg.txt" and search for the block by the dGPU device id.

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]  


itsage liked
ReplyQuote
philw
(@philw)
Trusted Member
Joined: 3 years ago
 

@goalque No Intel, just AMD Radeon R9 M290X 🙂

Given up on all my Macs...but successfully running: Gigabyte Designare Z390, Core i9-9900K, 64GB RAM, 2x Internal GTX 1080TI, 2x GTX 1070 eGPU (Sonnet eGFX)

 
2018 Gigabyte Z390 Designare (GTX1080TIx2) [9th,8C,K] + GTX 1070 @ 32Gbps-TB3 (Sonnet Breakaway 350) + Win10 [build link]  


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 
Posted by: psonice

- attach EGPU after login, logout and back in: corrupt internal display with visible mouse, external display connected to eGPU working fine 

This was good news. The eGPU monitor as the primary (the dock visible)? If so, you can use SwitchResX's internal screen disabling feature to get rid of UI lag.

If you disconnect the eGPU display, is it possible to use CUDA-Z or other GPGPU-oriented apps?

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
psonice
(@psonice)
Estimable Member
Joined: 2 years ago
 
Posted by: goalque

Does it have Intel iGPU at all? If not, then there is no workaround atm due to Nvidia eGPU & AMD dGPU framebuffer conflict. Furthermore, your dGPU may appear differently in ioreg than with MBPs. Pls type "ioreg -l > ~/Desktop/ioreg.txt" and search for the block by the dGPU device id.

No intel GPU. 

Took a look in ioreg. The device ID according to system profiler is 0x6938. Searching for that gives no direct matches but various strings beginning with that number. Items that match:

AMD9000ControllerWrangler
AMDRadeonX4000_AMDRadeonHWServicesVI
AMD9000Controller
AMDRadeonX4000_AMDTongaGraphicsAccelerator

There's also some serious WTF grade oddness going on now. I have the external display connected to the iMac directly instead of the eGPU (which is currently disconnected). Well, the mac fires up OK with both monitors "working", but it's now detecting the internal (27"/5K) display as 18". Wat. And it thinks it has an 8:9 aspect ratio and offers 800x900 resolution. It's a bit stretched to say the least...

Don't have SwitchRes but ResExtreme reports it as 18" with odd resolutions too.

Will reboot without EFI and see if that still happens.

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

.

ReplyQuote
philw
(@philw)
Trusted Member
Joined: 3 years ago
 

I wish Apple would hurry up with whatever the new Mac Pro is.... I feel like iMac and C4D / Cuda rendering are destined to be troublesome 🙂 unless I ditch all my GPU renderers and spend the cash on processor cores for Arnold instead...

Given up on all my Macs...but successfully running: Gigabyte Designare Z390, Core i9-9900K, 64GB RAM, 2x Internal GTX 1080TI, 2x GTX 1070 eGPU (Sonnet eGFX)

 
2018 Gigabyte Z390 Designare (GTX1080TIx2) [9th,8C,K] + GTX 1070 @ 32Gbps-TB3 (Sonnet Breakaway 350) + Win10 [build link]  


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 

@psonice iMac's Thunderbolt ports are wired to AMD dGPU - as with the nMP, I suppose you cannot use any of them normally, while the Nvidia eGPU is plugged in.

There should be matches: ioreg -l | grep 0x6938 (or 0x69381002). 1002 is vendor id. Would be interesting to see the result of this command:

ioreg -n GFX0@0 | sed -E '/{/,/\| }$/!d' | grep \"device-id\" | sed 's/.*\<\(.*\)\>.*/\1/' | sed -E 's/^(.{2})(.{2}).*$/\2\1/'

 

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
psonice
(@psonice)
Estimable Member
Joined: 2 years ago
 
Posted by: goalque

Would be interesting to see the result of this command:

ioreg -n GFX0@0 | sed -E '/{/,/\| }$/!d' | grep \"device-id\" | sed 's/.*\<\(.*\)\>.*/\1/' | sed -E 's/^(.{2})(.{2}).*$/\2\1/'

 

That's a lot of of regex 😉 Output of that: 6938

And yes, there are matches for 0x69381002.

What do you think the block is here? It's clearly workable somehow as it works fine under 10.13.3 with the old enabling script, just not with Apple's changes with 10.13.4+. Is the AMD/Nvidia framebuffer conflict new in 10.13.4?

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

.

ReplyQuote
 of  68