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

23d1
 23d1
(@23d1)
Active Member
Joined: 4 years ago
 

Are you certain you boot and login with the eGPU disconnected? Once logged in, connect, still not working?

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

.

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

Quite certain. I've even done the login, logout, plug egpu with monitor disconnected (wait 15 secs) then connect monitor, etc. I had it working just fine under .13.3 but made the mistake of upgrading when I was sixty days out on my last backup thanks to a backup server relocation.

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
lao454490095
(@lao454490095)
New Member
Joined: 3 years ago
 

A possible bug with the script:

When running the script in iTerm2 (a terminal alternative in Mac OS), iTerm2 is killed soon after the countdown. Running in Terminal is fine.

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

.

ReplyQuote
lao454490095
(@lao454490095)
New Member
Joined: 3 years ago
 

setup: MacBookPro13.3 with ARP 460 dgpu + 10.13.4 17E202 + 1080ti with akitio node enclosure

ran the script successfully. However, with egpu connected before boot, the system experiences crazy lag (~5s before any mouse click takes effect) after logging in both internal and external displays. After trying out the suggestion like `hotplug -> log out -> log` and two of the step sets in known issues, the lag is still not solved. Also, after hotplug, the egpu is shown as Disconnect "null". After benchmarking with Geekbench, the OpenCL score of my 1080ti card is lower than that of the ARP 460.

I see other users having similar problems less than a month ago and there seemed to be no solution for them, but could you provide any suggestion at the moment?

Thanks

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

.

ReplyQuote
Pigeo
(@pigeo)
New Member
Joined: 3 years ago
 

I'm having a similar issue to @llao454490095. I am new to the community and have not yet gotten my eGPU (Akito Node + EVGA 1080 Ti) to properly work. Currently after running the automated steps (along with the pre-requisite steps) - this is the end result:  https://imgur.com/a/VpPiDxO

The card does not display in the 'About Mac' window. When connected, in the upper-right hand corner, it's called (null), but in the Systems Report - it is detected fine.

I would really appreciate any help or suggestions, spent a solid afternoon trying to debug this...

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

.

ReplyQuote
piet
 piet
(@piet)
New Member
Joined: 3 years ago
 

Thank-you.

Your script ran successfully using a fresh install of 10.13.4 17E202 on a 2016 TB Macbook Pro with discrete AMD graphics running a TitanXp in a Mantiz Venus box.

I had previous eGPU scripts running on 10.13.3, also excellent.

DaVinci Resolve is running candle test 6 blur nodes @ 17 fps and 66 TNR nodes @ 16 fps.
Valley 3148.

The same card in my 8-core i7-4820 3.7 GHz Windows 10 PC ran the candle tests at 22 fps and 17 fps respectively, it does not have a fast drive, but was able to run Valley at 4821.

Our 12-core Mac Pro runs at 5 and 6 fps, Valley 1207.

I have to hot-plug after login, logout, and log back in before I can get an image beyond the mouse cursor on my external screens.
The card is named properly in the About this Mac window but appears as "null" under the eGPU menubar item.
The eGPU disconnects on the software side but I am hit and miss on shutting down without a kernel panic.
I have to choose my GPU in DaVinci Resolve preferences to get the performance I want for the task at hand.  "Auto" doesn't always choose properly and it seems that playback is faster with "CUDA" selected in most cases.  Renders are faster in all cases I've come across using "Auto".

I can't thank you enough.  This set-up runs my jobs faster than our trash can Mac Pro is able to, though I am about to apply your fantastic script to that machine as well.  

I go home earlier and my computer runs overnight less often than it used to.

Piet in Vancouver, BC

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: 4 years ago
 

Hi all,

Due to an immense workload at the time, I was and still am unable to further improve the script.
Today however, I've found a little and made a few fixes and tests. I'm not yet finished on the v0.2α, but if you have some time to experiment then go ahead and try the new things in the v0.2α (see note below!!!) branch.
These include:
- bugfixes for CUDA (a lot has gone wrong there in the initial phrasing, only logic though, nothing that effects performance)
- the -A flag for NVIDIA dGPU users and multiple eGPU users. This might help them to get their system to post with the eGPU connected on boot
- "old wranger problem (new wrangler but detection fails; not if the actual wrangler replacement is present)" should be fixed, if not please do report.

postponed for now are:
-- iTerm fix
-- "purge system", this function would use a custom uninstaller to really purge the system from all eGPU related things. This might be helpful for corrupt systems
-- macOS beta detection for testing ahead of releases
-- some fine-tuned manual updates

Cheers!
fr34k

if you've got another idea or tip what I should work on next

P.S: To use the script use this bash <(curl -s "https://raw.githubusercontent.com/learex/macOS-eGPU/v02testing/macOS-eGPU.sh"), the v0.2α is changing constantly, so rather try the v02testing branch for executions.

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)


n9yty, goalque and itsage liked
ReplyQuote
Ekohn00
(@ekohn00)
Eminent Member
Joined: 3 years ago
 

@fr34k
Sorry to report, but I got the same old wrangler issue:

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.

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: 4 years ago
 

@ekohn00
OK, strange
might you please see what the --checkSystem flag outputs for the AGW version? also what build are you on?

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
Ekohn00
(@ekohn00)
Eminent Member
Joined: 3 years ago
 

@fr34k
no information, same output.  unless I did something wrong.

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

.

ReplyQuote
 of  77