[SCRIPT] PurgeWrangler: AMD + NVIDIA eGPUs for all Thunderbolt Macs
 
Notifications
Clear all

[Solved] [SCRIPT] PurgeWrangler: AMD + NVIDIA eGPUs for all Thunderbolt Macs  

 of  170
  RSS

Sovereign
(@sovereign)
Active Member
Joined: 3 years ago
 
Posted by: mac_editor
Posted by: itsage

@rhenriques11 Another possible reason Apple blocked TB1/2 Macs from external GPU in 10.13.4 is to comply with Intel eGFX certification. In my observations, sleep and wake-up with an attached eGPU are not reliable. I wish Apple had given more explanation of non-TB3 exclusion.

It might just be this - but they sure have done a lazy job of excluding TB1/2 from what I've seen.

Don't ever encourage them to do better.  Mr. Green

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

.

mac_editor and itsage liked
ReplyQuote
rhenriques11
(@rhenriques11)
Eminent Member
Joined: 2 years ago
 

This is outstanding!! Check what appears in the menu bar eGPU widget if we startup with the eGPU connected to the monitor instead of the internal GPU! The name is recognized correctly. 

Screen Shot 2018 04 07 at 19.13.40

If two are connected, they appear just fine in the system profiler

Screen Shot 2018 04 07 at 19.21.14

but the name of the second one will be generic into the widget

Screen Shot 2018 04 07 at 19.21.25

It seems that the ports where we connect the eGPU's matter. Things seem only to work great if I connect to port 2 and 5. Otherwise some apps have CUDA errors.

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

.

charleszhao, PsyPryss, mac_editor and 3 people liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 
Posted by: rhenriques11

This is outstanding!! Check what appears in the menu bar eGPU widget if we startup with the eGPU connected to the monitor instead of the internal GPU! The name is recognized correctly.

Dual screen output working?

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

This is outstanding!! Check what appears in the menu bar eGPU widget if we startup with the eGPU connected to the monitor instead of the internal GPU! The name is recognized correctly.

Dual screen output working?

I have a Monitor directly connected to the CPU and another connected to one of the eGPUs. Both working good. The other external eGPU is just for processing. Agisoft photoscan, for instance, can use all available GPUs for calculations.

Here's how processing power is distributed accordingly to the processing power of each GPU. Notice how the once (in 2013) top notch AMD Fire Pro 500 now pales when compared to the Nvidias. 

Screen Shot 2018 04 07 at 20.16.50

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

.

ReplyQuote
rmvz3
(@rmvz3)
Trusted Member
Joined: 3 years ago
 
Posted by: Sovereign

It is in /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/

Thank you, Sovereign.

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

.

ReplyQuote
charleszhao
(@charleszhao)
Active Member
Joined: 2 years ago
 

"i have the same problem after i discrete NVIDIA GPU, use purge-nvda.sh, and also enable egpu on tb2 script. reboot and plug; the interal screen freez and external screen have no output signal. 

my mac is a late 2013 mbp retina with gtx 750m with Breakaway and rx580 8g"

guess what, not work just because my rx580 is something wrong, after i fixed the card, the script works fine

WX20180423 225132@2x
Snip20180421 1

 

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

.

ReplyQuote
Sickntired
(@sickntired)
New Member
Joined: 2 years ago
 

This thread has allowed me to use my AMD Vega 64 with my Mac Mini 2014 very easily!  Thanks!

However, I also have an Nvidia 1080 Ti that I would prefer to use because of its speed and because the card is quieter. 

What exactly do I need to do to get the 1080 Ti card working?  I haven't actually connected it yet as I wanted to be sure I did any necessary steps first. 

Thank you for any help!

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

.

ReplyQuote
rhenriques11
(@rhenriques11)
Eminent Member
Joined: 2 years ago
 
Posted by: rmvz3
Posted by: Sovereign

It is in /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/

Thank you, Sovereign.

From my experience, the AppleGPUWrangler.kext from 10.13.3 seems to be a lot more stable than the one from 10.13.4 Beta1. You will notice, in some cases, a slower startup, but the overall stability seems to be a lot better after. I was experiencing, in the beginning  occasional hangs during shutdown and, sometimes, the second eGPU failed to mount. Now it's solved with AppleGPUWrangler.kext 3.16.2 from MacOS 10.13.3. 

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

.

ReplyQuote
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

I second this statement. I was unable to get my Mac mini 2012 with a Sonnet box and RX580 to work with any of the scripts.

I was able to copy the 10.13.3 kext from Time Machine, rebuild kext cache and now all is working fine.

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


ReplyQuote
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

Yes. I had the same problem. I ended up restoring the kext from 10.13.3 via Time Machine and rebuilt the kext cache manually from the command line.

i think there might be an issue with one of the scripts that I used from here that did either incorrect tb1/2 detection patching and/or incorrect kext cache regeneration. I know I used the early version that would overwrite the original backup, so maybe that was part of my problem too.

i’ve read In one of the posts of a user that used the original script prior to tb1/2 auto detect having to pass in tb2 on a tb1 Mac mini to get it working. With that switch removed and now relying on auto detect being the only option.

i hope if the above is true the guys providing us help can fix this before the next OSX update reverts these changes.

Either way, thanks to all the folks in this forum for all the help and guidance this week.

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


ReplyQuote
 of  170