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

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

 of  21
  RSS

wicknest
(@wicknest)
Active Member
Joined: 2 years ago
 
Posted by: fr34k

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

what exactly do you mean by go again? is there a workaround, or am i just stuck in a loop?

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

@wicknest
simply execute again. (up arrow + enter)

EDIT: Did it work now? (No answer in about 30min either means all good or the system fell apart)

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
bellman
(@bellman)
New Member
Joined: 2 years ago
 

Thanks for the script! I'm getting the following checksum error:   https://imgur.com/a/pvjDZPP

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

@bellman
will look into this... Give me a few moments.

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
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
 

thanks a bunch once again. everything seemed to download normally. if there is any other questions, what is the best way to reach you?

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

@wicknest
just post in the thread, then my answers will reach everyone. be sure to include @fr34k
If it's really personal info you can PM me. If it's ok for the public to know, the thread is better.

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
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
 

Understood. One more problem. The drivers downloaded, and I plug in my eGPU. I got the "null" issue, so I restarted my Mac. Once it started back up, all I have is a black backlit screen. I can hear a YouTube video playing, but I cant see anything. What should 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: 2 years ago
 

@bellman
I've found the bug and already committed. Wait approx 5min for GitHub to distribute.
Thanks!

I've also added a message, that you will have to re-run the script after the Mac has been rebooted since the script couldn't read all information since you're using a T82 controller and that one had to be unlocked first. You're the first one to test this route. Be sure to report any findings, oddities or success. This is really helpful!


@wicknest
You will just have to live with the "null" we're still doing research in that area. The eGPU should still work fine even if "null" is displayed. (Sometimes a (hot-plug then) logout might be necessary to get an external Monitor to work)

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
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
 
  1. So even though null is displayed, my MacBook should still be registering it and using it? Looking in the "about this Mac" section still displays the default graphics (Radeon Pro 555/Intel HD graphics 630). Also I'm currently not going to use an external monitor, just going to use the computer itself for everything. 

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

@wicknest
That is correct. about this Mac does not display correctly with the "null" problem (and some other cases as well)
The eGPU should still work correctly (for CUDA e.g.).
Just be sure NOT to hot unplug the eGPU this causes a panic or pressing the disconnect button: same result (a panic).

Also you might experience troubles when shutting down your MacBook since it automatically boots when a power is connected. (depending on your eGPU enclosure)
You can either try disabling this behaviour (I'll post commands tomorrow) or not doing a shutdown but always rebooting and unplugging the eGPU the moment it's powered down (takes a bit of practice).

I will include such a disabling command in the script at some point.

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
wicknest
(@wicknest)
Active Member
Joined: 2 years ago
 

I was able to restart my Mac and get it to display "Nvidia gtx 1070" instead of "(null)". However, I still have the same issue with the eGPU not showing up in the graphics section of "about this Mac", even though I have "use Nvidia web driver selected". Is it still being used but it just doesn't display?

Edit: just read your previous response. It randomly went to black screen after acting normally. Just going to restart and not worry about that. In response, you're saying to only unplug and plug in the eGPU when it's powered down?

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

@wicknest
The internal monitor won't be accelerated by an eGPU. Only external ones or apps on the internal if the app dev has explicitly coded that into the app.

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)


ikir liked
ReplyQuote
bellman
(@bellman)
New Member
Joined: 2 years ago
 

@fr34k great turn around 🙂 thanks for being available for this. New behaviour:

first run: installed t82, then restart

second run: connected egpu then prompted to disconnect, installed NVIDIA drivers and enabler, then restart

state: experiencing "null" issue in tray icon, but otherwise can detect the gpu!  https://imgur.com/a/KWnsxBM

Thanks again for your help, I'll let you know if any other odd things come up.

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


fr34k liked
ReplyQuote
SiliconRane
(@siliconrane)
New Member
Joined: 2 years ago
 

Good Evening @fr34k

Been lurking for a while, decided to write and post up either success or failure with this script. I am downloading 10.13.4 atm and will follow your instructions diligently. 
System Configuration:
MacBook Pro (15-inch, 2016)
Processor: 2.9GHz Intel Core i7
Memory: 16GB
Graphics (Native): Intel HD Graphics 530 / Radeon Pro 460
eGPU Enclosure: Akitio Node (TB 3) - Modified with a Corsair SF600 PSU and Noctua Fans. 
eGPU Card: NVIDIA GeForce GTX 1080ti. (No base overclock)
Monitor Attached to eGPU: Dell U3818DW via Display Port Connector. 

Update:
After installing 10.13.4 (17E202), running your script, with default commands and restarting I have the following:


Startup with with eGPU connected:
 semi-normal startup with the usual graphics glitches during startup. After startup desktop appears normal and basic applications function. 
Graphics Switching is set to automatic at this point.
Internal display is driven by Intel GPU and the External Display is driven by the NVIDIA eGPU. 
Disabling automatic graphics switching causes severe input lag and the internal screen goes blank. Checking the box to re-enable automatic graphics switching rectifies this issue. 
Any application that requires the system to switch from using the Intel GPU to the AMD dGPU causes severe input lag and the internal screen goes blank. This has been tested on MetalBench, Valley, World of Warcraft, Tomb Raider, etc. . . (METAL, OPENCL, OPENGL)

Here is a snapshot of what the Console is spitting out: 

 

default 21:42:54.559688 -0400 kernel kPEEnableScreen 1
default 21:42:54.614182 -0400 WindowServer [WARN] - Attempting to get 3-channel linearization table capabilities from plane with no 3-channel linearization table support
fault 21:42:54.715345 -0400 kernel AMDRadeonAccelerator: IOAccelDisplayPipeTransaction time out after 100ms. framebufferIndex=0
fault 21:42:54.715352 -0400 kernel framebufferIndex=0, wsaa=0
fault 21:42:54.715354 -0400 kernel eventInterruptEnabled=0, transactionInterruptEnabled=1, vblInterruptEnabled=0
fault 21:42:54.715355 -0400 kernel powerOff=0, pipeTerminated=0, acceleratorEnabled=1, fWSAA=0
fault 21:42:54.715357 -0400 kernel lastIOGraphicsMessageEvent=81, fbIndex=0
fault 21:42:54.715358 -0400 kernel transactionQueueReadCount=162, transactionQueueWriteCount=163
fault 21:42:54.715360 -0400 kernel lastCompletedTransaction: ID=161 dirtyBits=0x1 options=0x1
fault 21:42:54.715414 -0400 kernel pendingTransaction ID=162, isTransactionComplete()=0, dirtyBits=0x2c0, options=0x1, errorCode=0x0, submittedReturn=0xe0014042
fault 21:42:54.715418 -0400 kernel readTransaction ID=163, dirtyBits=0x1, options=0x0, errorCode=0x0, submittedReturn=0xe0014042, event is finished
default 21:42:56.575335 -0400 kernel --> IOP: FB:0 has been busy for 121 cycles with 0x30 transactions, busy? 0.
default 21:42:56.653311 -0400 kernel AGC:: [pid:196] Sending Event: 1:0
default 21:42:56.653321 -0400 kernel AGC:: WS SETUP: 0
default 21:42:56.656857 -0400 kernel AGC:: Switch completed, PEG active
default 21:42:56.671304 -0400 sharingd Display changed (ID: 0x4280C42, added: YES, removed: NO)
default 21:42:56.671390 -0400 sharingd Display changed (ID: 0x7BD7F3BD, added: NO, removed: YES)
default 21:42:56.684430 -0400 kernel kPEDisableScreen 1
default 21:42:56.684792 -0400 kernel [key:0x100/on:0] fPSREnablekeys: 0x00000bdf -> 0x00000adf (fullset:0x00000fff)
default 21:42:56.689396 -0400 ARDAgent event ref 0x0
default 21:42:56.701786 -0400 WindowServer [WARN] - Attempting to get 3-channel linearization table capabilities from plane with no 3-channel linearization table support
default 21:42:56.704510 -0400 kernel FB0 Conection status change: Connected --> Disconnected
default 21:42:56.708496 -0400 kernel kPEEnableScreen 1
default 21:42:56.785075 -0400 MirrorDisplays -[DisplaysDFRController _displaysChanged:] NSConcreteNotification 0x7fa0405289a0 {name = com.apple.mpf.displaysChanged; object = <MPDisplayMgr: 0x7fa040522fa0>}
default 21:42:56.785150 -0400 MirrorDisplays hasProjector
fault 21:42:56.824773 -0400 kernel AMDRadeonAccelerator: IOAccelDisplayPipeTransaction time out after 100ms. framebufferIndex=0
fault 21:42:56.824779 -0400 kernel framebufferIndex=0, wsaa=0
fault 21:42:56.824782 -0400 kernel eventInterruptEnabled=0, transactionInterruptEnabled=1, vblInterruptEnabled=0
fault 21:42:56.824783 -0400 kernel powerOff=0, pipeTerminated=0, acceleratorEnabled=1, fWSAA=0
fault 21:42:56.824785 -0400 kernel lastIOGraphicsMessageEvent=81, fbIndex=0
fault 21:42:56.824786 -0400 kernel transactionQueueReadCount=164, transactionQueueWriteCount=165
fault 21:42:56.824787 -0400 kernel lastCompletedTransaction: ID=163 dirtyBits=0x1 options=0x0
fault 21:42:56.824832 -0400 kernel pendingTransaction ID=164, isTransactionComplete()=0, dirtyBits=0x2c1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042
fault 21:42:56.824834 -0400 kernel readTransaction ID=165, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042, event is finished
default 21:42:56.882514 -0400 WindowServer Surface testing disallowed updates for 10 sequential attempts...
default 21:42:57.025744 -0400 kernel AGC:: mux-regs 5 3 5f 1f 0 8 severity 0 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:1f power-state 0 3D idle HDA idle : AGC Dump State Timer
default 21:42:57.655275 -0400 kernel AGC:: WindowServer started pid 196 WS count 3
default 21:42:57.655304 -0400 kernel AGC:: [WindowServer pid:196 mux-aware] starting, non-mux-aware app count 0 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:1f power-state 0 3D idle HDA idle
default 21:42:57.655334 -0400 kernel AGC:: [WindowServer pid 196 mux-aware] exiting, non-mux-aware app count 0, runtime: 0:00:00.000
default 21:42:57.655337 -0400 kernel AGC:: WindowServer died pid 196 WS count 2
default 21:42:58.675347 -0400 kernel --> IOP: FB:0 has been busy for 121 cycles with 0x31 transactions, busy? 0.
default 21:42:58.676332 -0400 WindowServer Surface test allowed updates after 388 attempts (1552 ms)
default 21:42:58.771445 -0400 WindowServer Surface testing disallowed updates for 10 sequential attempts...
fault 21:42:58.775599 -0400 kernel AMDRadeonAccelerator: IOAccelDisplayPipeTransaction time out after 100ms. framebufferIndex=0
fault 21:42:58.775605 -0400 kernel framebufferIndex=0, wsaa=0
fault 21:42:58.775607 -0400 kernel eventInterruptEnabled=0, transactionInterruptEnabled=1, vblInterruptEnabled=0
fault 21:42:58.775608 -0400 kernel powerOff=0, pipeTerminated=0, acceleratorEnabled=1, fWSAA=0
fault 21:42:58.775609 -0400 kernel lastIOGraphicsMessageEvent=81, fbIndex=0
fault 21:42:58.775610 -0400 kernel transactionQueueReadCount=165, transactionQueueWriteCount=166
fault 21:42:58.775612 -0400 kernel lastCompletedTransaction: ID=164 dirtyBits=0x2c1 options=0x1
fault 21:42:58.775618 -0400 kernel pendingTransaction ID=165, isTransactionComplete()=0, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042
fault 21:42:58.775621 -0400 kernel readTransaction ID=166, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042, event is finished

Hot plugging the eGPU has a similar effect where the internal display continues to function, the eGPU is detected with the external display turned off. Turning off the external display disconnects it from the system and the internal desktop is switched back to a single screen with the eGPU being detected. Turning on the external display again leads to the same situation as before with a blank screen and the Mac switching to extended desktop mode. Logging out under these situations results in a Kernel Panic and subsequent restart. 

Logging out and connecting the eGPU - Testing Now. Will Update Shortly.

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

@bellman
süperb!

I've explained a few lines about the null issue in the posts above.

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
(@gregor_zimmermann)
Active Member
Joined: 2 years ago
 

Thank you @fr34k!

I got it to work on my MacBook Pro Mid 2014, MacOS 10.13.4 
The only minor issue I have is, that my Mac crashes everytime,
I try to use the "Disconnect"-Button that appears in the status 
bar.

Screen Shot 2018 05 06 at 12.58.31 AM
Screen Shot 2018 05 06 at 12.57.55 AM
Screen Shot 2018 05 06 at 12.57.23 AM

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


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

@wicknest
No hot plug is OK (works best in most cases). For some configs you need to hot plug then logout to get the eM (external Monitor) to work.
But hot un-plug is not. -> This panics, just as the disconnect button in the system tray.

Unplugging only when powered down. Plugging in can be done while being logged in.

EDIT: I will update the README and the initial post with more info about everything tomorrow.


@gregor_zimmermann
Known, is being researched.

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
(@gregor_zimmermann)
Active Member
Joined: 2 years ago
 

Thank you for the super fast answer @fr34k, one more tiny side note - I can't use the brightness buttons anymore.
Guess I have to use a 3rd party tool for this for the time being... 🙂

EDIT: Sleep (closing the lid) and then reopening the lid results in a black internal screen - eGPU not connected. 

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


fr34k liked
ReplyQuote
ICULikeMac
(@iculikemac)
Estimable Member
Joined: 2 years ago
 

Hi all,

Firstly thanks fr34k, that update for CUDA worked perfectly, cheers however I still cannot get my external monitor to work at all!

Is anyone else still having problems getting their eM to work? 

I've tried:

1. Start - hot plug (just eGPU) 15 sec - plug in DP cable - black eM however on built in display can see 1070 showing up for eM but its just black/grey
2. Start- login - hot plug - dp cable - logout - still black eM
3. Start - hot plug - plug in dp - restart - same issue. 

Any other ideas that have worked for others? 

Cheers all.

2019 13" MacBook Pro (i7 & 16GB RAM) - MacOS + Win10
Late 2012 Mac Mini - MacOS + Win10
Asus XG Station Pro (RX570 8GB + RTX 2080)


ReplyQuote
(@donald_martin)
New Member
Joined: 2 years ago
 

@mardarethedog What monitor do you use for the 1080TI? Also, try running GPUsniffer before using Premiere Pro. Right click Premiere Pro - "Show Package Contents".

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


ReplyQuote
Robert Avram
(@robert_avram)
Active Member
Joined: 2 years ago
 

@fr34k
Thank you for the suggestions. I got it working on my headless HDMI eGPU setup.
I need a headless HDMI in the HDMI port of my eGPU because I want to mirror that screen onto my LG 5K UltraFine display. The latter is a THUNDERBOLT display and cannot go driectly in the EGPU. The Headless HDMI + Mirroring is the only solution I found to accelerate the images on my LG 5k Ultrafine.

Here's what I did

1) Logged in, no EGPU, NO 5K ULTRAFINE, NO HEADLESS HDMI
2) Hot-plugged eGPU - Icon appear in status bar
3) Logged out
4) Plugged the Headless HDMI in the eGPU
5) Plugged LG 5k Ultrafine display on the 2nd right sided TB3 port.
6) Closed my MBP dedicated display to only have LG UltraFine active.
7) Logged in and set the LG Ultrafine 5K display to mirror my headless HDMI display on the eGPU
8) Success!

If I hot-plug the eGPU with a headless HDMI while logged in, I get a black screen with my mouse, on the internal display OR the LG Ultrafine display.

However, if I log out and do everything mentioned before, it works as in 10.13.3.

Thanks a lot!

I attached my setup

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


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 2 years ago
 

Outstanding! I've been using the previous wrangler substitution in the prior version of 10.13.4. I've decided to clone my working system and test  @fr34k script. Everything went just smoothly, perfect! I've had the latest Nvidia Driver and Cuda installed. The script replaced everything for the right choice (noticed that it downgraded the Nvidia Driver back to xxx.103 version). After the reboot things work pretty much as they worked in 10.13.3. We do not have all the functionality advertised by Apple, such as hot plug and unplug, but all the hardware seems to be used just fine, at least by some of the apps that justified my eGPU's acquisition. 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. I've testes to connect the externals to N4 and N5 and, in this case, I got a black screen and have to force restart. 
I sure hope that  @fr34 and the other talented guys working on this can improve things to put it on pair with Apple's solution for TB3 machines/AMD's. The least that Apple and Nvidia should do was to pay you guys a lot for all this effort. I'll surely contribute with  a small Paypal donation once the script is finished.

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


goalque and fr34k liked
ReplyQuote
wicknest
(@wicknest)
Active Member
Joined: 2 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.

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


ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 2 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: 2 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: 3 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
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


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: 2 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: 2 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: 2 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
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)
Eminent Member
Joined: 2 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 TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 2 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: 3 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
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
 of  21