automate-eGPU EFI - eGPU boot manager for macOS and Windows  

@ozzy the purge-nvda patches (or part of them) affect boot quite early on (before POST). This would be MuxSetting=1 for this app. Specifically, to ensure boot is on iGPU, a previously applied NVRAM command (on last boot) takes effect on the next boot (in some cases this doesn’t happen, so it needs to be reapplied). Hence the EFI app might sometimes be late when applying that. You can refer to the command line link in my signature for the NVRAM command(s) relevant, or for more clarity, purge-nvda source. We have discussed MuxSetting=1 vs. applying the NVRAM command on prior boot and IIRC both managed to disable switching to the dGPU (though I have had more luck more often with directly applying NVRAM when I had the 2014 MBP). So the only addition needed would be a boot-arg to disable NVIDIA cards (should be in command line link). End result however, is that NVRAM values will persist across boots so you aren’t getting the dynamic experience EFI offers (booting with it = patched, booting without it = remnant effects of NVRAM values), so you might as well combine using EFI + purge-nvda (so you have an easy way to uninstall the NVRAM changes appropriately). Note that I haven’t personally tried these modifications to the EFI app or combined EFI + purge-nvda before, but logically it should work. 

@Mac_editor Thanks for the detail, super helpful and now I understand a bit more what it's doing. I'll just combine the purge_nvda and EFI elements together like you suggested, and then if I want to use the laptop on the go or use sleep I'll just disable the purge_nvda bit.

@ozzy For Windows, my experience on the 2014 was easy. But this guide states you might have some work to do (for AMD eGPU). Instead of the optional Clover recommendation there, you can use this EFI app to accomplish the same.

@mac_editor Yea, I saw both your and that build guide. My windows install is definitely in MBR not UEFI mode. I’m hopeful I won’t have to go through all of that and re-install Windows though, since I already have  nando’s DIY eGPU 1.35 tool up and running. I’ve been using that for the last 2 years to get my nVidia 1070 to work in Windows. I’m hopeful I can keep using it as is but with the AMD eGPU. I emailed Nando to ask, but will also test it out once the new card comes in.

I’m also compiling a bunch of benchmarks at the moment since I think it will make for some interesting comparisons. Will be able to test 1070 vs. Vega 56 in Windows, 10.3.6, and 10.14.4 (Vega only). Will also be able to see the difference between the 2012 MBP 15” (thunderbolt 1) with the Vega 56 in 10.14.4 and the 2018 13” MBP (4 thunderbolt 3 ports) with he Vega 56 in 10.14.4

So I just got a GT710 to mess around with. It works in macOS using purge-wrangler just fine, but if I uninstall purge-wrangler and then try to use the EFI to get it working it crashes and restarts about halfway into booting. Has anyone else had an issue using the EFI to get these old Kepler cards working?

@nu_ninja In the config.plist, try deleting the parameter NvidiaWeb under SystemParameters. Let me know how it goes.

@mac_editor

Turns out it was just my flash drive deciding to die today. Got it working now. No changes to the plist required

Hi everyone,

First of all thanks everybody for the great work here to make eGPUs working!

I have an issue booting my Windows 10 installation. Mac OS boots fine. However, one I choose the Windows option, it only flashes "Saving" on the bottom for a moment and then reverts to "Ready" and stays there. The activity LED of the thumb drive is flashing for some time after that, but it stops after 10-15 sec and nothing more is happening. My Windows installation is on a separated USB-C SSD and not on the internal drive. Could that be an issue?

Thanks in advance for any help.

Thanks for this!

I'm on a 2013 15" Macbook Pro (High Sierra 10.13.6) that's connected to a Aorus box, currently with a GTX 1060 inside.

After creating the EFI boot USB and doing all the steps, including plugging in the eGPU which lights up etc., installing NVIDIA web drivers (387.10.10.40.124) the system seems to see the GPU but only as "NVIDIA Chip Model". 

Am I missing something? Is the internal dGPU still throwing it off and needs purge-wrangler?

Thanks for any hints--Sascha

Got the AMD Vega 56 installed. I installed purge-nvda and then rebooted in 10.13.6 using the EFI boot USB stick and it worked perfectly right out of the gate. Did some benchmarking and now installing 10.14.4. Windows however I haven't been able to get anywhere yet - just blank internal and external screens with the eGPU connected. Can't even get the DIY eGPU tool to load. I emailed Nando to get his thoughts on it.

Benchmarks comparing 1070 to Vega 56 in 10.13.6 are quite interesting. I'll post the full details after I do much more in 10.14.4, with my 2018 13" MBP, etc. But for starters here are the results in the direct 10.13.6 comparisons on the same computer:

• Deus Ex: Mankind Divided Very High settings - Vega 56 60% faster than 1070 in both 1440p and 1080p (35.9 FPS in 1440p)
• Rise of the Tomb Raider Very High settings - Vega 56 38% faster than 1070 in both 1440p and 1080p (57.5 FPS in 1440p)
• Total War Warhammer 1 High settings - Vega 56 35% faster than 1070 in 1080p (my 1440p 1070 baseline was lost) (46.7 FPS in 1440p)
• Heaven benchmark Ultra settings - Vega 56 18% slower in 1440p and 21% slower in 1080p than 1070 (34.4 FPS in 1440p)

Seems like the drivers for AMD make a huge difference in 10.13.6. Will see how much faster they get in 10.14.4. Interestingly, at 1440p the 10.13.6 FPS numbers for the Vega 56 match or beat the Windows 10 FPS numbers with the 1070. Deus Ex is basically even and TW: Warhammer and RotTR the Vega OS 10.13.6 combo wins by a fairly substantial amount over Windows 10 with the 1070.

@ozzy
it's very interesting that in MacOSX the Vega56 is much better than in Windows. I don't think it would outperform a GTX1070 in this way (60%, 38%, 35%...)

You are saying you cannot get it run in Bootcamp at all? Which MacBook model are you referring?

@ozzy A nice set of Metal API games! 🙂

@emanuelediba got it working with a Mid 2012 15" MBP on Windows:

https://egpu.io/forums/mac-setup/automate-egpu-efi-egpu-boot-manager-for-macos-and-windows/paged/18/#post-56145

@ozzy Nice benches! Do you happen to have Dirt Rally as well? Could be another good game to benchmark (it has a built in one).

Posted by: goalque

@ozzy A nice set of Metal API games! 🙂

Yes! I am still owing some Metal benchmarks, too, but I have do admit that the only Metal-MacOSX benchmark I have is gfxMetal, which is a little thin....Looks though as the Vega56 had a clear edge, which is nice.

Posted by: ozzy

• Deus Ex: Mankind Divided Very High settings - Vega 56 60% faster than 1070 in both 1440p and 1080p (35.9 FPS in 1440p)
• Rise of the Tomb Raider Very High settings - Vega 56 38% faster than 1070 in both 1440p and 1080p (57.5 FPS in 1440p)

@ozzy

Could you please post the exact settings and FPS of those benchmarks? With AA and all details? Preferably in 1440p, but 1080p is great, too. You have them only for MacOSX, haven't you? It would be great if you could setup Windows, too and get those benchmarks, too. 

This would be one of the greatest contribution. Thank you in advance!

(PS: Vega56 60% faster than a GTX1070, most impressive, on eGPU-Windows every GPU is doing very bad in Deus Ex: Mankind Divided, this includes a GTX1080 Ti and even worse: Radeon VII)
(PPS: I have a lot of cards and can "cross-test" both games, which are two of my favorite testing games in Bootcamp, this could become most interesting).

@goalque Thanks for that link. That's the second person that got Windows to work with AMD on this laptop model that I've seen (@Mac_editor linked to the other). The difference is both of them had Windows installed manually in UEFI mode vs. the MBR mode I'm in from the bootcamp assistant. If I can't get it to work in a couple more days with Nando's help, then I'll go that route.

@mac_editor I don't have any of the Dirt games unfortunately. I do have a bunch more games I could test and would be happy to if desired, but not that one.

@OliverB I'll upload all the results when I finish them across computers. To clarify what I said earlier, on the same computer and same OS 10.13.6, the Vega 56 was significantly faster than the 1070 in all but Heaven. That's likely due to Metal drivers being much better for AMD. Seperately, on that same computer the Vega 56 was faster (not significantly, but somewhat) in some games on 10.13.6 than the same games in Windows 10 with the 1070. I haven't gotten Windows working yet with the Vega 56 so can't quite compare that, but working on it.

PS - it appears the AKiTiO Node PSU isn't quite good enough in some cases. I haven't had any problems in games at all, but it has shut off twice now while running the Heaven benchmark :(. I'll keep an eye on it and maybe need to under-volt.

@ozzy,

I was once making a big set of benchmarks comparing a Vega56 and my EVGA GTX1080Ti in Windows and in MacOSX.
The result was most interesting, because in Windows the Vega56 got humiliated beyond belief while in MacOSX having been a real competitor.  Unfortunately I didn't have such big Metal titles in MacOSX, so I am expecting your results with great joy.

If you bought from Steam, you also have the Windows version. Would be interesting to know if Metal can beat DX11 or DX12:

https://egpu.io/forums/mac-setup/metal-api-shines-rx-480-reaches-60fps-on-macos-10-12-4-fhd-ultra-high-settings/

It's been two years and I haven't seen anyone else posting Metal game benches until now. Always those same Valley screenshots. Gaming on macOS is not that bad.

@goalque you are absolutely right. Using Valley/Heaven benchmarks for comparing nVidia with AMD is not really fair. I still don't know if this "bias" was deliberate... with Superstition it is not that bad.

EDIT: Superposition, haha

Yea, I've got the Windows versions of everything and have direct comparisons on the 1070. Until I get Windows working on my 2012 15" MBP I won't be able to post the Vega 56 direct Mac vs. Windows comparisons though.

I'll also have 2018 13" MBP to 2012 15" MBP comparisons that will highlight some of the TB1 vs. TB3 differences (processors are obviously different too, but they are at least both quad-core). Sadly my 2018 13" MBP is a work one that I can't do bootcamp on, so no Windows benchmarks from it, only from the 2012 15" MBP.

It is amazing how plug and play eGPUs are in 10.14.4 with the 2018 13" MBP though. After a couple users of patches and drivers and complications it's kind of nice 🙂

I think most of the other games I could benchmark are all OpenGL unfortunately (Civ VI, Mad Max, Shadow of Mordor, all of the Borderlands games, Tomb Raider etc.). I could see if Hitman has a benchmark, I think that may have been Metal

Posted by: ozzy

I'll also have 2018 13" MBP to 2012 15" MBP comparisons that will highlight some of the TB1 vs. TB3 differences (processors are obviously different too, but they are at least both quad-core).

Actually the difference in CPU/RAM will play a big role in games, so this comparison will be difficult. I have two different MacBooks, too(TB2 vs TB3) and only synthetic benchmarks can be compared (unfortunately) cross-MacBooks. Best is Unigine Superposition, which stresses most GPU compared to CPU.

EDIT: If found my TB2 vs TB3 analysis here.

Looking forward to seeing these benchmarks... maybe some sort of pinned mega thread full of benchmarks might be good with a way for all users to submit their own?

I started documenting my results here:

https://www.notion.so/eightarmedpet/7460661cce3e4cc3b98fd2e24abe35f2?v=b97d67731f95457aa21d6d2f0deea233

Posted by: ozzy

@goalque Thanks for that link. That's the second person that got Windows to work with AMD on this laptop model that I've seen (@Mac_editor linked to the other). The difference is both of them had Windows installed manually in UEFI mode vs. the MBR mode I'm in from the bootcamp assistant. If I can't get it to work in a couple more days with Nando's help, then I'll go that route.

Newer AMD cards can't boot in BIOS mode. You need to install Windows 10 manually in UEFI. You will never get any output from the eGPU with Windows installed via Bootcamp Assistant 

You can also hotplug the eGPU in your 2012 MBP while using purge-wrangler 😉

@emanuelediba yea, nando confirmed that last night. Trying to reinstall windows in UEFI mode. For some reason the windows installation kept giving an error halfway through last night. I tried re downloading the iso image and will try again tonight or tomorrow and hope it works this time.

Did you convert the hybrid mbr to regular guid partion map?

This is something I had to do when switching to uefi mode on the 13" 2012 MacBook pro. I used gdisk in macos to do the partion map change

@nu_ninja No. I wiped out my existing bootcamp partition to return the Hard Drive to a single partition using the Boot Camp Assistant. I then created the Windows install USB using the Bootcamp Assistant. Then I used Disk Utility to format the hard drive and add an HFS+ partition. I rebooted off the USB, and in the windows setup instructions I deleted the HFS+ partition and then created a new partition with the unallocated space to install onto. It does the initial install ok, but then when it restarts and continues the installation it runs into an error and then gets caught in a restart loop.

When I next try I'm going to do three things differently:
1) disable the purge_nvda before installing in case the mux setting is causing any problem
2) use unetbootin to create the USB install rather than the bootcamp assistant
3) make sure all peripherals (including an external hard drive) are disconnected during the windows install

Hopefully this will work. Any other suggestions?

That might be fine, I would just check using gdisk to make sure you have a "protective" mbr and not a "hybrid" mbr

Posted by: nu_ninja

That might be fine, I would just check using gdisk to make sure you have a "protective" mbr and not a "hybrid" mbr

Thanks - will do

Took a bit more work than I expected, but I managed to get Windows installed in UEFI Mode. Not sure whether it was the disabling of purge-nvda, using UNetbootin, re-downloading ISO (I had to split parts of the ISO also because one of the files was too big for FAT32), or disconnecting peripherals/other hard drives that did it, but it works now. I also built a DSDT.aml file and put it in the automate-EFI USB stick and it works great.

I paid a lot of attention to the following sites:

• https://fgimian.github.io/blog/2016/03/12/installing-windows-10-on-a-mac-without-bootcamp/
• https://twocanoes.com/using-larger-windows-10-isos-with-boot-camp-assistant/
• https://egpu.io/forums/builds/mid-2012-15-macbook-pro-non-retina-rx58010gbps-tb1-gigabyte-gaming-box-via-tb3-to-tb1-adapter-macos10-13-4-win10-clarketus/
• https://egpu.io/forums/builds/2011-early-15-macbook-pro-hd6750m-gtx1050ti10gbps-tb1-sonnet-egfx-breakaway-box-350w-via-tb3-to-tb2-adapter-macos-win10-uefi-fsp/
• https://egpu.io/forums/pc-setup/fix-dsdt-override-to-correct-error-12/

The steps I followed were slightly different then shown in those guides though. In particular, I couldn't disable the intel drivers from installing/updating. It hasn't seemed to cause any problems for me though. I also haven't received any error 12 problems after doing the DSDT override, and therefore didn't need to do any PCI-to-PCI bridge disabling. 

Only two challenges at the moment:

• Seems like I have to boot twice in Windows to get the screens to load. The first time after the spinning load-up I just get black screens on both internal and external monitors. I have a cursor that I can move around, but nothing else. If I hard shut down with the power button and then turn back on it works the second time
• I seem to be tripping the PSU a bit more in Windows when benchmarking than I did in Mac OS. In one case I monitored the power draw and it never got above 180 W, which should be in easy range for the 400W PSU in the Akitio Node. Maybe I'll have to undervolt it a bit

I'll try running some of the same benchmarks in Windows to see the results.

@goalque @mac_editor @itsage Question to experts. The "boot efi black screen" problem was mentioned couple of times here (it wasn't easy to read through all 19 pages) but with no proposed solution, still I hope you can possibly recommend something here. In some case I cannot reach the very first screen of this automate-EGPU EFI (screen that asks you to push "q") on my Mac Mini 2014, instead I can only see blank black screen (tried to wait for 10min). In the same time with the very same USB stick I can see that screen when trying to boot on my MacBook Pro late 2013. I tried enabling debug.log but I can see no log created, apparently it cannot reach any meaningful stage. What can possibly be wrong with my Mac Mini? Maybe there is a way to get some details on why it fails?

Some details:
- both macs have Bootcamp (probably does not matter yet, but Windows 10 EFI)
- both running same 10.14.4 on APFS
- used mac_editor's script to format USB stick with AMD settings
- here is how folder structure looks like https://imgur.com/a/udNPUhH
- tried to load from both USB and small partition on main disk
- plist contents https://pastebin.com/6CAMP5xU
- SIP disabled
- no other workarounds applied
- never tried other bootloaders
- EGPU disconnected

PS: and actually my only goal is to solve "error 12" on Windows 10 but disabling/enabling PCI switches/roots does not seem to work for me. TESTSIGNING mode is not recommended and so far I wasn't able to make GPU to be allocated in "large memory" segment. All other ways to override DSDT.aml have warning that only sane way is to use automate-egpu efi.

Which partition is blessed as default boot volume? I never used a 2014 Mac mini with eGPU so I'm not sure if it's similar to the 2018 Mac mini regarding boot behavior. What I found most reliable is to hold OPTION at boot then select the EFI volume. I have also moved automate-eGPU EFI to a 24MB FAT partition on the internal drive. Give this a try a see if it helps.

@koskokos I had a 2014 Mac mini and its firmware was very sensitive to small changes in eGPU detection algorithm (which is far from perfect anyway). Unfortunately you can’t use this EFI on a 2014 Mac mini. I recall that Windows 10 should work without any hacks. Use Thunderbolt port closest to the USB ports.

Posted by: itsage

Which partition is blessed as default boot volume? I never used a 2014 Mac mini with eGPU so I'm not sure if it's similar to the 2018 Mac mini regarding boot behavior. What I found most reliable is to hold OPTION at boot then select the EFI volume. I have also moved automate-eGPU EFI to a 24MB FAT partition on the internal drive. Give this a try a see if it helps.

Thanks for the suggestion, at most recent attempt I'm using 200MB FAT partition instead of USB stick and APFS macOS partition set as startup one. Anyway it probably doesn't matter in light of @goalque last comment.

Posted by: goalque

@koskokos I had a 2014 Mac mini and its firmware was very sensitive to small changes in eGPU detection algorithm (which is far from perfect anyway). Unfortunately you can’t use this EFI on a 2014 Mac mini. I recall that Windows 10 should work without any hacks. Use Thunderbolt port closest to the USB ports.

@goalque When I tried to make it work without any hacks on Windows 10 (build 1903), I got infamous "error 12" when hot-plugging. When eGPU is connected before Windows boot, I got a black screen on output from mac mini's iGPU and eGPU both (iGPU connected through mini DisplayPort to DisplayPort cable, occupying second (farther from USB one) thunderbolt, and eGPU connected through HDMI to HDMI cable). As for eGPU itself, it works alright, as I checked on macOS side using purge-wrangler and automate-egpu-efi failed to boot.

I'm going to list my guesses, maybe some of them will make some sense to you:

- What is the most reliable way to get around or not to lead Windows into showing "error 12"?

- Should it be done in some particular order before or after boot?

- Should I reinstall Windows and follow some particular steps?
- Should I try using different Windows build instead of 1903, for example 1803?

- Should I stop using second thunderbolt as DisplayPort output for iGPU and use HDMI only?
- With "no hacks" I guess you meant no DSDT.aml as well but trying that using "test mode", I cannot see eGPU put in "large memory" segment. I think PCI bridge/root itself should be put there first, but I don't know how to achieve it.

Yep, no DSDT modifications. It involved lots of trial and error when I tested three different AMD cards, almost three years ago. The FW, Win10 version and AMD drivers are now different of course but it is worth trying the same. I found an old email, here’s a snippet of it:

”You need TWO monitors in order to boot into Windows 10 successfully with a 2014 Mac mini. Install the latest drivers by hot-plugging the eGPU, right clicking the basic display adapter (or R9 390 if Windows drivers are already installed), and pointing to the folder where the AMD drivers (Crimson 16.9.1) are downloaded, you can also check "include subfolders".

After the latest drivers are installed, shut down and keep Mac mini's HDMI interface connected, and the TB cable attached to the port closest to the USB ports. I used a DP interface from the eGPU, and all my UEFI AMD GPUs (R9 390, R9 Nano and RX 480) booted 100% into Windows 10.

You can disconnect the HDMI after logged in (iGPU is not visible under the device manager), but on every startup the Mac mini's HDMI interface is necessary, if and only if the eGPU has an UEFI vBIOS.

My U28D590D monitor has a built-in two monitor functionality, so that works too (DP-DP cable and HDMI-HDMI cable to the same monitor).”

@goalque Thanks so much it works in a perfect fashion. Clean Windows install and I just put dummy hdmi plug into Mac Mini and now it works.

Posted by: koskokos

@goalque Thanks so much it works in a perfect fashion. Clean Windows install and I just put dummy hdmi plug into Mac Mini and now it works.

Great! I was about to say that a HDMI dummy plug should do the job as well 😀