Setup & Software Discussions
2013 13" MacBook Pro [4th,2C,U] + RX 480 @ 16Gbps-TB2>TB3 (AKiTiO Node) + macOS ...
 

2013 13" MacBook Pro [4th,2C,U] + RX 480 @ 16Gbps-TB2>TB3 (AKiTiO Node) + macOS 10.13 [jonwatso]  

  RSS

jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 

 

First of all, A massive thank you to the community here on eGPU.io you guys have been a world of help getting this all up and running.


Implementation on macOS 

Setup was super easy and straight forward, I followed a tutorial that my friend Lance made on youtube 

UPDATED 30/04/2017 - You can run the automate eGPU script without any mods to the script as RX480 support has been added for 10.12.4, I would still recommend following the youtube tutorial to enable all the compute units. The script that goalque made for enabling all the compute units made a massive difference in performance. Running separate tests before and after can be found here (Before and After enabling all the compute units)

I have the node plugged into a dell 4K display and everything seems to be working great. No issues with putting the mac to sleep when the eGPU is enabled. I did initially have some lag with UI elements when I first plugged in the display, However this was caused by the internal display still being rendered (Know issue). Seeing how I want to use the mac in "clamshell mode" I utilised the disablemonitor application to disable the internal monitor which got rid of the lag. I'd recommend closing the lid of the mac after you've disable the screen otherwise you may find some lag on startup with the lid closed. 

 

Final Cut Pro - running with eGPU (RX480)

You can get final cut to work by moving the driver files for your integrated gpu out of the extensions folder. However this will remove the ability to get hardware acceleration from the integrated graphics. So this means when I reboot my MacBook Pro without the eGPU I get NO hardware acceleration. I've made an AppleScript application to enable and disable the iGPU (See below) which is working well for me and makes turning off the iGPU Painless. 

 

 

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


Zetthard, itsage and ikir liked
ReplyQuote
may
 may
(@may)
Eminent Member
Joined: 3 years ago
 

Hello. can you run brucex fcp benchmark with success? What is your result? https://blog.alex4d.com/2013/10/30/brucex-a-new-fcpx-benchmark/

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


ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 

I ran the benchmark a total of 7 times and there were no issues at all. I am only including the last 3 results as I messed up the first 4 (wrong format / had other apps open). 

  1. 32 Seconds
  2. 33 Seconds
  3. 35 Seconds 

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


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

@jonwatso similar results for me on FCP on an RX 480 4GB

Interesting to see that kext file mods for iGPU-only macs are a necessity to get FCP working. Not the case with all macs w/ dGPU.

Benchmark: https://egpu.io/forums/builds/mid-2014-macbook-pro-w-750m-rx-480-akitio-node-on-macos-win-10/

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 (Mantiz Venus MZ-02)


ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 
Posted by: mac_editor

 

@jonwatso similar results for me on FCP on an RX 480 4GB

Interesting to see that kext file mods for iGPU-only macs are a necessity to get FCP working. Not the case with all macs w/ dGPU.

Benchmark: https://egpu.io/forums/builds/mid-2014-macbook-pro-w-750m-rx-480-akitio-node-on-macos-win-10/

   

Great write up! Yeah I am pretty disappointed that deleting the Kext files is the only way to get final cut to work as everything else works great. It was the same story in Lightroom. I would've preferred if the iGPU and eGPU worked together. Oh well it's a good work around in the mean time albeit a bit messy. 

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 

Script App for Enabling / Disabling the Intel integrated graphics


I've made a fairly basic script that enables and disables the internal iGPU. It does this by first backing up the igpu driver files and then deleting them from the extensions folder, and then copies them back when enabling them. I've written it so that it always makes a backup before making any changes. I've tested it on a couple of macs and seems to work great and makes enabling / Disabling the iGPU super easy. You can open the app in apple script so that you can modify it and make it work with your Mac's iGPU. It's currently set up for the Intel HD5000 igpu so you will need to modify the script if you want it to work with other macs, just use the find and replace function in Script editor i.e replace "HD5000" with "HD3000". I've tried and tested it on my 13" MacBook Pro late 2013 without any issues.  SIP Needs to be turned off for this script to work. 

Disclaimer: The script is setup to always back up first before making any changes, However you are using this script at your own risk and I am not responsible for anything that may go wrong. 

I hope you find this little tool helpful. 

 How to modify the script


Open Script editor >Open “iGPU Tool” > Find > Replace “AppleIntelHD5000” with “The Name of your driver”

Chances are your Mac will utilise one of the Driver bundles below as of 10.12.4. 

  •  AppleIntelHD (Intel HD Graphics)
  • AppleIntelHD3000 (Intel HD3000 Graphics)
  • AppleIntelHD4000 (Intel HD4000 Graphics )
  • AppleIntelHD5000 (Intel Iris / Intel Iris Pro )
  • AppleIntelSKL (Intel Skylake i.e Intel HD 530)
  • AppleIntelBDW (Intel Broadwell Graphics aka HD6000)

 

So for example if you are doing this on a new 2016 MacBook Pro I would write; Replace “AppleIntelHD5000” with “AppleIntelSKL” and then go Save > Save as Application. 

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


ikir liked
ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 

Here are a bunch of benchmarks from my eGPU. The main goal for these tests was to find out how much of a performance gain I was getting over my integrated graphics rather than comparing them to other systems / cards. For the iGPU all the tests are done on the internal screen and with the eGPU all tests are done using my dell 4K Display. Due to that annoying bug on Mac OS I had to run the GPU benchmarks in 1280x800 to get the full screen mode (on the internal screen). Overall I am very happy with the GPU performance gain that I got from adding an eGPU to my setup.

 

FCP - BruceX 5K

eGPU - 33 Seconds

iGPU - 2:03 Minutes 

 

Unigene Valley (Open GL / 1280X800 Ultra / 8xAA )

eGPU - 2093

iGPU -  254

 

Unigene Heaven (Open GL / 1280X800 Ultra / Normal Tessellation / 8xAA )

eGPU - 1161 

iGPU -  187 

 

Lux Mark 

eGPU: 14133

iGPU: 1733 

 

Geekbench 4 compute benchmark

eGPU: 113851

iGPU: 2054

 

Something worth noting, the CPU runs 25 Degrees cooler when running with the eGPU 

 

Unigine benchmarks 

  

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


artik liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago

ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 
Posted by: mac_editor

25 degrees cooler? Holy s***.

Yeah it's a pretty decent change! I guess the iGPU being on the same chip as the CPU causes the massive difference in heat.

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 

If anyone is curious, As it currently stands the setup works flawlessly in High Sierra 10.13, However the deletion of the driver files is still requried to get final cut to work though I would say this will change after 10.13 is officially released. 

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 
Posted by: jonwatso

If anyone is curious, As it currently stands the setup works flawlessly in High Sierra 10.13, However the deletion of the driver files is still requried to get final cut to work though I would say this will change after 10.13 is officially released. 

This will most likely be resolved in a future update to FCP/macOS. The most interesting aspect of this is that, at least on dGPU macs, I hope that instead of load overflowing from discrete to external graphics, both chips are optimally used.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 (Mantiz Venus MZ-02)


jonwatso liked
ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 
Posted by: mac_editor
Posted by: jonwatso

If anyone is curious, As it currently stands the setup works flawlessly in High Sierra 10.13, However the deletion of the driver files is still requried to get final cut to work though I would say this will change after 10.13 is officially released. 

This will most likely be resolved in a future update to FCP/macOS. The most interesting aspect of this is that, at least on dGPU macs, I hope that instead of load overflowing from discrete to external graphics, both chips are optimally used.

I can't wait for Final Cut to work without deleting any system files. I hope you're right with the optimization of utilising both GPU's. Given what I've read / seen on developer.apple.com it looks like this may be how eGPU's are utilised. Time will tell. Exciting times. 

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 

Great info and post (just been pestering you on reddit), thanks for sharing... you should pop a pic of your final set up in this thread too @jonwatso

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


jonwatso liked
ReplyQuote
dream3
(@dream3)
Estimable Member
Joined: 3 years ago
 

Heyyo jonwatso!

 

I have a brand-new setup with a aorus 1080 and a 2015 macbook pro 15" iGPU only running MacOS 10.12.6. I followed both goalque's and rasta's guide but at the end the system would see the GPU but not use it for acceleration.

The first clue was that Photoshop wouldn't let me choose the 1080 under GPU selection. Other graphic applications would also ignore the eGPU. Games like League of Legends were the same. The only software that worked from the start was a game called Bioshock, which I had bought from the App Store. I genuinely wonder why.

First off I have to say it is pretty weird that I had to actually look for a solution for this. I'd imagine more people to have faced the same issues with an iGPU-only machine.

Well I've used your clever script for disabling the iGPU and BAM, worked. Now Photoshop sees the 1080. However, I was hit with a MAJOR UI lag in the external monitor. Again following your advice, disabled the internal screen at it is now flawless.

However, why wouldn't my 1080 be able to accelerate both displays? I would really like to use 2 screens. Are you aware of a workaround for that?

 

Sorry for the long post, first time I'm putting my hands on this eGPU thing and it's a complicated mess for my head 😛

 

MacOS: 15" Retina Macbook Pro 2015 Iris Pro only
Windows 10: Tornado F5 laptop with discrete GTX 1060
eGPU: GIGABYTE RX 580


ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 

sorry for the late reply! I believe its due to the limited bandwidth of the thunderbolt connection and because of this, it is unable to accelerate both screens. I would love to see this changed. I believe once eGPU support is officially implemented this year we should see better support in things for applications like photoshop etc. 

 

My recommendation for multiple displays, is to simply plug two displays into the eGPU as it is more than powerful enough to run multiple displays. 

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


ReplyQuote
Ramses Abascal
(@ramses-abascal)
Active Member
Joined: 1 year ago
 

First of all thanks for sharing this great script and the tool, I was so frustrated, the main reason of my eGPU was the need to speed up my render times in Final Cut Pro X and after installing my Akitio Node with Radeon HD 7970 and Final Cut crashing over and over I was desperate... but thanks to this amazing igpu tool it was easy to disable the HD4000 and only use the HD 7970 
Before BruceX 3:07 average
After Bruce X 45 secs in the last 3 test
also the Heaven Benchmark improved
[img] [/img] [img] [/img]

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


jonwatso liked
ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 

Glad it worked well for you 🙂

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


ReplyQuote
Ramses Abascal
(@ramses-abascal)
Active Member
Joined: 1 year ago
 

Hello, hope that someone could give an advice, Since yesterday when I started the Mac Mini and the Akitio Node, it works just for few minutes, as soon as I opened youtube it went to blank screen, I restarted and i happened the same.. I plug it to my macbook pro and same problem... ANY IDEA?

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
 

@ramses-abascal The issue might be with your HD 7970 rather than the AKiTiO Node.

Best ultrabooks for eGPU use

eGPU enclosure buying guide


ReplyQuote
Ramses Abascal
(@ramses-abascal)
Active Member
Joined: 1 year ago
 

Thanks, I will swap the graphics card , to be sure...

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


ReplyQuote
Rowley
(@rowley)
Active Member
Joined: 12 months ago
 
Posted by: jonwatso

Script App for Enabling / Disabling the Intel integrated graphics


I've made a fairly basic script that enables and disables the internal iGPU. It does this by first backing up the igpu driver files and then deleting them from the extensions folder, and then copies them back when enabling them. I've written it so that it always makes a backup before making any changes. I've tested it on a couple of macs and seems to work great and makes enabling / Disabling the iGPU super easy. You can open the app in apple script so that you can modify it and make it work with your Mac's iGPU. It's currently set up for the Intel HD5000 igpu so you will need to modify the script if you want it to work with other macs, just use the find and replace function in Script editor i.e replace "HD5000" with "HD3000". I've tried and tested it on my 13" MacBook Pro late 2013 without any issues.  SIP Needs to be turned off for this script to work. 

Disclaimer: The script is setup to always back up first before making any changes, However you are using this script at your own risk and I am not responsible for anything that may go wrong. 

I hope you find this little tool helpful. 

 How to modify the script


Open Script editor >Open “iGPU Tool” > Find > Replace “AppleIntelHD5000” with “The Name of your driver”

Chances are your Mac will utilise one of the Driver bundles below as of 10.12.4. 

  •  AppleIntelHD (Intel HD Graphics)
  • AppleIntelHD3000 (Intel HD3000 Graphics)
  • AppleIntelHD4000 (Intel HD4000 Graphics )
  • AppleIntelHD5000 (Intel Iris / Intel Iris Pro )
  • AppleIntelSKL (Intel Skylake i.e Intel HD 530)
  • AppleIntelBDW (Intel Broadwell Graphics aka HD6000)

 

So for example if you are doing this on a new 2016 MacBook Pro I would write; Replace “AppleIntelHD5000” with “AppleIntelSKL” and then go Save > Save as Application. 

@jonwatso Hi, I downloaded your iGPU tool but nothing seems happen in my early-2015 MBP 13'', internal graphic card can't disable after reboot. Is it the problem what I updated the latest MacOS Mojave 10.14.2 beta?
I would like to use internal display with eGPU acceleration, but my PS cc 2019 can't recognize the eGPU...Rx460, could you please give me some advice?
Thank you!

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


ReplyQuote
jonwatso
(@jonwatso)
Trusted Member
Joined: 3 years ago
 

Hey Rowley, 

This will be an issue with my script, as I only wrote it to work with Sierra, if you update the location for the files in the script it should work. However this script is redundant now due to the the "prefer egpu" feature in Mojave. Luckily we've come along way since this script 🙂

2017 15" MacBook Pro RP560 i7 3.1Ghz - 16GB RAM
Akitio Node + Sapphire RX480 8GB (Reference Card)
Dell 4K DELL P2715Q Display


ReplyQuote
reptilianbrain
(@reptilianbrain)
Trusted Member
Joined: 3 years ago
 

Hey @jonwatso, your script is in fact a life saver - it makes Chrome works well as well as Adobe apps.  Thanks so much.

What's interesting is that if I run it (High Sierra) the internal screen doesn't turn off unless I log out. I am assuming either eGPU takes over and runs it as Optimus (unlikely though?) or the suppressed (via purge-nvda and purge-wrangler scripts) dGPU (750M) rises from its sleep and powers the apps. In any case it's a much better performance than just eGPU where the Chrome is always using Integrated graphics even for external display and Adobe doesn't detect eGPU.

I wonder if there is any way to run it on startup (basically - load the OSX and auto- "disable iGPU") and then again on log-out (basically run "enable iGPU"), because that's essentially what I need to do now every time (otherwise I may take laptop with me and login into a black screen (dGPU is disabled via purge- scripts).

Any chance you could add some kind of command-line parameters to it?  Thanks again for sharing it!

MBP 2013 750M + Akitio [email protected]RX570 (OSX) & GTX1080 (Bootcamp)


ReplyQuote