UPdate 2023-09-10: Avoid black screen on Ryzen 7

Support Graphics & Display
1

Reading the actual announcement, I found for the UPdate 2023-08-11 the topic “Avoid black screen on Ryzen 7”
Based on the solution from @linux-aarhus was recommended:

You may be able to avoid black screen if you - prior to rebooting after the update - sync the latest stable kernel - currently - Linux 6.5.

My machine has a AMD Ryzen7 Pro 4750U and my kernels are

$ mhwd-kernel -li
Currently running: 5.15.128-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux510
   * linux515
   * linux54

Actually, I don’t need a newer kernel. I’ve done the update 2023-08-11 mid August without any problem.
But, in regards to the issue, I’d appreciate your recommendation? I haven’t starte the actual UPdate yet …
Thank you!

2

Pretty sure that issue was only affecting people with 7xxx graphics cards.

3

Although, removal is expected - it has to marked EOL on kernel.org - then will be taken down - so if you are indoubt - add linux64 to the pacman package list

Assuming an up-to-date mirror - otherwise refresh mirrorlist - using Global pool

sudo pacman-mirrors -c Global
sudo pacman -Syu linus64 linux64-headers
1 Like
4

You may want to install 6.5.2 kernel from unstable branch to fix this issue.

1 Like
5

Thank you @linux-aarhus and @philm, but that overwhelms me:

Screenshot_20230911_094918
Screenshot_20230911_0949181150×930 103 KB

  • 6.4 plus 6.5 or 6.5 only?
  • Install or use that kernel?
  • How to install from unstable branch without changing the branch completely?
  • Any “easier” option?

Since the issue "Avoid black screen on Ryzen 7… " is listed under the UPdate 2023-08-11 which i’ve done without any problem, is it likely to have a problem now?

6

Do nothing and carry on as usual. Your system is not affected.

7

More information about my system:

$ inxi --admin --verbosity=7 --filter --no-host --width
System:
  Kernel: 5.15.128-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=3fb81935-3c2a-4b83-ae67-7b8f75e23839 rw apparmor=1
    security=apparmor resume=UUID=338139c5-0361-42c0-9573-dbd00f711a01
    udev.log_priority=3 acpi_backlight=none
  Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 20UH001QGE v: ThinkPad T14s Gen 1
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 20UH001QGE v: SDK0J40697 WIN
    serial: <superuser required> UEFI: LENOVO v: R1CET65W(1.34 ) date: 06/17/2021
Battery:
  ID-1: BAT0 charge: 29.8 Wh (65.2%) condition: 45.7/57.0 Wh (80.1%)
    power: 24.4 W volts: 11.1 min: 11.5 model: SMP 5B10W139 type: Li-poly
    serial: <filter> status: discharging cycles: 1314
Memory:
  System RAM: total: 32 GiB note: est. available: 30.59 GiB
    used: 4.72 GiB (15.4%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 PRO 4750U with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 2 gen: 3 level: v3 note: check built: 2020-22
    process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1
    microcode: 0x8600106
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB
    desc: 2x4 MiB
  Speed (MHz): avg: 2095 high: 3907 min/max: 1400/1700 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2039 2: 2212
    3: 3144 4: 3358 5: 2369 6: 1967 7: 2112 8: 1805 9: 1447 10: 1509 11: 1488
    12: 1417 13: 1535 14: 1415 15: 1806 16: 3907 bogomips: 54319
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibrs ibs
    irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
    pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    pfthreshold pge 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 v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme vmmcall
    wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_rstack_overflow mitigation: safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5
    code: Vega process: GF 14nm built: 2017-20 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 06:00.0
    chip-ID: 1002:1636 class-ID: 0300 temp: 66.0 C
  Device-2: IMC Networks Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-2:2 chip-ID: 13d3:5405
    class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 21.1.8 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: ChiMei InnoLux 0x14f2 built: 2018
    res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2 size: 309x173mm (12.17x6.81")
    diag: 354mm (13.9") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.1.6-2 renderer: AMD Radeon Graphics (renoir
    LLVM 15.0.7 DRM 3.42 5.15.128-1-MANJARO) direct-render: Yes
...
8

well, 6.5 kernel series has an issue which may produce black screens on Ryzen APUs. If your older kernel doesn’t have it no issue there. Kernel 6.5 black screen regression — Linux Stable Kernel Updates

1 Like
9

Thank you @philm. I’m not sure that I understand the full story, but @brahma mentioned my question to an issue of an AMD-User running 6.1.19-1-MANJARO (linux61), e.g. not 6.5 kernel.

  • Can we find out, if 6.* kernels are the problem and 5.* kernels are safe for this issue?
  • Can you foresee, when a fix for the 6.? will be available?

I’d appreciate your recommendation for my next steps; currently I’m delaying the UPdate …

1 Like
10

I have no idea why you are trying to stick on older kernels with newer hardware.
If I were you I would be chasing 6.5+ as best I could.
(not to mention 6.4 brought a number of advances, like ext4 getting faster)
I also dont think your device is one of the ones affected by this issue.
Even if it were … you have multiple kernels installed.

So, if I were you I would:

Go ahead and install the latest available (6.5) along with your updates
(sudo pacman -Syu linux65 linux65-headers)

Then … reboot, check the newer kernel … if black screen then reboot and use an earlier one.

(and once you are happy and comfortable … go about removing excess kernels until you have 2 or 3 total, ex: 5.15 & 6.5)

11

I afraid my problem not in the kernel (or not only in the kernel). For me it doesn’t work even with 4.19. 5, and 6 (6.1, 6.4, 6.5) also show black screen. What I able to reproduce, that problem in something that changed between 22 and 23 snapshot, because I can easily reinstall 22 from USB (everything breaks after update), but cannot even start USB with 23.