System cannot wake up

Ask Fedora
, , , , ,
1

Hello !

For the last week or so, my Fedora desktop has stopped being able to wake from sleep. When trying to wake it up, the lights turn on, the peripherals get power (keyboard lights turn on), but nothing on the screens, and the computer is not responding at all (for example, pressing caps lock does not turn on the corresponding keyboard light).

Of course, the system is fully up to date.

Reading other topics on failures to wake up, I tried to follow troubleshooting steps without success, but here are the results of a few commands people asked for on those topics:

inxi -Fzxx 
System:
  Kernel: 6.11.3-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.5 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B550M-PLUS v: Rev X.0x
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 3205
    date: 08/14/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 16 MiB
  Speed (MHz): avg: 2995 min/max: 400/4464 boost: enabled cores: 1: 2995
    2: 2995 3: 2995 4: 2995 5: 2995 6: 2995 7: 2995 8: 2995 9: 2995 10: 2995
    11: 2995 12: 2995 bogomips: 93606
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 22 [Radeon RX 6700/6700
    XT/6750 XT / 6800M/6850M XT] vendor: Sapphire driver: amdgpu v: kernel
    arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: DP-1,DP-3
    empty: DP-2,HDMI-A-1,Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:73df
  Device-2: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-2:2 chip-ID: 1b3f:2247
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 24.1.3
    compositor: gnome-shell driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96
  Monitor-1: DP-1 pos: primary,left model: Idek Iiyama PL2492H
    res: 1920x1080 dpi: 93 diag: 604mm (23.8")
  Monitor-2: DP-3 pos: right model: Idek Iiyama PL2492H res: 1920x1080
    dpi: 93 diag: 604mm (23.8")
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.1.7 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon RX 6700 (radeonsi navi22 LLVM
    18.1.6 DRM 3.59 6.11.3-200.fc40.x86_64) device-ID: 1002:73df
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:ab28
  Device-2: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
    Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
    lanes: 16 bus-ID: 0a:00.1 chip-ID: 1002:1637
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
    lanes: 16 bus-ID: 0a:00.6 chip-ID: 1022:15e3
  Device-4: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-2:2 chip-ID: 1b3f:2247
  API: ALSA v: k6.11.3-200.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: AzureWave driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 07:00.0 chip-ID: 14c3:7922
  IF: wlp7s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: e000 bus-ID: 08:00.0 chip-ID: 10ec:8125
  IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-7.2:5 chip-ID: 13d3:3585
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 1.82 TiB used: 782.1 GiB (42.0%)
  ID-1: /dev/nvme0n1 vendor: Crucial model: CT2000P3PSSD8 size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 31.9 C
Partition:
  ID-1: / size: 1.31 TiB used: 782.06 GiB (58.4%) fs: btrfs
    dev: /dev/nvme0n1p7
  ID-2: /boot/efi size: 96 MiB used: 47.7 MiB (49.7%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 29.8 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p6
Sensors:
  System Temperatures: cpu: 46.9 C mobo: 28.0 C gpu: amdgpu temp: 41.0 C
    mem: 40.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 32 GiB note: est. available: 31.14 GiB used: 9.4 GiB (30.2%)
  Processes: 473 Power: uptime: 18m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 33
    Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Zsh v: 5.9
    running-in: gnome-terminal inxi: 3.3.36
cat /sys/power/mem_sleep 
s2idle [deep]

Now, to be honest, sleep/wake has never been very stable on Fedora on this machine. It has usually worked about 90% of the time, with the failures being either similar to the one described above, or the computer seemingly turning on completely (keyboard lights toggling on caps lock + ping responding) but nothing on the screen, or even the screens turning on successfully and the lock screen displaying the correct time and updating it but USB peripherals not working at all. This was similar to the behaviours described in this topic : Fedora 40 - Monitors won't wake when return from system suspend . That was annoying, but livable.

However, the current behaviour of 0% wake success is very recent, only for the last week or so. I tried on Wayland, on X, on the login screen : same behaviour. I don’t know what could have changed besides system updates.

I believe all relevant information on my setup is present in the result of the inxi -Fzxx command, if I missed anything don’t hesitate to ask.

Any help would be very much appreciated. I tried scouring the forums & reddit for similar problems, but they are each different just enough so that I don’t know what else to try.

Thank you very much in advance !

4 Likes
2

Added amd, amdgpu, gnome

3

Added desktop, f40, workstation

4

Do you boot any other OS’s on this system? Can you disable wake-on-lan or wake-on-wifi in your BIOS (BIOS network firmware with minimal capabilities can clash the linux drivers)?

Sleep/wakeup involves vendor firmware, and Linux developers have been working hard to minimize linux power requirements (with companies hoping sell large number of linux systems into cubical farms). Your issues are unlikely to be specific to Fedora, as kernel support follows Advanced Configuration and Power Interface (ACPI) open standard. My Dell systems support a kernel command-line option: acpi_osi=linux.

As is often the case, Arch Linux has good documentation for linux power managent.

If your vendor doesn’t provide BIOS updates that solve your problem you will have to work around broken sleep/wake support. Please check for a newer BIOS with fwupdtool or the vendor’s web site. For workarounds, you should search for sleep/wake and your model across other linux forums.

In the short term, you may want to disable sleep in Gnome settings. My desktop systems are on UPS’s so use /etc/systemd/sleep.conf.d/sleep.conf:

# systems that manage UPS should never sleep
# See systemd-sleep.conf(5) for details.
[Sleep]
AllowSuspend=no
AllowHibernation=no
5

I seem to have the same issue, I have just opened a bug report on bugzilla mentioning this thread. If you find more information, or the issue turns out to not be the same feel free to comment there so the maintainers can see it.

6

The latest kernel 6.11.3-200.fc40 appears not to work well with some AMD gpus. Use a previous one to exclude this cause, and report back.

7

Can you provide an example? Some links to those discussions would be useful

8

I’m having the same problem with kernel 6.11.3. Going back to 6.10.12 works fine. Using AMD 7900 XTX.

Seems like every few months I hit another problem where my system won’t resume from suspend. Most of them end up being amdgpu issues, but some I’ve never dug into. After a few updates they go away.

Over a few years running Fedora I’ve been largely problem free, with the exception of wake from suspend issues over and over again.

9

Thank you to everyone, rolling back the Kernel seems to work ! I should have thought to try it :person_facepalming:

10

@arantes555 Kernel 6.11.4 is up, does that work?

11

Many users will agree. I was pleasantly surprised that this 5-year old Dell Latitude laptop supports a command-line option acpi_osi=linux and has not had power management issues with Fedora 40 or now, with 41 beta.

12

I tried it for a day. Woke up successfully twice, failed to wake twice. So, better than 6.11.3, but still bad, so I went back to 6.10

1 Like
13

Same problem here. Booting 6.10.12-200.fc40.x86_64 works. However 6.11.4-201.fc40.x86_64 fails to wake up every single time.

inxi -Fzxx 
System:
  Kernel: 6.11.4-201.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: KDE Plasma v: 6.2.2 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Fedora Linux 40 (KDE Plasma)
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX B650-A GAMING WIFI v: Rev 1.xx
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 2613
    date: 04/12/2024
CPU:
  Info: 12-core model: AMD Ryzen 9 7900 bits: 64 type: MT MCP arch: Zen 4
    rev: 2 cache: L1: 768 KiB L2: 12 MiB L3: 64 MiB
  Speed (MHz): avg: 3489 min/max: 545/5482 boost: enabled cores: 1: 3489
    2: 3489 3: 3489 4: 3489 5: 3489 6: 3489 7: 3489 8: 3489 9: 3489 10: 3489
    11: 3489 12: 3489 13: 3489 14: 3489 15: 3489 16: 3489 17: 3489 18: 3489
    19: 3489 20: 3489 21: 3489 22: 3489 23: 3489 24: 3489 bogomips: 177590
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: ASUSTeK
    driver: nvidia v: 560.35.03 arch: Ampere pcie: speed: 16 GT/s lanes: 16
    ports: active: none off: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:2504
  Device-2: Insta360 Link driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-2.4.1:10 chip-ID: 2e1a:4c01
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.3
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: DP-1 model: LG (GoldStar) HDR DQHD res: 3840x1080 dpi: 81
    diag: 1244mm (49")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11:
    drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    display-ID: :0.0
  API: Vulkan v: 1.3.296 surfaces: xcb,xlib,wayland device: 0
    type: discrete-gpu driver: N/A device-ID: 10de:2504 device: 1 type: cpu
    driver: N/A device-ID: 10005:0000
Audio:
  Device-1: NVIDIA GA106 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:228e
  Device-2: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-6:2 chip-ID: 0b05:1a52
  Device-3: Razer USA Seiren Mini driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 3-2.3.3:8
    chip-ID: 1532:0531
  Device-4: Insta360 Link driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-2.4.1:10 chip-ID: 2e1a:4c01
  API: ALSA v: k6.11.4-201.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 08:00.0 chip-ID: 8086:15f3
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Foxconn driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 09:00.0 chip-ID: 14c3:0616
  IF: wlp9s0 state: down mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-11:5 chip-ID: 0489:e0e2
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 931.51 GiB used: 446.96 GiB (48.0%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SNV2S1000G size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 41.9 C
Partition:
  ID-1: / size: 929.91 GiB used: 446.49 GiB (48.0%) fs: btrfs dev: /dev/dm-0
    mapped: luks-15748bab-5b44-4b3c-9152-51b3c40e161f
  ID-2: /boot size: 973.4 MiB used: 459 MiB (47.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 929.91 GiB used: 446.49 GiB (48.0%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-15748bab-5b44-4b3c-9152-51b3c40e161f
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 48.1 C mobo: 35.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 31.05 GiB used: 6.15 GiB (19.8%)
  Processes: 551 Power: uptime: 46m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: 82 pm: nix-usr pkgs: 67 pm: rpm pkgs: N/A note: see --rpm
    pm: flatpak pkgs: 15 Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.26
    running-in: yakuake inxi: 3.3.36
1 Like
14

I can’t help but notice we both have an MT7922 card in our systems … Maybe there’s a link ? I’ll try removing it and checking if it helps. Maybe you can try too ?

15

Unfortunately mine is under the I/O shield. If I could remove it without disassembling the whole PC, I would have replaced it for an Intel one long ago.
We both have that card because we both have an mid/entry level AMD motherboard.

Anyway, I also have seen other people having a similar problem with that card, but their workaround (disabling the card at suspend and enabling it at resume) doesn’t seem to work for me.

16

Consider things that can differ across the same hardware:

  • vendor firmware versions – new linux kernels often require changes
  • kernel ACPI command-line options
  • BIOS/UEFI netboot/PXE settings: netboot loads a minimal firmware package that may conflict with firmware loaded by linux (due vendors not testing/supporting linux)
  • dual boot: sometimes the other OS affects the state of network hardware. The order in which different OS’s are used can make a difference. You may need a power-off restart after using another OS.

Problems with network hardware in linux are generally present across multiple linux distros using the same kernel and binary firmware blobs, so solutions often appear in the help forums for other distros. Since Fedora is an early adopter of new kernels, you may need to stick with an older kernel or use a USB dongle while periodically searching for a fix.

17

Mine was actually an add-in PCIe card. I bought an Mercusys MA86XE which was described as having an Intel chipset, but I got the V2 which uses the MediaTek MT7922…

In any case, I just removed it, and preliminary results look good, already 3 wakeups without problem.

18

So, did it work?

I still have problems with 6.11.5

19

After 2 days, and multiple wakeups, I can report 0 failures to wake up.

It does seem like removing the MT7922 card fixed it for good.

1 Like
20

Had the same wake problem, Following information found from many searches: I have msi motherboard. In bios found there is a wake setup. Wake on lan, or usb, something like that. Last option was to enable OS. That did it! No more problems with restore from sleep!