Created attachment 280019 [details] simple app for the amdgpu sys interface When the Xfce desktop is visible at 4K and idling, the engine clock is fixed at level 6: 1220MHz and you can not change that. The temperature is 38 C. When the monitor is sleeping, then the engine clock is 300Mhz. The automatic power management works with 2560x1600 and lower resolutions as espected. I tested with my python app and I have latest drivers, including firmware files. My monitor is ASUS VP28UQG and I use the display port. System: Host: ryzenpc Kernel: 4.20.0-rc6 x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x serial: <root required> UEFI [Legacy]: American Megatrends v: 4023 date: 08/20/2018 CPU: 6-Core: AMD Ryzen 5 1600 type: MT MCP speed: 2851 MHz Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.3 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 3840x2160~60Hz OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.27.0 4.20.0-rc6 LLVM 7.0.1) v: 4.5 Mesa 19.0.0-devel (git-9ebc00f 2018-12-13 bionic-oibaf-ppa)
(In reply to fin4478 from comment #0) > simple app for the amdgpu sys interface You might consider if you are trying out radeon-profile. https://github.com/marazmista/radeon-profile
(In reply to nancy from comment #1) > (In reply to fin4478 from comment #0) > > > simple app for the amdgpu sys interface > > > > You might consider if you are trying out radeon-profile. > > https://github.com/marazmista/radeon-profile That uses the same sysfs api and uses old qt or special modules (like qtchartview) that are not compatible with latest qt packages. In other words that app is broken on several distributions. When programming simple GUIs, use python gtk that does not break so easily.
Adding amdgpu.ppfeaturemask=0xffffffff to the kernel command line makes the powerplay feature to work normally at 4K. uname -r 4.20.0-rc3+
the above kernel command line is still necessary in 2022 with mesa 22. Why has this not been fixed in source to not need the clock/voltage adjustment parameter for automatic clocks when using 4K monitor output?
The driver set minimum required clocks to meet the required bandwidth and voltage for the attached displays. When you enable overclocking (via the bit in ppfeaturemask), that gets partially disabled to allow the user to manually adjust the clocks at their own risk.