Setup & Software Discussions
[SCRIPT] automate-eGPU.sh v1.0.1 - macOS eGPU installation tool
 

[SCRIPT] automate-eGPU.sh v1.0.1 - macOS eGPU installation tool  

 of  9
  RSS

Menneisyys
(@menneisyys)
Eminent Member
Joined: 3 years ago
 

Thanks for the tip! Instead of apple_set_os, I decided to use the latest rEFInd versions’ spoof_osx_version feature (with the default 10.9 value) to avoid having to install external GRUB to directly execute apple_set_os in a bootchain, before passing the execution to Bootcamp’s boot loader.  

 

With spoofing in place, the iGPU indeed starts to be seen by both DIY eGPU Setup 1.35-test4c (officially acquired version; without spoofing, it lists the iGPU as „off” and not „on”) and Windows. 

 

Windows required disabling the HD4000 in Safe Mode NOT to get a black screen upon loading. (This is after - also in Safe mode so that it doesn’t end up displaying the „This computer does not meet the minimum requirements for installing the software” error message - installing the latest HD4000 driver, win64_153343.4425. That is, the driver should be OK.) Note that disabling the dGPU in the Device Manager of Windows, that is, trying to force the system to use the now-accessible (spoofing) and driver-helped (see prev. forced install) iGPU doesn’t work. The screen doesn’t become black any more, but it just freezes the last sandclock animation frame. (Tested with both internal-only and connected mDP screen.)

 

(Note that not any kind of i/dGPU disabling work in DIY eGPU Setup 1.35 on this 3rd-gen i-Core CPU (WRT iGPU) / not even after packing (dGPU; it constantly freezes in DIY eGPU Setup when trying to disable. Also note that „gpu-switch” didn’t work at all in either normal or Safe Mode. In the latter, I tried it with the HD4000 - in Device Manager - enabled too, not only with being disabled. I kept getting the „Error code was: 1, Error message was: Incorrect function.” error messages for both batch files; both run as admin. Finally, also note that the Resources tab of the HD4000 shows „the device isn’t using any resources because it has a problem”.)

 

Unfortunately, the eGPU (in the Node) is still nowhere to be seen by either Windows or DIY eGPU Setup 1.35 after a normal reboot (meaning NOT executing automate-eGPU.sh before the reboot) from MacOS. Only the enclosure itself (when I remove the graphic card from it) is visible in both Device Manager (as „System Devices > Thunderbolt”) and in the external storage eject menu if and only if

  • we’ve booted in with it (no hot plug-in)
  • we haven’t booted right from MacOS (in this case too, the card-less enclosure will also be invisible).

In this case, the Node firmware updater can’t detect the enclosure - just like with the non-spoofed case. 

 

Executing automate-eGPU.sh right before booting into (spoofed and in-Device-Manager-disabled-HD4000) Windows:

 

 

  • the -a parameter results in no changes
  • without any parameter, the loading process freezes on the rEFInd screen (unlike with the -a / no-automate-eGPU.sh-execution cases, and like the cases of trying to reboot from Windows or directly powering up the system, without initiating the reboot from MacOS).

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
 

If the -a mode is switched on, it is the same as booting without the eGPU in your case.  Your TB controller doesn’t see the card or enclosure in the pre-boot firmware environment.

This thread is dedicated to the automate-eGPU.sh script. For further discussion about Windows and apple_set_os.efi, please step into this thread:

https://egpu.io/forums/mac-setup/how-to-keep-mbps-irisiris-pro-activated-when-booting-into-windows-boot-camp/

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


ReplyQuote
Menneisyys
(@menneisyys)
Eminent Member
Joined: 3 years ago
 

Thanks for the answer!

Do I get this right? I should only see the eGPU in Bootcamp when

- rebooting from MacOS where

- I've also run the automate-eGPU.sh script right before the reboot (in the same MacOS session)?

That is, Windows hasn't detected my eGPU at all because, while I did reboot from MacOS, I haven't executed automate-eGPU.sh in the same MacOS session?

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
 

The -a mode is valid on the next reboot. It stays persistent between macOS restarts because of the daemon process. Once Windows has loaded, and you restart, you have to go through macOS. 

AFAIK, the -a mode in your case is not helpful. Correct me if the eGPU appears in Windows.

As for Windows, your best approach is to use methods in the linked thread, not this script at all.

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


ReplyQuote
Anchoricex
(@anchoricex)
Trusted Member
Joined: 3 years ago
 

I am so glad this script exists. I'll be giving it a go next week when my Titan X shows up to pair with my Akitio Node on my 2016 Macbook 15" touchbar. 

Just curious, will I have any issues using the TB3 ports to the right of my keyboard? All the videos I've seen shows enclosures plugged into the left side, but mine will be sitting in a vertical dock and the left ports will be given to other peripherals.

Also does the script need to be executed every time I want to use the eGPU? 

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


ReplyQuote
Rapunzel
(@rapunzel)
Eminent Member
Joined: 3 years ago
 
Posted by: FricoRico

 

Please bear with me as I will release a beta compatible version soon.

   

Any update? I installed the newest beta and I am ready to test. 😉

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


ReplyQuote
DANgerous25
(@danfalconar)
Estimable Member
Joined: 3 years ago
 
Posted by: Anchoricex

 

I am so glad this script exists. I'll be giving it a go next week when my Titan X shows up to pair with my Akitio Node on my 2016 Macbook 15" touchbar. 

Just curious, will I have any issues using the TB3 ports to the right of my keyboard? All the videos I've seen shows enclosures plugged into the left side, but mine will be sitting in a vertical dock and the left ports will be given to other peripherals.

Also does the script need to be executed every time I want to use the eGPU? 

   

I have a late 2016 13" MBP+TB. All four of the TB3 ports work in MacOS, and despite there being claims that the left/right ports don't dish out the same bandwidth I didn't notice any real difference in performance when I did a simple comparison using Unigine Heaven. The bad news in my case, was that in Windows I could ONLY get the right ports to work. Using the left ports caused BSOD.

Oh, and no. You don't need to run the script multiple times. You only need to run it once and you're good.

late-2017 27" iMac Pro RPVega64 + [email protected] (AKiTiO Node) + MacOS 10.13.2
late-2014 27" iMac 5k R9 M295X + [email protected] (AKiTiO Node via TB3->TB2 adapter) + macOS10.13 & Win10


ikir liked
ReplyQuote
Rapunzel
(@rapunzel)
Eminent Member
Joined: 3 years ago
 

I got it working by replacing  9500  with 9510 in the script. But it lacks metal, that means no acceleration. So better wait for the  professional coder to update the script. 😉

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


ReplyQuote
Rapunzel
(@rapunzel)
Eminent Member
Joined: 3 years ago
 

I tried the non beta version and the card was not accelerated as well. So this might be a problem with the MSI RX 460? Does anybody know?

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


ReplyQuote
Rapunzel
(@rapunzel)
Eminent Member
Joined: 3 years ago
 

After running macOS some time and checking the system information again, metal support does appear. But the GUI is not accelerated.

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


ReplyQuote
Misha
(@misha)
New Member
Joined: 3 years ago
 

Hello! This sскшзе solved the problem of starting the system with my 750m. And for this many thanks to the developers! The work in the professional applications (premiere and resolve) looks convincing. When I start the Unigine Heaven, after a few seconds the system crash. What is the reason for this?

Macbook mgxc2 (2014 with 750m), akitio thunder2, GTX 970 by NVidia, Corsair VS550 PSU, External monitor Benq 3201 4k


ReplyQuote
ikir
 ikir
(@ikir)
Prominent Member
Joined: 3 years ago
 

10.2.4 is live!!! Reports? Are Radeon working? Are they any better?

Nvidia maybe will update drivers tomorrow.


MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD
my awesome Radeon VII eGPU
my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64


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

I haven’t heard from FricoRico. He has been busy. Feel free to take up the challenge. We can’t be the only programmers in this world 🙂

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


itsage liked
ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

If you’re using RX 470 or RX 480 for your eGPU, don’t update to 10.12.4 just yet. AMD9500Controller.kext was removed in this build and replaced by AMD9510Controller.kext.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ikir liked
ReplyQuote
ikir
 ikir
(@ikir)
Prominent Member
Joined: 3 years ago
 
Posted by: itsage

 

If you're using RX 470 or RX 480 for your eGPU, don't update to 10.12.4 just yet. AMD9500Controller.kext was removed in this build and replaced by AMD9510Controller.kext.

   

Any performance changes?


MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD
my awesome Radeon VII eGPU
my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64


ReplyQuote
ed_co
(@ed_co)
Reputable Member
Joined: 3 years ago
 
Posted by: itsage

 

If you're using RX 470 or RX 480 for your eGPU, don't update to 10.12.4 just yet. AMD9500Controller.kext was removed in this build and replaced by AMD9510Controller.kext.

Meaning? Not support at all? Bad peformance? Differences? Cheers.

mid-2017 Macbook Pro RP560 + MSI GTX 1080Ti Gaming [email protected] (Mantiz Venus) + macOS10.13 & Win10


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

For those who can't wait:

sudo ./automate-eGPU.sh -url  https://images.nvidia.com/mac/pkg/367/WebDriver-367.15.10.45f01.pkg 

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


itsage liked
ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

The script identifies RX 470/480 cards by AMD9500controller.kext. This kext file no longer exists in 10.12.4. Running automate-eGPU.sh 1.0.0 on macOS 10.12.4 may not get an RX 470/480 eGPU working.

@Goalque, would manually adding 067DF1002 to the plist in AMD9510controller.kext be a temporary workaround?

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ReplyQuote
Daelin
(@daelin)
Trusted Member
Joined: 3 years ago
 
Posted by: itsage

 

@Goalque, would manually adding 067DF1002 to the plist in AMD9510controller.kext be a temporary workaround?

   

yes it is (but needs a bit more than just adding it)

https://egpu.io/forums/mac-setup/rx-480-working-with-10-12-4/

🙂 🙂

MacBook Pro 15" 2017, AMD RP560
Devil Box + MSI GTX 1080Ti Gaming X

Bricked thanks to rEFInd:
MacBook Pro 15" Late 2013, GT 750M


goalque liked
ReplyQuote
Rapunzel
(@rapunzel)
Eminent Member
Joined: 3 years ago
 

I replaced 9500 woth 9510 and could use the script with an rx 460. if you also add the id to the plist it should probably work

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: itsage

 

The script identifies RX 470/480 cards by AMD9500controller.kext. This kext file no longer exists in 10.12.4. Running automate-eGPU.sh 1.0.0 on macOS 10.12.4 may not get an RX 470/480 eGPU working.

@Goalque, would manually adding 067DF1002 to the plist in AMD9510controller.kext be a temporary workaround?

   

At the moment, the script is not compatible with macOS 10.12.4 + RX 470/480. 

Manual method is of course possible, AMD9510Controller.kext & AMDRadeonX4100.kext are correct for the RX 470/480. Just add the device id and IOPCITunnelCompatible key.

No problem with TB2-TB2. AMD eGPU + Node + TB3-to-TB2-adapter + TB2 Mac should also work on macOS 10.12.4 if kext mods are done correctly and caches are rebuilt. 

2016 13" MBP (non-touch) gives the eGPU screen output, but no whoosh, no acceleration with AMDs. The USB-C trick that was necessary to have acceleration on macOS 10.12.2/10.12.3 + AMDs, doesn’t work after macOS 10.12.4 upgrade.

 

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


ReplyQuote
Rapunzel
(@rapunzel)
Eminent Member
Joined: 3 years ago
 
Posted by: goalque
Posted by: itsage

The script identifies RX 470/480 cards by AMD9500controller.kext. This kext file no longer exists in 10.12.4. Running automate-eGPU.sh 1.0.0 on macOS 10.12.4 may not get an RX 470/480 eGPU working.

@Goalque, would manually adding 067DF1002 to the plist in AMD9510controller.kext be a temporary workaround

TB3 MBPs give the eGPU screen output, but no whoosh, no acceleration with AMDs. The USB-C trick that was necessary to have acceleration on macOS 10.12.2/10.12.3 + AMDs, doesn’t work after macOS 10.12.4 upgrade.

Same on 10.12.5 Beta 1. 🙁 Any idea how to get acceleration? After some time of running Metal support is shown but no acceleration takes place.

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
 

If you can do firmware downgrade, that might be the only possible way. Apple has blocked this workaround.

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


ReplyQuote
Rapunzel
(@rapunzel)
Eminent Member
Joined: 3 years ago
 
Posted by: goalque

 

If you can do firmware downgrade, that might be the only possible way. Apple has blocked this workaround.   

Do you mean the Macbook Pro firmware?!

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

ReplyQuote
Daniel Reed
(@dread64)
New Member
Joined: 3 years ago
 
Posted by: goalque

    

At the moment, the script is not compatible with macOS 10.12.4 + RX 470/480. 

 

...

TB3 MBPs give the eGPU screen output, but no whoosh, no acceleration with AMDs. The USB-C trick that was necessary to have acceleration on macOS 10.12.2/10.12.3 + AMDs, doesn’t work after macOS 10.12.4 upgrade.

 

   

What is this "whoosh"?  youtube vid of it would be super helpful, anyone? 

I've read the "whoosh" mentioned but have never heard it for TB1/2 attached eGPU setups for MBP and nMP.

Then again, I never connect them to monitors and just use them for CUDA/nVidia or more OpenCL/AMD

Using a HDMI ghost plug didn't result in any "whooshes" for me and I do appear to have metal support and acceleration in Resolve/Redcine/benchmarks

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


ReplyQuote
Gargulec
(@gargulec)
New Member
Joined: 3 years ago
 

Akitio Node 3 +980TI nvidia doesn’t work after macOS 10.12.4 upgrade.
Is there any solution?

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


ReplyQuote
ikir
 ikir
(@ikir)
Prominent Member
Joined: 3 years ago
 
Posted by: Gargulec

 

Akitio Node 3 +980TI nvidia doesn’t work after macOS 10.12.4 upgrade.
Is there any solution?

   

Have you reinstalled script with new Nvidia drivers?


MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD
my awesome Radeon VII eGPU
my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64


ReplyQuote
Gargulec
(@gargulec)
New Member
Joined: 3 years ago
 

I had to manually delete the eGPU.kext from library and reinstalled script.

Now all work ok.

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


ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 
Posted by: Daniel Reed
Posted by: goalque

At the moment, the script is not compatible with macOS 10.12.4 + RX 470/480. 

TB3 MBPs give the eGPU screen output, but no whoosh, no acceleration with AMDs. The USB-C trick that was necessary to have acceleration on macOS 10.12.2/10.12.3 + AMDs, doesn’t work after macOS 10.12.4 upgrade.

What is this “whoosh”?  youtube vid of it would be super helpful, anyone? 

I’ve read the “whoosh” mentioned but have never heard it for TB1/2 attached eGPU setups for MBP and nMP.

Then again, I never connect them to monitors and just use them for CUDA/nVidia or more OpenCL/AMD

Using a HDMI ghost plug didn’t result in any “whooshes” for me and I do appear to have metal support and acceleration in Resolve/Redcine/benchmarks

At about :21 sec in this video you can see the fans spun down as the screen with Apple booting logo came on. The “whoosh” sound often described in eGPU implementation with AMD cards is this very instance of the booting process. macOS recognizes and loads the proper drivers for the AMD GPU; the GPU’s fan would spin up to max speed for a split second then settle to its normal operating speed.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ReplyQuote
Anchoricex
(@anchoricex)
Trusted Member
Joined: 3 years ago
 

Anyone have any luck/leads on downgrading the firmware? 

Goalque: Is this the method you tried? 3 year old question I don't know if this is still possible. http://apple.stackexchange.com/questions/103720/how-to-downgrade-efi-firmware-back-to-version-1-6

Edit: This would be a little more recent, back from Yosemite days, but appears to be the same (ish?) process:  https://forums.macrumors.com/threads/guide-how-to-get-back-old-efi-after-downgrade-from-yosemite.1803934/

From what I gather it is [obviously] absolutely crucial you get the absolute correct firmware for your laptop. 

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


ReplyQuote
Rapunzel
(@rapunzel)
Eminent Member
Joined: 3 years ago
 

Stupid question: If i use a conversion to Thunderbolt 2, will it then work?

Macbook Pro 2016 - TB3toTB2 - TB2toTB3 - Akitio Thunder3

 

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: Anchoricex

 

Anyone have any luck/leads on downgrading the firmware? 

Goalque: Is this the method you tried? 3 year old question I don't know if this is still possible. http://apple.stackexchange.com/questions/103720/how-to-downgrade-efi-firmware-back-to-version-1-6

Edit: This would be a little more recent, back from Yosemite days, but appears to be the same (ish?) process:  https://forums.macrumors.com/threads/guide-how-to-get-back-old-efi-after-downgrade-from-yosemite.1803934/

From what I gather it is [obviously] absolutely crucial you get the absolute correct firmware for your laptop.

Yep those and one that no one has yet tried:

goalque$ sudo /usr/libexec/efiupdater -p expanded.pkg/FirmwareUpdate.pkg/Scripts/Tools/EFIPayloads/ --force-update
EFI currentVersion: [0000000000000000]
EFI updateVersion:  [0000000002050007]
EFI found at IODeviceTree:/efi
Will need to copy 8388608 bytes to EFI system partition
Aggregate boot path is IODeviceTree:/[email protected]/[email protected]/[email protected]/AppleS3XController/[email protected]/@1:2
GPT detected
Booter partition required at index 3
System partition found
Booter partition found
Preferred system partition found: disk0s1
…
Background color default set successfully

However, after restart it was the same firmware. Very possible that efiupdater requires MultiUpdater.efi inside the package. Apple’s firmware update mechanism is not documented anywhere. Internally it is running a "bless" and sets NVRAM variables pointing to the firmware binary.

This is definitely a TB3 firmware or MBP firmware issue. The 13" touchbar model seems to work better:

https://egpu.io/forums/mac-setup/performance-issue-with-amd-r9-fury-x-on-13-mbp16aktio-node

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


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 

My Mac mini 2012 (Sierra 10.12.3 and RX 470) worked quite well for a while with the automate script setup.
I DID NOT UPGRATED TO 10.12.4!

After a reboot the Mac mini does not recognized the RX 470 (only the internal Intel 4000).
I ran thru the automate script setup again it worked (until the next reboot -> Power OFF/ON?)

Any suggestions?

Thank you...
Barni

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


ReplyQuote
DANgerous25
(@danfalconar)
Estimable Member
Joined: 3 years ago
 

Hello all, I'm sorry if this question has been answered elsewhere but I can't find it. Is the automate-eGPU script officially compatible with MacOS 10.12.4 (specifically with the 980 TI), and if so what is the procedure for getting it to work. I can see from recent posts that some people are using it but there seem to be extra procedures / exception cases in its use.

Alternatively if there's a way for me to determine this info myself then let me know, I haven't found an obvious way of doing so.

late-2017 27" iMac Pro RPVega64 + [email protected] (AKiTiO Node) + MacOS 10.13.2
late-2014 27" iMac 5k R9 M295X + [email protected] (AKiTiO Node via TB3->TB2 adapter) + macOS10.13 & Win10


ReplyQuote
ikir
 ikir
(@ikir)
Prominent Member
Joined: 3 years ago
 
Posted by: DANgerous25

 

Hello all, I'm sorry if this question has been answered elsewhere but I can't find it. Is the automate-eGPU script officially compatible with MacOS 10.12.4 (specifically with the 980 TI), and if so what is the procedure for getting it to work. I can see from recent posts that some people are using it but there seem to be extra procedures / exception cases in its use.

Alternatively if there's a way for me to determine this info myself then let me know, I haven't found an obvious way of doing so.

   

As far I know it is compatible, because Nvidia released drivers 1-2 days after macOS update. Just run the script.


MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD
my awesome Radeon VII eGPU
my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64


ReplyQuote
 of  9