[EFI Loader] Error 12 Fix in Boot Camp for Apple T2 Security Chip Macs (apple_set_os loader v0.5)
The Alpine-Ridge DP Data Sheet was posted recently at #1,319 . I wonder if it would be possible to alter the DisplayPort In/Out path by poking some bytes...
@joevt Many thanks for the suggestions!
I have tested connecting the display after boot, and also changing order of connection. Although I'm only able to test it between the eGPU and display, as it needs to be cold booted in order to be detected.
I've come to the conclusion that perhaps where it isn't working in my case, but has in other cases I've read - may be down to whether or not the LG5K monitor is the 1st generation (27MD5KA-B, alpine ridge?), or the 2nd generation (27MD5KL-B, titan ridge?). Mine is the 1st generation unfortunately, but I should be able to get my hands on the 2nd generation display in the next few days to test this. I'm hoping at the very least this setup will work via the DisplayPort out of the Black Magic using a Moshi bi-directional DP to USB-C cable.
Will be sure to report back if successful
Another option: connect two displays (maybe use dummy adapters) to the other Thunderbolt port of the same Thunderbolt bus that contains the Black Magic eGPU (use a Thunderbolt dock or Thunderbolt to dual DisplayPort or HDMI adapter). Then connect the LG UltraFine 5K display to the Black Magic eGPU. The first two displays should be provided by the DisplayPorts of the MacBook Pro's Vega 20 so that there is no DisplayPorts remaining for the LG except for those from the Blackmagic eGPU's Vega 56.
This can only work if the Windows drivers are smart enough to see that there are more DisplayPort In adapters in the chain, besides those of the host controller.
An LG UltraFine 5K display requires a Thunderbolt connection to do 5K. A DisplayPort to USB-C cable can only provide 4K to the LG UltraFine 5K.
Update! I switched out the monitors, and can confirm that on the newer 2nd generation LG5K, the monitor connects perfectly via the Moshi bi-directional DP/TB3 cable using the Vega 56 card. Many thanks again to all on this forum who helped me get this working through their posts.
One question I do still have, is whether future updates to Mac OS are likely to prevent the apple_set_os loader from working it's magic?
@joevt, running at 4k yes!
I have tried connecting via thunderbolt, but in my case the windows screen hangs black for around thirty seconds, and when it comes back the Vega 56 is no longer detected. Although I have read reports here of a similar behaviour on the 16" MacBook Pro, where the eGPU connects with full 5k thunderbolt connectivity when the display comes back - so it may be possible!
I'm more than happy running the display at 4k in my case, which is adequate for all that I need to do in windows - and the solution is elegant, I can simply replace the thunderbolt cable with the Moshi cable on the back of the monitor and boot into windows with the eGPU detected every time.
Steps to replicate, for anyone who comes across this thread and may want to try are;
- Upgrade Black Magic eGPU Pro to firmware version 1.2
- Create bootcamp partition and install windows version 18362.30, install bootcamp support drivers.
- Boot into safe mode, and wipe graphics drivers using DDU .
- Install drivers from bootcampdrivers.com (April 2020 RED gaming edition)
- Upgrade windows manually to .295
- Disable automatic updates via registry
- Take ownership of and replace pci.sys (not sure if this step is required on .295, but I did it anyway)
- Disable T2 Security, allow booting from external media, keep password protection enabled.
- Install modified apple_set_os.efi as per OP
- Boot into windows and disable Intel UHD Graphics
- Reboot with eGPU connected via thunderbolt to laptop, and moshi DP/TB3 cable to display (must be 2nd generation 27MD5KL-B LG5K) - it's detected by windows and no port dancing is required.
- Create restore point
- Enjoy the eGPU with significant increase in FPS.
After giving up for a while, following the EXACT steps in the OP's post worked. Port swapping every time is a bit annoying, but Microsoft's Flight Sim was finally playable .
(eGPU plugged in top left, dock plugged in bottom left)
MacOS Version: macOS Big Sur Preview
Windows Version: 20201.rs_prerelease.200822-1922
Removing my previous post since I got it working.
What was causing me issues was that I didn't rename the existing efi correctly and the new one couldn't find it to load! I have to port swap to get it to work, otherwise I get an error 10 or 12 - I got both and don't recall which combination of hot/cold/swapping was causing it.
Does Big Sur require some changes to this file for it to work? After updating to Big Sur beta, my AMD eGPU 5700XT gets a code 12 now no matter what fix I try (and have had my AMD eGPU successfully working in Bootcamp while running Catalina 10.15.6 prior to upgrading to Big Sur). I have since completely erased my entire SSD on my 2019 16" MBP w/5500m and installed Catalina via internet recovery - I still cannot get my eGPU to work again, even after restoring from a backup with winclone 8, as well as a fresh install of the same ISO file of windows I had it working previously with on Catalina 10.15.6. So either something in .7 changed or Big Sur updated some firmware or such and it won't let me roll back by simply deleting the SSD contents... I've tried clearing SMC and NVRam as well. Thoughts?
Just want to mention that, though I've been updating windows builds and using my eGPU and this boot loader successfully for the last year or so through 2004, the latest update of windows or MacOS has killed eGPU use on my Sonnet 350. Rolling back windows with a fresh install didn't seem to help. Anyone else has had this workaround stop working?
Edit: Reading through the post above, I'm thinking it's related to installing Big Sur on an external drive.