Laptop Monitor not working after update


Since the last package update, my laptop monitor is not functioning correctly. However, my external monitors, which are connected, work fine, and I can see all of them in the display configuration. I can still use the laptop monitor in the BIOS settings.

I hope one of you can help me with this.

inxi -Fx

  Host: MyFedoraLaptop Kernel: 6.6.6-200.fc39.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 2.40-13.fc39 Desktop: KDE Plasma v: 5.27.9 Distro: Fedora
    release 39 (Thirty Nine)
  Type: Laptop System: LENOVO product: 82UU v: Yoga Slim 7 Pro 14ARH7
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76463 WIN
    serial: <superuser required> UEFI: LENOVO v: KHCN29WW date: 03/09/2023
  ID-1: BAT0 charge: 57.1 Wh (100.0%) condition: 57.1/61.0 Wh (93.6%)
    volts: 17.5 min: 15.4 model: Celxpert L19C4PH3 status: full
  ID-2: hidpp_battery_0 charge: 29% condition: N/A volts: 3.8 min: N/A
    model: Logitech G Pro Wireless Gaming Mouse status: discharging
  Info: 8-core model: AMD Ryzen 7 6800HS Creator Edition bits: 64 type: MT MCP
    arch: Zen 3+ rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 626 high: 1899 min/max: 400/4785 cores: 1: 400 2: 400
    3: 400 4: 400 5: 1418 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 400 14: 1505 15: 1899 16: 400 bogomips: 102208
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Device-1: AMD Rembrandt [Radeon 680M] vendor: Lenovo driver: amdgpu
    v: kernel arch: RDNA-2 bus-ID: 32:00.0 temp: 44.0 C
  Device-2: IMC Networks [] driver: uvcvideo type: USB bus-ID: 5-1:2
  Device-3: Logitech C920 PRO HD Webcam driver: snd-usb-audio,uvcvideo
    type: USB bus-ID: 7-1.2.2:8
  Display: wayland server: v: 1.20.14 with: Xwayland v: 23.2.2
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution:
    1: 1920x1080 2: 1920x1080 3: 1440x900
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms:
    active: wayland,x11,surfaceless,device inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.0 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi rembrandt LLVM
    17.0.6 DRM 3.54 6.6.6-200.fc39.x86_64)
  API: Vulkan v: 1.3.268 drivers: radv,llvmpipe surfaces: xcb,xlib,wayland
    devices: 2
  Device-1: AMD Rembrandt Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 32:00.1
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo
    driver: snd_pci_acp6x v: kernel bus-ID: 32:00.5
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel bus-ID: 32:00.6
  Device-4: Logitech C920 PRO HD Webcam driver: snd-usb-audio,uvcvideo
    type: USB bus-ID: 7-1.2.2:8
  Device-5: Logitech [] driver: hid-generic,snd-usb-audio,usbhid type: USB
    bus-ID: 7-1.3:4
  API: ALSA v: k6.6.6-200.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.0 status: active
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: Lenovo driver: mt7921e v: kernel bus-ID: 01:00.0
  IF: wlp1s0 state: up mac: f0:a6:54:8a:de:77
  Device-1: Foxconn / Hon Hai MediaTek Bluetooth Adapter driver: btusb v: 0.8
    type: USB bus-ID: 3-3:3
  Report: btmgmt ID: hci0 rfk-id: 2 state: up address: F0:A6:54:8A:DE:78
    bt-v: 5.2 lmp-v: 11
  Local Storage: total: 476.94 GiB used: 49.58 GiB (10.4%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD PC SN740
    SDDPMQD-512G-1101 size: 476.94 GiB temp: 24.9 C
  ID-1: / size: 475.35 GiB used: 49.19 GiB (10.3%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 347.2 MiB (35.7%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 49.4 MiB (8.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 475.35 GiB used: 49.19 GiB (10.3%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
  System Temperatures: cpu: 50.8 C mobo: 30.0 C gpu: amdgpu temp: 43.0 C
  Fan Speeds (rpm): N/A
  Processes: 411 Uptime: 1h 6m Memory: total: 16 GiB note: est.
  available: 13.33 GiB used: 4.45 GiB (33.3%) Init: systemd
  target: graphical (5) Compilers: N/A Packages: 19 note: see --rpm
  Shell: Bash v: 5.2.21 inxi: 3.3.31

After about 20 minutes in standby, the screen surprisingly starts working again. Unfortunately, I have no idea what caused it.

Surprises from computers are rarely good – they are often symptom of deeper problems.

It could help others with the same issue if you can provie more data. Fedora’s journactl comand-line tool collects a massive amount of detail, so it is an art to extract the lines that are relevant to your issue. Making a note of the time the built-in display wakes up will help. The frst step is to make sure your system is fully updated (including Lenovo firmware) so you aren’t chasing a bug that has been fixed and so other users will have the same software.

Unfortunately, the issue is recurring. I am using the latest BIOS version for the model, and based on the commands, there don’t seem to be any other updates available for my device.

sudo fwupdmgr get-devices
sudo fwupdmgr refresh
fwupdmgr get-updates

Thank you for the suggestion with journalctl. Apart from a few other warnings, I found BIOS bugs errors:

Dez 20 15:05:16 MyFedoraLaptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP7.DEV0], AE_NOT_FOUND (20230628/dswload2-162)
Dez 20 15:05:16 MyFedoraLaptop kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220)
Dez 20 15:05:16 MyFedoraLaptop kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010)
Dez 20 15:05:16 MyFedoraLaptop kernel: ACPI BIOS Error (bug): Failure creating named object [\_TZ.TZ01], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 20 15:05:16 MyFedoraLaptop kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)

Dez 20 15:05:17 MyFedoraLaptop kernel: ACPI Error: No handler for Region [ECSI] (000000002abf1985) [EmbeddedControl] (20230628/evregion-130)
Dez 20 15:05:17 MyFedoraLaptop kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261)
Dez 20 15:05:17 MyFedoraLaptop kernel: ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
Dez 20 15:05:17 MyFedoraLaptop kernel: ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
Dez 20 15:05:17 MyFedoraLaptop kernel: ACPI: \_SB_.UBTC: failed to evaluate _DSM c298836f-a47c-e411-ad36-631042b5008f (0x6)
Dez 20 15:05:17 MyFedoraLaptop kernel: ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2

Since the Lenovo laptop is not officially supported for Linux, I can only hope that this will be resolved over time.

Hello @clueless-user ,
Please run these commands in a terminal cat /sys/firmware/acpi/platform_profile_choices and cat /sys/devices/system/cpu/amd_pstate/status and … sudo ls /sys/devices/system/cpu/cpufreq/policy0/*amd* and also sudo cpupower frequency-info it could be related to the choice of drivers for your AMD CPU, there is poor ACPI support and newer CPU’s from AMD use pstate instead which gives better fine grained control and better responses to wake up from suspend.

1 Like
>> cat /sys/firmware/acpi/platform_profile_choices
low-power balanced performance

>> cat /sys/devices/system/cpu/amd_pstate/status

>> sudo ls /sys/devices/system/cpu/cpufreq/policy0/*amd*
/sys/devices/system/cpu/cpufreq/policy0/amd_pstate_highest_perf  /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_lowest_nonlinear_freq  /sys/devices/system/cpu/cpufreq/policy0/amd_pstate_max_freq

>> sudo cpupower frequency-info
analyzing CPU 6:
  driver: amd-pstate-epp
  CPUs which run at the same hardware frequency: 6
  CPUs which need to have their frequency coordinated by software: 6
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 400 MHz - 4.79 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 400 MHz and 4.79 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 2.80 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.79 GHz.
    AMD PSTATE Nominal Performance: 111. Nominal Frequency: 3.20 GHz.
    AMD PSTATE Lowest Non-linear Performance: 38. Lowest Non-linear Frequency: 1.09 GHz.
    AMD PSTATE Lowest Performance: 14. Lowest Frequency: 400 MHz.

So you are using the amd-pstate-epp driver, which is the better one for power management than the ACPI one. So I am not too certain that this isn’t something else causing your issue of coming out of suspend. Unfortunately I don’t have a Laptop with an AMD cpu to test on.

Alright, if you have another idea I can test let me know.

Dez 22 12:20:33 MyFedoraLaptop kscreenlocker_greet[5881]: kscreenlocker_greet: Lockscreen QML outdated, falling back to default
Dez 22 12:20:33 MyFedoraLaptop kscreenlocker_greet[5881]: PAM unable to dlopen(/usr/lib64/security/ /usr/lib64/security/ cannot open shared object file: No such file or directory
Dez 22 12:20:33 MyFedoraLaptop kscreenlocker_greet[5881]: PAM adding faulty module: /usr/lib64/security/

I also found these. When I use “ls /usr/lib64/security/” I can’t find In the changelogs it is also written that this has been removed because it is not activated by default. Maybe I’ll try to reinstall my system soon even if I don’t like this option.

Definitely, if there is an issue with returning from suspend then the password access module could be involved. An alternative to a fresh install could be to use the “repair an existing Fedora System” option of the installation media (everything iso I believe).

See kscreenlocker merge request to make screenlocker configurable and update documentation. I didn’t find a rpm that provide – not sure if you have some outdated configuration or the lack of a was a packaging error.

Thanks for your help guys. After the Christmas holidays, I went back to the problem. For some reason I haven’t tried this yet, but in the end I reinstalled the packages pam and kscreenlocker with the command sudo dnf reinstall pam and the same for kscreenlocker. Now it seems to work