I recently installed Nobara Linux on my desktop (it’s Fedora-based) and it works well except for one pretty major issue: my desktop does not 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). My system is completely up-to-date.
Here is some system info that is apparently commonly requested on issues such as this:
inxi -Fzxx
System:
Kernel: 6.19.7-200.nobara.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 15.2.1
Desktop: GNOME v: 49.4 tk: GTK v: 3.24.51 wm: gnome-shell dm: GDM
Distro: Nobara Linux 43 (GNOME Edition) base: Fedora 43
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B550-A GAMING v: Rev X.0x
serial: <superuser required> part-nu: SKU Firmware: UEFI
vendor: American Megatrends v: 2401 date: 05/25/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Solar Keyboard K750
serial: <filter> charge: 100% status: full
Device-2: ps-controller-battery-ac:fd:93:38:a2:92 model: N/A serial: N/A
charge: N/A status: full
CPU:
Info: 12-core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2
rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
Speed (MHz): avg: 4100 min/max: 563/4674 boost: enabled cores: 1: 4100
2: 4100 3: 4100 4: 4100 5: 4100 6: 4100 7: 4100 8: 4100 9: 4100 10: 4100
11: 4100 12: 4100 13: 4100 14: 4100 15: 4100 16: 4100 17: 4100 18: 4100
19: 4100 20: 4100 21: 4100 22: 4100 23: 4100 24: 4100 bogomips: 182395
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060] vendor: Micro-Star MSI
driver: nvidia v: 580.126.09 arch: Ampere pcie: speed: 16 GT/s lanes: 16
ports: active: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 07:00.0
chip-ID: 10de:2503
Device-2: Huawei UVC Camera driver: snd-usb-audio,uvcvideo type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 3-3:5 chip-ID: 12d1:4321
Display: wayland server: Xwayland v: 24.1.9 compositor: gnome-shell
driver: gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: DP-1 model: Dell P2014H res: 1600x900 dpi: 92
diag: 501mm (19.7")
Monitor-2: HDMI-A-1 model: LG (GoldStar) ULTRAWIDE res: 2560x1080 dpi: 97
diag: 730mm (28.8")
API: OpenGL v: 4.6.0 vendor: nvidia v: 580.126.09 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
display-ID: :0.0
API: Vulkan v: 1.4.328 surfaces: N/A device: 0 type: discrete-gpu
driver: nvidia device-ID: 10de:2503 device: 1 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo,vulkaninfo gpu: lact, nvidia-settings,
nvidia-smi x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA GA106 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 07:00.1 chip-ID: 10de:228e
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 09:00.4 chip-ID: 1022:1487
Device-3: C-Media Blue Snowball driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-2:2 chip-ID: 0d8c:0005
Device-4: Huawei UVC Camera driver: snd-usb-audio,uvcvideo type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 3-3:5 chip-ID: 12d1:4321
Device-5: DisplayLink StarTech.com USB3SDOCKHDV
driver: cdc_ncm,snd-usb-audio type: USB rev: 3.2 speed: 5 Gb/s lanes: 1
bus-ID: 4-4.2:3 chip-ID: 17e9:4307
API: ALSA v: k6.19.7-200.nobara.fc43.x86_64 status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.4.10 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: 06:00.0 chip-ID: 8086:15f3
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Ralink MT7601U Wireless Adapter driver: mt7601u type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-2:14 chip-ID: 148f:7601
IF: wlp9s0f3u2 state: down mac: <filter>
IF-ID-1: enp9s0f3u4u2i5 state: down mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-3:3
chip-ID: 0a12:0001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6
Drives:
Local Storage: total: 2.27 TiB used: 965.78 GiB (41.5%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T3X0C-00SJG0
size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 43.9 C
ID-2: /dev/sda vendor: Western Digital model: WD5000AAKX-22ERMA0
size: 465.76 GiB speed: 6.0 Gb/s serial: <filter>
ID-3: /dev/sdb vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB
type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
ID-1: / size: 859.96 GiB used: 157.47 GiB (18.3%) fs: btrfs
dev: /dev/nvme0n1p3
ID-2: /boot size: 1.9 GiB used: 924.8 MiB (47.5%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 859.96 GiB used: 157.47 GiB (18.3%) fs: btrfs
dev: /dev/nvme0n1p3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 28 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 68.96 GiB used: 0 KiB (0.0%)
priority: -1 dev: /dev/nvme0n1p4
Sensors:
System Temperatures: cpu: 59.2 C mobo: 43.6 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB note: est. available: 62.69 GiB used: 9.87 GiB (15.8%)
Processes: 611 Power: uptime: 3h 10m wakeups: 0 Init: systemd v: 258
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 112
Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.0 running-in: ptyxis-agent
inxi: 3.3.40
cat /sys/power/mem_sleep
s2idle [deep]
It did successfully wake from sleep once, but it was immediately after a reboot. So whatever is causing it likely happens late in the boot process or has to do with something I start up later, but I’m not sure what.
Any help would be appreciated here. Thanks in advance!