That's good, everything is ok. What macOS build number? Get an external monitor or:
https://egpu.io/forums/mac-setup/potentially-accelerate-all-applications-on-egpu-macos-10-13-4/
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]
I am on MacBook Pro 2018 with TB3. May be that's the difference?
Maybe, TB1/TB2 patches are not applied in the config.plist. Maybe they are now necessary. Can anyone confirm TB2 Mac + Nvidia eGPU? Working or not?
I could not get your script to work, if you see my above earlier post.
3D Cinema 4D/Octane Artist
Gigabyte Aorus GTX 1080 Gaming Box w/ TB2to3 Adapter
2013 Mac Pro
2014 MacBook Pro
@natemac00 I wasn't sure what did you mean by "some update I accidentally clicked on yesterday". The security update?
I suppose this can be fixed by editing the config.plist, add TB1/TB2 patches.
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]
@natemac00 I wasn't sure what did you mean by "some update I accidentally clicked on yesterday". The security update?
I suppose this can be fixed by editing the config.plist, add TB1/TB2 patches.
I'm guessing it was the security update cause it didn't change the 10.13.6 part.
3D Cinema 4D/Octane Artist
Gigabyte Aorus GTX 1080 Gaming Box w/ TB2to3 Adapter
2013 Mac Pro
2014 MacBook Pro
I recall reading somewhere that booting into a recovery partition may resolve some firmware kinks. For those facing issues with automate-eGPU EFI consider trying to boot into recovery, and from there choose your startup disk and boot normally. Then retry the USB with the app. More debugging options could be SMC/NVRAM resets.
purge-wrangler ✧ tbt-flash ✧ purge-nvda ✧ set-eGPU
Insights Into macOS Video Editing Performance
Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]
@goalgue I'm on Mojave 10.14, should i downgrade to High Sierra to use set-eGPU.sh ?
"Note: Mojave has this built-in now. As of this time, the new OS does not respect plist settings for some reason."
I want to use my Aourus GTX 1070 Gaming box for Octane renderer, is that even possible ?
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.@goalgue I'm on Mojave 10.14, should i downgrade to High Sierra to use set-eGPU.sh ?
"Note: Mojave has this built-in now. As of this time, the new OS does not respect plist settings for some reason."I want to use my Aourus GTX 1070 Gaming box for Octane renderer, is that even possible ?
Nvidia web drivers don’t exist for Mojave.
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]
Ok thanks for the fast answer @goalque, I will downgrade to 10.13 and try again.
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.A really nice feature of @goalque's EFI Boot Manager is the
deactivation of dGPUactivation of iGPU for 15" MacBook Pro in both macOS and Windows. I accidentally left the PCI Express Controller 1901 [to Radeon 450 dGPU] disabled when booted into macOS. Prior to using this EFI boot manager, next boot into Windows partition would result in a stuck Windows logo boot screen. Well this time the boot manager assisted Windows to use the iGPU for the internal display. All was working great.In one of my progress updates, I mentioned storing the precompiled dsdt.aml file on this boot loader could provide Large Memory allocation in Boot Camp. My 2016 15" MacBook Pro is now effectively working in Windows as a iGPU-only Thunderbolt 3 laptop. The only non-working functionality is brightness adjustment. Large memory allocation helps me resolve error 12 with both Nvidia and AMD eGPU. I was actually able run two AMD RX 580 eGPUs once I disabled one of the PCIe Controllers to TB3 ports. Truly amazing work by @goalque!
Goalque's Tool is amazing, but not absolutely necessary for Bootcamp. By deactivating all drivers before plugging the eGPU I could get Windows to run solely on eGPU, no patch whatever necessary. Ok, I can't change the resolution one the internal display (run officially by Microsoft Basic Device Driver), but I don't really care.
PS: If I use the Efi-Bootdriver to boot my windows I get error 43....Of course for the unlocking of nVidia in macOsx this is a must. Shame on apple and its politics.
2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680
2018 15" MacBook Pro (RP560X) [8th,6C,H] + RX 5700 XT @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 & macOS 10.15.4 // Navi vs Radeon VII vs GTX 1080 Ti [build link]
Error 43 is usually driver/power related, when I tried the EFI bootloader Windows booted was if it was a fresh instal in a way and it had to re recognise all my peripherals and I had error 43 too until I reinstalled drivers.
2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10
---
LG 5K Ultrafine flickering issue fix
2018 Mac Mini [8th,6C,B] + RX 580 @ 32Gbps-TB3 (AKiTiO Node Lite) + Win10 20H2 [build link]