Nouveau/Nvidia drivers prevent laptop to resume after suspend (fresh Fedora 42 installation)

Ask Fedora
, , ,
1

Hello everyone,

I recently installed Fedora 42 Workstation on my laptop (Thinkpad P15v Gen3) and so far everythink works correctly except something related to Nvidia/Nouveau drivers.

When either of them is loaded, I can’t resume from suspend. The screen would power on but stay black. The keyboard is irresponsive.

If I disable Nouveau/Nvidia (via Grub boot commands for example) the system works as expected.

I’ve tried different solutions (tested using Nouveau, Nvidia from RPMFusion, Nvidia from proprietary installer, etc…).

Here are more details about the system :

inxi -bxx 
System:
  Host: ThinkPad-Leo Kernel: 6.15.3-200.fc42.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 15.1.1
  Console: pty pts/1 wm: gnome-shell DM: GDM Distro: Fedora Linux 42
    (Workstation Edition)
Machine:
  Type: Laptop System: LENOVO product: 21EM000YFR v: ThinkPad P15v Gen 3
    serial: PF4BH10C Chassis: type: 10 serial: PF4BH10C
  Mobo: LENOVO model: 21EM000YFR serial: L1HF33L002Y
    part-nu: LENOVO_MT_21EM_BU_Think_FM_ThinkPad P15v Gen 3 UEFI: LENOVO
    v: N3KET47W (1.25 ) date: 11/08/2024
Battery:
  ID-1: BAT0 charge: 29.1 Wh (48.9%) condition: 59.5/68.0 Wh (87.6%)
    volts: 12.1 min: 11.6 model: LGC 5B10W13960 serial: 933 status: charging
CPU:
  Info: 8-core AMD Ryzen 7 PRO 6850H with Radeon Graphics [MT MCP]
    arch: Zen 3+ speed (MHz): avg: 1096 min/max: 404/3201
Graphics:
  Device-1: NVIDIA TU117GLM [T600 Laptop GPU] vendor: Lenovo driver: nvidia
    v: 575.64 arch: Turing pcie: speed: 2.5 GT/s lanes: 8 bus-ID: 01:00.0
    chip-ID: 10de:1fb6
  Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M]
    vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s
    lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5,
    HDMI-A-1, Writeback-1 bus-ID: 67:00.0 chip-ID: 1002:1681 temp: 43.0 C
  Device-3: IMC Networks Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-1:2 chip-ID: 13d3:56fb
  Display: unspecified server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: amd mesa v: 25.0.7 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi rembrandt LLVM
    20.1.6 DRM 3.63 6.15.3-200.fc42.x86_64) device-ID: 1002:1681
  Info: Tools: api: glxinfo gpu: nvidia-settings,nvidia-smi x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Network:
  Device-1: Qualcomm QCNFA765 Wireless Network Adapter vendor: Lenovo
    driver: ath11k_pci v: kernel pcie: speed: 8 GT/s lanes: 1 bus-ID: 02:00.0
    chip-ID: 17cb:1103
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 6000 bus-ID: 04:00.0 chip-ID: 10ec:8168
Drives:
  Local Storage: total: 1.38 TiB used: 13.5 GiB (1.0%)
Info:
  Memory: total: 16 GiB note: est. available: 14.88 GiB used: 4.12 GiB (27.7%)
  Processes: 463 Power: uptime: 17m wakeups: 0 Init: systemd v: 257
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 8 Compilers:
    gcc: 15.1.1 Shell: Sudo v: 1.9.15p5 running-in: ptyxis-agent inxi: 3.3.38

This is the output of journactl --boot=-1 -n 100 after failing to resume (and a hard reboot) :

journactl --boot=-1 -n 100

juin 30 11:19:58 ThinkPad-Leo systemd-logind[1562]: The system will suspend now!
juin 30 11:19:58 ThinkPad-Leo ModemManager[1671]: [sleep-monitor-systemd] system is about to suspend
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.6414] manager: sleep: sleep requested (sleeping: no enabled: yes)
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.6418] device (enp4s0f0): state change: unavailable → unmanaged (reason ‘unmanaged-sleeping’, managed-type: ‘full’)
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.6483] device (p2p-dev-wlp2s0): state change: disconnected → unmanaged (reason ‘unmanaged-sleeping’, managed-type: ‘full’)
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.6486] manager: NetworkManager state is now ASLEEP
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.6488] device (wlp2s0): state change: activated → deactivating (reason ‘sleeping’, managed-type: ‘full’)
juin 30 11:19:58 ThinkPad-Leo systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service…
juin 30 11:19:58 ThinkPad-Leo systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
juin 30 11:19:58 ThinkPad-Leo audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=NetworkManager-dispatcher comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
juin 30 11:19:58 ThinkPad-Leo kernel: wlp2s0: deauthenticating from c0:3c:04:91:cb:44 by local choice (Reason: 3=DEAUTH_LEAVING)
juin 30 11:19:58 ThinkPad-Leo com.discordapp.Discord.desktop[5309]: 11:19:58.688 › [GatewaySocket] Performing an expedited heartbeat reason: network detected offline.
juin 30 11:19:58 ThinkPad-Leo wpa_supplicant[1831]: nl80211: send_event_marker failed: Source based routing not supported
juin 30 11:19:58 ThinkPad-Leo wpa_supplicant[1831]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=c0:3c:04:91:cb:44 reason=3 locally_generated=1
juin 30 11:19:58 ThinkPad-Leo wpa_supplicant[1831]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.7842] device (wlp2s0): state change: deactivating → disconnected (reason ‘sleeping’, managed-type: ‘full’)
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.7848] dhcp4 (wlp2s0): canceled DHCP transaction
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.7848] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Withdrawing address record for 2001:861:8bb2:e410:8c74:8718:2837:1e2e on wlp2s0.
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.7848] dhcp4 (wlp2s0): state changed no lease
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address 2001:861:8bb2:e410:8c74:8718:2837:1e2e.
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.7850] dhcp6 (wlp2s0): canceled DHCP transaction
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::ccb6:4f60:7c8b:7b61.
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.7851] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Registering new address record for fe80::ccb6:4f60:7c8b:7b61 on wlp2s0.*.
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.7851] dhcp6 (wlp2s0): state changed no lease
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Withdrawing address record for fe80::ccb6:4f60:7c8b:7b61 on wlp2s0.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::ccb6:4f60:7c8b:7b61.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
juin 30 11:19:58 ThinkPad-Leo audit[1687]: NETFILTER_CFG table=firewalld:8 family=1 entries=26 op=nft_unregister_rule pid=1687 subj=system_u:system_r:firewalld_t:s0 comm=“firewalld”
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.174.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Withdrawing address record for 192.168.1.174 on wlp2s0.
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.8174] device (wlp2s0): set-hw-addr: set MAC address to 3A:87:59:3B:87:79 (scanning)
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.174.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: New relevant interface wlp2s0.IPv4 for mDNS.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Registering new address record for 192.168.1.174 on wlp2s0.IPv4.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Withdrawing address record for 192.168.1.174 on wlp2s0.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.174.
juin 30 11:19:58 ThinkPad-Leo avahi-daemon[1531]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
juin 30 11:19:58 ThinkPad-Leo wpa_supplicant[1831]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=FR
juin 30 11:19:58 ThinkPad-Leo wpa_supplicant[1831]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=FR
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.8992] device (wlp2s0): supplicant interface state: completed → disconnected
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.8993] device (wlp2s0): supplicant interface state: disconnected → interface_disabled
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.8993] device (wlp2s0): supplicant interface state: interface_disabled → disconnected
juin 30 11:19:58 ThinkPad-Leo systemd-resolved[1498]: wlp2s0: Bus client reset search domain list.
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.8995] device (wlp2s0): state change: disconnected → unmanaged (reason ‘unmanaged-sleeping’, managed-type: ‘full’)
juin 30 11:19:58 ThinkPad-Leo systemd-resolved[1498]: wlp2s0: Bus client set default route setting: no
juin 30 11:19:58 ThinkPad-Leo systemd-resolved[1498]: wlp2s0: Bus client reset DNS server list.
juin 30 11:19:58 ThinkPad-Leo chronyd[1541]: Source 212.227.232.161 offline
juin 30 11:19:58 ThinkPad-Leo chronyd[1541]: Source 62.210.217.202 offline
juin 30 11:19:58 ThinkPad-Leo chronyd[1541]: Source 51.15.191.239 offline
juin 30 11:19:58 ThinkPad-Leo chronyd[1541]: Can’t synchronise: no selectable sources (4 unreachable sources)
juin 30 11:19:58 ThinkPad-Leo chronyd[1541]: Source 51.68.44.27 offline
juin 30 11:19:58 ThinkPad-Leo geoclue[2349]: WiFi scan failed
juin 30 11:19:58 ThinkPad-Leo wpa_supplicant[1831]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=BR
juin 30 11:19:58 ThinkPad-Leo NetworkManager[1811]: [1751275198.9944] device (wlp2s0): set-hw-addr: reset MAC address to 04:7B:CB:BB:E3:F2 (unmanage)
juin 30 11:19:59 ThinkPad-Leo wpa_supplicant[1831]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
juin 30 11:19:59 ThinkPad-Leo wpa_supplicant[1831]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
juin 30 11:19:59 ThinkPad-Leo wpa_supplicant[1831]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
juin 30 11:19:59 ThinkPad-Leo wpa_supplicant[1831]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
juin 30 11:19:59 ThinkPad-Leo wpa_supplicant[1831]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
juin 30 11:19:59 ThinkPad-Leo wpa_supplicant[1831]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
juin 30 11:19:59 ThinkPad-Leo gnome-shell[2960]: Cursor update failed: drmModeAtomicCommit: Argument invalide
juin 30 11:19:59 ThinkPad-Leo systemd[1]: Reached target sleep.target - Sleep.
juin 30 11:19:59 ThinkPad-Leo systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions…
juin 30 11:19:59 ThinkPad-Leo suspend[7960]: nvidia-suspend.service
juin 30 11:19:59 ThinkPad-Leo logger[7960]: <13>Jun 30 11:19:59 suspend: nvidia-suspend.service
juin 30 11:19:59 ThinkPad-Leo kernel: rfkill: input handler enabled
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSource/ldac
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSink/aac
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSource/aac
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSink/opus_g
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSource/opus_g
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSink/sbc
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSource/sbc
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSource/faststream
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSource/faststream_duplex
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSink/opus_05
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSource/opus_05
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSink/opus_05_duplex
juin 30 11:19:59 ThinkPad-Leo bluetoothd[1749]: Endpoint unregistered: sender=:1.105 path=/MediaEndpoint/A2DPSource/opus_05_duplex
juin 30 11:19:59 ThinkPad-Leo gsd-media-keys[3111]: Unable to get default sink
juin 30 11:19:59 ThinkPad-Leo gsd-media-keys[3111]: Unable to get default source
juin 30 11:20:00 ThinkPad-Leo uresourced[1874]: Setting resources on user-1000.slice (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100)
juin 30 11:20:00 ThinkPad-Leo uresourced[1874]: Setting resources on user@1000.service (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100)
juin 30 11:20:00 ThinkPad-Leo uresourced[1874]: Setting resources on user.slice (MemoryMin: 0, MemoryLow: 0, CPUWeight: -, IOWeight: -)
juin 30 11:20:00 ThinkPad-Leo systemd[1]: nvidia-suspend.service: Deactivated successfully.
juin 30 11:20:00 ThinkPad-Leo systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
juin 30 11:20:00 ThinkPad-Leo audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=nvidia-suspend comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
juin 30 11:20:00 ThinkPad-Leo audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=nvidia-suspend comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
juin 30 11:20:00 ThinkPad-Leo systemd[1]: Starting systemd-suspend.service - System Suspend…
juin 30 11:20:00 ThinkPad-Leo systemd[1]: user@1000.service: Unit now frozen-by-parent.
juin 30 11:20:00 ThinkPad-Leo systemd[1]: session-2.scope: Unit now frozen-by-parent.
juin 30 11:20:00 ThinkPad-Leo systemd[1]: user.slice: Unit now frozen.
juin 30 11:20:00 ThinkPad-Leo systemd[1]: user-1000.slice: Unit now frozen-by-parent.
juin 30 11:20:00 ThinkPad-Leo systemd-sleep[8004]: Successfully froze unit ‘user.slice’.
juin 30 11:20:00 ThinkPad-Leo systemd-sleep[8004]: Performing sleep operation ‘suspend’…
juin 30 11:20:00 ThinkPad-Leo kernel: PM: suspend entry (s2idle)
juin 30 11:20:00 ThinkPad-Leo kernel: Filesystems sync: 0.044 seconds

As you can see there is nothing after the suspend.

Any help would be appreciated. Thank you in advance ! :slight_smile:

2

It sounds like a bug, I have seen a few other suspend / resume issues recently.

3

I’ve found that nvidia-powerd fails to start, could it be linked to the error ?

sudo journalctl --boot=-1 --no-hostname | grep nvidia 
juil. 01 23:27:09 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-powerd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
juil. 01 23:27:09 systemd[1]: Started nvidia-powerd.service - nvidia-powerd service.
juil. 01 23:27:09 nvidia-powerd[1477]: nvidia-powerd version:2.0 (build 1)
juil. 01 23:27:10 nvidia-powerd[1477]: ERROR! Allocate Root client failed 0x59
juil. 01 23:27:10 systemd[1]: nvidia-powerd.service: Deactivated successfully.
juil. 01 23:27:10 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-powerd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
juil. 01 23:28:43 audit[16560]: SOFTWARE_UPDATE pid=16560 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 msg='op=install sw="kmod-nvidia-6.15.4-200.fc42.x86_64-3:575.64-2.fc42.x86_64" sw_type=rpm key_enforce=0 gpg_res=0 root_dir="/" comm="dnf" exe="/usr/bin/dnf5" hostname=? addr=? terminal=? res=success'
juil. 01 23:28:43 akmods[1459]: Building and installing nvidia-kmod [  OK  ]
juil. 01 23:28:44 kernel: nvidia: loading out-of-tree module taints kernel.
juil. 01 23:28:44 kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
juil. 01 23:28:44 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
juil. 01 23:28:45 kernel: nvidia 0000:01:00.0: enabling device (0006 -> 0007)
juil. 01 23:28:45 kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  575.64  Release Build  (dvs-builder@U22-I3-AF02-18-4)  Tue Jun 10 18:43:58 UTC 2025
juil. 01 23:28:45 kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
juil. 01 23:28:47 kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 0
juil. 01 23:28:47 kernel: nvidia 0000:01:00.0: [drm] No compatible format found
juil. 01 23:28:47 kernel: nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes
juil. 01 23:28:48 systemd[1]: nvidia-fallback.service - Fallback to nouveau as nvidia did not load was skipped because of an unmet condition check (ConditionPathExists=!/sys/module/nvidia).
juil. 01 23:28:50 gnome-shell[16660]: Added device '/dev/dri/card0' (nvidia-drm) using atomic mode setting.
juil. 01 23:28:57 gnome-shell[17549]: Added device '/dev/dri/card0' (nvidia-drm) using atomic mode setting.
juil. 01 23:28:59 systemd[17376]: Started app-gnome-nvidia\x2dsettings\x2duser-17707.scope - Application launched by gnome-session-binary.
juil. 01 23:29:27 gnome-software[17744]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform.GL.nvidia-575-64/x86_64/1.4 complete
juil. 01 23:29:27 gnome-software[17744]: /var/tmp/flatpak-cache-IOYE92/org.freedesktop.Platform.GL.nvidia-575-64-HFYE92/repo-oYzEg4: Pulled runtime/org.freedesktop.Platform.GL.nvidia-575-64/x86_64/1.4 from flathub
juil. 01 23:29:27 systemd[1]: var-tmp-flatpak\x2dcache\x2dIOYE92-org.freedesktop.Platform.GL.nvidia\x2d575\x2d64\x2dHFYE92.mount: Deactivated successfully.
juil. 01 23:29:28 flatpak-system-helper[18987]: system: Pulled runtime/org.freedesktop.Platform.GL.nvidia-575-64/x86_64/1.4 from /var/lib/flatpak/repo/tmp/flatpak-cache-R20E92/repo-oYzEg4
juil. 01 23:29:28 flatpak-system-helper[18987]: system: Updated runtime/org.freedesktop.Platform.GL.nvidia-575-64/x86_64/1.4 from flathub
juil. 01 23:29:58 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
juil. 01 23:29:58 suspend[19233]: nvidia-suspend.service
juil. 01 23:29:58 logger[19233]: <13>Jul  1 23:29:58 suspend: nvidia-suspend.service
juil. 01 23:29:58 systemd[1]: nvidia-suspend.service: Deactivated successfully.
juil. 01 23:29:58 systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
juil. 01 23:29:58 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
juil. 01 23:29:58 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
4

When reporting an issue you should include enough detail to allow others with similar hardware to reproduce the issue, in particular the Nvidia model. Quoting Nvidia developer forum:

  • Nvidia-powerd is only for mobile Ampere gpus so it’s useless with [other models]

The post recommends that you “disable and mask the service”, but I think that just eliminates the messages.

5

Hi, thank you for your response. I was not aware that nvidia-powerd was only for mobile Ampere GPUs, so I guess the message is not relevant.

My original message contains the output of inxi -bxx, which additional informations should I give to have enough details about my system ? Thank you.

6

I checked and Google searches now find this topic. Resume after suspend is a common issue with 6.15 kernels, so worth searching for other reports. Power management is always a “work in progress” as vendors try to get linux power demands that compare well with Windows (so they can capture volume purchases for cubicle farms where there are watts per seat limits for both power and cooling demands).

You should check for vendor firmware updates.

[Systemd issue 37590] (Freezing user space processes failed · Issue #37590 · systemd/systemd · GitHub) deals with resume from suspend issues. You might get some ideas or be able to add details that help resolve the problem.

7

cat /sys/power/mem_sleep
s2idle or deep = S3 ?

if it’s S3 then it could be a BIOS bug. It may work better with s2idle if available.

have you verified settings in
/usr/lib/modprobe.d/nvidia-power-management.conf

Also read /usr/share/doc/xorg-x11-drv-nvidia/html/powermanagement.html

8

Hello,
It’s s2idle. I should probably mention that everything works as expected on Ubuntu, so I don’t think it’s related to the firmware.

For now I’ve removed the nvidia drivers, so nvidia-power-management.conf was removed. Do you know what setting I should verify ?

9

Hello again,
I’ve tried to add options nvidia NVreg_DynamicPowerManagement=0x00 in /usr/lib/modprobe.d/nvidia-power-management.conf (and in /etc/modprobe.d/nvidia-power-management.conf just in case) (as suggested here) but with no success.

I think my problem is different as the system doesn’t fail to suspend but doesn’t wake up. I can’t open a tty after trying to resume.

I’ve also found that, even with no driver enabled for the discrete Nvidia GPU, it uses a lot of energy to the point that I need to disable it using envycontrol to keep my laptop useful (without it the battery lasts ~1h30). I have no idea why it happens.

10

bro is the same bug im facing for months, its annoying.

i always have to reboot to make computer usable again, always happens when return from supension.

11

Hi, that’s not completely true : Nvidia-powerd is mandatory also for Ampere and any other newer GPUs. (like my ADA RTX 4060)

For example, on Fedora 42 updated as of today, withot nvidia-powerd the TDP of GPU is limited at 55W (RTX 4060 mobile Legion 5 slim):

    GPU Power Readings
        Average Power Draw                : N/A
        Instantaneous Power Draw          : 590.01 W
        Current Power Limit               : 55.00 W
        Requested Power Limit             : 55.00 W
        Default Power Limit               : 55.00 W
        Min Power Limit                   : 5.00 W
        Max Power Limit                   : 105.00 W

While instead after manually starting Nvidia-powerd, the TDP is correct:

    GPU Power Readings
        Average Power Draw                : N/A
        Instantaneous Power Draw          : 590.01 W
        Current Power Limit               : 100.00 W
        Requested Power Limit             : 100.00 W
        Default Power Limit               : 55.00 W
        Min Power Limit                   : 5.00 W
        Max Power Limit                   : 105.00 W

Moreover I’ve to say that Nvidia-powerd in fedora 42 fails to start automatically:

Jul 20 11:58:50 fedora nvidia-powerd[1119]: nvidia-powerd version:2.0 (build 1)
Jul 20 11:58:50 fedora nvidia-powerd[1119]: ERROR! Allocate Root client failed 0x59
Jul 20 11:58:50 fedora systemd[1]: nvidia-powerd.service: Deactivated successfully.

And that’s a pretty terrible bug, in this way I only use 50% of my GPU power!

Still didn’t figured out how to solve the startup error of nvidia-powerd…if some help I’ll appreciate!

12

Please see my previous answer: nvidia-powerd is needed for Ampere and any newer gpus as well.

13

Thank you for your answer, however nvidia-powerd is correctly installed and runs on startup, so this is not the issue.

14

I have tried to copy /etc/modprobe.d and /usr/lib/modprobe.d config files related to nvidia from my (working correctly) Ubuntu drive. It did not changed anything.

For good mesure here are the files, if someone find anything useful in them.

/etc/modprobe.d/nvidia-graphics-drivers-kms.conf 
# Nvidia modesetting support. Set to 0 or comment to disable kernel modesetting
# and framebuffer console support. This must be disabled in case of Mosaic or SLI.

options nvidia-drm modeset=1
/usr/lib/modprobe.d/nvidia-graphics-drivers.conf 
# Nouveau must be blacklisted here as well beside from the initrd to avoid a
# delayed loading (for example on Optimus laptops where the Nvidia card is not
# driving the main display).

blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off

# Enable complete power management. From:
# file:///usr/share/doc/nvidia-driver/html/powermanagement.html

options nvidia NVreg_TemporaryFilePath=/var/tmp
options nvidia NVreg_EnableS0ixPowerManagement=1
options nvidia NVreg_PreserveVideoMemoryAllocations=1
/usr/lib/modprobe.d/nvidia-kms.conf 
# This file was generated by nvidia-prime
# Set value to 1 to enable modesetting
options nvidia-drm modeset=1
/usr/lib/modprobe.d/nvidia-runtimepm.conf 
options nvidia "NVreg_DynamicPowerManagement=0x02"
15

and

I wonder if that is some holdover from the now outdated Nvidia docs.

Major changes to ACPI were made for the 6.15 kernels – @myselfleo which kernel did you use on Ubuntu?

16

Ubuntu is using 6.8.0-60.
On Fedora the problem was already there with 6.14, so maybe something changed between those 2 versions ?

17

Power management in linux has been under pressure to match Windows, I assume driven by vendors hoping to sell large volumes to cubicle farms. The changes often require updates to ACPI/BIOS firmware from vendors, so firmware that works for a 6.8 kernel may need updating for newer kernels.

18

My firmware is up to date, so basically I’m stuck until some update changes something ? It seems strange to be tbh