[Sticky] [SCRIPT] Enable AMD & NVIDIA eGPUs on TB1/2/3 Macs on macOS 10.13.4+  

Page 2 / 31 Prev Next
  RSS

TheFurious
(@thefurious)
Active Member
Joined: 9 months ago
Posts: 13
April 5, 2018 2:34 pm  
Posted by: theitsage
Posted by: mac_editor

Has anyone tried with tb1 Mac? Haven’t heard of a success yet and can’t test on my end.

I will try tonight with a 2011 17" MBP [TB1]. It was successful with kext swap so I bet your script will work.

 

@thefurious RX 460/560 is a bit of a wild card. While there are drivers and support, I've seen issues with external monitor output. I will test using Breakaway Puck 560 and provide an update.

Thanks a lot!

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 3:06 pm  

@devild and I were privately discussing getting NVIDIA eGPUs to work on 10.13.4 and are onto something. More patching needed (and not sure what), but if you use the kext-swapping trick for AMDGPUWrangler (from 10.13.3/4 B1) with an updated NVIDIAEGPUSupport for 10.13.4, it should work for now without hot-plug support. @devild got it working in his testing. Nice going!

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


goalque, theitsage and devild liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 3:16 pm  

@fr34k I created a local version of your TB script to test because got a 'newLine' error when executing with curl. Nonetheless, on my test system, for the system_profiler grep command, the first line oddly was "Speed: Up to 20 / 10 Gb/s x1", hence match fails for TB2. Testing on my daily installation (10.13.4), I get the correct output. On the scratch installation on which I test scripts, I got the above output, though it is worth noting it is running 10.13.5 B1.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 12 months ago
Posts: 387
April 5, 2018 3:20 pm  

@mac_editor
that was the plan all along.
It was just a sample code.
Speed: Up to 20 / 10 Gb/s x1 ? wow that's an odd output, so you will need to refine it...

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 3:25 pm  
Posted by: fr34k

@mac_editor
that was the plan all along.
It was just a sample code.
Speed: Up to 20 / 10 Gb/s x1 ? wow that's an odd output, so you will need to refine it...

Copy that.

Exactly, never seen that output before. Maybe a beta thing.. Let's see.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1314
April 5, 2018 3:37 pm  
Posted by: mac_editor

@devild and I were privately discussing getting NVIDIA eGPUs to work on 10.13.4 and are onto something. More patching needed (and not sure what), but if you use the kext-swapping trick for AMDGPUWrangler (from 10.13.3/4 B1) with an updated NVIDIAEGPUSupport for 10.13.4, it should work for now without hot-plug support. @devild got it working in his testing. Nice going!

So the AppleGPUWrangler was the cause for everything as I suspected? I quickly looked that IOFramebuffer part was mostly unchanged (not yet available from https://opensource.apple.com).  Haven't had any time to play with Nvidia cards.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 3:39 pm  
Posted by: goalque

So the AppleGPUWrangler was the cause for everything as I suspected? I quickly looked that IOFramebuffer part was mostly unchanged (not yet available fromhttps://opensource.apple.co m" target="true"> https://opensource.apple.com ). Haven't had any time to play with Nvidia cards.

Seems to be the case. I don't have an NVIDIA card to play with + I have an annoying Mac even if I did.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


goalque liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 4:01 pm  
Posted by: goalque

I have a feeling that Apple kept Intel happy, and left a backdoor for us. If they deliberately wanted to block older TB technology, there are more effective ways to accomplish that in the EFI level.

I think so too. The fact that drivers activate regardless of the patch is a big giveaway.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
PsyPryss
(@psypryss)
Eminent Member
Joined: 11 months ago
Posts: 49
April 5, 2018 4:17 pm  

Looks like it works on a fresh install of 10.13.4  on a tb1 mbp. 

Thanks to everyone who helped make this happen!!!

Mid 2012 15" (Non-Retina) MPB GT650M + RX580 (AKiTio Node via TB3 -> TB2/TB1 Adaptor) macOS 10.13.4/Win10


mac_editor and theitsage liked
ReplyQuote
kyorosweb
(@kyorosweb)
New Member
Joined: 1 year ago
Posts: 4
April 5, 2018 4:23 pm  
Posted by: PsyPryss

Looks like it works on a fresh install of 10.13.4  on a tb1 mbp. 

Thanks to everyone to help make this happen!!!

Yes!! It works on a 2011 mbp13 too!!!



Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


theitsage and mac_editor liked
ReplyQuote
ikir
 ikir
(@ikir)
Prominent Member
Joined: 2 years ago
Posts: 756
April 5, 2018 4:33 pm  

Great news posted on eGPU.it as well

eGPU.it | LG 34" 4K 34UC88 curved ultrawide display
MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD --> my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64


ReplyQuote
punk.kaos
(@punk-kaos)
Active Member
Joined: 2 years ago
Posts: 15
April 5, 2018 4:48 pm  

Worked great on my 13in MBA with an RX560 after I patched my kexts for IOPCITunnelCompatible. Thanks a ton!

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1314
April 5, 2018 4:52 pm  
Posted by: punk.kaos

Worked great on my 13in MBA with an RX560 after I patched my kexts for IOPCITunnelCompatible. Thanks a ton!

That was quick! Thanks for reporting 🙂

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


punk.kaos and mac_editor liked
ReplyQuote
secretsquirrel
(@secretsquirrel)
Active Member
Joined: 12 months ago
Posts: 11
April 5, 2018 4:56 pm  

Thanks for the script, worked like a charm on a MacBook Pro 2014 and TB2.

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


mac_editor liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 4:58 pm  

I think I can now mark the script as "safe-to-use" - touch wood.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


tiagoamaro and theitsage liked
ReplyQuote
joysthokkins
(@joysthokkins)
Active Member
Joined: 12 months ago
Posts: 9
April 5, 2018 5:04 pm  

Thank you!✨

rMBP 2014 750m 10.13.4 + Sonnet Breakaway 550 + Sapphire Vega 64 –> iMac 2009 as display
DaVinci Resolve Studio 15b5 | FCPX 10.4.3


ReplyQuote
Roman E
(@roman_e)
New Member
Joined: 8 months ago
Posts: 1
April 5, 2018 5:24 pm  

Will this fix the displaylink issues outlined here?

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 5:26 pm  
Posted by: Roman E

Will this fix the displaylink issues outlined here?

Reading a bit about it, I'd say no, but you're free to try 😉

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
(@mikey_schreurs)
Active Member
Joined: 11 months ago
Posts: 12
April 5, 2018 5:41 pm  

Mac Pro Late 2013 with XFX RX580 is working! Like a charm. Thank you so Kindly for your work!

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


artik and mac_editor liked
ReplyQuote
igerard
(@igerard)
Estimable Member
Joined: 2 years ago
Posts: 117
April 5, 2018 5:49 pm  
Posted by: mac_editor
Posted by: goalque

I have a feeling that Apple kept Intel happy, and left a backdoor for us. If they deliberately wanted to block older TB technology, there are more effective ways to accomplish that in the EFI level.

I think so too. The fact that drivers activate regardless of the patch is a big giveaway.

I think that Apple just want to be sure that nobody is going to ask support on that, in case of something go bad.

ok to make it working, but don’t  want to get request for old machines with a lot of differents configurations because computer around since a long time.

anyway... very good news

MBP 2018, Touch Bar, i7 2.6 GHz, 32 GB RAM, 1T SSD, Radeon 560X... very nice!
eGPU : Akitio Node + RX 580 + GTX 980 Ti + Vega64


goalque and theitsage liked
ReplyQuote
PsyPryss
(@psypryss)
Eminent Member
Joined: 11 months ago
Posts: 49
April 5, 2018 5:54 pm  

@mac_editor
I tried uninstalling purge_nvda after installing purge_wrangler and can’t boot in to the system. Anyway to get it to boot in again? I tried the system restore to remove the files in Library/Application Support but there aren’t any references to purge_nvda. Any way to get it to boot again?

Mid 2012 15" (Non-Retina) MPB GT650M + RX580 (AKiTio Node via TB3 -> TB2/TB1 Adaptor) macOS 10.13.4/Win10


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 6:02 pm  
Posted by: PsyPryss

@mac_editor
I tried uninstalling purge_nvda after installing purge_wrangler and can’t boot in to the system. Anyway to get it to boot in again? I tried the system restore to remove the files in Library/Application Support but there aren’t any references to purge_nvda. Any way to get it to boot again?

Are you working with multiple installations here? If you run two macOS installations on the same machine, and run purge-nvda.sh on one installation, kexts are moved and NVRAM is updated. But then if you boot into the other installation that did not run the patch, the NVRAM value is discarded, and the system that ran the patch won't boot. I will be updating purge-nvda.sh with a solution that works across system installations soon.

So if you installed purge-nvda.sh on both systems, and then uninstall on one, the other won't boot because the NVRAM value has reset, while kexts are still somewhere. So on the installation that is not booting, you can try in Single User Mode (select this install on boot then Press and hold CMD+S immediately):

mount -uw /
cd <navigate to where purge-nvda.sh is>
./purge-nvda.sh uninstall

 I need more context here so can't say what's up in your system. You can simply install macOS 10.13.4 on top without data loss in the worst case.

Also in /Library/Application Support/ folder name should be Purge-NVDA if its there with the backup of your kexts if it ran fine.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
Sovereign
(@sovereign)
Active Member
Joined: 2 years ago
Posts: 19
April 5, 2018 6:27 pm  
Posted by: mac_editor

@devild and I were privately discussing getting NVIDIA eGPUs to work on 10.13.4 and are onto something. More patching needed (and not sure what), but if you use the kext-swapping trick for AMDGPUWrangler (from 10.13.3/4 B1) with an updated NVIDIAEGPUSupport for 10.13.4, it should work for now without hot-plug support. @devild got it working in his testing. Nice going!

Umm, but is there an updated NVIDIAEGPUSupport for 10.13.4? Haven't seen one or am I missing something?

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 6:28 pm  
Posted by: Sovereign
Umm, but is there an updated NVIDIAEGPUSupport for 10.13.4? Haven't seen one or am I missing something?

@fr34k & @devild are working on it.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


fr34k and Sovereign liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 12 months ago
Posts: 387
April 5, 2018 7:05 pm  
Posted by: mac_editor
Posted by: Sovereign
Umm, but is there an updated NVIDIAEGPUSupport for 10.13.4? Haven't seen one or am I missing something?

@fr34k & @devild are working on it.

and @mac_editor as well!
There's a lot that is connected here...

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


Fry-man22 and mac_editor liked
ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 2 years ago
Posts: 3201
April 5, 2018 7:17 pm  

Ideally we'll have a script/installer that identifies your Mac + eGPU configuration then injects the necessary workarounds to make it "just work".

Best ultrabooks for eGPU use

eGPU enclosure buying guide

86 external GPU build guides


PsyPryss, artik and Sovereign liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 12 months ago
Posts: 387
April 5, 2018 7:19 pm  

@itsage
currently on it.
I'll code as much as possible into my 
script

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 7:25 pm  
Posted by: theitsage

Ideally we'll have a script/installer that identifies your Mac + eGPU configuration then injects the necessary workarounds to make it "just work".

You read our minds. Already implemented automatic thunderbolt detection (thanks to @fr34k) and some other enhancements for purge-wrangler.sh (will mark as release later).

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


PsyPryss, theitsage and fr34k liked
ReplyQuote
laimis17
(@laimis17)
Active Member
Joined: 9 months ago
Posts: 11
April 5, 2018 7:32 pm  

@mac_editor Patch applied successfully. Sadly eGPU is not enabled on my TB1 devices: mac mini late 2012 and mbp 17 late 2011. But i think it has to do something with gpu that i'm using: Radeon Pro WX 4100.

Tried applying automate-eGPU script on top. Don't do this. Kernel paniced and made system unbootable. Restored by copying AMD* kexts from another system.

MBP17 late 2011 TB1 Radeon Pro WX 4100


goalque liked
ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 9 months ago
Posts: 38
April 5, 2018 7:34 pm  

"AMDGPUWrangler (from 10.13.3/4 B1) with an updated NVIDIAEGPUSupport for 10.13.4" 
Is it posible to provide this updated NVIDIAEGPUSupport for 10.13.4?
Cheers

PS: Ops, just saw that @fr34k & @devild are working on it. 🙂
Fingers crossed

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 7:49 pm  

Could people test the new version of the script (1.1.0)? Its not changing any patching and won't affect eGPU support, but is simply an improved and somewhat better written version. Download it here. The usage guide in the initial post does not apply to this new script as there are slight changes. To run it follow the instructions here. I want people to test this so that I can confirm I have a good foundation to develop any further "patching" - the nitty gritty.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1314
April 5, 2018 8:16 pm  
Posted by: laimis17

@mac_editor Patch applied successfully. Sadly eGPU is not enabled on my TB1 devices: mac mini late 2012 and mbp 17 late 2011. But i think it has to do something with gpu that i'm using: Radeon Pro WX 4100.

Tried applying automate-eGPU script on top. Don't do this. Kernel paniced and made system unbootable. Restored by copying AMD* kexts from another system.

Automate-eGPU.kext is for 10.13 only as the menu selection says. Reinstalling from the recovery (Command-R) won't wipe your personal files, just the S/L/E folder. A good way to start over if you don't have a Time Machine backup.

Add IOPCITunnelCompatible true into AMDBaffinGraphicsAccelerator personality (preferably by overriding from the codeless kext), rebuild caches and try again.

RX 560 activated this way as @punk.kaos said, why wouldn't others as well? They are both Baffin.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
macunix
(@macunix)
New Member
Joined: 8 months ago
Posts: 3
April 5, 2018 8:46 pm  

I had an issue with 1.0 where the TB1 patch didn't work, but he TB2 patch did.  I have a Mid-2013 Macbook Air with TB1.  I will test the 1.1 script and let you know.

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1571
April 5, 2018 8:49 pm  
Posted by: macunix

I had an issue with 1.0 where the TB1 patch didn't work, but he TB2 patch did.  I have a Mid-2013 Macbook Air with TB1.  I will test the 1.1 script and let you know.

Interesting, are you sure you typed in the correct option (for v1.0):

sudo ./purge-wrangler.sh patch tb1

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
laimis17
(@laimis17)
Active Member
Joined: 9 months ago
Posts: 11
April 5, 2018 9:06 pm  

@goalque You were right again. 
It's so beautiful i want to cry!
So, TB1 works!

Guys. @goalgue @mac_aditor Thank You.
Please send me Your paypal account.

MBP17 late 2011 TB1 Radeon Pro WX 4100


goalque, fr34k and mac_editor liked
ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 9 months ago
Posts: 38
April 5, 2018 9:35 pm  

mac_editor, in the newest 1.1.0 script, while following the instructions i get:

sudo ./purge-wrangler.sh patch tb2

sudo: ./purge-wrangler.sh: command not found

I've tested with 

"sudo: ./purge-wrangler.sh" only and it seems to work

However I'm missing the newest NVIDIAEGPUSupport for things to work. At least the boxes are seen in thunderbolt port and CUDA panel detects connected GPU's 

As mentioned, that instruction is for v1.0.0, not v1.1.0. NVDAEGPUSupport needs more work at the moment.

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
Page 2 / 31 Prev Next