[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

smEca
(@smeca)
New Member
Joined: 3 years ago
 

I just tried to migrate from the temporary script (for 17E199), but the nvidia10134Uninstall.sh seems no longer online. Can someone help me. Thx in advance.

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

.

ReplyQuote
ed_co
(@ed_co)
Reputable Member
Joined: 4 years ago
 
Posted by: Keith Walls

I removed the patches on 13.4 with the --uninstall command, updated to 13.5, then ran the .2a script. It worked with no errors. Unfortunately, I don't have time to wipe the system and try again. I'm heading for Berlin in a few hours. I'll work on it again when I get home in a week.

@fr34k @Keith Walls
So if I want to update to 10.13.5, I should do it in that way? First uninstall and then install it again?

2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.13 & Win10 [build link]  

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

so found out my lockup problem is related to the new Nvidia driver version 387.10.10.10.35.106. Once I Rerun the script with driver version 30.107 everything works fine. Any idea?
Thanks.

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

.

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

@y81r
Well, the script will do EVERYTHING! Just follow the instructions and the script will set up your system for eGPU. My script has portions in it that are critical to the execution and a panic induced by an unexpected eGPU connection or removal might render the system in an unrecoverable state. But as @mac_editor already stated, my script won’t allow an execution with an eGPU connected. Or more generally: The critical parts are secured trice. There are numerous safety measures in it preventing it from being easily killed, the system panicking, or other bad things.
If you follow the instructions carefully it will all work out well. Well, some report .5 not working as it should, but that’s something I can’t tackle atm since I’m neither at home nor around my Mac nor do I have time for research. These things must wait some weeks.

@smeca
Oh I thought everyone already migrated. I’ll try restoring as soon as possible. Might take some days until I can do that.

@ed_co
Man unistall is Never needed before an upgrade. All systems are designed to stop working after an upgrade to avoid crashing. That’s why the script needs to be re-executed every time, and why I incorporated the short command. This time however, please ensure that you have a full backup as not everything seems to work smoothly.

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

I had an important project with tight deadlines, so I postponed migration to minimize that something screw up in the middle of project. I'm using egpu for CGI rendering on mac for over year now and I'm happy that people like you exists.

I'm probably the last one. I apologize
thx

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

.

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

@fr34k
Thanks for your replay!
I'm very frustrated after two days, I have the system reinstalled two times and each time not get the eGPUs to run, I think that it is due to macOS10.13.5.
I also could not find a downgrade to 10.13.4 that works.

Thanks anyway.

Greetings from Germany

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

.

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

When running the script, it could not detect my egpu. 

   waiting 20 seconds for user to connect eGPU

   20..19..18..17..16..15..14..13..12..11..10..9..8..7..6..5..4..3..2..1..0

   fetching eGPU information                                              [done]

 

--- eGPU has not been connected ---

Interrupt...

   cleaning system                                                        [done]

The script has failed.

Nothing has been changed.

I am running an akitio node with a 1080 ti and a thunderbolt 3 to thunderbolt 2 adapter. My computer is an early 2015 macbook pro retina.

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

.

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

@fr34k @goalque

Hi thanks for the tool and instructions. However, cuda is not able to detect my external 1080Ti.

  • The script runs successfully and no errors.
  • System report shows "NVIDIA Chip Model".
  • deviceQuery shows only the internal GT 750M

@philw had similar question in this thread:
https://egpu.io/forums/mac-setup/script-fr34ks-macos-egpu-sh-one-script-all-solutions-fully-automated/paged/2/
I followed @goalque's answer, reinstalled high sierra, it actually installed 10.13.5 (17F77). I had to remove NVDAEGPUSupport.kext in order to boot. Then I ran through the macOS-eGPU.sh again, same problem as before.

What should I do next to fix it? Help appreciated!

 

I have:

MacBook Pro (Retina, 15-inch, Mid 2014)
NVIDIA GeForce GT 750M 2048 MB
macOS 10.13.4 (17E199)

AkiTio Node TB3 w/ Geforce 1080Ti

ACool

BTW, I was using a TB3 to TB2 converter. The HW setup should not have any problem as I tried eGPU support on the same setup a year ago on macOS 10.12, and I was able to get 1080Ti detected back then.

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

.

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

ok after many trial and error, I found that if I plug in the eGPU right after I hear the sound during reboot, I can reliably get my 1080Ti detected properly. Everything works fine after that. Now I'm running:
10.13.5 (17F77)
web driver : 387.10.10.10.30.107

The issues I found so far:

  1. if the internal display was turned off due to sleep or close the lid, it won't come back up. This is a problem as I have to force a reboot to get the display back.
  2. the disconnect not quite working. Once it stuck in disconnecting, another time it turned off the internal display after disconnecting, so due to problem #1 I still have to reboot.
  3. If I boot up with the eGPU connected (with or without display connected to eGPU), it won't boot up.
  4. If I connect the eGPU after laptop boot up, it will be detected as "Nvidia Chip Model" and won't work.

I'll try more and report back. In the meantime, if I can get some help on #1 and not have to loose the display that would be great!

Thanks
A

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

.

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

@acool
thank you so much for your detailed report, I will test your approach and hope it works. 
I need the gpus to render 3D projects in the office and can not lose time anymore for testing things around, if it does not work now I will return to my two 1080tis on my Win10 system at home where it has been almost two years without any problems.
Result: NVIDIA on Mac is a nightmare.

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