I got some progress here!
My System is now at 10.13.4 with security update working almost flawlessly except for one tiny detail.
I got It running by running the script in phases.
It seems that the default NVidia driver version that the script installs for my setup, paired with the EGPU Enabler is not compatible even with the discreet GPU. So I gave a try and reproduced the script's default behaviour and used the options flags to do a semi-custom installation. Here's what I did:
- ran the script selecting the same driver version present in my 10.13.3 working environment by passing "--install --nvidiaDriver 378.10.10.10.25.104". Script rebooted by the end;
- without anything plugged in, as recommended in the original post, ran the script passing "--unlockNvidia --nvidiaEGPUsupport --unlockThunderboltV12"
- after script rebooted, I shutdown the MBP, plugged in the EGPU and eM, and started It again. BAM! Works flawlessly. OpenGL, Metal acceleration OK, tested in Heroes of the Storm, World of Warcraft and Rise of the Tomb Raider. The "Disconnect Nvidia GEForce GTX 970" Icon works like a charm. Hot Pluggin in, gives me Black screen on External monitor, but a Reboot solves the issue.
Conclusion:
Maybe there's some detail in the default behaviour of the script for this setup that is missing or in the wrong order? I dont know... I hope this information helps you to enhance It.
The only thing that is not working is that the Audio port in my Lenovo Y27F Monitor is not beign detected in MACOS, only Windows.
Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970
This is quite big news. Interesting that an older driver works so much better.
"The Disconnect Nvidia GEForce GTX 970" Icon works like a charm?
No kernel panic?
automate-eGPU EFI ● apple_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]
This is quite big news. Interesting that an older driver works so much better.
"The Disconnect Nvidia GEForce GTX 970" Icon works like a charm?
No kernel panic?
No Kernel Panics. The Programs using the eGPU close and the Internal screen becomes the main screen (wallpaper that was on eM went to the Internal)
Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970
No Kernel Panics. The Programs using the eGPU close and the Internal screen becomes the main screen (wallpaper that was on eM went to the Internal)
So you are the second. My Mid 2015 behaves the same way and I am also using an older driver (387.10.10.30.103), not that old as you. How about hot-unplug?
automate-eGPU EFI ● apple_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]
No Kernel Panics. The Programs using the eGPU close and the Internal screen becomes the main screen (wallpaper that was on eM went to the Internal)
So you are the second. My Mid 2015 behaves the same way and I am also using an older driver (387.10.10.30.103), not that old as you. How about hot-unplug?
Hot unplug gives Kernel Panic. No luck there. But I think It's way too much to expect from using such an old driver (It's a 378 driver!). I'm not sure which of .104 or .106 have a better performance on 10.13.3. I will try 106 now. Cause my first try I went right back to .104.
Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970
@leoleal You are the champ ... I followed your steps, and I can confirm now that my external monitor is working as well now!
When I do hot-plug it as usual the black screen, but log-out login and it work ... Also I can confirm that the disconnect icon work well ... It will close the application and deactivate eM ... no kernel-panic ... however when I unplug the cable after disconnect I will get kernel panic.
Hot unplug gives Kernel Panic. No luck there. But I think It's way too much to expect from using such an old driver (It's a 378 driver!). The .104 or .106 have a better performance on 10.13.3. I will try them now. Cause my first try I went right back to .103.
This is very expected. Apple's documentation says that drivers need to be updated in order to handle surprise removal. We will try to find a workaround.
automate-eGPU EFI ● apple_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]
Hot unplug gives Kernel Panic. No luck there. But I think It's way too much to expect from using such an old driver (It's a 378 driver!). The .104 or .106 have a better performance on 10.13.3. I will try them now. Cause my first try I went right back to .103.
This is very expected. Apple's documentation says that drivers need to be updated in order to handle surprise removal. We will try to find a workaround.
Good luck, man! I wish I had more Driver Programming knowledge to help more...
And thank you for the solution. If you need testing, hook me up! I have a couple of states of the OS backed up in Time machine.
Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970
I'd just like to second that @LeoLeal steps at least got OpenGL back working for me. Not sure whether it was doing it in a 2-step sequence, or just using the old nVidia driver. But I followed his steps, uninstalling the script, then installing the 10.25.104 driver, then rebooting and installing the rest of the eGPU enabler stuff, and I am back running in 10.3.4 again. The Heaven benchmark works again on the eGPU.
However, disconnecting still causes a kernel panic (it looks like it's going to work, but then it panics. I wonder if it's because of dropbox, as I get a screen saying that is preventing the disconnect, but then it panics before I can force close it).
Hot plugging and logging out/in doesn't work. Deus Ex Mankind Divided still doesn't work - but it never has under any iteration of drivers or enablers in 10.3.x unfortunately. I don't still have Hitman installed to test, and don't have Tomb Raider yet, but will check that at some point.
The other problems that still exist are those that have existed since 10.3.x - no brightness controls, the dGPU is always active instead of the iGPU (which impacts battery life), etc. I haven't tested the internal screen waking from sleep yet, but I imagine that will still be a problem.
I'd just like to second that @LeoLeal steps at least got OpenGL back working for me. Not sure whether it was doing it in a 2-step sequence, or just using the old nVidia driver. But I followed his steps, uninstalling the script, then installing the 10.25.104 driver, then rebooting and installing the rest of the eGPU enabler stuff, and I am back running in 10.3.4 again. The Heaven benchmark works again on the eGPU.
However, disconnecting still causes a kernel panic (it looks like it's going to work, but then it panics. I wonder if it's because of dropbox, as I get a screen saying that is preventing the disconnect, but then it panics before I can force close it).
Hot plugging and logging out/in doesn't work. Deus Ex Mankind Divided still doesn't work - but it never has under any iteration of drivers or enablers in 10.3.x unfortunately. I don't still have Hitman installed to test, and don't have Tomb Raider yet, but will check that at some point.
The other problems that still exist are those that have existed since 10.3.x - no brightness controls, the dGPU is always active instead of the iGPU (which impacts battery life), etc. I haven't tested the internal screen waking from sleep yet, but I imagine that will still be a problem.
Rise of the Tomb Raider has subpar performance. I believe that is because It's made FOR 10.13.4, so I tend to believe also that the game uses Metal 2 API, and Nvidia driver 378 does not have Metal 2 Implementation.
Maybe we have to wait NVidia to release a version that works with EGPU properly.
Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970