MacPro 2013 macOS Catalina + Win10 Bootcamp for CG and gaming
Hello everyone and thanks for your amazing pioneering efforts.
I'm a trash can user and i've joyfully discovered egpu's forum some days ago.
I'm putting so much effort in doing my homework.
I've expanded my knowledge a lot since I started roaming around threads, guides and builds but still I feel like asking some questions to you, wise people.
Thing is, I'm a total newbie so please be patient if I sound confused or lost.
As a CG aritst and gamer I feel like the time has come to give the proper boost to what I thought it was just an outdated and hopless, very well refined trash can.
I use macOS environment for 2D graphics and Win10 for 3D and games.
MacPro6,1 running 6-Core Intel Xeon E5
FP D500 x2
Thunderbolt Display Apple 27"
My expansion plans:
RazerCore X TB3 Enclosure + Radeon RX5700XT + Apple TB3>TB2 adapter + Thunderbolt cable
See that coming: will that work?
As stated on AMD's site, the card requires a Typical Board Power of 225W - https://www.amd.com/en/products/graphics/amd-radeon-rx-5700-xt
My MP has a max power consumption of 238W, as shown here - https://support.apple.com/en-us/HT201796
I don't know if it even fits or matters anything since I'm going to power it externally, maybe someone could make it clearer for me.
Anyway, the PSU recommended for the card is 600W and the RazerCoreX should cover it.
I mainly use Eon Vue on Windows 10.
As stated on Eon's website, a graphic card with 3D mark score of 10.000 or better is recommended. I checked https://benchmarks.ul.com/compare/best-gpus to take knowledge and found out the 5700XT has a very good score and a decent price.
I'm currently running Win10 version 1909 and I'm aware I need to downgrade to 1809, as learnt on AJ Scarcella's https://egpu.io/forums/mac-setup/mac-pro-6-1-rx-580-egpu-bootcamp-success-somehow/ illuminating thread. My question is, what 1809 version should I install? Will March 2019 be good or should I go for an earlier one to be safer?
I know I have to use automate-eGPU EFI + pre-compiled DSDT.aml and then disable some PCI-to-PCI Bridges. Will that mess up with my Thunderbolt Display? Should I always use the bottom left TB ports for eGPU and display?
Will Catalina be friendly to the new eGPU once I boot back into macOS and after I run Mac Editor's purge-wrangler.sh?
Should I always boot via automate-eGPU EFI ?
I know that's a lot of questions but the 2013 MP is a messy thing to deal with and I wasn't able to find all the answers by myself. Hope you don't bother.
I'll be more than happy to provide more informations if needed. Suggestions about gear and installation recommendations will be much appreciated as well.
Thanks in advance for your support and for making all this possible!
I'm just a little ahead of you in my learning but I can answer this....
First off, I have a similar 2013 nMP with 12 core CPU, 48gig ram, 1Tb SSD. I have just replaced my Razer X with a Razer X Chroma. Had a little issue with USB but I suspect it was the load on my hub from downstream MyBook Duo's that were further hub(ed) together. The only part the Razer X Chroma might have played was when the Mac saw the additional hub of the Razer. IDK and it isn't significant for your setup imho.
All the power the Radeon RX5700XT needs comes from the Razer X. But I'm not sure you'll be able to use your thunderbolt display with that videocard?? The whole idea is to have 4k quality graphics on your monitor. The Thunderbolt display doesn't quite get there. Besides, all it has is a thunderbolt1 DisplayPort connection and the graphics card you are looking at appears to have 3 DisplayPort connections and one HDMI connection. Might work with an adaptor? Of course, you should see better gameplay than the iGPU D500's can provide.
I would think it would be better to get a 4k monitor and use the thunderbolt monitor on Thunderbolt bus1 or 2 and the eGPU on Bus 0 (either of the two bottom ports)
I have not used Automate-eGPU EFI at all until now. It wasn't needed for the Mac install. I'm trying to get the Win10 side working these last several days so I am no help there.
Boot into MacOS normally and Follow this - https://egpu.io/forums/mac-setup/script-enable-egpu-on-tb1-2-macs-on-macos-10-13-4/
and particularly this - https://github.com/mayankk2308/purge-wrangler/wiki/Beginne r's-Guide
You should have no problem on the Mac side!
Thanks for your help!
I’m aware the 5700xt it’s a 7k pixels and more native card and my old Apple Display is a 1440p. My monitor and visual experience, in terms of resolution, won’t benefit much from the new eGPU. I mostly need the new gpu for boosting render and workflow speed in Vue on Windows 10, the 2D apps I work with on macOS have no particular issue with the older dGPUs but, of course, if I can add more power to them as well I’ll be more than happy.
I was worried about the TB ports because on win10 you have to disable some PCI to PCI Bridges in order to free up memory for the eGPU to work. Don’t know if the TB Display Monitor could cause any issue.
Just in case, I have another hdmi monitor to try with if I screw up something.
Any other question were Bootcamp related.
Thanks a lot for your infos about the enclosure and macOS, I appreciate!
At least, I think I can order the whole new stuff and start experimenting.
I’d just need to know what win10 1809 update should I fresh install. Anyone?
I did the disable pci-to-pci bridges as per this thread. Read it to the end
but that’s as far as I could go. I was on Win10 build 1903. I ended up with a blank screen and a never ending loop in recovery mode. Searching for a fix now.
@dogloop Welcome aboard and good to see more 6,1 owners trying eGPU! My first recommendation is to start step-by-step. This particular Mac is tricker than most to set up in Windows Boot Camp. It's best to use the HDMI connection from the nMP to a single monitor during the setup process so that the Thunderbolt ports are all free up. There are three main hurdles that you'd need to overcome.
The first is Thunderbolt device detection in Boot Camp. The latest firmware on the nMP is not blocking Thunderbolt eGPU in Windows so you should be good as long as you have macOS 10.4.4 or newer installed. The second hurdle is error 12 due to lack of resources. In my experience, automate-eGPU EFI with the modified DSDT.aml is a necessity to allocate Large Memory for the Radeon eGPU. Without which the eGPU would encounter error 12.
The last is driver conflicts between Radeon dPGU and eGPU. The modified drivers from bootcampdrivers.com help with this. You would likely encountered error 43 too so it may need some PCI Express root ports disabled. The Win10 version with most reported successes is 1809 Redstone 5. You can download the ISO from this website.
Is this old post relevant at all to these errors?
Is this old post relevant at all to these errors?
Nope, it did not help in my case with the Mid 2015 15" MBP. PCIe expansion is different than Thunderbolt.
here I am with my new eGPU gear and new troubles 🙂
Bootcamp is still reluctant.
I'm on win 1809 Redstone5. In device manager I have the Thunderbolt entry and PCI Slot 2 (PCI bus 21, device 3, function 0) flagged yellow by Win with error 12. I don't have any large memory entry.
So, here's what I did:
- Installed automate-eGPU EFI via bash as per mac_editor instructions (choose Nvidia patch even if my eGPU is AMD)
- Downloaded nando4 nMP precompiled DSDT folder, dropped everything in the EFI drive \EFI\CLOVER\ACPI\WINDOWS. I don't know if I should use Winmerge to modify something, if so, please point me to some detailed instructions.
- Ran the load batch file in DSDT folder. BSOD after reboot, windows starts again in Test mode only.
- I rebooted in safe mode, ran the unload batch file as instructed and reverted things to normal state.
Just to make it a bit clearer for me, does the dsdt.aml start working again after rebooing via EFI?
Seems I have to fix something about the dsdt.aml but I'm quite confused about the whole thing.
Thanks in advance!
@dogloop Make sure to rename the file to "dsdt.aml" and place it in the correct directory. That's all you need to do. The EFI boot loader will take care of the rest, no need to execute anything in Windows or enable Test mode.
thank you for your suggestions as always.
I have now renamed the dsdt.aml file.
There’s another file named dsdt-modified.dsl, should rename that one too? Because if I do it will replace another file with the same name in the folder.
I also kept everything else in the folder, should I remove the other files instead?
Anyway, I tried keeping and removing them, still no Large Memory entry in Device Manager.
Here’s what I tired next:
I DDUed everything off. After that win10 finally detected my 3rd display adapter. The first and last one are yellow flagged for missing drivers.
I was installing Adrenaline drivers from Bootcampdrivers, Nov19 Red edition, but I got a beautiful BSOD during the process, right after Windows had finally named all the devices correctly.
I had a restore point set at windows bootcamp fresh install. The system has just finished restoring.
Device Manager shows 3 display adapters again, two of them flagged for missing drivers.
Still no Large Memory entry and I tried to look for it everywhere around in Device Manager.
Think I’m going to DDU everything again, try with the blue edition drivers and report back.
Sorry for messing up with the dsdt process, looked quite an easy one, I can’t understand what I’m doing wrong, that’s why I keep asking! Oh and thanks for your patience 🙂
Nope, blue drivers are not the solution. BSOD and repairing again, might it be related to Large Memory allocation?
Anyway, I think I’ll wait for your support before screwing everything up again.
@dogloop The "dsdt.aml" is the only file I copied to /EFI/CLOVER/ACPI/WINDOWS volume. As soon as I boot into Windows through automate-eGPU EFI, my nMP has "Large Memory" allocation. If yours doesn't have it, don't connect the eGPU just yet and redo the EFI volume to get "Large Memory" first.
new EFI boot through batch done, necessary fix applied, config.plist modified.
dsdt.aml renamed and placed in \EFI\CLOVER\ACPI\WINDOWS volume, only file in folder.
No Large Memory showing up.
Anything else I should try?
Hi, tried that too.
I'm now trying to create my on dsdt.aml from scratch, I now it doesn't make so much sense but I'm stuck here and I have to try something...
Thanks for your help anyway!
All you have to do is to open MaciASL app on macOS, edit DSDT and save the file from menu: File > Save As...
I edited the dsdt adding the ‘QWordMemory’ (64-bit) entry as per guideline.
Saved the file on macOS, renamed DSDT and manually added .aml extension.
No Large Memory on Device Manager
What am I doing wrong?
so guys, errrr this is quite embarassing...
I finally made it, Large Memory has been allocated.
I solved all of my problems inside Device Manager by selecting View > Resources by type.
Yes, that was it.
Large Memory entry has probably been there all the time, so I can finally state I never had issues with Large Memory allocation at all. Sorry for being such a pain in your arses!
Feel free to laugh hard! 😀
So, I’m back! 🙂
I have something to report that may need your suggestions once again.
I had successfully set up my eGPU, working both on Bootcamp and Catalina.
Bootcamp drivers from bootcampdrivers.com, September Edition Red worked fine with my system. I tried to install the Blue Enterprise Edition, which I prefer, but couldn’t get past atikmdag.sys error which caused BSOD during installation. Had so many system crash that I decided to clean install Bootcamp once again just to be sure it was stable. Anyway...
Everything was fine at first, but after a while Windows10 started freezing while booting, on win logo screen the spinning dots just freeze and automatically reboot to automate-egpu EFI launch screen.
If I unplug the eGPU everything starts working again.
There are two main changes I can recall that may have caused this issue.
I thought I needed purge wrangler to get my eGPU working on macOS, installed it via Terminal and after that I noticed eGPUed Bootcamp was dead.
So I uninstalled purge wrangler, via Terminal as per guide, and noticed my eGPU was working perfectly fine on macOS without it, I’m only missing the eject button on state bar.
I’m really not sure if pw may have caused any problem, that’s why I’m asking for your opinion.
I switched back to my Apple Thunderbolt Display, plugged in the trashcan upper left port. Unfortunately, I did so many changes lately and I can’t remember if I ever booted successfully into win10 since I plugged the TDisplay back in! Do you think a second Thunderbolt connection may be problematic on windows startup?
To get rid of any doubt I’m reinstalling Catalina right now. I already reinstalled Bootcamp as well and set everything up again to see if the error was gone but no. It still freezes. Quite stupidly, I didn’t try to switch back to my HDMI monitor...
I was also a bit worried about the pci-e bridges I disabled, but as I told you, if I unplug the eGPU Bootcamp works fine. Moreover, I only disabled pci-e bridges that were not connected to any device.
It would be great to know how can I troubleshoot to get more clues about the occurring issue...
Thanks once again for your support!
Reinstalling Catalina got things even worse. With my eGPU connected even macOS gets stuck on boot screen and falls back to startup!
Did some more troubleshooting though:
on bootcamp I DDUed everyting off just to be sure it was not some driver related issue.
Problem was still there so it was not.
Then I re-enabled all the PCI bridges I previously disabled and fixed the issue.
I found out that disabling PCI bus 17, device 10, function 0 crashes windows on startup, even if disabled alone. Reading around in the forum I learnt that may be related to the dGPUs.
I'll try to boot back to macOS and see if things got back to normal.
Thing is that now I can't get past error43 even disabling every other free PCI bridges and the Broadcom Network adapter stopped working for some reason...
I switched back to my hdmi monitor and looks like that freed up some precious resources. Curiously, the only PCI bridge disabled now is PCI bus 17, device 10, function 0 the one that caused my latest pile of troubles.
In the end, my eGPU is now working with only one PCI Bridge disabled.
I can't boot anymore into Catalina via automate-eGPU EFI like I did before. It gets stuck on apple logo and loading bar and then it dies. Miserably.
Any advice? Think I'll try purge wrangler and normal boot again, tomorrow.