New (2013) nMP eGPU User with Install
 
Notifications
Clear all

New (2013) nMP eGPU User with Install  

 of  3
  RSS

VmanJeff
(@vmanjeff)
Active Member
Joined: 1 year ago
 
Posted by: @itsage

@vmanjeff How has your eGPU setup been working? We'd love to see a build guide once you have a chance.

 

@itsage Hey I was just thinking about you!  (and Mac_Editor )....

OK... So I think things have been stable and working OK. It's kind of a mixed bag for me though as the primary purpose was to get Premiere Pro PLAYBACK stable without dropped frames and then secondary was faster renders.  For these two goals I'm gonna have to say it was a non-starter. I'm still working with Premieres settings to optimize depending on my source material but I'm finding overall the program won't stop dropping frames nor render any faster for the most part. But I'm sure SOME of this is me and my settings. I also know from reading that Premiere has poor support and use of eGPU's at this point. I can confirm that with Activity Monitor/GPU History. Little if any activity on any GPU, internal D500's or eGPU Radeon VII . No matter the settings in "About" when right click on the program icon, or in program settings "render"...use Metal or Use OpenGL (hardware) or Use Open GL (use Software). I even read a post that suggested Premiere Pro 2020 was broken and Premiere Pro 2019 fixed the issue for the most part with that user. So I installed 2019. It seemed to help but not much.

LOTS of CPU activity for playback and rendering on both 2020 and 2019.

BTW..... I upgraded my 6 core to a 12 core CPU over the weekend. Same results as above. I dig that teardown, though! It was fun. So....

As far as the eGPU setup I have (Razer with Radeon VII , T-bolt 3 to T-bolt 2 adaptor, plug in eGPU on bus 0 (bottom row of Thunderbolt ports on 2013 nMP , PurgeWrangler script) I feel it has been very stable. As you can see above I've been in Premiere a lot over the last 4 - 5 days and in Win10 also (more on that below) trying to work out so issues with other tasks besides the eGPU. All the while the eGPU has operated without flaw except for that annoying fan start-up when I shut down. But as I said I just turn the eGPU off after a few minutes (and the DISAPPEARING "Disconnect Radeon VII GPU" titlebar menu item!) Yes @mac_editor , the menu item was NOT there on boot this morning?! but as I began making my way toward trying automate-eGPU-efi  to attempt a Win10 eGPU boot, I ran into a problem with using the USB boot menu....again, see below.... so when the frozen computer was rebooted, the disconnect eGPU menu was back again. I even removed a couple items from that menu that I never use to see if it was a space thing.  Here's the set-up I'm running....

2013 nMP (now) 12 core 48gig RAM, 1Tb Aura Pro x2 SSD internal boot drive

Razer Core X with XFX Radeon VII

PurgeWrangler

3 monitor system with following connections -

1 - Top Graphics card DP connector --> 32in LG HD monitor used as Primary

2 - next Graphics card DP connector --> empty as it seemed to not work when HDMI port was in use

3 - Next Graphics card DP connector --> 27in LG HD monitor

4 - Bottom Graphics card HDMI connector --> Direct connect to 47in LG HDTV

2013 nMP connections - 

Looking at the back I would number all connectors

This post was modified 1 year ago

NEW = 27” 2019 iMac i9, 1Tb SSD, 128gig ram, Tb3 port to OWC Thunderbolt3 ProDock to OWC Helios PCIe for eSATA, Tb3 port to Razer Chroma w/AMD Radeon VII, connected via DP to 32” 4K monitor and via HDMI to 47” 4k TV Monitor
Internal Vega 48 for iMac display
OLD = Mac 2013 nMP 12 core Xeon, 48Gig RAM, 1Tb SSD, AMD FirePro D500 (2) internal GPU
eGPU --> Razer Core X Chroma, AMD Radeon VII, attached through T-bolt3 to T-bolt 2 adaptor attached to T-bolt bus0Port6


ReplyQuote
VmanJeff
(@vmanjeff)
Active Member
Joined: 1 year ago
 

2013  nMP  connections - 

Looking at the back I would number all connectors left to right, top to bottom.... DISREGARD any previous posts by me assigning bus and port numbers to the T-bolt connections. The names below are correct referring to Apples nMP port assignments per this Apple document https://support.apple.com/en-us/HT202801

1 USB --> external SSD

2 USB --> unused*

3 USB --> external hub with harddrives, diskdrive and misc USB devices as needed

4 USB --> keyboard

5 T-bolt (bus1Port1) --> T-bolt to HDMI converter to Amplifier**

6 T-bolt (bus2Port2) --> empty (reserved 😉

7 T-bolt (bus1Port3) --> OWC Helios 1 slot PCIe box to RAID5 storage farm

8 T-bolt (bus2Port4) --> T-bolt 2 cable to T-bolt2-to-T-bolt3 adapter to NAS for T-bolt transfers

9 or 10 (bus0Port5&6) --> eGPU (use on either port)

11 HDMI connector --> Empty

Notes -

*I have a suspicion I either have overloaded the USB capabilities of this system or semi-fried USB#2 as it seems to exhibit strange behavior when used. Or the current HUB config is not allowing more direct plug-in devices??  

**T-bolt # 5 T-bolt (bus1Port1) used for multi-channel audio out to amplifier. This is the only way I know to get digital audio out of the nMP without changing the Amp I already have. The HDMI connection from the Radeon VII sends 60Hz 4k video to the HDTV but my amp will not pass 60Hz. Therefore nMP T-bolt #5 T-bolt (bus1Port1) is used to output audio as set in MIDI control found in Applications/Utilities.  Normal sound is set in Prefs with system sound assigned to 32in LG and output audio assigned to the DP (T-bolt) #5 T-bolt (bus1Port1). The side perk (if you can call it one!) is that this connection also shows up on the HDTV monitor on input 2 as a 1920x1080 30Hz signal. 

The HDTV is intended for Premiere Pro playback monitoring and as such PP can be set to display either the eGPU HDMI out or the nMP HDMI out. Neither display setting seems to affect system ability and headroom. Nor affect my ability to get a smooth running Premiere experience.

I tried Da Vinci Resolve and my limited experience with the trial showed better results as Resolve takes advantage of eGPU's. I might try Final Cut but I;'m not inclined to pay $300 just to see. If there was a demo or another user who could drop a note on this I would be happy!

 

To this point I do not have a working Bootcamp Win10 eGPU experience. But I can boot to Win10 without changing up monitors as the nMP #5 T-bolt (bus1Port1) connection to the Amplifier thankfully allows that. Under normal operation in MacOS I can switch between the HDTV eGPU and nMP desktops (without disturbing the Mac main and secondary monitors) by using the TV remote to simply switch between input 1 and input 2 on the TV. What use this is is debatable (at least for me).  But if I want to boot into Win10 Bootcamp I switch the TV input to nMP and re-boot the Mac holding down the Option key. The main and secondary monitors blank and eventually the HDTV shows the boot men. I simply choose efi to boot from (This menu used to show "windows" as an option but somewhere after Mavericks and a Win10 re-install it just shows efi and I cannot seem to change it. There were also nice icons in the boot menu at one time but there are gone now too, replaced with the tired yellow HD icons.....its the little things 🙂 So I select efi and I can boot into Win10 which is displayed on the HDTV. The other two monitors are sadly blank for the time being. And Win10 can be operated normally from here but its kinda uncomfortable since that TV is hung above the other two.

Which leads me to my questions for @itsage and @mac_editor     I see itsage has had some success running an eGPU with Bootcamp Win10 on a nMP. I began this journey this morning.....

 

Which leads me to my questions for @itsage and @mac_editor     I see  itsage  has had some success running an eGPU with Bootcamp Win10 on a  nMP . I began this journey this morning.....

It seems I need to format a USB stick in Fat32 and put Automate-eGPU EFI on the stick and bot from that. First question is the directory tree for this... 

stick--(folder)EFI--(folder)Boot

                                 --(folder)Clover

 

Or put the folders at the root. Silly, I know....

So I have both on my stick and re-booted holding down option with the eGPU DISCONNECTED. I get to the start-up screen and select the Automate-eGPU efi boot and see the load screen where it says my system and then "no eGPU found". I press "q" and go to the menu and select windows and it freezes. Same behavior when selecting mac. So I plug in the eGPU and same behavior in both selections.

I then tried the reset command and re-booted to Mac. Well this is when my eGPU HDMI connection failed and did not return. I checked all connections and shut down. Restarted and the eGPU HDMI connection reset upon desktop load AND the "disconnect eGPU" menu item was back ??? (told you I'd get back to it)

So I seem to remember I need to copy my efi partition to the stick (which I did not do). But IDK.  So where it go from here??

This post was modified 1 year ago

NEW = 27” 2019 iMac i9, 1Tb SSD, 128gig ram, Tb3 port to OWC Thunderbolt3 ProDock to OWC Helios PCIe for eSATA, Tb3 port to Razer Chroma w/AMD Radeon VII, connected via DP to 32” 4K monitor and via HDMI to 47” 4k TV Monitor
Internal Vega 48 for iMac display
OLD = Mac 2013 nMP 12 core Xeon, 48Gig RAM, 1Tb SSD, AMD FirePro D500 (2) internal GPU
eGPU --> Razer Core X Chroma, AMD Radeon VII, attached through T-bolt3 to T-bolt 2 adaptor attached to T-bolt bus0Port6


ReplyQuote
joevt
(@joevt)
Noble Member
Joined: 4 years ago
 

The disk labels are created with the bless command:

[Please login to see this]

The disk labels might not work for the EFI partition, but they will work for a different MS-DOS (FAT32) partition (so you don't see "EFI Boot" in the Startup Manager (hold Option key at startup).

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


itsage liked
ReplyQuote
itsage
(@itsage)
Founder Admin
Joined: 4 years ago
 

@vmanjeff Boot Camp eGPU setup is a convoluted process for many Macs, especially so for the 2013 Mac Pro. For several years the firmware actually blocks the use of eGPU in Boot Camp. Fortunately newer firmware came out right around Catalina launch that removed this restriction. You can read through this discussion where several nMP users, myself included were able to get it working after disabling multiple PCIe root ports as well as using automate-eGPU EFI boot loader.

LinkedIn | Twitter | Facebook | Youtube | Instagram
 
external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide

 
2020 13" MacBook Pro [10th,4C,G] + RX 6700 XT @ 32Gbps-TB3 (CM MasterCase EG200) + Win10 1903 [build link]  


ReplyQuote
VmanJeff
(@vmanjeff)
Active Member
Joined: 1 year ago
 
Posted by: @itsage

@vmanjeff Boot Camp eGPU setup is a convoluted process for many Macs, especially so for the 2013 Mac Pro. For several years the firmware actually blocks the use of eGPU in Boot Camp. Fortunately newer firmware came out right around Catalina launch that removed this restriction. You can read through this discussion where several nMP users, myself included were able to get it working after disabling multiple PCIe root ports as well as using automate-eGPU EFI boot loader.

Thank you @joevt  It made more sense as I thought about it and read your post.

@itsage  I'm reading through that post now. But still stuck on automate.egpu menu screen. When I select either boot option (win or Mac), automate.egpu freezes and a hard reboot is the only thing that works. I think I'm missing some files. I'll keep researching.

And to be more precise... I used terminal to make the thumb drive with itsage's installer then removed "apple_set_os.efi" as noted in https://egpu.io/forums/bootcamp/mac-pro-6-1-rx-580-egpu-bootcamp-success-somehow/

Plowing through that post now it find hints as to why its freezing on me.

I've been through Device manager on the Win10 Bootcqamp side and see no triangles (yellow bangs as I've now been initiated to :)) And I really think Windows just doesn't see the eGPU at all so I am at a loss as to my next step. I assumed automate.egpu would get me a step further but ??!!

This post was modified 1 year ago

NEW = 27” 2019 iMac i9, 1Tb SSD, 128gig ram, Tb3 port to OWC Thunderbolt3 ProDock to OWC Helios PCIe for eSATA, Tb3 port to Razer Chroma w/AMD Radeon VII, connected via DP to 32” 4K monitor and via HDMI to 47” 4k TV Monitor
Internal Vega 48 for iMac display
OLD = Mac 2013 nMP 12 core Xeon, 48Gig RAM, 1Tb SSD, AMD FirePro D500 (2) internal GPU
eGPU --> Razer Core X Chroma, AMD Radeon VII, attached through T-bolt3 to T-bolt 2 adaptor attached to T-bolt bus0Port6


ReplyQuote
VmanJeff
(@vmanjeff)
Active Member
Joined: 1 year ago
 

OK...before I forget what I did here's what I did 🙁

Reading all the info gets confusing and starts to seem like a circle with links to links to !! So my references here are a bit lacking. But it was a bust anyway to this point....

I've read where build 1903 was a problem and where it was not a problem so I wasn't sure. I decided to proceed anyway.

I decided that my inability to get Automate-eGPU EFI to get past the terminal menu option to boot Windows (or Mac) was probably due to not having the DSDT file(s) in the Windows directory of the tool. So I had also read somewhere that there was no need to compile the override since pre-compiled versions were at this link https://www.mediafire.com/folder/9xrm0bg8jj0z5/DSDT_override_resources

So I got the one for the 2013 MacPro and corrected the name of the modified file and put all the files in Automate-eGPU EFI under EFI/CLOVER/ACPI/WINDOWS  

Tried to run Automate-eGPI EFI again but it would just hang when i selected "windows" for boot. I also read some things which led me to believe it needed pointed to my EFI directory for boot but IDK??

So I booted Win10 and went to Device Manager and found the entry that was probably the eGPU. The only little yellow triangle in the tree. Under the PCI-to-PCI Bridges. I found in a post where certain PCI-toPCI Bridges were disabled to allow the eGPU to be 'seen' so I did that.

  • PCI bus 17, device 10, function 0
  • PCI Slot 4 (PCI bus 21, device 5, function 0)
  • PCI bus 0, device 30, function 0

This one was also in the list but under it in the tree was a Thunderbolt entry and I wasn't sure if disabling it would affect that connection so I did not disable

  • PCI bus 21, device 0, function 0

And now I'm not sure 100% which one I did not disable but It turns out that just disabling three was enough to remove the triangle from the eGPU entry.

Not too sure where to go I decided to reboot. Windows booted normally and actually found the Razer Core X Chroma, put up a nice splash screen and said it was setting up the device. It finished setting up and notified me of such. But within 12.24 seconds my screen went blank and did not come back. I did a hard reboot and made it restart 3 times to get to automatic repair. Booted in safe mode and having the USB stick inserted navigated to the DSDT directory and in terminal I ran the bat file thinking I would enable the correct memory allocation and be good to go. The file ran and it seemed successful but again I was at a loss as to either run the video driver uninstall or reboot to check on memory space and then run the uninstall. I decided to reboot but that just sent me in an endless loop of Automatic repair. Safe mode would not work. It errors with a "ACPI BIOS ERROR" and the restore point I created would error out near its end so no dice there. I even went to command prompt and hurt my brain remembering how to navigate through there! But I got to the DSDT directory and uninstalled it. But I am still in an endless loop of "fix-it's".

So I would hope someone comes along and points me in the right direction.  LOL  It was so cool seeing that splash screen 😉

I have a Winclone image waiting in case I need it but its not current....  Should have made a current one....

This post was modified 1 year ago

NEW = 27” 2019 iMac i9, 1Tb SSD, 128gig ram, Tb3 port to OWC Thunderbolt3 ProDock to OWC Helios PCIe for eSATA, Tb3 port to Razer Chroma w/AMD Radeon VII, connected via DP to 32” 4K monitor and via HDMI to 47” 4k TV Monitor
Internal Vega 48 for iMac display
OLD = Mac 2013 nMP 12 core Xeon, 48Gig RAM, 1Tb SSD, AMD FirePro D500 (2) internal GPU
eGPU --> Razer Core X Chroma, AMD Radeon VII, attached through T-bolt3 to T-bolt 2 adaptor attached to T-bolt bus0Port6


ReplyQuote
VmanJeff
(@vmanjeff)
Active Member
Joined: 1 year ago
 

@itsage I know you guys are running a pretty big forum but could you take a quick look at my post above and confirm I either can fix that issue through some means or that I need to re-install Windows. I might just do there-install and move back to the version that seems to be working...

 

Thanks!!

NEW = 27” 2019 iMac i9, 1Tb SSD, 128gig ram, Tb3 port to OWC Thunderbolt3 ProDock to OWC Helios PCIe for eSATA, Tb3 port to Razer Chroma w/AMD Radeon VII, connected via DP to 32” 4K monitor and via HDMI to 47” 4k TV Monitor
Internal Vega 48 for iMac display
OLD = Mac 2013 nMP 12 core Xeon, 48Gig RAM, 1Tb SSD, AMD FirePro D500 (2) internal GPU
eGPU --> Razer Core X Chroma, AMD Radeon VII, attached through T-bolt3 to T-bolt 2 adaptor attached to T-bolt bus0Port6


ReplyQuote
itsage
(@itsage)
Founder Admin
Joined: 4 years ago
 

@vmanjeff I tried Boot Camp eGPU on my nMP last year but have not tried recently. What I recall necessary was Win10 1809 and automate-eGPU EFI boot loader with the pre-compiled dsdt.aml file. I also disabled some PCI Express root ports to finally get the eGPU going. Also Windows 10 1903 was attempted but eGPU failed to work using the same procedure.

My recommendation is to get back to 1809 version. Try booting into Windows with the automate-eGPU EFI boot loader without eGPU connected. Once you can successfully boot into Windows through it and confirm there's Large Memory allocation, you can proceed to cold-boot with the eGPU connected. I don't have a nMP Boot Camp guide but this 2016 15-in MacBook Pro build guide details a very similar setup procedure (skip the part about enabling iGPU). 

 

LinkedIn | Twitter | Facebook | Youtube | Instagram
 
external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide

 
2020 13" MacBook Pro [10th,4C,G] + RX 6700 XT @ 32Gbps-TB3 (CM MasterCase EG200) + Win10 1903 [build link]  


ReplyQuote
VmanJeff
(@vmanjeff)
Active Member
Joined: 1 year ago
 

@itsage

Thank you sir!

It seems that Automate-eGPU EFI doesn’t work on my system. I can see it’s prompts when I run it from the startup menu but when I click “Windows” for startup it does nothing. Freezes and I need to hard reboot. 
another thing I’m not clear on is if I need to make my own DSDT file or use the one found online from Nando4. 
Then how to place the file. I’ll read the link you provided and re-read the DSDT override thread. Also the Automate-eGPU thread. 
The order in which to apply these steps is a little confusing. But since I couldn’t get Automate-eGPU to run I manually ran what I though was the correct file for DSDT override from command line in Win10. But on reboot I couldn’t get back in. 
anyway, I’ll try the previous Win build and work from there. 
thanks again

NEW = 27” 2019 iMac i9, 1Tb SSD, 128gig ram, Tb3 port to OWC Thunderbolt3 ProDock to OWC Helios PCIe for eSATA, Tb3 port to Razer Chroma w/AMD Radeon VII, connected via DP to 32” 4K monitor and via HDMI to 47” 4k TV Monitor
Internal Vega 48 for iMac display
OLD = Mac 2013 nMP 12 core Xeon, 48Gig RAM, 1Tb SSD, AMD FirePro D500 (2) internal GPU
eGPU --> Razer Core X Chroma, AMD Radeon VII, attached through T-bolt3 to T-bolt 2 adaptor attached to T-bolt bus0Port6


ReplyQuote
VmanJeff
(@vmanjeff)
Active Member
Joined: 1 year ago
 

@itsage

@mac_editor

 

OK I took a break from all this as it was driving me nuts. But on a lark during a cold rainy day I decided to disable some PCI to PCI bridges as explained by @AJ_Scarcella on his Bootcamp eGPU Setup post for nMP. I figured since this got me ahead when I was running Win10 build 1903 that I would do it again. But ultimately attempting DSDT override gave me a bricked Bootcamp.

I downgraded Win10 to build 1809 as per the downloads page in this forum. But could not get automate eGPU to work. Possibly because of Catalinas was of using EFI and Apples change to APFS volumes. IDK, couldn't find any info or help to get her to boot with automate eGPU.  Also no DSDT override or any other modifications suggested in various posts were done.

Just disable several PCI to PIC Bridges and see if error 12 would go away.

It did on the second disable. On the third disable my screen flickered and boom....eGPU!

I know much more info is needed but at this point I'll share this...

Disabled (in this order)....

PCI Slot 4 (PCI Bus 21, Device 5, Function 0)

PCI bus 0, Device 30, Function 0

At this point I noticed the yellow triangle on the PIC bus with the eGPU went away. Encouraged I disabled....

PCI Bus 17, Device 10, Function 0

Thats when the screen blanked and a few moments later the eGPU was identified and all three monitors came to life.

To digress I have two monitors hooked up to the eGPU via DP. A 32in LG and a 27in LG. A third display (HDTV) hooked up via eGPU HDMI and also through a separate HDMI coming from the nMP T-bolt Bus1Port1 to an HDMI converter to an external surround amplifier to the HDTV. This is the connection I need to use to boot into win10 as the eGPU was not working. I needed Win10 for various vdeo production reasons so even though the eGPU did not work, the desktop on the HDTV was an OK interim.

So when I disabled the third PCI to PCI Bridge the nMP T-bolt port stopped working and the HDTV went blank. But the other two monitors sprand to life and I though maybe the HDTV connection to the eGPU would also be active now. It was so I have 3 displays through the eGPU at this point.

Some problems I'm seeing.....

 In display settings I cannot change the custom scale factor

The audio to the amplifier no longer works (probably because one of the internal GPU's is now yellow triangled in Device Manager) But I was able to change the audio out to the HDMI output of the Radeon VII) That same internal GPU's is now showing error 43. I think I get why. I need to update the drivers with BootCampDrivers latest.....

There may be more but I'm just happy to get this far as it will make it a lot easier to do my video processing work!

 

My fear now is.... This all just happeded. I have not rebooted the system "for changes to take effect". I know this might solve a problem or two listed above but !! Basking in this success at this moment ...lol

I would question where to go from here.... From my reading it would seem I need to DDU (in safe mode??) and then install BootCampDrivers version.

Here's some screenshots .... Then I'll reboot....and pray

Annotation 2020 02 19 091851
Annotation 2020 02 19 075815
Annotation 2020 02 19 075737
Annotation 2020 02 19 080907
Annotation 2020 02 19 084551

 

 

 

Annotation 2020 02 19 084551

NEW = 27” 2019 iMac i9, 1Tb SSD, 128gig ram, Tb3 port to OWC Thunderbolt3 ProDock to OWC Helios PCIe for eSATA, Tb3 port to Razer Chroma w/AMD Radeon VII, connected via DP to 32” 4K monitor and via HDMI to 47” 4k TV Monitor
Internal Vega 48 for iMac display
OLD = Mac 2013 nMP 12 core Xeon, 48Gig RAM, 1Tb SSD, AMD FirePro D500 (2) internal GPU
eGPU --> Razer Core X Chroma, AMD Radeon VII, attached through T-bolt3 to T-bolt 2 adaptor attached to T-bolt bus0Port6


ReplyQuote
 of  3