For some reason, my monitors do not wake up after going into sleep/hibernate mode. Any suggestions on how to fix this? I use 2 monitors as well if that helps.
Anyone that may be able to help will need a lot more information about your setup.
Please post the output of inxi -FGxx as prefornatted text using the </> button.
What have you configured for power saving?
System:
Host: fedora Kernel: 6.7.11-200.fc39.x86_64 arch: x86_64 bits: 64
compiler: gcc v: 2.40-14.fc39
Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.12 wm: kwin_x11 dm: 1: GDM
note: stopped 2: SDDM Distro: Fedora Linux 39 (KDE Plasma)
Machine:
Type: Desktop Mobo: Micro-Star model: B450-A PRO MAX (MS-7B86) v: 4.0
serial: <superuser required> UEFI: American Megatrends LLC. v: M.D0
date: 05/17/2021
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: 2261 high: 3800 min/max: 2200/4672 boost: enabled cores:
1: 2200 2: 2200 3: 2200 4: 2200 5: 2200 6: 2199 7: 2200 8: 2199 9: 2200
10: 2199 11: 2089 12: 3800 13: 2200 14: 2200 15: 2200 16: 2200 17: 2200
18: 2200 19: 2200 20: 2200 21: 2200 22: 2200 23: 2200 24: 2200
bogomips: 182399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 550.67
arch: Turing pcie: speed: 2.5 GT/s lanes: 16 ports: active: none
off: DVI-D-1,HDMI-A-1 empty: DP-1 bus-ID: 26:00.0 chip-ID: 10de:1f06
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 81
Monitor-1: DVI-D-1 mapped: DVI-D-0 note: disabled pos: primary,right
model: Lenovo D27-30 res: 1920x1080 dpi: 81 diag: 685mm (27")
Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: left
model: Lenovo LEN D27-20B res: 1920x1080 dpi: 82 diag: 686mm (27")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.67
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060
SUPER/PCIe/SSE2
API: Vulkan v: 1.3.275 surfaces: xcb,xlib device: 0 type: discrete-gpu
driver: N/A device-ID: 10de:1f06 device: 1 type: cpu driver: N/A
device-ID: 10005:0000
Audio:
Device-1: NVIDIA TU106 High Definition Audio driver: snd_hda_intel v: kernel
pcie: speed: 8 GT/s lanes: 16 bus-ID: 26:00.1 chip-ID: 10de:10f9
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 28: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-1:2 chip-ID: 0d8c:0005
API: ALSA v: k6.7.11-200.fc39.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
status: active 2: pipewire-media-session status: off 3: wireplumber
status: active 4: pipewire-alsa type: plugin 5: pw-jack type: plugin
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168
IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: 2c:f0:5d:5d:4f:36
IF-ID-1: virbr0 state: down mac: 52:54:00:b7:9b:d8
Drives:
Local Storage: total: 931.51 GiB used: 498.46 GiB (53.5%)
ID-1: /dev/nvme0n1 vendor: Kingston model: SA2000M81000G size: 931.51 GiB
speed: 31.6 Gb/s lanes: 4 serial: 50026B7683CFB5DE temp: 37.9 C
Partition:
ID-1: / size: 929.91 GiB used: 498.18 GiB (53.6%) fs: btrfs dev: /dev/dm-0
mapped: luks-27af6cf0-7d89-4926-b0d6-456432c04b87
ID-2: /boot size: 973.4 MiB used: 268.5 MiB (27.6%) 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: 498.18 GiB (53.6%) fs: btrfs
dev: /dev/dm-0 mapped: luks-27af6cf0-7d89-4926-b0d6-456432c04b87
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 10 MiB (0.1%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 51.9 C mobo: N/A gpu: nvidia temp: 51 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 10.45 GiB (33.4%)
Processes: 650 Power: uptime: 8h 44m wakeups: 0 Init: systemd v: 254
target: graphical (5) default: graphical
Packages: 66 pm: flatpak pkgs: 59 pm: snap pkgs: 7 Compilers: gcc: 13.2.1
Shell: Bash v: 5.2.26 running-in: konsole inxi: 3.3.33
And the power saving settings you are using?
When you say that it does not wake up the monitors what are you doing to wake the system?
How do you know that the rest of the system has woken up?
Did you ssh into it from another system for example?
This problem only occurs when I put my computer to sleep, not rebooting or shutting down. The system has woken up after putting it to sleep, but for some reason my monitors do not wake up for some reason. The only way to get my monitors to start displaying is by rebooting or turning the computer off completely and then turning it back on.
I also do not have another OS or Distro installed, it’s only Fedora.
if possible for comparison
and there is still the previous kernel, you can try booting through it
for example kernel-6.7.10-200
on kernel-6.7.11-200 I also experienced a similar problem regarding sleep and usb detection, the cause of which is currently unknown
with the previous kernel boot everything runs normally
Ah interesting. How long has this problem been going on for you? For me its been around a month.
When reporting problems it is good practice to apply vendor BIOS and Fedora updates so you aren’t chasing a solved problem.
Power management is always problematic with newer kernels because vendors have a variety of mechanisms and give priority to Windows support. Fortunately, large organizations are watching power requirements (my former workplace was designed for 300 watts per user, so plugging in another laptop could trip a breaker and shut down 4 other cubicles). Power management problems with systems aged 0 to 5 years usually to get fixed with BIOS and kernel updates. The new 6.8.4 kernel has helped others with similar problems.
1 Like
in the last week or so
currently in my case, via kernel update 6.8.4-200.fc39.x86_64 from update repository
this problem can be resolved
Linux dell-5480 6.8.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 4 20:45:21 UTC 2024 x86_64 GNU/Linux
1 Like