Problem with AMD Ryzen graphics and power management

Support
1

I have AMD Ryzen 5 4600G with integrated AMD Radeon Graphics.
I have problem with power management. Turn off screens does not work.
Well the screens actually turns off, but immediately comes back on.

Any ideas how to solve this problem ?

System:
  Host: heebo-desktop Kernel: 6.11.11-1-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.2.4 Distro: Manjaro Linux
Machine:
  Type: Desktop Mobo: ASRock model: X300M-STX serial: <superuser required>
    UEFI: American Megatrends LLC. v: P2.00 date: 10/25/2024
CPU:
  Info: 6-core model: AMD Ryzen 5 4600G with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 2994 min/max: 400/4308 cores: 1: 2994 2: 2994 3: 2994
    4: 2994 5: 2994 6: 2994 7: 2994 8: 2994 9: 2994 10: 2994 11: 2994 12: 2994
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir [Radeon Vega Series /
    Radeon Mobile Series] driver: amdgpu v: kernel
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X:
    loaded: amdgpu unloaded: modesetting dri: radeonsi gpu: amdgpu
    s-res: 3840x1080 resolution: 1: 1920x1080 2: 1920x1080
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.8-arch1.1
    renderer: AMD Radeon Graphics (radeonsi renoir LLVM 18.1.8 DRM 3.59
    6.11.11-1-MANJARO)
  API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: radeontop wl: wayland-info
    x11: xdpyinfo,xprop
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
    Audio driver: snd_hda_intel
  Device-2: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    driver: snd_hda_intel
  API: ALSA v: k6.11.11-1-MANJARO status: kernel-api
  Server-1: PipeWire v: 1.2.7 status: active
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 9c:6b:00:3e:4c:8b
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
  IF: wlp3s0 state: down mac: 8e:23:41:2e:b2:77
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: F4:26:79:FB:71:8C bt-v: 4.2
Drives:
  Local Storage: total: 704.25 GiB used: 150.47 GiB (21.4%)
  ID-1: /dev/nvme0n1 vendor: KIOXIA model: EXCERIA G2 SSD size: 465.76 GiB
  ID-2: /dev/sda vendor: Crucial model: CT128MX100SSD1 size: 119.24 GiB
  ID-3: /dev/sdb vendor: Crucial model: CT128MX100SSD1 size: 119.24 GiB
Partition:
  ID-1: / size: 448.43 GiB used: 48.63 GiB (10.8%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 296 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A gpu: amdgpu temp: 34.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 13.52 GiB used: 4.23 GiB (31.3%)
  Processes: 334 Uptime: 4h 18m Shell: Zsh inxi: 3.3.37
2

I think you may benefit from a newer kernel - 6.11 is unsupported.

1 Like
3

Well no help with newer kernel. I tried both 6.12.4-1 and 6.13.0rc2-1.

4

Have you tried logging in using Wayland?

If that is not enough I suggest to switch branch.

→ Switching Branches - Manjaro

1 Like
5

I switched to testing branch and it did not help either. :frowning:
Maybe I have to start learning what is Wayland. :slight_smile:

6

Thanks! Wayland logging did the trick!!!

1 Like
7

Next time you reboot, pause at the Login Screen (SDDM).

Look to the bottom, left corner and choose Wayland as your default session. It will remain the default untill you change it again using the same method.

Then, continue to login.

You are using AMD graphics which are usually a good combination with Wayland.

Regards.

2 Likes
8

I’m glad your problem is solved.

Let’s give credit where credit is due; it was @linux-aarhus who first suggested Wayland. I’ll change that for you.

Regards.

9

The KDE developers prioritize Plasma Wayland over X11 for good reasons.

Since Manjaro Plasma uses X11 as default (for reasons I don’t understand) I just thought that testing Wayland would be good idea.

I think it is great is took no more than that. :slight_smile:

1 Like
10

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.