Framework Desktop not recognizing EGPU without BIOS reflash - fixable in linux, or should I contact framework?
Here's a summary of my issue:
https://community.frame.work/t/egpu-not-recognized-on-framework-desktop-get-cable-property-failed-5/82392/6
Essentially, I discovered that my A500 GPU does not get recognized at all in my framework desktop, just giving that cable error every framework user appears to get based on my research, but the device works fine on another Thunderbolt setup.
I assumed, perhaps TB3 just isn't supported by the framework, and this is my fault, until I did a bios reflash... and the device registered. It worked fine in Windows and appeared in Linux, until unplugged and replugged, in which it once again lost all recognition, even with a cold shutdown and reboot.
This persists until, once again, I reflash the BIOS to a new revision - in which, once again, the device will appear - again, surviving restarts and appearing on both OSes - until I unplug and replug. Then, bamn - gone.
My Question:
I do not need the device to work in Windows, just Linux. Is it possible that some OS level flag, feature, or otherwise could recover this situation? Or am I SOL, and should just contact framework directly? I'm worried that, since my usage of an EGPU is technically an edge case, that framework won't care or blame this issue on me, and I will just look kinda dumb.
I have indeed tested full functionality on technically two devices now - with multiple unplugs, using the same cabling. I am 100% confident the FW desktop itself is at fault.