horizon69
(Ufuk Basal)
January 6, 2025, 12:22pm
1
After a while after turning on the computer, amdgpu performance drops in all games. Changing the resolution solves the problem temporarily.
For video:
https://www.reddit.com/r/Fedora/comments/1huow7f/amd_rx_6700_xt_low_performance/
Are you using steam with overlay disabled? If so try turning the overlay back on. When off it is know to damage performance.
horizon69
(Ufuk Basal)
January 8, 2025, 10:41am
3
Overlay is enabled and also this performance damage affects bottles(flatpak),heroic launcher and lutris but when I change resolution, refresh rate or logout and login gnome session performance back to normal
horizon69
(Ufuk Basal)
January 9, 2025, 5:21pm
4
I found solution!
My problem seems like same with this
https://wiki.archlinux.org/title/AMDGPU#High_idle_power_draw_due_to_MCLK_locked_at_MAX_(1000MHz),_or_MIN_(96MHz)_causing_low_game_performance_(on_6.4_kernel)
And I started reading this
Fix_MCLK_Clock_Stuck_Arch_Linux_Guide.md
# Fix AMD GPU high idle power MCLK (vram / memory clock) stuck at 96 MHz / 1000 MHz for high refresh rates on Arch Linux Wayland & Xorg
On certain resolutions & refresh rates or multi-monitor setups, you might have noticed that your GPU MCLK (vram / memory clock) is stuck at the highest clock frequency (1000 MHz) [[1](https://gitlab.freedesktop.org/drm/amd/-/issues/1403)] [[2](https://gitlab.freedesktop.org/drm/amd/-/issues/2646)] causing higher GPU idle power draw. On Linux kernel 6.4.x, AMDGPU MCLK (vram/memory) clocks at the lowest, causing major FPS drops while gaming [[1](https://gitlab.freedesktop.org/drm/amd/-/issues/2657)] [[2](https://gitlab.freedesktop.org/drm/amd/-/issues/2611)]. This is likely due to a monitor not using Coordinated Video Timings (CVT) with a low V-Blank value for the affected resolutions & refresh rates. The higher clocking behavior is due to:
> [Well, the reason the clocks get forced to max in some cases is to avoid the flickering you are seeing. There is a certain latency required to change the mclk. The hardware needs to hide that mclk switch during some blanking period of the display otherwise you would see flickering. If the blanking periods are too short or not alignable (in the case of multiple displays), the driver has to use a fixed mclk to avoid the flickering. In your case, it appears that the latency of switching to/from the 96Mhz mclk is right on the edge of what is possible given the monitors blanking periods. **You may need to slightly lengthen the hblank or vblank periods in your display's modeline**.](https://gitlab.freedesktop.org/drm/amd/-/issues/1403#note_1190208)
The monitor's non standard timings values were likely set that way to keep its pixel clock values within display cable bandwidth constraints that are more relevant on higher resolutions & refresh rates, which is why this issue tends to occur on high resolutions & refresh rates.
### HDMI
This file has been truncated. show original
This solution working but also too complicated
This one much more easy
sudo nano/etc/default/grub
And add this command to GRUB_CMDLINE_LINUX
video=DP-3:1920x1080MR@164(change according to your own monitor specifications)
save it and update grub config
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
reboot
and select new refresh rate
1 Like