[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

Mize
 Mize
(@mize)
Eminent Member
Joined: 2 years ago
 

Is there a table of successes and failures based on Mac model?
Would love to find out if and how anyone has this working on an iMac Pro.

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

Hey all,

I just to let you know I followed the installation instruction, to enable the eGPU, scripted finished successfully, however I am experiencing the issue with the black external monitor (with mouse cursor)  which is connected to eGPU, also at the task bar I can see only disconnect null.

Screen Shot 2018 05 06 at 13.25.00

I already tried some suggested workaround, like logout, boot without egpu wait 15s... and all other of them, however none has been successful, anyway I will keep trying and update you with the progress, my setup :

MBP 13" 2017 with TB + Aorus Gaming Box GTX1070
MacOs version: 10.13.4 (17E202)
Latest nvidia drivers: .107

Screen Shot 2018 05 06 at 13.25.34
Screen Shot 2018 05 06 at 13.25.44

Edit: some of the system logs error:

Screen Shot 2018 05 06 at 13.59.30
2017 13" MacBook Pro [7th,2C,U] + GTX 1070 @ 32Gbps-TB3 (AORUS Gaming Box) + macOS 10.13 & Win10 [build link]  

ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 3 years ago
 
Posted by: leoleal
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.

Still no luck.

As soon as I remove NVDAEGPUSUPPORT.kext from extensions folder, the OS comes back to normal operation. But trying to reapply It with the script results in the same behaviour. Boots get stuck with cursor (active) in the internal screen and apple progress bar frozen. Nothing plugged In.

When applying the script, tho. I Noticed a specific message that looks not so good to me right after It says It's Installing EGPU Support:

Patching...
 Set: Entry, "autoCheck", Does not exist.

Does that mean anything?

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


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

@lexine, thanks for the system log. It says the same what @Username reported earlier regarding black screens:

https://egpu.io/forums/mac-setup/wip-nvidia-egpu-support-for-high-sierra/paged/8/#post-22991

WindowServer [ERROR] - Fallback GPU Display Pipe transaction submission failed

Framebuffer issues I guess. I recall there was some driver developer discussions that Apple is going to deprecate IOFramebuffer and said that it is not officially supported.

http://www.displaylink.com/downloads/macos

"We have become aware that installing macOS release Version 10.13.4 will cause DisplayLink connected displays to go blank after the OS upgrade"

Can you try other monitors/display interfaces?

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
ed_co
(@ed_co)
Reputable Member
Joined: 3 years ago
 
Posted by: fr34k

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

@fr34k @goalque
Oh, it is a pity. I thought that the new approach was for everything, not just 10.13.4.
Which by the way, could you please, tell us how this new stuff works? I think that was goalque's idea, right? Could you please explain, how it works? What exactly is it going under the hood? I liked the previous approach of yifanlu, and I am curious how it works now 😉
Today, if nothing comes up, I will install 10.13.4
Cheers guys

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

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

When I stepped up to 10.13.3 I often suffered from long boot times which came from Nvidia drivers crashing during boot. That was the cause of the black screen.
Downgrading the Nvidia drivers sovled everything.

I usually have two 27" Eizo monitors but I can't fit them both on the desk right now.
But I have connected my Mac mini HDMI out to the Eizos HDMI in and the DisplayPort from the eGPU to the same Eizo.
That way I have boot screen on Inpu1 and eGPU screen on input 2 Smile

That means I get full acceleration on my 27" over DisplayPort yet EFI boot screen if I wish.

The extra HDMI screen I've placed far right in the monitor setup in macOS.

Present: 2012 Mac mini + PowerColor RX 56 Vega Nano @10Gbps-TB1 + PowerColor Mini eGFX 180F via Apple TB3 to TB2 + macOS Catalina 10.15.4

Previous: 2012 Mac Mini + GTX1070 @ 10Gbps-TB1 (AKiTiO Thunder3 via Apple TB3 to TB2 adapter) + macOS

 
2012 Mac Mini [3rd,4C,Q] + GTX 970 @ 10Gbps-TB1>TB3 (AKiTiO Node) + macOS 10.12.4 [build link]  


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 

@fr34k
Oh, it is a pity. I thought that the new approach was for everything, not just 10.13.4.
Which by the way, could you please, tell us how this new stuff works? I think that was goalque's idea, right? Could you please explain, how it works? What exactly is it going under the hood? I liked the previous approach of yifanlu, and I am curious how it works now 😉
Today, if nothing comes up, I will install 10.13.4
Cheers guys

Yes, 10.13.4 workaround was my idea and yifanlu's workaround is still necessary - the script just automates the process. If you are curious, look at the GitHub source code Smile We want to avoid lower-level technical discussion regarding binary patches.

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]  


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

@leoleal
Nah, you just found a bug... Nothing to worry about: I haven't tested if something even exists before I do an action on it. 

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
 

Thank you for helping us all, @fr34k !

Do you believe it is what's bugging my OS? not even standalone internal screen works for me. I' m restoring 13.3 time machine backup.

If I can help you with further tests, lemme know, cause I'm keeping the clean 13.4 backup ready to go.

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


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

@leoleal
No, I don't think so.
I've just committed the fix.
What this was about:
I deactivate automatic driver updates for NVIDIA drivers and there the "autoCheck" value must be set to 0. I don't know why it didn't exist but it should not have any 
effect on that.


@leoleal
can you boot with an eM attached directly to your
Mac?

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
 of  75