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

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

@fr34k
So I ran into the issue of formatting the SSD. Like me, i'm sure a lot of other people are using these workaround steps that you've provided for us for the intention of using their mac for gaming. 

I downloaded Steam, and it gives me an error that says "Steam requires that ______ be created on a case - insensitive filesystem". 
So i've talked to Apple support, and their best advice was to erase the SSD, and reformat it to something that isn't encrypted. (They recommended APFS)

I followed all the steps from your help and was able to download the Nvidia drivers, but now i'm concerned what will happen to all of that once I erase my SSD and reformat it to APFS.
Is the worst case scenario that I just have to restart your steps over? If so, then that's really no problem.

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

.

ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 3 years ago
 

MacBook Pro late 2013 with dgpu here. Me results usign the script:

removed nvidia driver and egpusupport Kext, reset pram, disabled sip and updated to 10.13.4 with security update (from 10.13.3). ran script in default mode.

when script rebooted, my mbp stood with a cursor in the internal screen with Apple logo and progress bar Stuck (cursor was  movable). Nothing  was plugged  in.

any ideas ?

Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970


ReplyQuote
wzienrgo
(@wzienrgo)
Active Member
Joined: 2 years ago
 

Updated the script and the NVIDIA pop-ups are all gone! Great work!
Tested for a while and everything is working well except for sleep/wake. The machine won't wake up after sleep with eGPU attached.

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


ReplyQuote
Charly4
(@charly4)
Eminent Member
Joined: 3 years ago
 
Posted by: leoleal

MacBook Pro late 2013 with dgpu here. Me results usign the script:

removed nvidia driver and egpusupport Kext, reset pram, disabled sip and updated to 10.13.4 with security update (from 10.13.3). ran script in default mode.

when script rebooted, my mbp stood with a cursor in the internal screen with Apple logo and progress bar Stuck (cursor was  movable). Nothing  was plugged  in.

any ideas ?

This happened to me some times with previous scripts and solutions, what I did is booting with another OSX and delete installed eGPU files placed in Library/Extensions but now I don't have idea where are the files maybe @fr34k can help with these, try to reset PRAM again this should work...

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


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

In my case I have a MacPro TrashCan with two internal AMD Fire Pro 500 and two external eGPU's, both Nvidia GTX 1080 Ti. All it's working now. If you have one of these models please take notice that it's important to choose the right thunderbolt ports used. MacPro has 6 TB2 ports and I was successful in connecting the screen to N2, one of the eGPU to the N1 and the second one to N5.

Photos, screenshots? Let see if we can enable all 6 TB2 ports for eGPU use, my automate-eGPU.sh script's -a mode did that earlier. @fr34k could implement the same functionality.

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]  


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

@wicknest
erase, format, install macOS, run script. That's all there is.


@leoleal
Resetting NVRAM/PRAM will disable the NVIDIA drivers, maybe there was a problem. Try the reset and boot into recovery mode and disable SIP again. See if you can then get a screen. Uninstall... reboot... run again. Post results! I will try adding all tweaks to the initial post.

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

@fr34k
Is it any way to now the version of your script I used so then compare it with versions with updates shown on  https://github.com/learex/macOS-eGPU/commits/master ??

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

@charly4
no I haven't 
implemented this. This should not be necessary as I will only add functionality and remove bugs. If you still have the terminal output or the time you executed I could see what I've changed since then. Why do you want to know 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
LeoLeal
(@leoleal)
Eminent Member
Joined: 3 years ago
 
Posted by: fr34k

@leoleal
Resetting NVRAM/PRAM will disable the NVIDIA drivers, maybe there was a problem. Try the reset and boot into recovery mode and disable SIP again. See if you can then get a screen. Uninstall... reboot... run again. Post results! I will try adding all tweaks to the initial post.

Thank you for the fast response. I reset PRAM and then I disabled SIP again after removing the previous solution. The problem with repeating the process for a retry, is that I cant have even the internal screen after the first script run... the screen stays black for the internal without anything attached to the system.

Im restored to Security Update right before applying the script. I have Timemachine backups for 13.3 how It was working in my setup, and 13.4 post security install (no solutions applied). Will keep trying.

One thing that I will try now is removing DuetDisplay. It installs a display driver and may be interfering with the solution(didnt interfere with 13.3). In the case I succeed, Ill post here.

Edit: @fr34k , I just retried without duetdisplay driver, and still no internal screen. I even booted with verbose mode in boot args, but the messages appear and then the apple comes and stay there, not allowing me to read what the boot messages wrote.

Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970


fr34k liked
ReplyQuote
Charly4
(@charly4)
Eminent Member
Joined: 3 years ago
 
Posted by: fr34k

@charly4
no I haven't 
implemented this. This should not be necessary as I will only add functionality and remove bugs. If you still have the terminal output or the time you executed I could see what I've changed since then. Why do you want to know that?

Just to know if its necessary to reapply the script

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


ReplyQuote
 of  75