> AMD are competent, they just have sucky crash-prone GPU drivers.
I have an AMD GPU on my desktop PC and I also have a Steam Deck which uses an AMD APU. Never had a driver crash on me on either system.
I have an AMD GPU on my desktop PC and I also have a Steam Deck which uses an AMD APU. Never had a driver crash on me on either system.
The issue is when using ROCm. Or more accurately when preparing to crash the system by attempting to use ROCm. Although in fairness as the other commenter notes it is probably a VRAM issue so I've been starting to suspect maybe the real culprit might be X [0]. But it presumably doesn't happen with CUDA and it is a major blocker to using their platform for casual things like multiplying matricies.
But if CPU and GPU share a memory space or it happens automatically behind the scenes, then the problem neatly disappears. I'd imagine that was what AMD was aiming for and why they tolerated the low quality of the experience to start with in ROCm.
[0] I really don't know, there is a lot going on and I'm not sure what tools I'm supposed to be using to debug that sort of locked system. Might be the drivers, might be X responding really badly to some sort of OOM. I lean towards it being a driver bug.
Ah yes. I'm pretty much only using it for games. It does seem that AMD's AI game is really lacking, from reading stuff on the Internet.