Stuck in Black screen after waking from suspend

Support
1

When I wake my devce from suspend state, the display remains totally black as if it’s has no power. I searched the forum but most of them have nvidia or amd graphics driver. Here’s my spec.

~$  inxi -Fxxxz
System:
  Kernel: 6.10.13-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A wm: kwin_wayland vt: 1 dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ASUS EXPERTBOOK B1500CEAEY_B1500CEAE
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: B1500CEAEY v: 1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: ASUSTeK v: B1500CEAEY.321 date: 12/22/2022
Battery:
  ID-1: BAT0 charge: 16.4 Wh (53.1%) condition: 30.9/42.1 Wh (73.4%)
    power: 15.4 W volts: 11.8 min: 11.8 model: ASUSTeK ASUS Battery type: Li-ion
    serial: N/A status: discharging cycles: 304
CPU:
  Info: quad core model: 11th Gen Intel Core i5-1135G7 bits: 64 type: MT MCP
    smt: enabled arch: Tiger Lake rev: 1 cache: L1: 320 KiB L2: 5 MiB L3: 8 MiB
  Speed (MHz): avg: 583 min/max: 400/4200 cores: 1: 583 2: 583 3: 583 4: 583
    5: 583 6: 583 7: 583 8: 583 bogomips: 38720
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-12.1 ports: active: eDP-1 empty: DP-1,
    DP-2, DP-3, HDMI-A-1 bus-ID: 0000:00:02.0 chip-ID: 8086:9a49
    class-ID: 0300
  Device-2: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-5:3 chip-ID: 13d3:56a2
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.4-arch1.0.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Xe Graphics (TGL GT2)
    device-ID: 8086:9a49 display-ID: :1.0
  API: Vulkan v: 1.3.295 layers: N/A surfaces: xcb,xlib,wayland device: 0
    type: integrated-gpu driver: mesa intel device-ID: 8086:9a49
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: ASUSTeK
    driver: sof-audio-pci-intel-tgl bus-ID: 0000:00:1f.3 chip-ID: 8086:a0c8
    class-ID: 0401
  API: ALSA v: k6.10.13-3-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.2.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 0000:00:14.3
    chip-ID: 8086:a0f0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Device-2: Intel Ethernet I219-V driver: e1000e v: kernel port: N/A
    bus-ID: 0000:00:1f.6 chip-ID: 8086:15fc class-ID: 0200
  IF: eno2 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-10:5 chip-ID: 8087:0026 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b rev: class-ID: 0104
Drives:
  Local Storage: total: 476.94 GiB used: 224.65 GiB (47.1%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN530
    SDBPNPZ-512G-1002 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 21106000 temp: 36.9 C scheme: GPT
Partition:
  ID-1: / size: 78.19 GiB used: 9.02 GiB (11.5%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 288 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 347.26 GiB used: 215.6 GiB (62.1%) fs: ext4
    dev: /dev/nvme0n1p4
Swap:
  ID-1: swap-1 type: partition size: 42.76 GiB used: 36.2 MiB (0.1%)
    priority: -2 dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 2000
Info:
  Memory: total: 40 GiB note: est. available: 38.87 GiB used: 6 GiB (15.4%)
  Processes: 261 Power: uptime: 18m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform Init: systemd v: 256 default: graphical
  Packages: pm: pacman pkgs: 1107 Compilers: gcc: 14.2.1 Shell: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.36
2

6.10 is EOL, try out a newer Kernel or switch to a LTS Kernel.

2 Likes
3

Please see the Stable Update 2024-10-10 announcement and look under the Known Issues and Solutions heading:

In particular, look at:

  • System freeze on suspend

…and as you are using KDE Plasma…

  • KDE Plasma hangs on Shutdown, Restart and Logout

Either of these issues may be contibuting to your problem.

Regards.

4

I downloaded the iso from manjaro website. Downgraded the karnel solved the issue.

5

I thought it was solved just by downgrading kernel. But found that this only happens if I have any android studio emulator running. What will be the effect of setting this parameter to false?

[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

Will it drain battery in sleep mode?

6

I saw that mentioned too (Arch forum); with some claiming it solved their issue and others claiming it made no difference at all.

With regard battery draining, I can only guess that it would be minimal. Without a laptop I can’t test the theory.

Perhaps there’s a setting in Android Studio that might help. Last time I used it was several years ago (it wasn’t very stable); maybe it’s best not to leave it running.

As mentioned by @Kobold kernel 6.10 has reached EOL; in fact, it has now been removed from the repos (no more updates), so it would be likely beneficial to switch to another; perhaps 6.11 or one of the LTS kernels.

Doing so might even improve things to some extent.

After switching kernels you should perform a system update.

7

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