Share:

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

Page 3 / 21
  RSS

fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 4:52 pm  

@robert_avram
why are you using a headless?
-> try:
a) no headless
b) no eM
c) login, hot plug eGPU, logout, plug monitor
d) login, hot plug, restart

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
wzienrgo
(@wzienrgo)
Active Member
Joined: 12 months ago
Posts: 8
May 5, 2018 5:00 pm  

Hi, thanks for the amazing work!
Just tried the script on my machine and it just works!  😀 

Here is my setup:
Mac: iMac Pro with 10.13.14 (17E202)
eGPU: Mantiz Venus with Gigabyte GTX 1080 Ti

I mainly use the eGPU for octane render so I ran octane bench right after the installation and the score is 187. So I guess the CUDA part is working well.
The NVIDIA Web Driver version is 387.10.10.10.30.103 and it shows there is an update (387.10.10.10.30.107), is it OK to update?

Here are still some little issues:
1. Booting with eGPU plugged in will result in a black screen. So I have to boot without eGPU attached and then hot plug. But no re-login is needed, the eGPU is just working right after hot plugging.
2. Disconnecting the eGPU from the menu bar icon (showing "Disconnect (null)" option) will crash the system and reboot.
3. The CUDA Preferences window will always appear after booting without eGPU.

Thanks again for the great work!

iMac Pro (macOS 10.13.14) + GeForce GTX 1080 Ti (Mantiz Venus)


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 5:03 pm  

@wzienrgo
1.) this seems to be system 
depended
2.) in research
3.) I'll add a few lines to deactivate NVIDIA driver updates and CUDA updates (those annoying pop-ups); the drivers that get installed have been tested multiple times, that's why they're not always up to date, but feel free to test them (please report afterwards)

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
(@keith_walls)
Eminent Member
Joined: 1 year ago
Posts: 34
May 5, 2018 5:13 pm  

Script ran to completion, no errors. Internal display is blank, external display looks fine. System running extremely slowly, won't even respond to keyboard/mouse.
Monitors and Driving cards displaying properly in "About..." When booted without the eGPU, everything looks fine except it's using the Intel iGPU instead of the AMD Radeou dGPU.

MacBook Pro 2017 (14,3); nVidial GTX 1080 Ti in Sonnettech enclosure.
17E202 OS level

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


ReplyQuote
Charly4
(@charly4)
Eminent Member
Joined: 2 years ago
Posts: 39
May 5, 2018 5:14 pm  

Hi guys,

Edit: I forgot to say THANK YOU GUYS!!

My setup:

- MacBook Pro Retina 2012 (iGPU Intel 400 dEGPU envidia 650M)
- Akitio Thunder 2 eGPU Enclosure
- Nvidia Geforce GTX 970
- Dell U2414H by DisplayPort to eGPU

Things working:

1- Booting process really fast.
2- eGPU detected correctly by the system in the sys prefs and the new eGPU desktop icon
3- External display on without any glitches or artifacts.
4- CUDA working

Not working:

1- System can't use eGPU as Open GL
2- Switching automatic graphic cards in System Preferences not working also gSwitch not working.
3- When system goes to sleep switch off everything, eGPU fans stop spinning but when wake up the sys the internal screen stay black, external connected to eEPU is working and also connecting another display by the HDM or DP ports of the Macbook works.
EDIT:
4- Disconnect "NVIDIA Geforce GTX 970" works, starts closing all apps in  external display and starting them in the internal screen, then switch off the display and eGPU but if I reconnect the eGPU Kernel Panic
5- Some minor graphic glitches or artifacts

Captura de pantalla 2018 05 05 a las 19.20.17

Macbook PRO Retina 2012 15" (Intel HD 4000 + Nvidia Geforce GT 650M)
Akitio Thunder 2 + Nvidia 970 GTX


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 5:17 pm  

@keith_walls
yeah, AMD dGPU + NVIDIA eGPU seem to be a bad combo. Don't uncheck automatic graphics switching. Already tested and all black is the result. If you want to test that, make sure not to move the mouse as you would be unable to find the toggle again.
I've got your predecessor and it's the same for me (at least when we tested it first, haven't tried since), extreme lag when booting with eGPU, hot-plug is boom and go (I need to logout for my eM to work)


@charly4
the problem here is the NVIDIA dGPU (OpenCL/GL). @mac_editor has the same problems. He's still searching for a reason. I can't since I don't own a NVIDIA dGPU Mac.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
Charly4
(@charly4)
Eminent Member
Joined: 2 years ago
Posts: 39
May 5, 2018 5:31 pm  

fr34k

First of all thank you again for your hard work and time...

I read it, just writing my experiences in case it helps someone.

@mac_editor wish you luck !! 😉

Macbook PRO Retina 2012 15" (Intel HD 4000 + Nvidia Geforce GT 650M)
Akitio Thunder 2 + Nvidia 970 GTX


mac_editor and fr34k liked
ReplyQuote
ccr
 ccr
(@ccr)
New Member
Joined: 12 months ago
Posts: 3
May 5, 2018 5:32 pm  

Great thank you @fr34k !

2017 MBP15 3.1GHz, 16GB, Sonnet eGFX650, Akitio Node, GTX1080, RX Vega 64


fr34k liked
ReplyQuote
(@keith_walls)
Eminent Member
Joined: 1 year ago
Posts: 34
May 5, 2018 5:34 pm  

fr34k et al.
Thanks for your hard work on this! It appears this will only work with this combo if the eGPU is plugged in after boot.

Anybody try this yet on an iMac Pro?

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


fr34k liked
ReplyQuote
ed_co
(@ed_co)
Reputable Member
Joined: 2 years ago
Posts: 386
May 5, 2018 5:46 pm  

@fr34k
Wow, nice!! Good stuff guys!!

As fr34k recommended, I was waiting to update till the moment there were a solution... And now the moment came. Unless you tell me it is not safe for me (mbp 15" 2017 + TB3 case + 1080ti)

The only that I did till the moment was:
Intall the NVDAEGPUSupport package several times (as new version/security packages of macOS were released), until a previous script that fr34k (I think) provided to install automatically the latest version of the package + the proper version of nVidia driver (which was the patched 106 version which was the one having the best performance).

Nothing more, nothing less.
I think that I can try the new method without updating to 10.13.4, right?
In order to uninstall what I have till now, I proceed to manually delete the /Library/Extensions/NVDAEGPUSupport.kext? Or do I should do anything more?

The only thing I should do is just to install in the following way and that's it?
bash <(curl -s  https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh)

Maybe it looks pretty lame to ask with all the help written, but I don't want to screw things up...
Thanks guys, you are awesome!!

E.

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


ReplyQuote
(@keith_walls)
Eminent Member
Joined: 1 year ago
Posts: 34
May 5, 2018 5:48 pm  

Geekbench 4 results (GTX 1080i eGPU)
CUDA 252637
Metal 205481
OpenCL 44478

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


goalque and fr34k liked
ReplyQuote
jarandaf
(@jarandaf)
Active Member
Joined: 1 year ago
Posts: 8
May 5, 2018 6:07 pm  

I am now trying to run the CUDA samples. For that, I am using the script with the --cudaToolkit/--cudaSamples flags, but I am not able to locate the corresponding /Developer directory. Any hints @fr34k?

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 6:08 pm  

@ed_co
OK:
1. The script still works for 10.13.3, I've excluded 10.12 since @goalque covered that in the automate-eGPU.sh
2. 10.13.3 does not need any changes, it's as good as it is.
3. only 10.13.4 needs more which now is covered by the script
4. No, the enabler still plays a key role in the whole setup, it is covered by the script, so uninstallation/deletion is not 
necessary. What I meant were 10.12 and earlier software. This uses other methods which interfere here. If you have a running 10.13.3 then there is nothing to uninstall.
5. With this script you now can upgrade to 10.13.4 and still have your eGPU working. This was not possible before this script was released.
6. Yes the command you posted is sufficient. The script will always execute fine without flags. It will then self-deduct what you want from it. If no eGPU solutions are installed (for NVIDIA or AMD on 10.13.X) it will at some point prepare a secure eGPU connection (don't connect the eGPU unless the script explicitly asks you to do so, the last you want to have is a panic during execution). This will prevent the system from loading the eGPU but not the script from extracting the information it needs. You then must disconnect the eGPU when the script tells you to. No earlier, no later. You've got 20s for each. I hope it's pretty self-explanatory. Since you have the enabler installed it will know that you're an NVIDIA guy with an already running setup (at least had) and not ask you to connect.
7. No ask, asking lets others get more explicit answers one as dev hasn't thought of.
8. To reiterate: your 10.13.3 setup is running: make a full backup first. It has worked for many but it might no work for you.

If something remained unclear, please ask again.


@jarandaf
researching, can you provide me with a little more detail? What did you do up to this point and what did you execute now? Was CUDA installed at first run?

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
ed_co
(@ed_co)
Reputable Member
Joined: 2 years ago
Posts: 386
May 5, 2018 6:21 pm  

@fr34k
2. Meaning? It will not do any change in my system being 10.13.3? If so, I don't even need to run the script... as it is currently working. I though that the new procedure does something in any macOS version...
6. I should run the command without any eGPU connected, I guess. And just follow the instruction when required, right? I was not thinking about running the script with eGPU connected.

Thanks man, I appreciate your hard work.

E.

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


ReplyQuote
jarandaf
(@jarandaf)
Active Member
Joined: 1 year ago
Posts: 8
May 5, 2018 6:35 pm  
Posted by: fr34k

@jarandaf
researching, can you provide me with a little more detail? What did you do up to this point and what did you execute now? Was CUDA installed at first run?

I first installed everything with no additional flags. As commented above, everything worked out with no issues (my eGPU is detected and I can use both internal/external monitors). Since I want to run some machine learning stuff on my box (mostly tensorflow/keras python libraries), I need for that the CUDA toolkit libraries. For that, I again run the script with the --cudaDriver flag. I then noticed that CUDA toolkit needs to be installed separately and run the script again with the --cudaToolkit flag. This should have installed the mentioned folder somewhere, but it didn't so I retried with the --cudaSamples flag (without noticeable changes). Here you can find more information about the CUDA Toolkit installation process.  The thing is you somehow deal with this (e.g. here) but it is not persisted anywhere. I guess this is not strictly necessary to make eGPUs work but some libraries within the toolkit may be potentially required by others (e.g. in this case Tensorflow).

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 7:15 pm  

@ed_co
2. Yes it does not change 10.13.3 at all. The new procedure is only required due to the update to 10.13.4
6. Yes the script will not run with an eGPU connected. It will simply refuse action to prevent panics during execution. This measure is for newbies that might think that would be a great idea, which it definitely is not.


@jarandaf
ah I might have found something. This just might be a logic error. Let me research further and fix that...


@jarandaf
Bug fixed. approx 5min till distribution complete.
Thanks for catching that one.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
(@keith_walls)
Eminent Member
Joined: 1 year ago
Posts: 34
May 5, 2018 7:52 pm  

On the iMac Pro, external monitor connected to GTX 1080 Ti is blank, even though "About Displays" is correct. No combination of events that I have tried will yield a different outcome. Benchmarks on the GTX are normal.

This is different behavior than the MacBook Pro/ GTX combination mentioned earlier.

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 7:56 pm  

@keith_walls
so logout with everything connected or only connecting the eM when logged out and booting with eGPU etc did nothing?

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
(@keith_walls)
Eminent Member
Joined: 1 year ago
Posts: 34
May 5, 2018 8:09 pm  

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

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: 2 years ago
Posts: 1369
May 5, 2018 8:18 pm  
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
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


fr34k liked
ReplyQuote
Mize
 Mize
(@mize)
Eminent Member
Joined: 1 year ago
Posts: 47
May 5, 2018 8:23 pm  

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: 1 year ago
Posts: 389
May 5, 2018 8:24 pm  

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.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
Posts: 13
May 5, 2018 8:38 pm  

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?

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 8:46 pm  

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

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
Posts: 13
May 5, 2018 8:55 pm  

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?

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


ReplyQuote
mardarethedog
(@mardarethedog)
New Member
Joined: 12 months ago
Posts: 3
May 5, 2018 8:55 pm  

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.

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


fr34k and goalque liked
ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
Posts: 13
May 5, 2018 8:57 pm  

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

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 8:57 pm  

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

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
Posts: 13
May 5, 2018 9:09 pm  

Okay so i ran that on its own, and was able to accept the terms. When it asks for a password, it doesn't let me input anything, it just has the key icon. What do i do here? I apologize for my extreme lack of knowledge, I'm not very good at this side of tech. I'm just trying to be extra careful so I don't damage anything. And thanks in advance for the incredibly fast responses. You're a huge help. 

Edit: I entered my password and it asked me to connect my eGPU, which I wasn't able to in time, and it started me over. What can I do to get that again? Just enter everything again and start over? Again, I very much apologize.

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 9:12 pm  

@mardarethedog
I remember deep deep in the Adobe's installations there's a "list" of supported cards. You must search a bit in the internet but if I recall correctly you simply must add your exact name and it will work. I don't know where that list is, though.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 9:15 pm  

@wicknest
Entering the password won't show stars or any other character simply out of security. The shell's output often is saved in logs and therefore you just need to type in your password and hit 
return. I might add such a note into the script. This just is a security measure. If you've already typed some characters, just press the backspace key often enough an begin anew.

EDIT: No worries. Yes, just rerun. It will also ask you to disconnect in time. Do that as well. BUT ONLY WHEN IT ASKS, NEVER EVER ERLIER OR LATER!!!!

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
Posts: 13
May 5, 2018 9:17 pm  

Awesome thanks. Were you able to see my edit on my previous response?

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 9:20 pm  

@wicknest
Were you able to see mine 😛

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
Posts: 13
May 5, 2018 9:24 pm  

sorry just saw it. it gives me the agreement again, but then automatically fails it and doesn't give me a chance to accept again.

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


ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
Posts: 13
May 5, 2018 9:24 pm  

https://imgur.com/a/VKe7MqB

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 1 year ago
Posts: 389
May 5, 2018 9:38 pm  

@wicknest
I haven't yet figured out how to prevent this. (I know about this bug)
Simply go again. The script is made so theoretically you can't break the system. (I hope it works now..., if not I'm still around for some time, although it starts getting late here...)

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
Page 3 / 21