My display doesn't offer upscaling resolutions. However, amdgpu.dc=1 + xf86-video-amdgpu does. When I change the resolution from native (2560x1440) to one of those automatically offered upscaling resolutions (e.g. 1920x1080), the value in "/sys/class/drm/card0/device/pp_dpm_mclk" gets set to default. I changed it before like this (to prevent flickering with 75Hz with my display): echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level echo "2" > /sys/class/drm/card0/device/pp_dpm_mclk The VRAM runs with its maximum clock as long as I don't change resolution. When I change the resolution like described above, the VRAM clock again gets dynamically changed according to load, which introduces nasty flickering in my case. The desired behavior would be that the change done to pp_dpm_mclk remains untouched when changing to a GPU upscaling resolution. I haven't checked if pp_dpm_sclk is affected as well. Other powerplay/overdrive/fan settings remain untouched by resolution change. Using latest linux-amd-staging-drm-next-wip-git kernel. Xorg session
Please attach the corresponding Xorg log file and output of dmesg.
Created attachment 142327 [details] dmesg.log
Created attachment 142328 [details] xorg.log
This is most certainly a duplicate of bug https://bugs.freedesktop.org/show_bug.cgi?id=107141 (which I would really really like to be fixed one day...)
Yeah, looks like that. It also happens when changing ttys.
*** This bug has been marked as a duplicate of bug 107141 ***
I gave up trying to use my monitor at it's supported 75hz. Locking mclk to fix flickering works only temporarily because it resets at certain events (sleep/wake, resolution changes). Why is this resolved?
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.