Radeon Pro Duo + Akitio Node
Has anyone successfully installed a Radeon Pro Duo in an Akitio node? The card I purchased is not being detected in Windows 10, although it seems to power up just fine*. I've had success with 98o ti, 1080 and a 1080 Ti being detected right away and usable, but not the Radeon Duo.
*to power up the Duo, I've temporarily rigged two 400W PSU to act like a single 800W.
- MSI PC laptop with thunderbolt
- Windows 10 64bit
- Akitio Node + Radeon Pro Duo
Unfortunately Radeon Duo (or any dual-GPU graphics card) is not supported in XConnect. At best, one of the internal GPUs will light up, but the second one won't.
thanks, that makes sense.
I tried the Pro Duo yesterday. The good news is it works in an eGPU enclosure (Mantiz Venus 550W PSU). The not so good news is it's the same performance as the Fury X. More interestingly is that Windows sees the card as two separate GPUs. One was functional, the other one was throwing error 12. Attached is a screen cap of Unigine Superposition benchmark I ran on it through a Razer Blade Stealth 4K internal display. The average FPS in 4K was mid 20s as you can see. However, with FreeSync enabled the on-screen motion was very decent.
This thing is quite a beast to hold. I was very impressed with its build quality. Gathering three 8-pin PCIe power cables to run this GPU is also a task. I tried the AKiTiO Node and Sonnet Breakaway Box. While these two enclosures could power the card on, they clearly did not have enough juice for the eGPU to function. The Mantiz Venus with its 550W Gold PSU was able to handle this graphics card. There's no way the radiator and hoses can fit inside the enclosure though.
Myabe fixing error 12....
Myabe fixing error 12....
Yes, Microssoft needs to fix Windows problem with error 12 as far as GPUs are concerned.
It is more complicated guys. Mcarver, please PM me.
Do we have any update on this? I would be interested to know.
Recently I tried to CrossFire between AMD Radeon R9 Nano (installed internally - CPU PCIe x16) and AMD Radeon R9 Nano (Aorus Gaming Box eGPU). My rationale was that since they removed the CrossFire bridge, they would no longer need to be next to each other. For Nvidia, you will either need to make an unusually long SLI bridge, or find a way to mount them close together.
The options showed up (latest drivers, Win10-Pro 64-bit) for CrossFire, but when clicked, the displays flickered and it reappeared with the AMD Settings frozen in the background and it needed to be killed. I think it is something to do with it loading the XConnect driver (I presume their standard driver crashes like the Linux one does if eGPU is suprise removed).
Hint: want to crash Linux hard? Yank out a Radeon eGPU without doing "echo 1 | sudo tee /sys/bus/pci/devices/..../remove" first.
But yeah, I do wonder if the CrossFire can be enabled for a dual-GPU graphics card in one eGPU enclosure - or two cards in the same enclosure with PCIe bifurcation. If anybody knows how to trick it into loading the standard driver for eGPU, then I reckon both the Radeon Pro Duo, and CrossFire between separate GPUs, can work.
@Sky11 if you represent AMD then you guys really need to look at the Linux driver, particularly for AMD Fiji GPUs.
R9 280X - works fine on Linux and Thunderbolt 3, as far as I can tell
R9 Nano - has atom bios loop when used with Linux and Thunderbolt 3 and other much more disturbing problems if you use tricks to get this part to succeed
My friend with eGPU RX 480 is too busy to try it on his
If I try with one Thunderbolt 3 port of the laptop (fails every time) then usually using the other port succeeds most of the time. But there are more problems....
With the R9 Nano (Fiji XT), you also get dmesg warning stack dumps if attaching an external monitor to eGPU. If you are using Linux 4.17-rc1 with amdgpu.dc=1 by default for all GPUs, inserting an external monitor on the eGPU locks the kernel up *hard*.
Surprise removal of any Radeon locks Linux up hard. Windows can handle surprise removal, so why has this not been ported to Linux?
External GPUs are not so reliable yet that this can be acceptable. If it has an error or shuts off with thermal cutoff, we cannot have it taking the kernel down with it and us losing work.
Plus it would be convenient to not have to "echo 1 | sudo tee /sys/bus/pci/devices/..../remove" first.
Also need to insert some sysfs entries in /sys/class/drm for changing the fan / cooling profile. I would like it to prefer cooling over silence. In Windows, this can be achieved. On Linux, it seems difficult with the amdgpu.ko.
Last thing, the amdgpu-pro driver does not support modern kernels since they changed something about fence.h. I could use an old kernel, but then I lose Thunderbolt support at around 4.13 or 4.14.
Either way, I hope AMD reads all of my reports, one way or another.
- Radeon Pro Duo: I cannot say much yet, but later this year there will laptops with which it will start working :).
- CrossFire between internal and external GPU - for the love of God and Queen of England, please don't do it. AMD does not and will not support CrossFire between internal and external GPUs because it cannot work properl.
However, AMD does have a technology which works with internal and external GPUs: https://pro.radeon.com/en/software/prorender
@goalque - are you saying that you had 2 external R9-390, connected to the same MacBook, and you saw CrossFire checkbox in Radeon Settings?
If yes, were you able to run anything using CrossFire? any performance gains?