- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 142
- Reaction score
- 7
Boys, has anyone dealt with this specific FPGA error on the newer DMA cards lately?
Picked up a 3rd Gen 35T and a 6th Gen 75T from Captain DMA, but I am hitting a wall. Getting a consistent FPGA error on both cards even after flashing the test firmware. I have already stripped back the BIOS—disabled IOMMU and Virtualization—but it is a no-go.
The 75T is throwing a constant green flash, but the host machine just refuses to acknowledge it properly. I am currently running the connection through a PCIe extension on a Thunderbolt/USB 4.0 port.
I have run DMA setups before on older hardware without a single hiccup, so I know the drill, but this architecture is being stubborn. Could it be a Thunderbolt lane mapping issue, or am I missing a quirk with these newer Gen 6 boards?
Has anyone else faced a handshake failure with these specific units on a laptop/eGPU-style setup, or is there a specific firmware/driver chain I should be looking at? Drop your thoughts below—if you have fixed this specific FPGA error, I am all ears.
Picked up a 3rd Gen 35T and a 6th Gen 75T from Captain DMA, but I am hitting a wall. Getting a consistent FPGA error on both cards even after flashing the test firmware. I have already stripped back the BIOS—disabled IOMMU and Virtualization—but it is a no-go.
The 75T is throwing a constant green flash, but the host machine just refuses to acknowledge it properly. I am currently running the connection through a PCIe extension on a Thunderbolt/USB 4.0 port.
- Technical Setup: Running a clean environment, drivers re-installed, yet the hardware handshake fails at the FPGA level.
- Troubleshooting So Far: Swapped from the 35T to the 75T assuming a hardware dud, but the symptoms remain identical.
- Current Status: Everything is clean on the BIOS side, but the device isn't showing up as it should.
I have run DMA setups before on older hardware without a single hiccup, so I know the drill, but this architecture is being stubborn. Could it be a Thunderbolt lane mapping issue, or am I missing a quirk with these newer Gen 6 boards?
Has anyone else faced a handshake failure with these specific units on a laptop/eGPU-style setup, or is there a specific firmware/driver chain I should be looking at? Drop your thoughts below—if you have fixed this specific FPGA error, I am all ears.
