It’s the time of the year - the holidays - when you tax your AMD GPU a little bit more than usual, because you maybe want to play a game or do some other fancy stuff that is somewhat more taxing than drawing an DE window in a ten year old OpenGL 3.3 implementation.
It’s heart-warming to see all the AMD bugs that fill the mesa bug tracker for years are still alive and kicking.
You can despise nvidia, but you have to respect them. They deliver if you play by their rules. But AMD? They pretend and fail hard. Over and over and over. And let’s not even go into HIP/rocm or the dark pit of video en-/decoding.
Hopefully Intel prevails in the discrete GPU market. There needs to be more competition.
I didn’t see this card before. Was only looking at the 7900xt and 7900xtx
Edit: I like the 6750xt because it’s price point was fantastic. I would have to get a Nvidia 3070 or 3070 Ti. Probably the TI to be better than this. Depends on who you ask or what review you look at. Too many biased opinions.
not sure what you are on about.
Did not have any notable bugs and always had great performance on my RX480, after that on the Vega64 and now on my 6750XT … something on your system seems to be broken.
lol - their discrete GPU’s are not even supported by their open source driver on linux, the only way you can run them is on modesetting and that is months after the release … way to go. They definitely won’t make it into my systems if they continue that way …
amdvlk is not installed by default and has weak performance - not sure why anyone would install it anyway. Removing xf86-video-amdgpu disables many features - not recommended and also not needed.
Simply install vulkan-radeon and lib32-vulkan-radeon and you won’t need to modify anything else.
i managed to get that ring gfx_0.0.0 timeout on my 6750 XT, too - but the reason was easily found. It happened within an hour after increasing my GPU undervolting value in corectrl, after reverting to the former value, my system was stable again for many hours of gaming.
Maybe you are also doing undervolting and did it too far …
That’s just the generic error that kernel lost connection to the GPU, which can happen for all kinds of reasons. Triggering a hardware failure due to undervolting is probably one of them.
I have seen many ring gfx_0.0.0 timeouts in last three months. They usually happening when I am just browsing web. I did not have any of these issues before kernel went 6.0.* But again this might be a bad GPU, Mesa, Picom or anything so it is very hard to debug… I can’t blame only Linux or Mesa because I had my share of problems also in Windows with Navi series cards. My wife has older RX570 and it has been rock solid.
My GPU is RX6600 (no undervolting or OC)
Latest soft reset points to Picom but I had tons of these even on Wayland.
