Interesting, so it's likely either the kernel update to 5.9.x or the fix of kernel-firmware-amdgpu took effect. In anyway, it's good to hear that the issue is gone :)