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

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

 of  21
  RSS

ohsoweird
(@ohsoweird)
Active Member
Joined: 3 years ago
 

For anyone interested in performance results using Davinci Resolve
Running 10.3.4 (17E202) and DaVinci Resolve 15 beta 2 running CUDA 387.178

With Nvidia GTX 1080ti eGPU Akitio Node Pro TB3 on iMac 2017 27" 4.2GHz, 64GB RAM
Standard Candle test results V10 Link (max out at 24fps), comparison indicates to previous eGPU results on 10.13.3 and Resolve v14:

09 Blur nodes @ 24fps
18 Blur nodes @ 24fps
30 Blur nodes @ 24fps
66 Blur nodes @ 13fps (Actually 13.5-14 = +1.5-2fps from previous 12fps)

(Temporal Noise Reduction Nodes)
1 TNR @ 24fps
2 TNR @ 24fps
4 TNR @ 24fps (Indicates 24 but with red dot on playback = +2fps from previous 22fps)
6 TNR @ 17fps (+2fps from previous 15fps)

I should say system runs VERY stable at the time being. Some caveats when it comes to powering the eGPU but otherwise superb!

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


ReplyQuote
SirLothar
(@sirlothar)
Eminent Member
Joined: 3 years ago
 

I ran the script.   All seemed to be fine, although it put something about "a system restore point" at the end.
I get the Nvidia drivers being showed as installed and the egpu disconnect icon with the correct name of the graphics card (GTX1070

BUT

macbook pro is still running the Iris card in system settings and in any benchmarks.   I've tried just connecting the aorus gaming box diretcly via TB3 and also with an external monitor (although not connected with any HDMI etc..) - just TB3 to macbook and then TB3 from macbook to monitor.

Any help appreciated.

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


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

ReplyQuote
ahalsaver
(@ahalsaver)
New Member
Joined: 2 years ago
 

1. A gigantic thank you for al the work you've put into this.

2. I ran into the same thing ohsoweird did, except I'm on 17E202 already.

You use the old wrangler patch. Please follow instructions on eGPU.io/GitHub.
Interrupt...
cleaning system                                                        [done]

The script has failed.
Nothing has been changed.

I used the sudo rm -rfv "/Library/Application Support/nvidia10134/" , but got the same output. I also tried I tried using the checkSystem parameter, (same result) and a couple of the uninstall scripts, but they couldn't find anything to uninstall. Any advice?

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


ReplyQuote
ICULikeMac
(@iculikemac)
Estimable Member
Joined: 2 years ago
 

Hi All, unfortunately I still cannot get my external monitor to work so if anyone has tried anything other than fr34k's recommendations on GitHub and it worked if you could share that would be amazing! I have a Dell 4K 24" w/  MBP 15" 2017 R560 & AGB 1070. 

I've already tried:

  • Black external Monitor with/without mouse
    • Step set 1
      • boot without eGPU
      • hot plug eGPU with monitor
      • log out
    • Step set 2
      • boot without eGPU
      • hot plug eGPU only (no external monitor)
      • wait 15 sec
      • log out
      • hot plug monitor
      • wait 15 sec
      • log in

Thanks in advance.

2019 13" MacBook Pro (i7 & 16GB RAM) - MacOS + Win10
Late 2012 Mac Mini - MacOS + Win10
Asus XG Station Pro (RX570 8GB + RTX 2080)


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

For those running into the "old wrangler patch" issue, simply reset kext permissions after uninstalling/recovering changes from purge-wrangler.sh (SIP must be disabled). The latest version of the script should take care of the permissions better, but if not:

sudo chmod -R 755 /System/Library/Extensions/

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


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

Hi there. I need help. I’ve installed the script following the instructions and everything went as expected but, since Nvidia drivers sucks and I had glitches on some apps, I selected the system drivers in nvidia menu to wait for a future nvidia update. 

The thing is today I’ve switch on my MacBook and it just don’t boot anymore.  It fills the white bar very slowly and it eventuality just stay there forever. 

I’ve tried a pram reset, smc reset, single user boot, safe mode boot, etc...
i can boot on recovery mode but I don’t have the original AppleGPUWrangler.kext file to restore it (I do have it in the Time Machine backup but I can’t restore files from Recovery boot)

It seems I’ll have to restore the backup but I wonder if is there something I could try before do it.

Any help is appreciated. Thx.

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


ReplyQuote
Mize
 Mize
(@mize)
Eminent Member
Joined: 2 years ago
 

I don't know if recovery mode includes networking, but running the script again from a terminal in recovery with the -U option would be my next try.

iMac Pro (2017), 3.2 GHz Xeon W, 32 GB, 1TB SSD, RX Vega 56 + AKiTiO Node Pro w/ Zotac 1080 Ti, working with login hack on 10.13.3 but BROKEN by Apple blocking Nvidia in 10.13.4. Boo-hiss you Apple!


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

I don't know if recovery mode includes networking, but running the script again from a terminal in recovery with the -U option would be my next try.

Hi Mize, thank you for helping me. In fact, that was the first thing I did too. It just does nothing. The prompt appears and it seems the script is not launched (nor downloaded). 

I t turns out that I’ve found a backup file of AppleGPUWrangler.kext on my disk root folder so I’m trying to restore via terminal. I want to cp -r the file but I get an read-only error. Then I try a chmod 777 but I get a read-only file system error. My bash knowledge is very limited. Someone?

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


ReplyQuote
udia
 udia
(@udia)
New Member
Joined: 2 years ago
 

Looking forward to installing on my machine tonight.

For the older script, after running the GPU enabler I performed the following steps to get the display working:

  1. Boot up the laptop, eGPU enclosure unplugged
  2. Once logged in, plug in and turn on eGPU enclosure
  3. Wait until OSX detects eGPU, shows a black screen on external display (detected, cursor visible, nothing else)
  4. Log out (this now shows the new background)
  5. Log back in to use.
    1. Full shutdown still required as unplugging the eGPU causes kernel panic.

I'll reply to this post with my experience with the new script.

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


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

I’ve ended restoring my time machine backup. 🙁

This is the last time I try this. It seems that my nvidia tb1 MacBook doesn’t really support this hack. I’ll wait until I get a new Mac or Apple re-enable it (if only...) I don’t have any need for egpu support on macOS anyway

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


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

Updated with no problems.
No issues so far, except the usual things:
- Login-logout-login process...
- When turning off after using eGPU, I have a black screen of death, and when you return to macOS it always says that there was a problem in the OS and had to restart...
For the rest, pretty much the same. I think with no improvements, except having the last OS.
Hopefully this could be resolved one day.
Thanks guys for your huge effort 😉

EDIT: just when I post this, I had glitches in my screen, like a diagonal thick line... I couldn't get a picture, and if I get it again, hopefully I can take a photo...

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


fr34k liked
ReplyQuote
ed_co
(@ed_co)
Reputable Member
Joined: 3 years ago
 

Another quick question. I realised that I did not installed the latest security update, and I did the whole process.
Once I installed it, Do I have to execute the command again?
Cheers.

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


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

@ed_co Yes. The script has to be ran following each system update.

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


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

@ed_co Yes. The script has to be ran following each system update.

I already did. Thanks!!
So, after the installation of the update. I executed again the script as before.
The difference was, the script realised the CUDA driver was already installed and with the latest version so, didn't need to install it. For the rest, pretty the same as the previous log.
Pretty straight forward. Nice, easy and clean.
Good job again 😉

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


ReplyQuote
Mize
 Mize
(@mize)
Eminent Member
Joined: 2 years ago
 

Seems there's a new hot-plug-logoff scheme that gets things working, but I can't find a post where someone spells it out. I've tried logging off then plugging in and logging back in but that results in black screen on the eGPU so if anyone can post the new way in 3rd grader terms I'd appreciate it.

iMac Pro (2017), 3.2 GHz Xeon W, 32 GB, 1TB SSD, RX Vega 56 + AKiTiO Node Pro w/ Zotac 1080 Ti, working with login hack on 10.13.3 but BROKEN by Apple blocking Nvidia in 10.13.4. Boo-hiss you Apple!


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

Seems there's a new hot-plug-logoff scheme that gets things working, but I can't find a post where someone spells it out. I've tried logging off then plugging in and logging back in but that results in black screen on the eGPU so if anyone can post the new way in 3rd grader terms I'd appreciate it.

Where?? Haven't seen... As far as I know, the log out and then login is always necessary...

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


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

Unfortunately the logout and login is not working for me as well ... Tried all possible steps, but outcome is still the same, black screen with the mouse cursor on external monitor connected to eGPU - post

What I found out is that when I try to mirror the displays the internal display will also turn into the black one with the mouse only...

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


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

You have full OpenCL, OpenGL and Metal acceleration when you just hot plug the eGPU. You don't have to do anything else.

The external monitor works exactly like a headless ghost adapter when the eGPU is hot plugged. Invisible windows on the external display can be moved to the internal display by the Spectacle app, and Valley runs smoothly on your internal display.

In order to have eGPU display output, you have to logout and hot plug the eGPU monitor, or boot with eGPU plugged in.

If it does not work as described above, it is very likely a framebuffer issue with the internal display or an incompatible external monitor.  You have to find a way to use the Intel graphics to drive your internal display. If the AMD dGPU is active, this will always result in black screens. If displays are in mirror mode, both the internal and external become black.

It seems that Nvidia dGPU equipped Macs and iMac Pros are the only exceptions - all other Macs should behave as described, right?

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


fr34k liked
ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

Tried the new script this afternoon on my 2016 15" w/ 460, razer core v2, gtx1080.  Installation went smoothly, but about the only thing that worked was CUDA.  Geekbench 4 had a blank entry under OpenCL, below the Intel and AMD entries in the menu, but selecting it did nothing.  Metal only listed the Intel and AMD igpu and dgpu.  Eject icon showed (null), external monitor was black with cursor, mirroring caused both screens to go black with cursor.  GTX1080 was listed in system profiler.

I tried booting with egpu attached, booting w/out egpu, hot plug, log in log out with eM attached, and booting w/out egpu or eM, hot plugging egpu, logging out and hot plugging monitor.  Behavior was basically the same.  Tried DP and HDMI outputs, HDMI didn't work at all.

I checked the console log and saw similar frame buffer errors to those listed above: link

I need this system fully operation for work tomorrow so I restored from Time Machine, and reenabled SIP for now. 

2019 16 Macbook Pro + Core v2 + Radeon VII MacOS 10.15.1
Core X Chroma + RTX 2080 Windows 10 1909
Asrock X570 Phantom Gaming ITX/TB3, Ryzen 5 3400G + Core v2 + Radeon VII Win10 1909


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

@Ningauble77: What Nvidia driver version? I recall OpenCL required the latest.

EDIT: just confirmed that also OpenCL and Metal work in Geekbench 4 (old .103 driver & GTX 980).

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


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

Tried the same as @ningauble77 : "booting with egpu attached, booting w/out egpu, hot plug, log in log out with eM attached, and booting w/out egpu or eM, hot plugging egpu, logging out and hot plugging monitor. ", did checked as well on my samsung TV, and it was still the same ...
the solution for 10.13.2 was working as well just fine for me ...
Also when I connect monitor without egpu directly to TB3--> hdmi on monitor, it is working, so I am quite surprised with this un-compatible monitor ...
Anyway huge difference is that he is running 15" with dGPU and I am on 13" with Intel GPU only, but seems that according the logs we might just have the same issue ... 

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 
Posted by: goalque

@Ningauble77: What Nvidia driver version? I recall OpenCL required the latest.

EDIT: just confirmed that also OpenCL and Metal work in Geekbench 4 (old .103 driver & GTX 980).

It was whatever the script installed by default, I believe the 107 driver?  I went into the nvidia web driver control panel to check for updates and it claimed I had the most recent version.

2019 16 Macbook Pro + Core v2 + Radeon VII MacOS 10.15.1
Core X Chroma + RTX 2080 Windows 10 1909
Asrock X570 Phantom Gaming ITX/TB3, Ryzen 5 3400G + Core v2 + Radeon VII Win10 1909


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

@goalque
The external monitor attached to the eGPU worked just fine at 10.13.3. They obviously broke something that is hard or impossible to fix with 10.13.4.

iMac Pro, nVidia GTX 1080 Ti eGPU

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

the solution for 10.13.2 was working as well just fine for me ...

A lot of things have been changed since 10.13.2. Driver developers have big problems on macOS 10.13.4:
 
https://appleinsider.com/articles/18/04/04/macos-10134-update-breaks-duet-display-air-display-usb-displaylink-drivers

"Apple performed a great deal of work on the graphics in macOS 10.13.4 to implement eGPU technologies, so it stands to reason the problems are related to that effort."

Anyway huge difference is that he is running 15" with dGPU and I am on 13" with Intel GPU only, but seems that according the logs we might just have the same issue ... 

Good point. These "display pipes" log errors are the common factor, mentioned in the darwin-drivers discussion groups as well.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
ICULikeMac
(@iculikemac)
Estimable Member
Joined: 2 years ago
 

Okay thanks for all the information everyone and as always appreciate the gigantic effort to get this far. My understanding so far is that the black screen with eM is unavoidable at this stage with dedicated GPU's and some monitors.

2019 13" MacBook Pro (i7 & 16GB RAM) - MacOS + Win10
Late 2012 Mac Mini - MacOS + Win10
Asus XG Station Pro (RX570 8GB + RTX 2080)


ReplyQuote
chipmunk
(@chipmunk)
New Member
Joined: 2 years ago
 

I have used tried the script as described. While I do get the eGPU working with CUDA in Maya/nuke I do only get a black external monitor.

Imac Pro (dGPU Vega 56)
OS: high Sierra 10.13.4  (17E202)
Akitio Node with Nvidia GTX 1080

tried 

  • Black external Monitor with/without mouse
    • Step set 1
      • boot without eGPU
      • hot plug eGPU with monitor
      • log out
    • Step set 2
      • boot without eGPU
      • hot plug eGPU only (no external monitor)
      • wait 15 sec
      • log out
      • hot plug monitor
      • wait 15 sec
      • log in

any idea? I have 24inch dell 4k monitor connected through DP to the eGPU. I tried different DP ports. no image.

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


ReplyQuote
wuyefeng
(@wuyefeng)
New Member
Joined: 2 years ago
 

Thanks!

MacBookPro 15 (2017) MacOS 10.13.4(2018-1) + Aorus GTX1080 Gaming Box + Aorus GTX1070 Gaming Box Success!

Cinema 4D R19 Octane 3.07R2

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


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

@ICULikeMac
As far as I can see, it is enabled?

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


ReplyQuote
TitaniumJones
(@titaniumjones)
New Member
Joined: 2 years ago
 

This script is great!
I have used it on both my Late 2013 iMac (TB1) and my Mid 2012 MacBook Pro (TB1)
Up until this point I have been holding off on upgrading to 10.13.4.
I see the some of the same issues such as kernel panics when disconnecting and 'null' when plugged in, however these are none issues in the grand scheme of things. 

I do however loose brightness control when the NVDAEGPUSupport.kext is loaded on my MacBook Pro.

I now only load the kext when I need to use the EGPU and unload it when not using it. Is this a known bug? Is there a work around?

MBP - mid 2012, iMac - late 2013, MacMini - mid 2011, xServe - 2009
Sonnet eGFX BREAKAWAY BOX, Nvidia GTX1060 Dual, CUDA rendering.


ReplyQuote
ICULikeMac
(@iculikemac)
Estimable Member
Joined: 2 years ago
 

Sorry my mistake, thanks Gregor. Updating my post now!

2019 13" MacBook Pro (i7 & 16GB RAM) - MacOS + Win10
Late 2012 Mac Mini - MacOS + Win10
Asus XG Station Pro (RX570 8GB + RTX 2080)


ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 2 years ago
 

OK, I'm a few days in now and have had - for the moment - to abandon the experiment. It started well, with everything working, but then:
- I had inconsistent results in terms of whether I got: eGPU external screen + blank internal screen; eGPU external screen + internal screen on iGPU; eGPU external screen + dGPU internal screen or eGPU external screen plus random visual noise on the internal screen. No obvious pattern here - it seems to depend on wind direction.
- the eGPU menu would sometimes show the disconnect (null) message - at other times it correctly identified the GTX 1080ti
-  The killer however was that, after the first 24 hours, I couldn't plug, unplug or even shut down the machine without a kernel panic - didn't matter when in the boot process I plugged in. If I booted with the eGPU already plugged, it would boot, but lag the OS X UI, and logging out and in again didn't fix it. Strange that it worked fine at first.

This is a great project, with a huge amount of hard work going in to it - I just need to let things stabilise a little before I try again.

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


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

@Technomad There is always a pattern. Computers do what we tell them to do. There are just bugs we need to hunt down Smile I know, would be more suitable job for Nvidia engineers.

It is good to keep in mind that troubleshooting requires patience and good strategies, macOS reinstallations, SMC/NVRAM resets, and making notes on the paper. You don't have to be a programmer. It might be as simple as changing the driver version as @LeoLeal proved.

Of course, good to warn that this is not suitable for everyone, you have accepted the risks.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


itsage liked
ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 2 years ago
 
Posted by: goalque

@Technomad There is always a pattern. Computers do what we tell them to do. There are just bugs we need to hunt down Smile I know, would be more suitable job for Nvidia engineers.

It is good to keep in mind that troubleshooting requires patience and good strategies, macOS reinstallations, SMC/NVRAM resets, and making notes on the paper. You don't have to be a programmer. It might be as simple as changing the driver version as @LeoLeal proved.

Of course, good to warn that this is not suitable for everyone, you have accepted the risks.

I entirely agree: my somewhat flippant point - insofar as there is one - is simply that I don't have the time at the moment to chase down and eliminate all the variables, so I can't give really effective feedback to the dev process, much as I'd like to be able to do so. I've been a developer/architect for nearly four decades, so would hope I've got a vague notion of software complexity by now 😉 I had no intention of sounding remotely snarky - I really appreciate the work that's being done here and would love to be able to contribute more.

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


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

Worked for me... maybe even including how to accelerate 5K LG display, downloading a game to test...

edit: Benchmarks dont appear to detect it.. ahh well...

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


fr34k and itsage liked
ReplyQuote
chipmunk
(@chipmunk)
New Member
Joined: 2 years ago
 

I tried what Leo has suggested with the older driver. still black screen on external. I can't even eject/unplug/turn off without the iMac Pro going down.

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


ReplyQuote
 of  21