I NEEDED to make a new post to get an answer for the old one because anything older than 20 hours (which is not cared about by enough people) falls into the Memory Hole.
.
Inb4 anyone asks “why can’t you just google” or “just spam the Devs”:
I have already “just google’d”, ONLY other forum posts asking for help WITH NO RESULTS came up.
Spamming the Devs will just get me banned, and it’s asshole behavior.
Regressing the Mesa drivers to the latest Mesa 24 release MAY just solve this, but I don’t want to do that for obvious reasons (which I STILL have to preventively list):
Newer Fedora KDE releases may need something from newer Mesa releases.
It’s very hot where I live so I missread the previous post, going off an assumption.
It’s been a while since last time I worked on that PC because I have been busy.
Now too it’s too hot for me to “digest” what is said here:
Long story short:
Since I don’t care about “the deep lore” of Linux incantations, ESPECIALLY NOW that it’s almost 30 italian degrees where I live, can I just get a set of instructions which are SURE to work and a short description about what they do?
What this does is update your bootloader (GRUB) to pass radeon.cik_support=0 and amdgpu.cik_support=1 to the Kernel, which tells radeon driver to not initialize and let amdgpu take over for your hardware.
I don’t know why the default is not to use amdgpu for these old hardware, but there might be issues when you switch over. If you want to undo the changes, run:
If you could not boot (i.e. black screen), you can edit the kernel command line at GRUB screen by pressing e and manually remove the two added parameters, then press Ctrl-X to boot. Afterwards run the above command to clear them out permanently.
With that said, if this issue was caused by an upgrade (and ideally you verified it), please file a bug so the problem can be fixed by Fedora maintainers.
I’ll apply it as soon as the other PC becomes available once again.
In regards of the “bug report” I’ve already filed a couple, but to MESA themselves, as I got told that “this issue is with them, not the Fedora teams”.
.
The issue was partially fixed in Mesa 25.0.x (something), but then it just came right back again.
I made this post here because, other that the quote down here, the second MESA report ended up having no further communications on it, so I didn’t get the answer I sought, which you may have just brought me.
Anyhow, with the parameters added, can you post the output of sudo journalctl -b 0 -k?
In case the output is too long, you can redirect it into a file then upload it to pastebin using: sudo journalctl -b 0 -k | fpaste, then send the link here.
I’d like to have the output of fpaste --sysinfo --printonly as well.
It’ll be some time before I can get to work on that PC again.
In the meantime please click on the second MESA link in Message_5; there already are a lot of files on there which shouldn’t have changed at all since when I uploaded them.