I made this for my own use but others might find it useful. Basically it's Clover with apple_set_os.efi feature included so you can boot directly into windows with the error 12 fix + iGPU enabled. Follow Mikeal's guide along with the attached Clover build. The included config.plist is set to boot automatically (no delay/GUI) a partition named "EFI" (Windows' default name). What I did is just place the dsdt.aml file into Windows' EFI partition on my external HDD so it boots directly. I've submitted a pull-request to clover so hopefully this will make it into the mainline.
NVIDIAEGPUSupport - Nvidia eGPU support for macOS High Sierra
Clover-DSDT+apple_set_os.efi - Macbook Pro Windows error 12 & iGPU fixed Bootloader
---
late-2016 13" MacBook Pro Touchbar + [email protected] (HP OMEN Accelerator) + macOS10.13 & Win10
2016 13" MacBook Pro [6th,2C,U] + GTX 1060 @ 16Gbps-TB3 (HP OMEN Accelerator) + macOS 10.13 & Win10 [build link]
@yifanlu, good work with the intergration.
I wanted to alert you about a detractor in using apple_set_os.efi. We've had several reports that booting via apple_set_os.efi results in a lowered CUDA-Z/AIDA64 host-to-device result in Windows. See report at https://egpu.io/forums/mac-setup/how-to-keep-mbps-irisiris-pro-activated-when-booting-into-windows-boot-camp/paged/6/#post-22513
Any workarounds that you can suggest or look out for?
eGPU Setup 1.35 • eGPU Port Bandwidth Reference Table
2015 15" Dell Precision 7510 (Q M1000M) [6th,4C,H] + GTX 1080 Ti @32Gbps-M2 (ADT-Link R43SG) + Win10 1803 [build link]
Interesting, I didn't know about the reduced performance. If I have to guess I would say this doesn't solve that problem as it runs the same code as apple_set_os.efi. The only thing this does is hide the boot menu so you can select your windows EFI partition and boot directly into windows quickly. I don't have an internal bootcamp setup so I can't test hot plugging.
NVIDIAEGPUSupport - Nvidia eGPU support for macOS High Sierra
Clover-DSDT+apple_set_os.efi - Macbook Pro Windows error 12 & iGPU fixed Bootloader
---
late-2016 13" MacBook Pro Touchbar + [email protected] (HP OMEN Accelerator) + macOS10.13 & Win10
2016 13" MacBook Pro [6th,2C,U] + GTX 1060 @ 16Gbps-TB3 (HP OMEN Accelerator) + macOS 10.13 & Win10 [build link]
Someones making a splash... ;-D
I've had issues when booting using apple_set_os.efi - Windows didn't recognise my 5K display last time I tried it, not sure if it makes a difference, but I created an EFI folder on an external which I use for storage alone.
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
2017 13" MacBook Pro [7th,2C,U] + RX 5700 XT @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.15.4 & Win10 2004 [build link]
After install Nvidia driver and reboot, I have infinite loading screen on Windows 10.
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.
Quick question: Does using the clover bootloader via a USB drive (apple_set_os.efi instructions) on a real mac come with the possibility of bricking the system (the mac firmware)? If yes, then is there a guaranteed non-brickable solution to use this bootloader? Note that I do not want to do a DSDT override. I do not have any understanding of the system at such a privilege level and how its associated with mac firmware, so apologies for the lack of context here.
From what I've read generally, direct installations on mac have bricked some macs, requiring flashing a chip on the logic board if one can find an EFI dump for one's mac.
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]