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
 

Oh yes, and you asked about running accelerated stuff - when the internal display is corrupted (in which case the external display is set to primary and is attached to the eGPU), the eGPU side works fine including acceleration.

As it happens I made a (demoscene) demo last weekend and I put a GPU selector in the UI - i.e. it'll list all available (metal capable at least) GPUs, and let you switch between them and see what performance is like immediately, so it's easy to check if there are any issues there. (If anyone is in need of a mostly useless but maybe entertaining app that lets you check GPU support:  https://demozoo.org/productions/188683/ )

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

.

ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 
Posted by: psonice
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?

Something new in 10.13.4.

https://egpu.io/forums/mac-setup/script-fr34ks-macos-egpu-sh-one-script-all-solutions-fully-automated/paged/7/#post-36175

Status update: I was able to bypass Clover's complex DefaultVolume logic. Now it's much simpler.

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
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

iMac users that have built-in AMD cards who are facing issues with NVIDIA eGPU: maybe disabling AMD GPU acceleration (I'm sure iMac Pro users don't want that so they should skip out) might help (cannot test myself):

sudo nvram boot-args="-amd_no_dgpu_accel"

Do try. If it doesn't work out, just reset NVRAM or do:

sudo nvram boot-args=""

In recovery or if you were able to boot.

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


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

Thanks @mac_editor. Just tried with the M370X, worked as intended, progress bar halted and the Apple logo stayed on the internal screen. Luckily, the USB stick "EFI Boot" came to rescue and produced Nvidia eGPU screen output. No dGPU acceleration, the internal display was still there. Oddly, moved windows into the darkness became half black as well 😀

I guess we need to disable the dGPU completely or the framebuffer part.

SIP nvram protection must be disabled, otherwise this command doesn't work.

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
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@goalque Thank you for testing 😉 

Switching the mux to iGPU would resolve internal screen stuck on Apple logo (ForceIntegrated).

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@goalque There is actually a very interesting agdp=<board-id> boot-arg too. So one can pass a different mac board ID to AppleGraphicsDevicePolicy. Wouldn't that be interesting. Have been posting on the macrumors forum (about failing dGPU) where I learnt about this one 😉

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


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

@goalque Thank you for testing 😉 

Switching the mux to iGPU would resolve internal screen stuck on Apple logo (ForceIntegrated).

The previous test was conducted with the ForceIntegrated=true flag.

Test 2: Unchecked "Automatic Graphics Switching" (dGPU always on), ForceIntegrated=false -> The same Apple logo and progress bar stuck at a halfway. The UI feels a bit snappier. Safari's top bar still goes black (gradient) sometimes if you move it too far to the left.

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
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

Interesting. I would have bet my money on the internal display working fine if the mux was set to iGPU. I can accomplish exactly this on my NVIDIA MBP (tho not using Clover). Not setting mux = same exact issue of Apple logo being stuck. Perhaps manually setting the mux (using the long NVRAM power prefs command) may help. Unsure.

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


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

Interesting. I would have bet my money on the internal display working fine if the mux was set to iGPU. I can accomplish exactly this on my NVIDIA MBP (tho not using Clover). Not setting mux = same exact issue of Apple logo being stuck. Perhaps manually setting the mux (using the long NVRAM power prefs command) may help. Unsure.

Maybe it's about timing, nvram setting takes control before my EFI app tries to switch gmux state (too late). I will play a bit more, interesting.

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
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@goalque You can make selected gmux state permanent with agc=-1 boot-arg if needed. Have detailed these commands in the troubleshooting guide's command line section. But may cause eGPU to not work. 

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


goalque liked
ReplyQuote
 of  68