Comment # 180
on bug 91880
from xuka@amail.club
From watching this bug progress over the last two years and not really improving, I guess this problem is never going to get fixed, at least not too soon. >From my testing last year, it would seem that the majority who have this problem own the MSI brand one, both 390 an 390x have the problem, and there isn't a proper workaround for it besides forcing the memory(maybe core) clock high, so it would seem that the clock is not being set correctly, or the "sensor" isn't realizing that clock should be increased. I have tried every kernel from the past year in hopes that this problem would be solved, with no successful test, I have tried using both AMDGPU and radeon modules, while blacklisting the other to make sure that there was not a problem with one, and still no success. On Windows 10, there is never an issue with artifacts, or crashes. If there is anyway to get this on a fast track to being fixed, please let everyone know, so that we can help, that is what community is for...I think.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
