4

I recently upgraded my system from 24.04 to 24.10. System suspend is not working. I am unable to resume from sleep. Could this be due to Nvidia? On my other laptop which has an Intel 3217u CPU system suspend is working fine. Is there a workaround?

Also I had taken a snapshot of /root and hidden folders of /home using Timeshift in Ubuntu 24.04. If I choose to downgrade from 24.10 to 24.04 using Timeshift, will there be any issues?

   OS: Ubuntu 24.10 x86_64
   Host: ASUS TUF Gaming A17 FA706IH
   Kernel: 6.11.0-8-generic
   Uptime: 24 mins
   Packages: 2842 (dpkg), 64 (flatpak)
   Shell: bash 5.2.32
   Resolution: 1920x1080
   DE: GNOME 47.0
   WM: Mutter
   WM Theme: Adwaita
   Theme: Yaru-dark [GTK2/3]
   Icons: Yaru-dark [GTK2/3]
   Terminal: gnome-terminal
   CPU: AMD Ryzen 5 4600H with Radeon Graphics
   GPU: NVIDIA GeForce GTX 1650 Mobile
   GPU: AMD Radeon Vega Series
   Memory: 5175MB / 30992MB
   Display server: Wayland
   Nvidia driver: 560

karel
  • 122,292
  • 133
  • 301
  • 332
Praneet
  • 41

4 Answers4

2

I encountered the same problem. After upgrading, my Xiaomi Mi Pro laptop to Ubuntu 24.10 doesn't wake up from suspend. The power button and mouse light up, but the screen stays black.

I removed the Nvidia proprietary drivers using:

sudo apt-get --purge remove "*nvidia*"

and installed the nouveau-firmware. Now it seems to be working fine.

It looks like there might be a bug in the Nvidia drivers.

The command sudo ubuntu-drivers list is freezes also. It doesn't produce any output or finish executing, it just gets stuck on the command line.

Update

I discovered that I was having issues with WiFi and Bluetooth connectivity, particularly related to system suspend. To address this, I created a systemd service file that disables wireless interfaces before suspend and re-enables them on resume.

Solution:

Create a custom systemd service file to manage WiFi and Bluetooth during suspend/resume.

  1. Open a new service file in a text editor with root permissions:

    sudo vim /etc/systemd/system/rfkill-suspend.service

  2. Add the following configuration:

    [Unit]
Description=Disable Bluetooth and WiFi before suspend, re-enable on resume
Before=sleep.target
StopWhenUnneeded=yes

    [Service]
Type=oneshot
ExecStart=/usr/bin/rfkill block bluetooth
ExecStart=/usr/bin/rfkill block wifi
ExecStop=/usr/bin/rfkill unblock bluetooth
ExecStop=/usr/bin/rfkill unblock wifi
RemainAfterExit=yes
    

    [Install]
WantedBy=sleep.target

  3. Save and close the file.

  4. Reload systemd to apply the new service:

    sudo systemctl daemon-reload

  5. Enable the service so it starts automatically:

    sudo systemctl enable rfkill-suspend.service

Now, Bluetooth and WiFi will be disabled just before suspend and re-enabled upon resume. This can help resolve connectivity issues related to suspend/resume cycles.

Pavel Smagin
  • 21
2

Running journalctl -b showed an error with nvidia:

Unit nvidia-suspend.service not found.

A github thread suggests disabling the nvidia-suspend service. The nvidia-suspend.sh has been removed in an update. But the system is still trying to run it, which is causing an error and blocking the suspend process.

The services should be disabled:

sudo systemctl disable nvidia-suspend.service
sudo systemctl disable nvidia-hibernate.service
sudo systemctl disable nvidia-resume.service

The linked github thread discusses other fixes, however these were sufficient for me to get my laptop to suspend normally.

James K
  • 268
  • 2
  • 16
1

I had a similar problem after upgrading to 24.10, suspend would not actually suspend (screen would blank, but pc would not go into suspend state then screen just came back on again).

I was already using nouveau as the active driver, but still had some nvidia packages installed.

Uninstalling all nvidia related packages as per the other answer resolved it.

I believe that one of those packages may have added a suspend/resume hook or similar that caused the failure as the nvidia module was not actually in use (just a theory)

David Collett
  • 11
0

Apparently, the suspend problem has been fixed starting from driver 565.

Addtional Drivers allowed me to choose nvidia-driver-570-server, which solved the problem in my case, after trying several of the many the suggestions.

https://gist.github.com/bmcbm/375f14eaa17f88756b4bdbbebbcfd029?permalink_comment_id=5527056#gistcomment-5527056

Bart
  • 121