Standby Not Waking Monitors

Having an issue with a fresh install and using the Standby power saving function.

When waking the system from Standby, the system seems to wake up as my mouse and keyboard are powered. The monitors wake from their sleep, but don’t display anything and then go right back to sleep. I can’t tell if there is actually anything going on, but I have to force shutdown and power back on to get the displays working again.

Hibernate worked without issue. System booted as expected after pressing the power button.

I tried searching this forum and others, but most issues seem to be related to nvidia drivers are other pieces of software I don’t have. For graphics, I’m using the iGPU of an Intel i5-11500.

Any ideas as to possible causes?

Did you also try tapping a key? I find my system sometimes doesn’t react significantly to only a mouse move.

Nonetheless, I’m sure someone will help further when they are able.

In the meantime, please provide your system information as described (below).

Regards.


What follows is from a standard template.

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.

Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:

Required Reading
Highly Recommended

Work with us, not against us

It is important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem. Please also be prepared to provide output from commands if/when asked.

Simply waiting for others to ask you questions is counter-productive – typically, nobody has a :crystal_ball: at their disposal – and your clear, concise and accurate input is often relied upon in order to help you.

Please help others to make informed suggestions based on information you provide.


System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

Suggested inxi command (use either):

inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)
inxi man pages (manual)
If running `inxi` within a `chroot` environment
  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0
Your privacy is respected

Update Announcements


Technical Resources


Tapping a key does not work. Keyboard stays lit up, but nothing happens with the monitors.

Output from inxi -zv6 (Edited 12/12/25)

System:
  Kernel: 6.12.61-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: KDE Plasma v: 6.5.3 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: H470M-STX serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends
    v: P2.00 date: 01/07/2021
Memory:
  System RAM: total: 16 GiB available: 15.24 GiB used: 2.5 GiB (16.4%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM0 type: DDR4 size: 8 GiB speed: 2933 MT/s volts: 1
    note: check manufacturer: G.Skill part-no: F4-3000C16-8GRS
  Device-2: ChannelB-DIMM0 type: DDR4 size: 8 GiB speed: 2933 MT/s volts: 1
    note: check manufacturer: G.Skill part-no: F4-3000C16-8GRS
CPU:
  Info: 6-core model: 11th Gen Intel Core i5-11500 bits: 64 type: MT MCP
    arch: Rocket Lake rev: 1 cache: L1: 480 KiB L2: 3 MiB L3: 12 MiB
  Speed (MHz): avg: 800 min/max: 800/4600 cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 65112
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 750] vendor: ASRock
    driver: i915 v: kernel arch: Xe ports: active: HDMI-A-1,HDMI-A-2
    empty: DP-1,DP-2 bus-ID: 00:02.0 chip-ID: 8086:4c8a
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 d-rect: 3520x1980 display-ID: 0
  Monitor-1: HDMI-A-1 pos: primary,top-left model: HP LV2311 res: 1920x1080
    hz: 60 dpi: 96 diag: 585mm (23")
  Monitor-2: HDMI-A-2 pos: bottom-r model: HP W2072a res: 1600x900 hz: 60
    dpi: 92 diag: 508mm (20")
  API: EGL v: 1.5 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: 25.3.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RKL GT1)
    device-ID: 8086:4c8a display-ID: :1.0
  API: Vulkan v: 1.4.328 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa intel device-ID: 8086:4c8a
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Intel vendor: ASRock driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:f1c8
  API: ALSA v: k6.12.61-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:0d4d
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb
  IF: wlp3s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-14:5 chip-ID: 8087:0aa7
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 1.03 TiB used: 33.41 GiB (3.2%)
  ID-1: /dev/nvme0n1 vendor: TeamGroup model: T-FORCE TM8FFE512G
    size: 476.94 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 46.9 C
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WDBA3V5000ANC-WRSN
    size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 44.9 C
  ID-3: /dev/sda vendor: PNY model: CS900 120GB SSD size: 111.79 GiB
    speed: 6.0 Gb/s serial: <filter>
  Message: No optical or floppy data found.
Partition:
  ID-1: / size: 94.73 GiB used: 7.73 GiB (8.2%) fs: btrfs dev: /dev/sda2
    label: N/A uuid: fe7cb117-10fc-4903-9a1a-f5cf72b13490
  ID-2: /boot/efi size: 299.4 MiB used: 648 KiB (0.2%) fs: vfat
    dev: /dev/sda1 label: N/A uuid: 2F1E-A295
  ID-3: /home size: 468.38 GiB used: 25.67 GiB (5.5%) fs: ext4
    dev: /dev/nvme0n1p1 label: Home uuid: 3683cd15-0c99-4854-a7b6-e062d58a296d
  ID-4: /var/cache size: 94.73 GiB used: 7.73 GiB (8.2%) fs: btrfs
    dev: /dev/sda2 label: N/A uuid: fe7cb117-10fc-4903-9a1a-f5cf72b13490
  ID-5: /var/log size: 94.73 GiB used: 7.73 GiB (8.2%) fs: btrfs
    dev: /dev/sda2 label: N/A uuid: fe7cb117-10fc-4903-9a1a-f5cf72b13490
Swap:
  ID-1: swap-1 type: partition size: 16.77 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda3 label: N/A uuid: 348b79f5-1b76-4b4e-ab10-1d73b13dedfe
Unmounted:
  ID-1: /dev/nvme1n1p1 size: 200 MiB fs: vfat label: N/A uuid: 402B-42A3
  ID-2: /dev/nvme1n1p2 size: 16 MiB fs: <superuser required> label: N/A
    uuid: N/A
  ID-3: /dev/nvme1n1p3 size: 366.69 GiB fs: ntfs label: N/A
    uuid: F0182C43182C0AE4
  ID-4: /dev/nvme1n1p4 size: 735 MiB fs: ntfs label: N/A
    uuid: C0A8CC20A8CC1736
  ID-5: /dev/nvme1n1p5 size: 98.14 GiB fs: ntfs label: Storage
    uuid: B0C406C6C4068F32
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002
  Hub-2: 1-6:2 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    lanes: 1 chip-ID: 05e3:0610
  Device-1: 1-6.1:4 info: Logitech M-U0007 [Corded Mouse M500] type: mouse
    driver: hid-generic,usbhid rev: 2.0 speed: 1.5 Mb/s lanes: 1
    chip-ID: 046d:c069
  Device-2: 1-6.2:6 info: BY Tech Gaming Keyboard type: keyboard,HID
    driver: hid-generic,usbhid rev: 2.0 speed: 12 Mb/s lanes: 1
    chip-ID: 258a:0049
  Device-3: 1-9:3 info: ASRock LED Controller type: HID
    driver: hid-generic,usbhid rev: 1.1 speed: 12 Mb/s lanes: 1
    chip-ID: 26ce:01a6
  Device-4: 1-14:5 info: Intel Wireless-AC 3168 Bluetooth type: bluetooth
    driver: btusb rev: 2.0 speed: 12 Mb/s lanes: 1 chip-ID: 8087:0aa7
  Hub-3: 2-0:1 info: super-speed hub ports: 8 rev: 3.1 speed: 10 Gb/s
    lanes: 1 chip-ID: 1d6b:0003
  Hub-4: 2-6:2 info: Genesys Logic Hub ports: 4 rev: 3.2 speed: 5 Gb/s
    lanes: 1 chip-ID: 05e3:0626
Sensors:
  System Temperatures: cpu: 32.0 C pch: 63.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 297 Power: uptime: 1m wakeups: 0 Init: systemd v: 258
    default: graphical
  Packages: pm: pacman pkgs: 1193 Compilers: N/A Shell: Zsh v: 5.9
    running-in: konsole inxi: 3.3.40

Thank you for the inxi output.

Manjaro Stable updates are now available.

Please read through the respective thread – particularly the Known Issues and Solutions section – to make sure there’s nothing that might affect your update.

Note that as from this update, KDE defaults to using Wayland.

Known Issues and Solutions:


If the issue persists after the update, I might suggest trying kernel 6.18 (LTS) to see if that provides any improvement.


I note that your BIOS/UEFI is rather old. Consider checking the ASRock site for an updated version. The latest available (non-beta) BIOS can often provide needed security mitigations and general improvements.


Once you have successfully updated your system, please edit your post (above) to include the new inxi output. From that point, Support for your issue can be resumed, if needed.

Regards.


Updated the inxi output above. With the update I switched from an x11 to a wayland session. I did not update the kernel and I did not update my bios as the symptoms have changed:

It definitely wakes from sleep and the displays come back on now, but I’m presented with black screens except for my panels, which are a dark gray color and any icons within the panel are black.

The mouse cursor shows up as well, but is unresponsive. The keyboard is once again lit up, but also still unresponsive.

That’s a definite plus.

This is new, though I’ve seen the “grey screen” mentioned.

And this too; in another topic the OP opted to reinstall.


Most of the issues (with the KDE edition) have been related to Plasma now defaulting to Wayland; and realised due to ignoring the Stable Update Announcement thread which contained information to avoid the problems:

Known Issues and Solutions

I suspect most were likely due to being in an “unsupported state” when they performed the update.

Even so, these you mention seem rather different. Hopefully, there will be something definitive soon, but so far very few reports of these issues have emerged.


As these are new – post-update – issues, then it might be best to open a new topic with a suitably descriptive title. As your inxi output is fresh, also copy that to the new topic.


Regards.

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