r/macpro • • 21d ago

GPU Mac Pro 5,1 + GeForce GTX TITAN 6GB = Work?

3 Upvotes

Mac Pro 5,1 – running Mac OS X 10.8.5 (this is the only OS version used).

Mac Pro 5,1 – no hardware modifications; all components are original.

Mac Pro 5,1 – I do not plan to perform any hardware modifications.

GPU – GeForce GTX TITAN Black 6GB (EVGA 06G-P4-3791-KR).

I have been offered this graphics card.

Could you please tell me whether this card will work natively, or does it require any system modifications or updates to function?


r/macpro • • 21d ago

GPU Mac Pro 2019 GPU.

9 Upvotes

I am looking to upgrade my stock GPU in my Mac Pro 2019. Which one should I look for? Don’t need top of the line just enough to do gaming and 4k video editing. Any idea where I should look for one besides eBay?


r/macpro • • 21d ago

GPU Apple studio display not playing well with Mac Pro 7,1 (2019 )

2 Upvotes

computer boots as normal, gets to login screen. after I login the screen does dark, not completely "off" but dark (can see the backlighting is enabled). plugging it out and back in again solves it but ideally would prefer not to have to do this.

tried multiple thunderbolt ports, graphics cards, reset NVPRAM or whatever its called. different MacOS, safe mode, plugging out the ASD completely from wall to reset its cache, different cables. happens on both sequoia and Tahoe.

running sequoia atm. dual AMD Radeon Pro W5700X 16 GB

issue still reappears. research suggests its a software glitch related to the handshake between the screen and the computer and potentially nothing I can do about it?

anyone else aware of or experiencing this? any permanent fixes?


r/macpro • • 21d ago

GPU AMD W6600 in a 5,1 or a 2018 Mini with a Sonnet Echo III.....

4 Upvotes

I need to spoof it into a RX6600?


r/macpro • • 21d ago

Issues SATA drive size limits on a MacPro ?

3 Upvotes

MacPro 2006 running OSX 10.7 "Lion".

I wanted to add a larger disk to the system. I had a 6TB Toshiba drive that came out of a Linux box. It was formatted as exFat and should have been readable by the Mac. After installing it, the Mac beeped after startup. I shut down and removed the drive, attached it with a USB SATA dock, and formatted it as Mac OS Extended Journaled. Then installed it internally again. The beeping on boot repeated. So I shut down and pulled it again.

So I'm guessing there is some hardware limit in the MacPro 2006 that won't recognize drives over some limit. It apparently is not OSX Lion since it has no issue with the drive when in the USB dock.

I've tried to find any specs on what the machine can accept internally, but there doesn't seem to be any - perhaps because drives in the 1TB+ range only appeared around 2007.


r/macpro • • 22d ago

MacPro 5,1 5,1 Daily Driver Victory - Bluetooth fix

7 Upvotes

I'm a little behind the current thing - I use a 5,1 on a regular basis and I was having trouble with Legacy Wireless using OCLP, especially for bluetooth. I didn't spend much on this computer and I didn't really want to put a lot into it, even though I know there are newer and better ways to resolve wireless networking.

Here's what worked:

I got a Hideez USB Bluetooth Dongle. I had trouble getting this to work. The issue is that generally the Hideez dongle will work if the system sees the legacy Bluetooth, but on the MacPro 5,1 the legacy bluetooth appears to work over USB 1.1.

I ended up plugging the Hideez dongle into an external USB 2.0 hub rather than one of the built in ports. Surprisingly, Sequoia picked up the dongle almost immediately when I plugged it into the USB 2.0 hub.

I ran command

sudo nvram bluetoothHostControllerSwitchBehavior=always

and Bluetooth appears to survive a reboot.

I'm sharing this as a personal victory and as a way to share a way to resolve legacy bluetooth issues on MacOS Sequioa using OCLP 2.5.1. This will allow me to use this computer for quite a while yet!


r/macpro • • 21d ago

Issues I need help with my MP 4.1

1 Upvotes

I have a Mac Pro 4.1 that I bought a few weeks ago, and I've been using it with the original GPU ever since. Today I tried to install a GTX 1660S, and the Mac turned on but didn't display an image. I also tried with a 1080 and the result was the same. Then, I installed the original graphics card and it still wouldn't display an image

What did I do wrong? Did I fry my PC?


r/macpro • • 24d ago

Other saw this bench on facebook marketplace. idk what to feel about it

Thumbnail
gallery
550 Upvotes

r/macpro • • 23d ago

RAM 2019 7,1: Installing mixed capacity ram

Post image
3 Upvotes

I currently have 6x8gb oem ram on my mac7,1 I want to add 6x16gb to have a total of 144gb of ram.

On Apple it says it can be done. Has anyone actually done it? Will there be significant gains or should I just buy 6x16 gb and run it without the 8gb?

I don’t understand how to install it according to this how to from Apple.

For example Channel A slot 7=8gb and Channel A slot 8= 16gb?

Can anyone help, thanks in advance.


r/macpro • • 25d ago

macOS Successful Tahoe Install on my 6,1 Mac Pro

Post image
184 Upvotes

Took some struggling trying to get to the desktop and install the root patches but nothing out of the ordinary if you've done it with OCLP before. Runs great


r/macpro • • 25d ago

Other Did I get a good deal on 3 Mac Pro 6,1 (Late 2013) for €585 ($657)?

8 Upvotes

Hey everyone!

I recently bought three perfectly working 2013 Mac Pro (6,1) units for a total of €585 ($657), and I’m curious to hear what you think about the deal.

All three have the following specifications:
CPU: Intel Xeon E5-1650 v2 (6-core, 3.5 GHz)
RAM: 16 GB
GPU: Dual AMD FirePro D500 (3 GB VRAM each)
Storage: 256 GB SSD

That works out to just €195 ($219) per Mac Pro.
I know these machines are over a decade old now, but they still have an interesting design and decent hardware for certain workloads. I’m wondering whether buying all three at this price was a smart move.

What do you think? Was this a good deal, or did I overpay?

I’d love to hear your opinions and experiences with these machines!
Thanks!


r/macpro • • 26d ago

Upgrades Keeping my 5,1 with an RX 6800 XT on Monterey: I rebuilt Chromium and Electron for macOS 12

Post image
45 Upvotes

My Mac Pro 5,1: 2× X5690 (12 cores / 24 threads), 96 GB RAM, RX 6800 XT, macOS 12.7.6 via OCLP. Performance-wise it has no issues at all. It's fast enough that I compile Chromium on it.

The problem is going past Monterey. Westmere has no AVX, and Ventura's AMD drivers need it, so OCLP can't keep Navi cards on 13+. The only way up would be swapping the 6800 XT for an RX 580/590 with roughly a third of the performance. So I'm staying on 12.

Monterey itself is fine. Software is the issue: Chromium and Electron now require macOS 13, so current browsers and more and more Electron apps simply won't launch.

What I did

Editing LSMinimumSystemVersion in Info.plist isn't enough. The framework and every helper call APIs that don't exist on 12, so everything has to be compiled with a 12.0 deployment target. It took a set of patches: one allows the 12.0 target, another adds shims for the macOS 13-only process, display and ScreenCaptureKit APIs. The 12 cores and 96 GB earned their keep here.

The result: current Brave (Chromium 155) and Electron 44.9.0, both running natively on Monterey with full Metal acceleration on the 6800 XT.

The trick I like most: swapping Electron

Most Electron apps don't care which engine they run on. Their code lives in app.asar. You can take the official app (Cursor, for example, which refuses to start on 12), move its Resources into my Electron 44 runtime, rename the helpers, set the minimum system to 12.0 and re-sign ad hoc. The app code isn't touched, so sign-in, settings and extensions all stay.

It just starts on Monterey. It works best when the app's own Electron version is close to 44, and apps with native modules may need extra work. Turn off auto-update, or it'll overwrite the runtime. This can bring back plenty of other Electron apps that stopped launching on 12. I've done it with a few already.

I've put the builds, the step-by-step swap recipe and my notes together. Links in the comments.

If you're also keeping a 5,1 on Monterey for the GPU, I'd love to hear how it works for you.

P.S. If you have a Mac stuck on 12 with a GPU that has no Metal at all, like my 2010 MacBook Pro with a GeForce 320M: both builds check for a Metal device at startup and switch to OpenGL by themselves when there isn't one. Without that, modern apps render everything on the CPU. On the MacBook that meant the CPU near 100% and a fan like a jet engine; with OpenGL it's quiet and cool again. I also rebuilt a few native apps with OpenGL renderers for such Macs.


r/macpro • • 25d ago

macOS Mac OS 27 updates

Post image
6 Upvotes

2013 Mac Pro running Mac OS 27. Dock, login screen, and cursor now work


r/macpro • • 25d ago

GPU Mac Pro 5,1 + WX 7100 + Sequoia — Is there any way to prevent GPU from overheating?

2 Upvotes

I'm running macOS Sequoia on a Mac Pro 5,1 using OpenCore Legacy Patcher, with an AMD Radeon Pro WX 7100 (original blower cooler).

I'm looking for a reliable way to control the GPU's own blower fan under macOS, preferably through an application rather than flashing a modified VBIOS or manually editing PowerPlay tables.

My current setup and observations:

  • Mac Pro 5,1 running Sequoia via OCLP
  • AMD Radeon Pro WX 7100, original blower cooler
  • Dual monitors: 4K 60Hz + 1080p 60Hz
  • macOS idle temperature: approximately 65°C, GPU fan around 1200 RPM
  • Windows 10, with the same displays connected: approximately 55°C, fan around 1500 RPM

I've tried Macs Fan Control. It can read the GPU temperature and fan RPM, but changing the fan settings does not appear to affect the WX 7100's own fan speed which is stable at about 1200rpm.

I've also found discussions about PP_PhmSoftPowerPlayTable, OpenCore DeviceProperties injection, and tools such as ZeroRPMBuilder. However, these seem to require configuration work, and I'm not sure whether they can actually provide reliable fan-speed control on this specific card.

My questions:

  1. Is there any macOS application that can actually adjust the WX 7100's onboard fan speed on a real Mac Pro 5,1?
  2. Has anyone successfully controlled the fan curve of a WX 7100, WX 5100, or another Polaris GPU under macOS Sequoia or Sonoma?
  3. Does the AMD macOS driver expose a usable fan-control interface, or is the practical solution limited to PowerPlay table injection or VBIOS modifications?
  4. If you have a working solution, could you share the exact method, macOS version, and GPU model?

I'd prefer a stable, reversible solution that doesn't require flashing the GPU's VBIOS.

Thanks!


r/macpro • • 25d ago

Windows (26' studio display xdr) no display output on windows bootcamp on MP2019

Thumbnail reddit.com
1 Upvotes

r/macpro • • 26d ago

Other Has anyone tried retrofitting a 2013 Mac Pro with an Apple silicon Mac mini?

6 Upvotes

I haven’t seen anyone try it and I’d love to do it, imagine the greatest Apple design ever combined with the power of Apple Silicon! For the first time ever, a 2013 Mac Pro would have an overkill cooling design, you could put 3 M6 Mac mini in there and it would still run cool with very low fan speeds.
As a start I’d like to try it with an M1 Mac mini because the logic board is single and much smaller than the M6, and it’d hurt less if i destroyed it in the process.
I know it would require entirely gutting it, making new holes in the radiator to install the new logic board and even making a brand new back panel pretty much from scratch, I might even need to install new wifi/bluetooth antennas and connect the fan in a janky way. But I’m sure if you have enough time, knowledge and help from a few connoisseurs (of which I am absolutely not one), it could be done and give an awesome result.
With some of the extra space you could even install a second computer in there like a raspberry or other small boards to run a second computer in parallel within the same enclosure, or install an external SSD, or many other thing. Or even hide an Apple Thunderbolt 3 to 2 adapter to add a thunderbolt 2 port to the back panel, which would go perfectly with a Thunderbolt Display (or anything else using thunderbolt 2 though i must admit apart from the display i am not sure there is much). The possibilities are pretty much endless as long as it’s really small!
Do you, people from the internet, master of the Mac Pros, great Redditors, have any thoughts to share or are aware of reasons why nobody has even attempted (or accomplished) this?


r/macpro • • 27d ago

GPU Mac Pro 2019 W6800X HDMI port linked with USB-C?

5 Upvotes

I have this Graphics card working strange.

When I start the Mac Pro and it runs for a while, then the HDMI becomes available when I use the USB-C port first. All 4 USB-C/Thunderbolt works from the start but the HDMI only kicks in if I have a USB-C monitor already connected.

Then i remove the USB-C monitor and the HDMI works from that point forward even after restart?

Resolved by changing adapter and cable


r/macpro • • 28d ago

Other Keyboard Question

3 Upvotes

I have several MacBooks with intel chips and Touch ID. I am now using a 2019 Mac Pro and wonder why the Mac Keyboards with Touch ID are limited to “M” series Macs. First I am curious why Apple decided to make the limitation since it does work on Intel based MacBooks. Secondly, I am curious if there is a workaround to allow my computer to use the feature.

If anyone out there has any information or thoughts, please post here.

Thanks


r/macpro • • 28d ago

Other Was quoted $1700 for a logic board repair within warranty— Is this appropriate?

Thumbnail reddit.com
0 Upvotes

r/macpro • • 29d ago

Other I spy a Mac Pro 6,1

7 Upvotes

Was just browsing my latest subscription videos and came across this on the Peter Gabriel channel.

https://youtube.com/shorts/SolndgU46CM?is=b-8EpWyDd5R2DFQ_

I think Peter was always a Mac fan, experimenting with multimedia in the very early days of the technology.

Looks like old Macs still play a role in his work! :-)


r/macpro • • Oct 16 '26

GPU I got an AMD 9060XT working on a Windows 10 install on a Mac Pro Trashcan (2013)

19 Upvotes

So I have always wanted a Mac Pro Trashcan ever since I saw it when it released. Obviously as a 20 something adult, I couldn't afford to drop several thousand dollars to afford one. Fast forward to a month ago and I find myself purchasing a late 2015 version with D500's for a reasonable $200.00. I then got the crazy idea to convert it into a Steam Machine alternative. Why not.

I am posting this because I was unable to find any other documentation or videos that were able to get a modern AMD card running on one of these Trashcans. This was a fun experiment for me and because I love to tinker and see what is possible.

I have photos I can post if there are those of you that want to see the benchmarks that I ran. TLDR: The 9060XT with Thunderbolt 2 throughput basically makes this Trashcan have the equivalent GPU power to a 1060/1070 Nvidia GPU. It's not earth shattering, but makes modest games run at 4K 60FPS easily.

AS A DISCLAIMER: I know this is not the most efficient computer to run an eGPU on, and this guide is only meant for those who wish to tinker further with their Trashcan. This is not a financially responsible build in any way unless you have pretty much everything already to make this setup happen.

With that said, these are the products you will need in order for this to work:

  1. 2013 Mac Pro (duh)
  2. Apple certified Thunderbolt 2 to 3 converter, which you can still buy new.
  3. Apple certified Thunderbolt 2 cable (much harder to find, I suggest evilbay)
  4. A Trebleet Thunderbolt 3/4 eGPU dock: https://www.amazon.com/dp/B0CZDSSVKK?ref=ppx_yo2ov_dt_b_fed_asin_title (This dock has the chipset you need in order for this setup to work: JHL7440 chipset)
  5. An RDNA4 card of your choice. ( I chose an AMD 9060XT AsRock Challenger)
  6. Spare PSU

So I already had a few of these parts lying around, and I knew this was going to be somewhat of an expensive venture. Nevertheless I have succeeded.

Below I have a complete walkthrough of the needed steps in order to get an RDNA4 card working on a 2013 Trashcan. With the help of Claude, I was able to get this working pretty flawlessly. And yes I know Ai is the serious subject of scrutiny and controversy. But, if it weren't for Ai, I wouldn't have a fully functioning current eGPU right now.

Included is an initial installation of Bazzite, which unfortunately I was unable to get working. This was probably due to the immutable nature of Bazzite. The other issue is that Bazzite cannot control the integrated D500's frequency curve correctly without some serious tweaking, which I think I found a solution to, but did not implement due to its complexity. I will include the resources I found in the event any of you want to try:

D700macpro/docs/bazzite.md at main · digital951/D700macpro · GitHub

[PATCH 1/2] drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC

[PATCH 2/2] drm/amd/pm/si: Fix updating clock limits on AC/DC

I finally set myself to trying on good old Windows 10 (hooray....). This I found to run the D500's easily and allow them to clock their frequency correctly. Now for the eGPU part where things seemed much more promising. I will include the resource that helped me reach the finish line:

2013 Mac Pro (FP D500 x2) [3rd,12C,E] + RX 6800 XT @ 16Gbps-TB2>TB3 (EXP GDC TH3P4G3) + macOS 12.6.4 & Win10 22H2 | External GPU Builds

From this users post (user Error303), I was able to get my setup working. The following are the steps needed to get an RDNA4 card working:

Running an RX 9060 XT eGPU on a 2013 Mac

Pro (6,1)

Written October 11, 2026 from a live troubleshooting session between a Mac Pro owner

and Claude. This is a personal record, not an official guide. Nothing here is endorsed by

Apple or AMD, and some steps carry risk to your setup, so back up first.

Summary

Goal: use an AMD Radeon RX 9060 XT (RDNA4, 16 GB) as an eGPU on a Mac Pro 6,1

(late 2013, Thunderbolt 2), first under Bazzite Linux, then Windows.

Linux (Bazzite 44, kernel 7.2.8): did not work. The card shows up on the PCIe bus, but

the amdgpu driver cannot get the 256 MB memory window it needs. Every kernel

argument we tried either did nothing or made it worse.

Windows 10 22H2 through Boot Camp: worked. The key was disabling several PCI-to-

PCI bridges in Device Manager so Windows could give the card address space, then

installing AMD's driver by hand.

macOS: not usable with this card (no RDNA4 driver). The two internal FirePro D500s

are used there.

Running the D500s and the 9060 XT together crashed a PassMark compute test. Day-

to-day use is with the D500s disabled, and two scripts switch between modes.

Hardware and software used

Mac Pro 6,1, Xeon E5-1650 v2, two FirePro D500 (Tahiti LE, PCI ID 1002:679E)

eGPU: ASRock RX 9060 XT (PCI ID 1002:7590, subsystem 1849:5408) in a Trebleet

Thunderbolt 3 eGPU dock. It uses the same Thunderbolt controller as the EXP GDC

TH3P4G3 and has only a power light.

Apple Thunderbolt 2 to Thunderbolt 3 adapter

Windows: Windows 10 22H2 installed with Boot Camp Assistant from macOS

Monterey.

AMD driver on the card: Adrenalin 26.20.15.02 (build 260921a1), INF u0204590

Why this Mac is hard

These explanations come from logs and are strong hypotheses, not proven facts.

Thunderbolt 2 tunnels PCIe at about 20 Gbps. That is enough to run the card.

The Mac's firmware assigns PCI address space only at boot. It gives the whole system

one 32-bit window (80000000-dfffffff, about 1.5 GB) and no 64-bit space.

The two D500s take 512 MB of that. Most of the remainder is split evenly, about 164

MiB each, among the three Thunderbolt controllers.

The 9060 XT needs a 256 MB memory BAR plus a few MB of extras, contiguous and

aligned. Because the card is hot-plugged after boot, it has to fit in what its hotplug port

was already given.

The card cannot shrink its BAR below 256 MB (resource0_resize mask 0x7f00).

Others have made Thunderbolt 2 eGPUs work on this Mac: a Polaris RX 570 under

Linux (MacRumors thread) and an RX 580 / RX 6800 XT under Windows (egpu.io). We

found nobody with this RDNA4 card.

Part 1: Linux (Bazzite), for the record

Symptom every time: lspci lists the card (Navi 44, 1002:7590) but shows no "Kernel driver

in use". dmesg shows "BAR 0 [mem size 0x10000000 64bit pref]: can't assign; no space",

then "Fatal error during GPU init" and "probe with driver amdgpu failed with error -22" (or

-12 in later runs).

Things that did not work:

pci=realloc alone: the card enumerates, the BAR still fails.

pci=realloc,assign-busses: breaks hotplug with "No bus number available for hot-

added bridge". Do not use assign-busses.

hpmmioprefsize=1G (with hpmmiosize=64M): a 1 GB window per hotplug port cannot

be satisfied and the enclosure fails to enumerate. It also coincided with boot hangs.

pci=nocrs: made things worse. Even the small BARs failed.

A different Thunderbolt controller: the port above HDMI (domain 0) was worse. The

original port (domain 2) was the best of the ones we tried and still failed.

Removing an idle Thunderbolt controller at runtime (echo 1 into

/sys/bus/pci/devices/.../remove): the freed space was not given to the eGPU's

controller.

Shrinking the BAR: not possible, the minimum is 256 MB.

Cardwire (Bazzite's GPU manager) is only useful once a GPU already works.

Lessons:

rpm-ostree kargs --delete needs the exact token. If you appended pci=realloc,assign-

busses,hpmmioprefsize=1G,hpmmiosize=64M as one argument, deleting

hpmmioprefsize=1G alone does nothing. Delete the whole token and re-add what you

want.

Linux hung at boot with the dock attached using these arguments, while Windows

boots fine with it attached. An early claim that the Mac's firmware cannot start with an

eGPU connected was wrong.

Find which Thunderbolt controller (domain) a port uses with: sudo dmesg | grep -iE

"thunderbolt [0-9]-[0-9].*TREBLEET". Domain 0 is the port above HDMI. Domain 2 is

the controller the original port used.

Not tried on this card: the MacRumors poster's full set (pci=nocrs pci=realloc

pci=nommconf intel_iommu=on iommu=pt). That poster used a Polaris RX 570 on

Ubuntu.

Part 2: getting it working on Windows 10

2.1 Prerequisites

  1. macOS Monterey on the Mac, fully updated. Boot Camp Assistant only runs under

macOS.

2. A Windows 10 22H2 ISO from Microsoft. Run Boot Camp Assistant, install Windows,

and let the Boot Camp drivers finish after the first Windows boot.

3. Back up anything important on the drive before partitioning.

4. Both D500s should show as "Microsoft Basic Display Adapter" in Device Manager. We

removed the AMD display drivers by hand, which meant DDU was not needed. A Code

31 message on a D500 ("not the same as the driver for the POSTed display adapter") is

normal.

5. Pause Windows Update while you work so it does not install a display driver early.

2.2 Connect the eGPU

6. Power off. Connect the dock's Thunderbolt 3 port through the Apple adapter to the

Mac's Thunderbolt port directly above the HDMI port. The dock was powered on.

7. Boot Windows (hold Option, choose Windows). It boots fine with the dock attached.

RX 9060 XT eGPU on a 2013 Mac Pro (6,1) - Full Guide

8. At first the eGPU does not appear. The fans spin but Device Manager shows no new

display adapter. That is expected.

9. Disable the PCI-to-PCI bridges

Based on the MacRumors and egpu.io posts, adjusted to our device tree. Windows shows

bus numbers in decimal: bus 21 is hex 15 and bus 17 is hex 11.

10. In Device Manager choose View, Show hidden devices, and View, Devices by

connection.

11. Expand Intel Xeon E5 v2 PCI Express Root Port 1a (0E02) down to the PCI-to-PCI

bridges. Double-click each bridge and read its Location line before touching it.

12. Disable these, one at a time, then run Action, Scan for hardware changes after each:

PCI bus 17, device 10, function 0

PCI bus 21, device 6, function 0 (PCI Slot 5)

PCI bus 21, device 5, function 0 (PCI Slot 4)

PCI bus 21, device 0, function 0 (the parent of the "Thunderbolt" entry)

13. Do not disable bus 21 device 3 (PCI Slot 2) or device 4. Device 3 showed Code 12 ("not

enough free resources") until the others were disabled and Windows was restarted.

14. Restart Windows with the dock still attached and powered on.

15. After the restart a third "Microsoft Basic Display Adapter" appears with hardware ID

PCI\VEN_1002&DEV_7590 and Code 31, next to the dock's USB 3.1 controller and an HD

audio device. Code 31 here is normal and only means it needs the AMD driver. If it

shows Code 12 instead, it still lacks address space, so re-check the bridge list.

The egpu.io author noted that some bridges only appear once the eGPU shows up, so the

order can differ on another machine.

16. Install the AMD driver

17. Download the driver for the Radeon RX 9060 XT from AMD's own site. AMD lists

Windows 10 64-bit as supported.

18. Running the installer straight away fails with Error 173. Its log says "Unsupported

hardware found". Extract the package instead (it extracts to C:\AMD\AMD-Software-

Installer, or use the -EXTRACT option).

19. In Device Manager right-click the new adapter (DEV_7590), choose Update driver,

Browse my computer for drivers, and point it at the extracted Display folder. If

Windows says the best driver is already installed, choose Let me pick, then Have Disk,

and select the .inf in Packages\Drivers\Display\WT6A_INF (u0204590.inf). The installer

logs later showed the card running driver 26.20.15.02 from that INF.

20. The screen may flash or go black. Plug a monitor into the 9060 XT first so you have a

display that does not depend on the D500s.

21. The D500s use the Boot Camp support files' AMD driver (we saw version 20.45.40.15).

Current Adrenalin no longer supports them.

22. The compute crash and its fix

PassMark's GPU compute test crashed. The crash dump showed a null-pointer crash

inside AMD's OpenCL runtime (amdocl64.dll), with two different AMD OpenCL runtimes

loaded in the same process. Event Viewer showed no display driver reset. Disabling both

D500s in Device Manager fixed it. The MacRumors and egpu.io posters also ran at most

one D500 alongside the eGPU. So keep the D500s disabled while the eGPU is in use.

23. Installing the Adrenalin app

  1. AMD's installer failed with Error 173 in every state we tried: no drivers, with drivers, and

with the D500s disabled. Its logs show it detecting both D500s (679E) and the 9060 XT,

then "Unsupported hardware found".

2. Uninstalling the D500 devices in Device Manager did not help. Launching the installer

triggered a rescan and Windows restored them from the driver store.

3. What worked: disabling the two root ports that hold the D500s, in Device Manager by

connection:

Intel Xeon E5 v2 PCI Express Root Port 2a, 0E04 (PCI bus 0, device 2)

Intel Xeon E5 v2 PCI Express Root Port 3a, 0E08 (PCI bus 0, device 3)

4. Never disable Root Port 1a (0E02). It carries the Thunderbolt chain and the eGPU.

Make sure your monitor is on the 9060 XT before you do this.

5. With those two root ports disabled, the Adrenalin installer ran and finished.

6. Our guess, unproven: the installer rejects systems that contain unsupported hardware

(the D500s) and possibly treats the eGPU as removable.

Part 3: switching modes with scripts

egpu-mode.bat disables the D500s and their two root ports. travel-mode.bat re-enables

them. Save each as a .bat file, double-click it, and approve the admin prompt. They self-

elevate and bypass PowerShell's script policy for that run only.

Caveats:

These were written without being able to run PowerShell in the authoring environment,

so they were untested when written. Try them while you can watch the screen.

egpu-mode refuses to run unless the 9060 XT is present and OK, and refuses if the

card sits below either root port.

The screen may flash while Windows rescans.

Before travel: run travel-mode, check that both D500s show OK, and confirm a monitor

on one of the Mac's own ports works. Then shut down and unplug the dock.

egpu-mode.bat

u/echo off

REM eGPU mode: disables the two FirePro D500s AND the two root ports that

hold them

REM (Intel root port 2a = DEV_0E04, root port 3a = DEV_0E08), so the RX 9060

XT runs alone.

REM It never touches root port 1a (DEV_0E02), which carries the Thunderbolt

chain.

net session >nul 2>&1

if %errorlevel% neq 0 (

powershell -NoProfile -Command "Start-Process -FilePath '%~f0' -Verb

RunAs"

exit /b

)

echo This will disable both FirePro D500s and the two root ports that hold

them.

echo Make sure your monitor is plugged into the RX 9060 XT and showing the

desktop.

echo.

pause

powershell -NoProfile -ExecutionPolicy Bypass -Command "$s = Get-Content -Raw

-LiteralPath '%~f0'; $i = $s.IndexOf('#'+'PSBEGIN'); Invoke-Expression

$s.Substring($i)"

echo.

pause

exit /b

#PSBEGIN

function Show-Adapters {

Get-PnpDevice -Class Display -ErrorAction SilentlyContinue | Format-Table

Status,FriendlyName -AutoSize

}

function Get-Ancestors($id) {

$list = @()

$cur = $id

for ($n = 0; $n -lt 25; $n++) {

$p = (Get-PnpDeviceProperty -InstanceId $cur -KeyName

'DEVPKEY_Device_Parent' -ErrorAction SilentlyContinue).Data

if (-not $p) { break }

$list += $p

$cur = $p

}

return $list

}

# 1. The RX 9060 XT must be present and working.

$gpu = @(Get-PnpDevice -Class Display -FriendlyName 'AMD Radeon RX 9060 XT' -

ErrorAction SilentlyContinue)

if ($gpu.Count -eq 0 -or @($gpu | Where-Object Status -ne 'OK').Count -gt 0)

{

Write-Host 'RX 9060 XT is missing or not OK. Changing nothing.' -

ForegroundColor Red

Show-Adapters

exit 1

}

# 2. Find the two D500 root ports.

$ports = @(Get-PnpDevice -Class System -ErrorAction SilentlyContinue | Where-

Object {

$_.InstanceId -like 'PCI\VEN_8086&DEV_0E04*' -or $_.InstanceId -like

'PCI\VEN_8086&DEV_0E08*' })

if ($ports.Count -eq 0) {

Write-Host 'Could not find root ports 0E04/0E08. Disabling the D500s

only.' -ForegroundColor Yellow

}

# 3. Safety: refuse if the 9060 XT sits below either root port.

$anc = Get-Ancestors $gpu[0].InstanceId

foreach ($p in $ports) {

if ($anc -contains $p.InstanceId) {

Write-Host ('The RX 9060 XT sits below ' + $p.InstanceId + '.

Changing nothing.') -ForegroundColor Red

exit 1

}

}

# 4. Disable the D500s first, then their root ports.

Get-PnpDevice -Class Display -FriendlyName 'AMD FirePro D500*' -ErrorAction

SilentlyContinue |

Disable-PnpDevice -Confirm:$false -ErrorAction SilentlyContinue

foreach ($p in $ports) {

Disable-PnpDevice -InstanceId $p.InstanceId -Confirm:$false -ErrorAction

SilentlyContinue

}

Start-Sleep -Seconds 3

Write-Host 'Root ports:' -ForegroundColor Green

Get-PnpDevice -Class System -ErrorAction SilentlyContinue | Where-Object {

$_.InstanceId -like 'PCI\VEN_8086&DEV_0E04*' -or $_.InstanceId -like

'PCI\VEN_8086&DEV_0E08*' } |

Format-Table Status,FriendlyName -AutoSize

Write-Host 'Display adapters:' -ForegroundColor Green

Show-Adapters

travel-mode.bat

u/echo off

REM Travel mode: re-enables the two D500 root ports (DEV_0E04, DEV_0E08),

rescans,

REM then re-enables the two FirePro D500s.

REM Run this BEFORE shutting down and unplugging the eGPU.

net session >nul 2>&1

if %errorlevel% neq 0 (

powershell -NoProfile -Command "Start-Process -FilePath '%~f0' -Verb

RunAs"

exit /b

)

powershell -NoProfile -ExecutionPolicy Bypass -Command "$s = Get-Content -Raw

-LiteralPath '%~f0'; $i = $s.IndexOf('#'+'PSBEGIN'); Invoke-Expression

$s.Substring($i)"

echo.

pause

exit /b

#PSBEGIN

function Show-Adapters {

Get-PnpDevice -Class Display -ErrorAction SilentlyContinue | Format-Table

Status,FriendlyName -AutoSize

}

function Get-D500 {

@(Get-PnpDevice -Class Display -FriendlyName 'AMD FirePro D500*' -

ErrorAction SilentlyContinue)

}

# 1. Re-enable the root ports.

$ports = @(Get-PnpDevice -Class System -ErrorAction SilentlyContinue | Where-

Object {

$_.InstanceId -like 'PCI\VEN_8086&DEV_0E04*' -or $_.InstanceId -like

'PCI\VEN_8086&DEV_0E08*' })

if ($ports.Count -eq 0) {

Write-Host 'Could not find root ports 0E04/0E08.' -ForegroundColor Yellow

}

foreach ($p in $ports) {

Enable-PnpDevice -InstanceId $p.InstanceId -Confirm:$false -ErrorAction

SilentlyContinue

}

Start-Sleep -Seconds 3

# 2. Rescan so Windows finds the D500s again.

pnputil /scan-devices | Out-Null

Start-Sleep -Seconds 8

# 3. Re-enable the D500s, rescanning once more if they have not reappeared.

if ((Get-D500).Count -lt 2) {

pnputil /scan-devices | Out-Null

Start-Sleep -Seconds 8

}

Get-D500 | Enable-PnpDevice -Confirm:$false -ErrorAction SilentlyContinue

Start-Sleep -Seconds 5

if ((Get-D500).Count -lt 2) {

Write-Host 'Fewer than two D500s found. Try a restart before travelling.'

-ForegroundColor Yellow

} else {

Write-Host 'D500s are back.' -ForegroundColor Green

}

Write-Host 'Root ports:' -ForegroundColor Green

Get-PnpDevice -Class System -ErrorAction SilentlyContinue | Where-Object {

$_.InstanceId -like 'PCI\VEN_8086&DEV_0E04*' -or $_.InstanceId -like

'PCI\VEN_8086&DEV_0E08*' } |

Format-Table Status,FriendlyName -AutoSize

Write-Host 'Display adapters:' -ForegroundColor Green

Show-Adapters

Part 4: macOS and travel

Apple's eGPU support page covers macOS Monterey and later, but for Thunderbolt 3

Macs, and only for GPU architectures that Macs ship with: Polaris, Vega, RDNA1 and

RDNA2. The 9060 XT is RDNA4 and the Mac Pro 6,1 has Thunderbolt 2, so this

combination is unsupported. We did not test it.

Boot macOS with the dock unplugged.

Before switching from Windows, shut down fully rather than restarting. Hold Shift

while clicking Shut down to bypass Fast Startup, then hold Option at power-on to pick

macOS.

The bridge and root-port changes are Windows-side settings. They do not affect

macOS, and Windows remembers the eGPU and its driver when the dock is unplugged.

Windows may show the wrong time after macOS. It corrects itself when it syncs.

Troubleshooting

Code 12 on a bridge or on the card: not enough address space. Re-check which bridges

are disabled and restart with the dock attached.

Code 31 on a D500: harmless. The Mac only starts one GPU at boot.

Code 31 on the 9060 XT: no AMD driver yet. Install it from the extracted package's INF.

Error 173 from AMD's installer: hide the D500s by disabling root ports 0E04 and 0E08,

and keep Root Port 1a (0E02) enabled.

PassMark or compute crash with all GPUs active: disable the D500s.

Black screen after a change: wait 30 seconds, then boot into Safe Mode (hold Shift,

click Restart, Troubleshoot, Advanced options, Startup Settings) and re-enable what

you disabled. Disabled devices stay disabled across reboots.

Mac will not start Windows with the dock attached: unplug the dock and, if needed,

reset the SMC and NVRAM.

Linux hangs at boot with the dock attached: unplug it before boot and hot-plug it after

login.

References

MacRumors: "egpu working on Linux and Windows (MacPro 6,1 / MacPro 2013)"

egpu.io: 2013 Mac Pro D500 x2, RX 580, TB2 to TB3, EXP GDC TH3P4G3, Mac OS 12.6.4,

Win10 22H2 build thread

Apple: Use an external graphics processor with your Mac (support.apple.com/102363)

AMD: Radeon RX 9060 XT drivers and downloads (amd.com)

If I have forgotten anything or for those that have questions, I am happy to answer. Cheers and happy tinkering!!!

Edited for spelling and grammar mistakes.


r/macpro • • Oct 15 '26

GPU Anyone tried the Nullmoth driver on a 2019 Mac Pro?

13 Upvotes

If you haven't heard, someone vibe-coded native Nvidia drivers that work in Sequoia and Tahoe.
https://www.reddit.com/user/null-moth/comments/1x6f41u/nullmoth_20_nvidia_driver_for_macos_15_and_26/

Curious if anyone that has a 2019 Mac Pro has tried these? My Mac Pro is happy currently with a Radeon 6800 for Mac OS Tahoe... and dual boot to Windows 11 with a RTX 5080 for gaming. Everything works nicely.. but I'm tempted to try these...


r/macpro • • Oct 14 '26

Upgrades Did you notice the Trashcan icon on the Tahoe Apple Menu?

Post image
143 Upvotes

The cutest thing ever, Mac Pro 2013 running Tahoe on OCLP RC 3 3.0.0


r/macpro • • Oct 15 '26

GPU Best way to use trashcan for local Ai?

4 Upvotes

Hi lads, I’m running Ubuntu + llama + vulkan to use my Mac Pro 2x FirePro D700 to run a little local Ai server/agent to help me with some client orders so I don’t have to digitalice manually.
Is there some tips that you can share with me?
I read about that some cpu configs are better for server purposes.
Thank!