Using RX 5500 / 5700/XT eGPU on Bootcamp W10 2004+ and 10.15.7 ? (Error: Code 43 with RX 5700)
Which method worked? set_apple_os, .sys, hackflags, or anything else?
Has anyone been able to use internal HDMI on the mac (loopback mode) for such setup?
(I have encountered an issue ‘Code 43’ with my Sonnet RX 5700 on W10. Please see more details in later posts. Any assistance would be greatly appreciated).
P.S. I have found this topic mentioning interesting fact regarding ATI Bootcamp 2019 drivers on W10:
It notes 10.15.7 as well, however, I am not sure on the complete stable setup / boot process / details.
Found another build working with MM 2018 by disabling iGPU in the Device Manager.
I wonder if there is a way to keep internal HDMI display alive (to use loop-back mode) somehow...
What I want to achieve is to use 2018 Mini with 5500 / 5700 card (cold-boot) and loopback mode, respectively, my monitor would be still connected to the Mini HDMI port.
Currently this is working for me with RX 5xx series (set_apple_os + disabling PCIe x16), however I wanted to be sure I will be able to do something similar with Navi when it arrives to me.
@susurs, For cold-boot into Boot Camp I've used the modified apple_set_os EFI v0.5 with Apple T2 Macs (2018 Mac mini, 2019 13-in MacBook Pro, 2020 Ice Lake MacBook Pro. This has worked with RX Vega 56, RX 5600 XT, and RX 5700 XT cards. Depending on the Windows 10 version, you may have to do the port dance.
Before you go too crazy, I've done this with both a Mac Mini 2012 and a Mac Mini 2018, using (on both) an RX 580 and a 5700 XT in a Razer Core X. The problem: I can't tell you exactly which steps I took in what order to get them working. Also, I haven't messed with trying to get it back into loopback mode. The good news: It's possible to get the eGPU up and running without messing with pci.sys or any other modifications except for purge_wrangler, and that only for the 2012! I didn't so much as use DDU.
What I did, as near as I can remember it (which may not be that well):
I think I initially hot-plugged into OS X on the 2018, and after that was able to cold-boot into it without problems. Trying to get back to Bootcamp, I did the whole plug in at random points during boot thing, and eventually it just managed to come up. After installing drivers, everything was fine. The only issue is that rebooting into Mac OS after spending time in Windows occasionally required me to unplug and boot through the iGPU.
On the 2012, I of course used the Apple Thunderbolt 2-3 adapter. It was also easily recognized by OS X after applying purge_wrangler. Getting into Windows was more difficult. I tried the port dance, and it once came up, but I made the mistake of telling the AMD installer to do a 'factory reset' (requiring a reboot) before it installed the drivers. On reboot, of course, it failed to recognize the GPU. I tried plugging into the iGPU and eGPU at the same time while booting Windows, and nothing seemed to work. The iGPU-attached monitor would keep flickering the Windows loading screen on and off in a loop, which made me think it had locked up.
Eventually, though, I tried screen sharing with the machine. Et voila, Windows was not in fact locked up, but running and logged in! It turned out the eGPU had been recognized as well, from a cold boot (as a basic graphics adapter). After that, I was able to install the AMD drivers (the installer might have told me to disable automatic driver updates first), and from then on cold booting has never been a problem for MacOS or Windows 10. One problem that I think is due to it being a Windows To Go installation (through a USB enclosure) is that I can't let it go to sleep; it'll fail to use the eGPU on wake. So I disabled sleep mode in the energy settings.
This was all under Catalina and 2004. The 2018 has now moved on to Big Sur and 20H2, still performing swimmingly.
So a key thing I guess a good idea to do first is to set your Windows side to let you remote in to your desktop. The AMD drivers require being able to see your AMD GPU before installing, even if only as a basic graphics adapter. Viewing your screen remotely will allow them to do that even if your actual display is not visible.
@itsage - did it worked just with set_apple_os and no aditional methods were needed on 2018?
For example, with RX 560 I needed to disable PCIe x16 in adition to efi in order to get rid of the ‘Code 12’. It did not matter in which of the 4 ports I plugged it in.
So I tried it... With Catalina 10.15.7 and MacMini 2018 everything works OOB.
W10 on the other side does not want to cooperate so far...
I had v2004 on the machine, and later tried all the tricks on 20H2 - nothing helps.
With .efi - The card gets recognised and shows up as basic display adapter with drivers uninstalled or after DDU.
I tried installing different drivers from Bootcamp com - Red / Blue and the ones from Nov 2019, as well as the latest ones from AMD’s site.
After the driver gets installed - the card shows up as 5700 and is partly recognised by GPU-Z (speeds are not displayed). But as soon as I do the necessary restart - the card is still recognised but Error 43 is there and does not go away.
If I hot-plug the card - I get Error 12 on any port I try. Nothing is plugged into other ports.
I have tried HackFlags, disabling PCIe 16x, 8x - nothing helps.
I even tried disabling iGPU. The signal then gets from the RX 5700, however it is laggy, without acceleration, and Code 43 is still displayed.
I even tryed attaching 2 TB cables as the card has 2 ports - no go.
I do not know what to try next. I could either update to some W10 Dev channel version, try DSDT, or try installing W10 1903 maybe...?
Any advice would be greatly appreciated!