I didn't see any vehicles. Or tanky classes. Or any support classes.
Looks not that much Tribes to me. Where is the fun if I can't fly a bomber over an enemy base that gets defended by engineers repairing canons and tanks shooting the shit out of the sky?
Might as well simply play Midair 2 then (which also doesn't have vehicles).
dmesg shows the same errors as in the referenced bug ticket. So I don't think missing firmware is the issue. I would not be surprised however, if the problem in general is a combination of amdgpu and firmware behavior. (IMO the hardware should not crash as hard as it does, so the firmware seems to be a bit wonky too)
While it's a possibility, I think it's unlikely, since the machine works fine with Windows. I also compiled the tkg 6.7.2 kernel which includes the revert-patch for the offending change and so far the machine booted three times without issues, so it seems to fit.
At least with my 1060 compositing wasn't an issue. But true, I rarely used Wayland. Do you have specific issues when compositing is enabled or do you just prefer the simpler rendering?
As I said... I had a lot of trouble in the past and went with nvidia most of the time. It wasn't just a quick shot picking that specific AMD card. My research ended up looking positive. The 6000 series wouldn't have cut it, since the AV1 encoder isn't good enough (or maybe not present at all; I forgot). I also buy this thing to last a few years, so having to take a card from the last generation would have certainly be the point where I just picked nvidia again.
I've set up Fedora Workstation 39 with hibernate to rule out potential issues caused by my current system. Rebooting from Linux to Linux still leads to dark boots before reaching the OS. This has kernel 6.6.12. Cold boots seem to be fine after having cut power to the PSU earlier.
So I fear that there is still a deeper issue somewhere. But I'll see what happens after those fixes get backported to 6.7 and hit archlinux. Until then I might have to live with Windows or don't reboot too often. I have yet to figure out how long I need to keep this machine off the power for it to behave like a cold boot. 10s apparently didn't cut it in my latest try (it's a new PC so I still have to learn its quirks).
I have the same problem with the LTS kernel. Just tried.
First time it booted but locked up on shutdown. The next cold boot it immediately went to black screen after loading amdgpu. ([drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed). Next boot too. All with kernel 6.6.14.
I am running Arch here as well. Most people who referenced that issue I linked also seem to come from Arch. So it seems like a problem due to the "latest" kernel. I don't accept this as an excuse, though. It's still a stable kernel an I don't expect drivers to be published that were not tested in advance. And it looks like this has happened here. Maybe bad timing on my part and this was/is the only hiccup in a long time (see "cursed"), but I guess I'll find out.
Even sex?