Setup & Software Discussions
[SCRIPT] fr34k's macOS-eGPU.sh - one script, all solutions, fully automated
 

[SCRIPT] fr34k's macOS-eGPU.sh - one script, all solutions, fully automated  

 of  21
  RSS

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

@goalque you’re able with boot with your 1060 plugged in with 387.10.10.10.30.107?

Yes, Apple logo & progress bar appear on the eGPU monitor at the end of the boot process (eGPU monitor set as the primary).

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
simplekitten
(@simplekitten)
Eminent Member
Joined: 1 year ago
 
Posted by: goalque
Posted by: simplekitten

@goalque you’re able with boot with your 1060 plugged in with 387.10.10.10.30.107?

Yes, Apple logo & progress bar appear on the eGPU monitor at the end of the boot process (eGPU monitor set as the primary).

hmm weird, mine couldn't is it because i have a nvidia dgpu and egpu + TB3 enclosure ?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

@simplekitten Your problem is likely the Nvidia dGPU and driver. I was using Apple's TB3 to TB2 adapter.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
simplekitten
(@simplekitten)
Eminent Member
Joined: 1 year ago
 

@goalque i've tried going through the success story etc. but couldn't find anyone with 10.13.4, nvidia e & dgpu with TB3 to TB2.
my setup:
Aorus 1080 gaming box --> TB3 to TB2 adapter --> TB2 cable --> late 2013 15" mbp.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@olivier_declementi)
Active Member
Joined: 1 year ago
 
Posted by: goalque

@simplekitten Your problem is likely the Nvidia dGPU and driver. I was using Apple's TB3 to TB2 adapter.

Hi goalque,

 For my case I have the exact same machine with you. 2015 15" with m370x. No joy.

 It doesn't work on bootcamp either (it was before)

Thanks

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

@goalque i've tried going through the success story etc. but couldn't find anyone with 10.13.4, nvidia e & dgpu with TB3 to TB2.
my setup:
Aorus 1080 gaming box --> TB3 to TB2 adapter --> TB2 cable --> late 2013 15" mbp.

@ovi_stoia has similar setup

"The only thing I had to do different was to connect the eGPU only after I see the Apple Logo".

This will be resolved in upcoming versions. @fr34k does not have time at the moment.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


fr34k liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: Olivier Declementi

Hi goalque,

 For my case I have the exact same machine with you. 2015 15" with m370x. No joy.

 It doesn't work on bootcamp either (it was before)

Thanks

We cannot help with "no joy", "something does not work". Pls try to describe you problem as detailed as possible and look at the system logs. Maybe the problem is the Aorus gaming box itself.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


fr34k liked
ReplyQuote
simplekitten
(@simplekitten)
Eminent Member
Joined: 1 year ago
 

@goalque ahh thank you!

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@olivier_declementi)
Active Member
Joined: 1 year ago
 
Posted by: goalque
Posted by: Olivier Declementi

Hi goalque,

 For my case I have the exact same machine with you. 2015 15" with m370x. No joy.

 It doesn't work on bootcamp either (it was before)

Thanks

We cannot help with "no joy", "something does not work". Pls try to describe you problem as detailed as possible and look at the system logs. Maybe the problem is the Aorus gaming box itself.

Hi,

 Thanks for the reply ... I have put all the information I got right there:  https://egpu.io/forums/mac-setup/script-fr34ks-macos-egpu-sh-one-script-all-solutions-fully-automated/paged/9/#post-36439

 If there is any places else I should look, I would be please to provide.

 By the way, which of the two TB port do you use? I just tried both and it does result in the same (plug when logo appear). Detected as a thunderbolt device but not in displays.

 I saw a lot of people having an Aorus box with the same problem, but I will bring back the box for warranty on Monday to clear any doubt.

Thanks,

 

Edit : Fun fact, when I plug the box, the layout of the website change a bit

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

@olivier_declementi Thunderbolt bus never shows the card. It appears under the graphics/displays and PCI. If nothing there, you might have a faulty box. Either a hardware or firmware issue.

Your first forum post indicates the same: "Then one day it stopped working. I can't get Windows to detect it anymore".

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
(@olivier_declementi)
Active Member
Joined: 1 year ago
 
Posted by: goalque

@olivier_declementi Thunderbolt bus never shows the card. It appears under the graphics/displays and PCI. If nothing there, you might have a faulty box. Either a hardware or firmware issue.

Your first forum post indicates the same: "Then one day it stopped working. I can't get Windows to detect it anymore".

Hi,

 Thanks a lot for your time. I was just wondering maybe it was due to the multiple update (both MacOS and Windows). As some people have to deal with rEFInd, etc ... Mine was working straight without any modifications, maybe an update came to screw everything up.

I will bring the box back to the shop tomorrow, let's see what happen when I get it back.

Thanks again.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@glenn_aitken)
Active Member
Joined: 1 year ago
 

Greetings.  Here are the observations:

Install fr34k's macOS-eGPU.sh

- Works using boot / logout / hotplug / login method.  Boots up plugged in but after login screen iM goes black, I am not using eM so cannot comment.
- Nvidia GTX1080 Ti running on Akitio Node Pro Thunderbolt 3 Enclosure
- Macbook Pro 15" late 2017 model
- see Screenshots for further information.  Doesn't show the GTX in About This Mac, but is showing in System report and all software (Resolve, AE, PP) show the card as available.

---
everything working perfectly on 2017 MBP 15", 10.13.4,  with NVidia 1080 Ti 🙂  Thanks guys amazing work!

EDIT: As a Build Guide:  https://egpu.io/forums/builds/2017-15-mbp-rp560-gtx1080ti32gbps-tb3-akitio-node-pro-macos10-13-4-glenn-aitken/#post-36501

 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


fr34k and goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: Glenn Aitken

everything working perfectly on 2017 MBP 15", 10.13.4,  with NVidia 1080 Ti 🙂  Thanks guys amazing work!

Great! One way people can contribute is to post also success stories, and answer the following question:

Do you get eGPU screen output out of the box if the computer is started from a powerless state or do you need to logout -> hot plug the display and login?

Please mention your Mac model, eGPU card & enclosure, monitor model, used display cables and adapters.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


fr34k liked
ReplyQuote
(@kyle_chung)
New Member
Joined: 1 year ago
 

Just to share my results on MacBook Pro 15" 2016:

macOS: 10.13.4 (17E199)
Nvidia 1070 + Akitio Node
Using eM (Samsung CF791)
Boot up with eGPU connected works.
Hotplugin then logout-login also works.

However, the UI performance on eM is bad. Everything can be a bit sluggish, especially when switching different apps/tabs.
Right now I can accept it since my primary use case is CUDA for deep learning, half of the time I only remote ssh to my mac so UI slowness is not an issue.

But in the long run I still expect this can be solved when better support is coming from either macOS or the web driver.

Btw I also dual-boot Windows in a external SSD (WTG, not bootcamp), and it works perfectly in Windows (But only after the DSDT override with a test mode enabled.)

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Daisaku
(@daisaku)
Eminent Member
Joined: 2 years ago
 

I used to use the old script but I have no idea how to uninstall it. I tried following what it said in the github for people who used to use the old scripts but I got error messages. Please help, thank you. 

Screen Shot 2018 05 13 at 10.39.16

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
ickys11
(@ickys11)
New Member
Joined: 1 year ago
 

@fr34k Thank you!  The script worked for me however a few things I'm noticing.
- I've lost brightness control on my keyboard F1/F2 keys as well as the brightness slider in system prefs
- System won't go to sleep when screen closed...and won't go to clamshell mode.
- Disconnect seems to work from the menu icon but I cannot unplug the thunderbolt cable without a kernel panic.

So with this config will I just have to fully shutdown after using the egpu everytime or is there a workaround anyone knows about.

Thanks again!

My system is a Mid-2012 MBP Retina, TB2, Akitio Node with GTX1060

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


fr34k liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@ickys11
nope not yet, research ongoing

et al
I'm still very busy and cannot do much right now. (I guess it was obvious that I didn't answer to any questions)
In the upcoming week(s) a few improvements will be on their way such as
- the "old wrangler" problem, there will be improvements to that (better instructions or if read permissions weren't set the will be etc.)
- multi eGPU setup
- NVIDIA dGPU
- tons of fixes (logic and bugs, especially CUDA)
- custom uninstaller for all parts (if corrupt installations are present)
- better disabling of auto update
- better termination of programs (iTerm support + kill of all other instances + only kill if something will be done -> move after deduction)

This will still take some time and it won't be one update, it will be gradual as I see something is finished. I'll give notifications in this thread of course.
Every time I have an idea I open new branches so one can see the changes. The master branch should always work, but please don't use the other ones/use them only if I PM you to test specific functions, they're highly experimental and often not finished. Therefore the script might exit, leaving your system in an unrecognised state.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ikir and Charly4 liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

Good news. I found a new EFI approach that does not require @fr34k's or @mac_editor's binary patches. No need to backup kexts because none of the system files are modified. The SIP can be fully enabled.

Both AMD and Nvidia cards work out of the box. I just tested this on Mid 2015 15" MBP (M370X)

Bad news:

1) the eGPU is not hot pluggable, neither AMD nor Nvidia
2) macOS wants to utilize AMD dGPU so the internal screen is sluggish

I could try to control the gmux switch in EFI so that the iGPU becomes always active

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
Markus Koepke
(@ghostronaut)
Eminent Member
Joined: 2 years ago
 

I can confirm the new script working on a Macbook Pro 15" Touch Bar 2017 (3,1 Ghz, 16GB Ram) with 10.13.4 and a Aorus Gaming Box 1080.

Macbook Pro Touchbar 2017 i7 3.1Ghz Kaby Lake 16GB Ram | Aorus Gaming Box 1080 | HTC Vive | Build guide


ReplyQuote
Charly4
(@charly4)
Eminent Member
Joined: 2 years ago
 
Posted by: goalque

Good news. I found a new EFI approach that does not require @fr34k's or @mac_editor's binary patches. No need to backup kexts because none of the system files are modified. The SIP can be fully enabled.

Both AMD and Nvidia cards work out of the box. I just tested this on Mid 2015 15" MBP (M370X)

Bad news:

1) the eGPU is not hot pluggable, neither AMD nor Nvidia
2) macOS wants to utilize AMD dGPU so the internal screen is sluggish

I could try to control the gmux switch in EFI so that the iGPU becomes always active

Great!!
Do you think that it would be usable in 2012 MBPR or just  in UEFI 2.0 compatible devices?

Macbook PRO Retina 2012 15" (Intel HD 4000 + Nvidia Geforce GT 650M)
Akitio Thunder 2 + Nvidia 970 GTX


ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 2 years ago
 

@goalque
Would It be easily "Undoable"?

You think It will behave better with NVidia Drivers than the EGPU Enabler (keep in mind that newer driver works flawlessly with Internal screen if I remove EGPU Enabler)?

Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970


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

@Charly4 I don't know yet. Starting from Late 2013 should work.

@LeoLeal it does not change anything in macOS so there is nothing to "undo/uninstall" if the EFI is executed from the USB stick.

Still examining if yifanlu's kext is required or can we do that part in EFI as well.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


Charly4 liked
ReplyQuote
kingbri
(@kingbri)
Eminent Member
Joined: 1 year ago
 

is it possible to run it on mid 2012? Why only late 2013?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
kingbri
(@kingbri)
Eminent Member
Joined: 1 year ago
 

I was successfuly able to install this script :). However, there is severe fps issues and lag. My bench could not be done because I was cringing at the 7fps. I was able to install on windows and works flawlessly, not sure why there is fps drop on my mac. Any fixes?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

is it possible to run it on mid 2012? Why only late 2013?

I don't know yet. Mac firmwares are separated into preUEFI and UEFI categories.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
kingbri
(@kingbri)
Eminent Member
Joined: 1 year ago
 

mid 2012 does use UEFI. It cannot run windows in UEFI, but in a hybrid MBR to emulate legacy

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

Apple's EFI implementation is not fully UEFI 2.0 compatible. Starting from 2013 it came much closer. Depends on implemented EFI protocols in the firmware.

If this turns out to be workable on most systems, it does not feel good if @mac_editor's and @fr34k's hard work went wasted :/

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
Robert Avram
(@robert_avram)
Active Member
Joined: 2 years ago
 

Weird bug

I am running eGPU with NVIDIA 1080GTX + TB3 + MacbookPro 2017 15 inch with AMD dGPU + Headless HDMI + LG UltraFine 5k

When running World of warcraft using the METAL API, no vsync, 60 HZ refrehs rate, I get the same FPS as in 10.13.3, however the whole game feels choppy.

Now if I change volume or brightness and it renders the MacOS UI showing the respective brightness increase the game runs smooth in the background. However, when it goes back to the game it is choppy again.

Please look at this video:
https://www.dropbox.com/s/s3wf08wpjl6cpwk/IMG_5120.MOV?dl=0

Benchmark in Heaven is smooth.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
kingbri
(@kingbri)
Eminent Member
Joined: 1 year ago
 
Posted by: Robert Avram

Weird bug

I am running eGPU with NVIDIA 1080GTX + TB3 + MacbookPro 2017 15 inch with AMD dGPU + Headless HDMI + LG UltraFine 5k

When running World of warcraft using the METAL API, no vsync, 60 HZ refrehs rate, I get the same FPS as in 10.13.3, however the whole game feels choppy.

Now if I change volume or brightness and it renders the MacOS UI showing the respective brightness increase the game runs smooth in the background. However, when it goes back to the game it is choppy again.

Please look at this video:
https://www.dropbox.com/s/s3wf08wpjl6cpwk/IMG_5120.MOV?dl=0

Benchmark in Heaven is smooth.

This is what I was talking about earlier. Apparently, I did some research and running windows would make the gpu perform significantly faster in games. Nvidia is optimized for directX, not metal. Metal is AMD's park

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Sovereign
(@sovereign)
Active Member
Joined: 2 years ago
 
Posted by: goalque

Apple's EFI implementation is not fully UEFI 2.0 compatible. Starting from 2013 it came much closer. Depends on implemented EFI protocols in the firmware.

If this turns out to be workable on most systems, it does not feel good if @mac_editor's and @fr34k's hard work went wasted :/

Just curious, but how does this EFI hack work in general?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
n9yty
(@n9yty)
Eminent Member
Joined: 2 years ago
 

@goalque I am glad it works for you, but those are the exact steps I had taken and it does not work here.

Upgraded to 17E202 (security update), ran the script (downloaded the driver version .107), restarted and boom.

I either end up with a black screen on the eGPU monitor with mouse pointer, or black screen on internal display with corruption and mouse pointer. It doesn't matter when I plug in, boot with it pluguged in, plug in and log out or whatever, the result is the same, one screen is black and unusable. Very frustrating considering it should be the same system. Clearly something else is fighting me here, but I don't know what it is. 🙁

I even used the uninstall and retried, no change. The only thing about that is, I have to have SIP disabled to run the script, and it installs the NVidia drivers, but I thought I had read many times that you must have SIP enabled for them to install properly. Maybe I am missing something there, and maybe it isn't even related.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Robert Avram
(@robert_avram)
Active Member
Joined: 2 years ago
 

@kingbri
I understand that. However, the same game running o the same system/settings in WINDOWED mode is much faster than full screen mode.

Additionally the FPS count as shown in game is the same, but the game feels smoother.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

@n9yty As if your MBP is stuck at using dGPU. I have no explanation for it unfortunately. Try changing "displays have separate spaces" and set the eGPU monitor as the primary if you can.

I observed that you have used Rastafabi's eGPU enabler earlier. This contains lots of 3rd party hacks. To be sure that you have a clear system, I would do disk erase & reinstall from the internet recovery, reset nvram, then start from the beginning (disable SIP). If still the same result, the reason must be your Aorus gaming box or the monitor. Does it work well without the eGPU monitor?

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


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

Just curious, but how does this EFI hack work in general?

Will let you know as soon as I have tested it on my other Macs. It is based on Clover bootloader but if does not work reliably, I may reconsider the old automate-eGPU.efi.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
n9yty
(@n9yty)
Eminent Member
Joined: 2 years ago
 

@goalque thanks for the suggestions. I instead created a fresh install on an external drive. I could not hot plug, still have a black screen, but didn't try the login/logout/etc, as I was more interested in seeing if I could boot with it. I was able to, and both displays did come up. It was very slow and laggy and first, but I ran both the Heaven (2155/85.6fps) and Valley (3066/73.3) benchmarks (highest setting, 8xAA), and the system performance seemed to improve. [Update, still a bit laggy as I use it]

I thought I thoroughly removed all the rastafabi stuff, I had run his uninstall and even thought I had manually verified it all, but I will check things again. It does perform a little different on this clean install. I really don't want to do that to my main install, but, well, it may be time to go through that pain.

I also thought that it might be some other kext, knowing the changes in 10.4... I know in the distant past I had used a DisplayLink device, but it is not attached and I am pretty sure I purged the drivers. I also have AirParrot2 installed, maybe it is messing with something. I will try to narrow it down to what might be conflicting.

By the way, when I did set my eGPU monitor as main, and was able to get it to boot up (internal screen not working), I did see that the internal display was listed under the Intel graphics, not the AMD, so I don't think it was (entirely) stuck at using the dGPU. But I am not yet up to speed on all the moving pieces.

Thanks for all your hard work and trying to help, I hope your EFI method proves successful, looking forward to trying that. 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
n9yty
(@n9yty)
Eminent Member
Joined: 2 years ago
 

UPDATE:  It is working!   Thanks @goalque

While booted from the external drive, I moved the AirParrot kext out of the way. I don't know if that was the whole source of the problem, but I rebooted with the eGPU connected and it is working fine on my main install. Yay!

However, when running some things they force the dGPU to kick in and the internal screen goes blank, and sometimes the system becomes like a snail. So a way to disable the dGPU would help a lot in my case I think. But still, this is real progress!

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


goalque liked
ReplyQuote
 of  21