Laptop screen stays black after shut down or suspend on Ryzen Yoga 6

Support Graphics & Display
,
1

Hey, I am new to Manjaro Linux and am experiencing problems with my Lenovo Yoga 6 with Ryzen 7840HS processor and Radeon 780m integrated graphics card.
System Info:

System:
  Kernel: 6.10.13-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.10-x86_64
    root=UUID=d9d718fc-84f2-4e1f-942f-8d78dbd0cddb rw quiet splash apparmor=1
    security=apparmor resume=UUID=dc40320a-fc4a-4701-bfb4-34781705e21b
    udev.log_priority=3
  Desktop: GNOME v: 46.5 tk: GTK v: 3.24.43 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 46.2 Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82Y8 v: Yoga Pro 7 14APH8
    serial: <superuser required> Chassis: type: 10 v: Yoga Pro 7 14APH8
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN
    serial: <superuser required> part-nu: LENOVO_MT_82Y8_BU_idea_FM_Yoga Pro 7
    14APH8 uuid: <superuser required> UEFI: LENOVO v: MLCN21WW date: 07/12/2023
Battery:
  ID-1: BAT0 charge: 64.5 Wh (85.8%) condition: 75.2/73.0 Wh (103.0%)
    power: 11.4 W volts: 16.9 min: 15.5 model: SMP L22M4PF4 type: Li-poly
    serial: <filter> status: discharging cycles: 50
Memory:
  System RAM: total: 32 GiB available: 27.1 GiB used: 3.02 GiB (11.1%)
  Message: For most reliable report, use superuser + dmidecode.
CPU:
  Info: model: AMD Ryzen 7 7840HS with Radeon 780M Graphics bits: 64
    type: MT MCP arch: Zen 4 gen: 4 level: v4 note: check built: 2022+
    process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x74 (116) stepping: 1
    microcode: 0xA704101
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB
    desc: 8x1024 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 400 min/max: 400/5137 scaling: driver: amd-pstate-epp
    governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400
    8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400 15: 400 16: 400
    bogomips: 121409
  Flags: 3dnowprefetch abm adx aes amd_lbr_pmc_freeze amd_lbr_v2 aperfmperf
    apic arat avx avx2 avx512_bf16 avx512_bitalg avx512_vbmi2 avx512_vnni
    avx512_vpopcntdq avx512bw avx512cd avx512dq avx512f avx512ifma avx512vbmi
    avx512vl bmi1 bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov
    cmp_legacy constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local
    cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms
    extapic extd_apicid f16c flush_l1d flushbyasid fma fpu fsgsbase fxsr
    fxsr_opt gfni ht hw_pstate ibpb ibrs ibrs_enhanced ibs invpcid irperf
    lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe msr mtrr
    mwaitx nonstop_tsc nopl npt nrip_save nx ospke osvw overflow_recov pae pat
    pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    perfmon_v2 pfthreshold pge pku pni popcnt pse pse36 rapl rdpid rdpru
    rdrand rdseed rdt_a rdtscp rep_good sep sha_ni skinit smap smca smep ssbd
    sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce
    topoext tsc tsc_scale umip user_shstk v_spec_ctrl v_vmsave_vmload vaes
    vgif vmcb_clean vme vmmcall vnmi vpclmulqdq wbnoinvd wdt x2apic x2avic
    xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves xtopology
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: Lenovo
    driver: amdgpu v: kernel arch: RDNA-3 code: Phoenix process: TSMC n4 (4nm)
    built: 2023+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1
    empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, HDMI-A-1, Writeback-1
    bus-ID: 63:00.0 chip-ID: 1002:15bf class-ID: 0300 temp: 30.0 C
  Device-2: Bison Integrated RGB Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1:2 chip-ID: 5986:215d
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
    compositor: gnome-shell driver: gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: InfoVision Optronics/Kunshan 0x05ab built: 2022
    res: 2560x1600 dpi: 208 gamma: 1.2 size: 312x195mm (12.28x7.68")
    diag: 368mm (14.5") ratio: 16:10 modes: max: 2560x1600 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.4-arch1.0.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon 780M (radeonsi gfx1103_r1
    LLVM 18.1.8 DRM 3.57 6.10.13-3-MANJARO) device-ID: 1002:15bf
    memory: 3.91 GiB unified: no display-ID: :0.0

I have already found multiple sources like in the ArchWiki about Ryten (which I can’t link here unfortunately because links are not allowed; google Ryzen Arch) telling me to update an option in UEFI setup. I just can’t seem to find that option in my BIOS. For the alternative of limiting the c-states to 1, I just don’t understand the ramifications of what this would do other than hopefully fix my problem.

I hope I chose the right channel for my problem and thanks in advance.

2

I was just granted rights to post links: Ryzen - ArchWiki

3

Hi and welcome,

Seems to be a Yoga 7.

And also has BIOS updates available.

I also note your machine has an Archwiki page with details.
Though it does not note an issue like this.

https://wiki.archlinux.org/title/Lenovo_Yoga_Pro_7_14APH8

I think this might be related to something like a PSR bug.
I have been experiencing the same on kernels 6.10+.

A quick workaround may be to simply try kernel 6.6.

But for some more info look here:

4

I have the same CPU and I’m on TUXEDO laptop that is supposed to be Linux compatible. It’s not.

I was told, that my laptop won’t get proper suspend and I have the same issue as you, just black screen and not waking up properly. TUXEDO has patches on their kernel for TUXEDO OS and sent them upstream, but they were not accepted. In result, there is no suspend on any Linux OS, aside TUXEDO OS…

This is almost a year and the situation hasn’t improved :frowning: .

No kernel version will fix it, unfortunately.

I guess, we can ask TUXEDO again what is the status of this issue, but since we are on cutting edge (I’m using unstable branch, so I’m basically on pair with Arch stable branch) and nothing has improved, this isn’t going well and may never be fixed.

I just learned to not use suspend and set the screen to turn off when lid is closed. This is not ideal, but that’s all we can do right now. It sucks.

I wish Tuxedo published a kernel module or some patch that we could install from AUR to make it work, but I suspect the kernel must be compiled with it. So theoretically we could compile our own kernel, but that is above my level of expertise and above what I’m willing to go. Too much trouble.

Here is info on my CPU:


 michaldybczak  Sirius16-Manjaro  ~  inxi -C
CPU:
  Info: 8-core model: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics bits: 64
    type: MT MCP cache: L2: 8 MiB
  Speed (MHz): avg: 400 min/max: 400/5137 cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
    15: 400 16: 400

Also, AMD CPU means that there is a very limited WiFi card choice, because most Intel cards won’t support AMD CPUs and ones that does, are pretty old and average. I wanted to buy the newest and most performant Intel WiFi card, but can’t.

Additionally, since some October update, on kernels 6.10 or 6.11, there is some kernel graphical bug, that makes the screen stutter badly. I switched to 6.6 and that seemed to fixed the issue, since I didn’t get that issue since then.

This taught me, that AMD isn’t that great for Linux as it is told everywhere, and I would be better with Intel CPU… Intel also has open source drivers for CPU and way more eyes for bugs, so you rarely experience serious bugs as on AMD…

Anyway, you can still try to fix it. It may be coincidence, and I’m wrong, or the issue was fixed but something else is still blocking the fix, so feel free to try out potential solutions, but you should be also warned, that there might be none.

2 Likes