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

Page 11 / 19 Prev Next
 

23d1
 23d1
(@23d1)
Active Member
Joined:10 months  ago
Posts: 14
May 25, 2018 5:31 pm  

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


ReplyQuote
Mize
 Mize
(@mize)
Eminent Member
Joined:6 months  ago
Posts: 45
May 26, 2018 2:52 pm  

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:4 months  ago
Posts: 4
May 27, 2018 8:48 am  

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.


ReplyQuote
lao454490095
(@lao454490095)
New Member
Joined:4 months  ago
Posts: 4
May 27, 2018 9:42 am  

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


ReplyQuote
Pigeo
(@pigeo)
New Member
Joined:3 months  ago
Posts: 1
May 29, 2018 12:53 am  

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...


ReplyQuote
piet
 piet
(@piet)
New Member
Joined:3 months  ago
Posts: 1
May 29, 2018 7:04 am  

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


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 5:21 pm  

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.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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 theitsage liked
ReplyQuote
Ekohn00
(@ekohn00)
Eminent Member
Joined:4 months  ago
Posts: 45
May 31, 2018 7:02 pm  

@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.


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 7:03 pm  

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

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 7:08 pm  

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


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 7:09 pm  

@ekohn00
???
I meant when you use the bash <(curl -s "https://raw.githubusercontent.com/learex/macOS-eGPU/v02testing/macOS-eGPU.sh") --checkSystem
please post the output of the terminal...
-merged, use master as usual

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 7:11 pm  

@fr34k
Understood.   this is exactly what I did.

 

 bash <(curl -s "https://raw.githubusercontent.com/learex/macOS-eGPU/v02testing/macOS-eGPU.sh") --checkSystem

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.

 

 

 


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 7:18 pm  

@ekohn00
might you try again? and then post the dev info...

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 7:21 pm  

(@fr34k)
Greatly appreciate the work!!!

 

--- dev info here ---

17G31f

2fbc408a4691e9db0df258fdc2d4658bd0b0dc814d0f25aa186a79316b306a98070b12fd4470fe636597e141bd5c2da2ab386cd8054e3ed4e15d5acdb8252483

--- dev info end ---

 


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 7:22 pm  

@ekohn00
might you be a beta tester???

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 7:23 pm  

@fr34k
yes sir


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 7:25 pm  

@ekohn00
ahhhh, of course
the script is NOT made for beta testers, it checks the wrangler via that sha512 string.
use the macos10135 branch, that one's unlocked.
beta detection will come at some point, probably by a --unlockBeta flag or something like that...

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 7:28 pm  

@fr34k
Did I get this wrong?

 

$ bash <(curl -s "https://raw.githubusercontent.com/learex/macOS-eGPU/macOS10135/macOS-eGPU.sh")

/dev/fd/63: line 1: 404:: command not found

 


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 7:30 pm  

@ekohn00
nope my fault macos10135

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 7:34 pm  

@fr34k
nothing is ever easy......   

bash <(curl -s "https://raw.githubusercontent.com/learex/macOS-eGPU/macos10135/macOS-eGPU.sh")

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.


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 7:43 pm  

@ekohn00
OK, therefore you either are on .4 beta or .6 beta .5 beta would have been open. I've now completely removed the check, therefore be careful. Might crash the system completely and render it un-bootable! (Wait a few minutes for GitHub toi distribute)

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 7:45 pm  

@fr34k
what the 
hell....going for the risk...worst case we reinstall the OS.
will try and report.


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 7:58 pm  

@ekohn00
see, all the allowed wrangler versions in the master are tested by me, @goalque, @mac_editor or some else who can handle any outcome. Therefore I block every other version to prevent people from accidentally crashing their system.

Atm the v0.2 is slapped together and must be properly coded first. I will add the --beta flag asaic (as soon as I can), but also add a huge warning, as I have no clue how the wrangler is programmed in those versions. asaiht (as soon as I have time), I will do that. Also the NVIDIA dGPU deactivation still isn't fully implemented yet. It's just that my University is requesting like crazy. The workload keeps me busy all day for weeks. And no change is in sight. I just thought for some slapped together still is better than not available, as it could fix a problem.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 8:08 pm  

@fr34k
I do appreciate the help and the "open" version.

Unfortunately, no joy, yet.  The script ran with no issues.  I used the longer version:

bash <(curl -s https://raw.githubusercontent.com/learex/macOS-eGPU/macos10135/macOS-eGPU.sh) --install --nvidiaDriver 387.10.10.10.30.107 --nvidiaEGPUsupport --unlockNvidia --unlockThunderboltV12

Thankfully, I can boot and use the Mac with no issues.  However, when I plug in the thunderbolt or try to boot with it in, the Mac locks up with the black screen of death.

More than happy to try other options, but was also thinking with this OS version, I might have to wait for an NVIDIA update??

thanks! 

 


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
May 31, 2018 8:13 pm  

@ekohn00
guessing from that your on .6 ...
could be an issue, yes
does the --checkSystem flag yield the correct parameters for the installed packages? some system information like the AGW will be blank but still

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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:4 months  ago
Posts: 45
May 31, 2018 8:19 pm  

@fr34k
This looks correct......  due to problems the eGPU is not plugged in.

Fetching system information...
   macOS info                                                             [done]
   system integrity protection                                            [done]
   thunderbolt version                                                    [done]
   GPU information                                                        [done]
   installed eGPU software                                                [done]
   installed patches                                                      [done]
   installed programs                                                     [done]
   fetching GPU related system information                                [done]



macOS-eGPU.sh (v0.1α)

Listing installation status of packages...
   NVIDIA driver                                           [387.10.10.10.30.107]
   NVIDIA eGPU enabler                                               [installed]
   AMD legacy drivers                                            [not installed]
   T82 unblocker                                                 [not installed]
   NVIDIA dGPU                                                   [not available]
   NVIDIA macOS 10.13.4 patch                                        [installed]
   unlocked thunderbolt version                                              [2]
   CUDA
      CUDA drivers                                               [not installed]
      CUDA developer drivers                                     [not installed]
      CUDA toolkit                                               [not installed]
      CUDA samples                                               [not installed]
Listing system information...
   macOS version                                                       [10.13.6]
   macOS build                                                          [17G31f]
   SIP status                                                                [0]
   thunderbolt interface version                                             [2]
   eGPU information
      connected eGPU                                                     [false]
   NVIDIA dGPU                                                           [false]
   AGW version                                                                []
Graphics/Displays:

ReplyQuote
ghostronaut
(@ghostronaut)
Eminent Member
Joined:8 months  ago
Posts: 22
May 31, 2018 9:11 pm  

@fr34k: Thank you for the script! Everything worked great when I first tested it, now it doesn't anymore ...
I ran the latest version of the script (it updated the CUDA drivers) without issue. When I boot into macOS with the eGPU (Aorus Gaming Box 1080) already attached, everything works for a couple of seconds, then my internal screen goes black and the performance on the external is super laggy. When I manage to log out (which takes a while because I have to do it on the laggy screen) and log back in, performance is good again for a couple of seconds, then back to the lag.

Any tips on what I could try? Hot plugging doesn't work at all, results on plug-in in black screens on both internal and external, on plug-out on system crash.


ReplyQuote
vouhardy
(@vouhardy)
Active Member
Joined:3 months  ago
Posts: 11
June 1, 2018 2:51 pm  

Hey everyone,
First of all, thank you @fr34k for such amazing work! all my good karma is with you
I've just gotten my Aorus GTX1080 today and went through the forums to find a proper installation guide, tried pretty much all available options but I am experiencing the symptoms @ghostronaut describing, initial glitchy screen followed by an extreme lag.

the glitch can be seen here
https://imgur.com/a/5QXAQWG

Specs:
macOS 10.13.4 (17E202)
MacBook Pro (Retina, 15-inch, Mid 2015)
We are exactly on the same boat here @ghostronaut 

Any suggestions would be highly appreciated
many thanks


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
June 1, 2018 2:53 pm  

@ghostronaut
@vouhardy

did you try hot-pluging after you logged out? so: boot -> log in -> log out -> plug -> log in

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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
vouhardy
(@vouhardy)
Active Member
Joined:3 months  ago
Posts: 11
June 1, 2018 2:54 pm  

Does this look okay to you? I would expect it work properly when it's also shown as the main gfx card. I've disabled dynamic switching too.

https://imgur.com/a/cHPkzQ9


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
June 1, 2018 2:56 pm  

@vouhardy
enable it!!!
Intel + NVIDIA = 😍
AMD + NVIDIA = 🤮

- yes it does -

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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 liked
ReplyQuote
vouhardy
(@vouhardy)
Active Member
Joined:3 months  ago
Posts: 11
June 1, 2018 3:09 pm  

Thank you for such quick reply! I just tried the "boot -> log in -> log out -> plug -> log in" cycle but no luck, it shows the gfx card as "null" but I am going to uninstall everything and give it a clean start now because I was testing the pretty script made by  @mac_editor.  

Other than uninstalling Nvidia driver itself, are there any other places I should be offloading? Apologize for my noob questions. I do live coded music and been lacking the graphics card to render my shaders so this is a quite big deal!:)

I will post my `checkSystem` file once I do a proper and clean install to avoid any confusion


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
June 1, 2018 3:14 pm  

@vouhardy
wait!
the null is no problem!!! In the system info it should be listed just normal. don't let the "null" confuse you!
@mac_editor's script uses the same tweaks developed by @goalque and me.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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
vouhardy
(@vouhardy)
Active Member
Joined:3 months  ago
Posts: 11
June 1, 2018 3:37 pm  

Aha!
Yes it shows null, 
The card is listed in the Nvidia Driver Manager but not shown in the "about this mac" menu, which still shows the active as `Graphics: Intel Iris Pro 1536 MB`

I've re-activated dynamic switching too. Are there any possible further actions to fix this?

you guys rock.


ReplyQuote
fr34k
(@fr34k)
Honorable Member Moderator
Joined:8 months  ago
Posts: 405
June 1, 2018 3:44 pm  

@vouhardy
not in about this Mac -> in the system information app. Only that app correctly shows the system's components. (the app you send the screenshot earlier)
You can try e.g. installing the CUDA driver and rendering a pic with blender or just fire up your favourite app and see if it's being recognised correctly.
We still don't know which functions don't get called when hot plugging but when booting with eGPU, that's why the "null" appears.
Also about my Mac most certainly has some flaws. For me everything works fine but I do have the "null" as well as the wrong info in about this 
Mac. The iM can't be accelerated (well it can using a headless, but not with software only...).

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh 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
vouhardy
(@vouhardy)
Active Member
Joined:3 months  ago
Posts: 11
June 1, 2018 3:45 pm  

Just to be clear, it is listed in the system info as you said @fr34k.

Here is the output of systemchecker flag
https://gist.github.com/cannc4/7a03596dd0e20f2fb48d9d1bd5bd96e4


ReplyQuote
Page 11 / 19 Prev Next