[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  76
  RSS

Keith Walls
(@keith_walls)
Eminent Member
Joined: 3 years ago
 

@fr34k

It won't even boot with everything connected.
If you plug in with the monitor off, it recognizes the card, and when you turn the monitor on, it then recognizes the monitor in "About Displays" but still black.

Logging out the last time I tried crashed the system.
Thanks!

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 
Posted by: Keith Walls

@fr34k

It won't even boot with everything connected.
If you plug in with the monitor off, it recognizes the card, and when you turn the monitor on, it then recognizes the monitor in "About Displays" but still black.

Logging out the last time I tried crashed the system.
Thanks!

And what happens if you log out without eM and then connect the monitor? Still crash? If so, PM us the kernel panic trace.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


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

No love for iMacPro.
Basically behaves identically to the temporary script. Blank external screen (but connected)  and internal screen turns yellow if I try to mirror the monitors. The one difference is that, after mirroring the monitors, if I reboot with the external monitor attached to the eGPU then it will eventually get to a login screen on the external monitor only (after some garbage signal) but it takes seconds between password keystrokes for the dots to appear in the password feel and after about five minutes of no response other than mouse pointer movement I hard shutdown. Did an uninstall for now, but ready to help if it means getting my 1080Ti back in macos. Off to run more Windows 10 for now.

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
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 3 years ago
 

The script will now deactivate automatic updates itself.
a) the annoying CUDA pop-up will no longer be displayed. You can always update CUDA be rerunning the script or by opening the CUDA prefpane. (you can use flags to only check CUDA, note the dependencies explained in the initial post)
b) to prevent lags in the future the NVIDIA driver updater will also be disabled. with 10.13.3 we've seen that specific older drivers work better. The ones the script installs have been tested. If you want to override the stability decision use the --forceNewest flag.

Those who want the updates disabled and have run the script successfully can just run it again.
I will add a flag in the future.

fr34k's macOS-eGPU.sh on GitHub or 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)


ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 3 years ago
 

i wanted to send you a personal message, but the forum wont let me for some reason. i had the script all typed out, and it just froze on terminal like this: https://imgur.com/hSMoJBV. All the menu bars at the top of my screen are blank. I have a Macbook Pro 2017 15" with touchbar updated to 10.13.4 and was trying to install nvidia drivers. is my system damaged? what do i do?

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

@wicknest
it just froze? wow. The script should output text even before something happens. Is this 
reproducible? If you type in the exact same does it freeze again? Have you an eGPU connected, if so remove before execution.

fr34k's macOS-eGPU.sh on GitHub or 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)


ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 3 years ago
 

so i just restarted my mac, and terminal gives me the terms of use agreement, and then says that the script was interrupted and failed. This is likely because i restarted my mac, but the terms of use never showed up when i first ran the script (thats why i restarted it). i'm not sure how to go back and accept the terms of use now. i can't run it again, because it won't let me unless i accept the terms. can you please help?

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

A huge thanks to everyone involved in making this happen. Everything works as advertised 😉

My setup: iMac (Retina 5K, 27-inch, 2017) w Radeon Pro 580 8G + tb3 Aktio Node Pro w 1080TI 11G

I don’t personally care about gaming performance and use the egpu exclusively for GPU acceleration in Premiere Pro.
Did a quick OctaneBench Cuda render test and got a total score of 178. The results were on par with the average GeForce GTX 1080 Ti benchmarks. Also, did a quick Premiere Pro/Media Encoder export of a 15 seconds timeline containing Quicktime Apple ProRes 4444 3840 x 2160 clips @ 59.94 FPS with Lumetri Color effects. Got the following results:

Render with Cuda Acceleration.- finished 1 second faster than Open CL and 2 seconds faster than Metal respectively.

- Preset Used: Vimeo 2160p 4K
- Video: 2720x1530 (1.0), 59.94 fps, Progressive, Hardware Accelerated, 00;00;15;54
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 48.00 Mbps
- Encoding Time: 00:00:43
05/05/2018 12:05:46 PM : File Successfully Encoded

Activity Monitor/GPU History shows Nvidia activity (as expected).

Render with Open CL

- Preset Used: Vimeo 2160p 4K
- Video: 2720x1530 (1.0), 59.94 fps, Progressive, Hardware Accelerated, 00;00;15;54
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 48.00 Mbps
- Encoding Time: 00:00:44
05/05/2018 12:07:11 PM : File Successfully Encoded

Activity Monitor/GPU History shows AMD activity.

Render with Metal

- Preset Used: Vimeo 2160p 4K
- Video: 2720x1530 (1.0), 59.94 fps, Progressive, Hardware Accelerated, 00;00;15;54
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 48.00 Mbps
- Encoding Time: 00:00:45
05/05/2018 12:08:55 PM : File Successfully Encoded

Activity Monitor/GPU History shows both NVIDIA/AMD activity which is very interesting.

Render with Software Only (CPU).

- Preset Used: Vimeo 2160p 4K
- Video: 2720x1530 (1.0), 59.94 fps, Progressive, Hardware Accelerated, 00;00;15;54
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 48.00 Mbps
- Encoding Time: 00:02:04
05/05/2018 12:11:23 PM : File Successfully Encoded

Activity Monitor/GPU History doesn’t show any GPU Activity.

I did hope for a more significant boost in PP’s rendering performance with the NVIDIA GPU. (Cuda encode was a mere second faster than Open CLRadeon Pro 580 8G ). I assume this has to do with either PP not being very good at utilizing the egpu or simply a CPU bottleneck. Nevertheless, I am pretty happy that Premiere is actually able to use the egpu.

Other notes:

Davinci Resolve 14 managed to finish the same export in under 30 seconds 😀 

The card isn’t detected in Lightroom and Photoshop. The GPU setting defaults for both to Radeon Pro 580.

That’s all for now. Thanks again!

EDIT:
Cuda accelerated export really SHINES with RED R3D RAW footage. Did a quick export and got the following:

19 seconds timeline with 8K and 6K footage scaled down to 4K

- Preset Used: Vimeo 2160p 4K
- Video: 2720x1530 (1.0), 59.94 fps, Progressive, Hardware Accelerated, 00;00;18;56
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 48.00 Mbps
- Cuda Encoding Time: 00:02:52 twice as fast as Open CL.
05/05/2018 05:09:07 PM : File Successfully Encoded

- Preset Used: Vimeo 2160p 4K
- Video: 2720x1530 (1.0), 59.94 fps, Progressive, Hardware Accelerated, 00;00;18;56
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 48.00 Mbps
- Open CL Encoding Time: 00:05:50
05/05/2018 05:26:13 PM : File Successfully Encoded\

- Preset Used: Vimeo 2160p 4K
- Video: 2720x1530 (1.0), 59.94 fps, Progressive, Hardware Accelerated, 00;00;18;56
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 1 pass, Target 48.00 Mbps
- Metal Encoding Time: 00:06:22
05/05/2018 05:54:54 PM : File Successfully Encoded

Mind blown! 😮 I am 100% sure that if it wasn’t for the CPU bottleneck, then the Cuda results would have been even better. So yeah, Cuda is still the king in the video editing world.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

fr34k and goalque liked
ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 3 years ago
 

https://imgur.com/a/6yG8pH6

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

@wicknest

OK you can see that the script has closed. It did not execute anything. Now press your up arrow and execute the same command again. Btw: flags are not necessary.
You could just run: bash <(curl -s https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh)

fr34k's macOS-eGPU.sh on GitHub or 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)


ReplyQuote
 of  76