search

pop-os / pop

A project for managing all Pop!_OS sources
https://system76.com/pop
2.43k stars 84 forks source link

Laptop wont wake from sleep - power button does nothing to wake #449

Open johnwbaxter opened 5 years ago

johnwbaxter commented 5 years ago

NAME="Pop!_OS" VERSION="18.04 LTS" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://system76.com/pop" SUPPORT_URL="http://support.system76.com" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" PRIVACY_POLICY_URL="https://system76.com/privacy" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic

When i set my laptop to lock (status bar menu -> button with padlock icon) and come back to it, it wont wake from sleep. Pressing the power button does nothing. This is a recent thing, it's been working fine up until the last week.

no-worky

ajfoster85 commented 5 years ago

Does the solution mentioned here help?

Basically you add rcutree.rcu_idle_gp_delay=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub

panzelva commented 5 years ago

Hello :) I have same problem with my Dell XPS 15 9570

NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

My /etc/default/grub file looks like this:

GRUB_DEFAULT=0
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash rcutree.rcu_idle_gp_delay=1"
GRUB_CMDLINE_LINUX=""

But the problem still persists.

mmstick commented 5 years ago

That's likely because we don't use GRUB. The correct change would be kernelstub -a rcutree.rcu_idle_gp_delay=1 to have kernelstub configure your systemd-boot loader entries.

panzelva commented 5 years ago

Hi, thanks for advice.

kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer.

It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time.

So I changed my search and found this and It looks like my problem was with s2idle.

After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone.

This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3
nazmulidris commented 5 years ago

I experienced the same problem on an Oryx Pro (oryp5 16") machine. It was working fine until I switched from Intel to Nvidia graphics option a few days ago.

mmstick commented 5 years ago

@nazmulidris Be sure to create an issue with support.

nazmulidris commented 5 years ago

@mmstick Thank you. I just created one :+1:

fiLLLip commented 5 years ago

After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone.

My cat /sys/power/mem_sleep showed s2idle [deep], but I ran the kernelstub command anyways. After reboot, suspend worked flawlessly.

My config: Dell Latitude 5491 with Nvidia graphics and Windows UEFI dual boot (no partition crypto)

dmitrijt9 commented 4 years ago

Hi, thanks for advice.

kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer.

It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time.

So I changed my search and found this and It looks like my problem was with s2idle.

After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone.

This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

I also switched sleep to deep and set delay to 1 using kernelstub. After reboot works everything fine. Thanks :)

My config: Dell XPS 9570 Nvidia graphics Pop!Os 19.10 Without partition encryption

Bearbobs commented 4 years ago

solved for me as well !

Hi, thanks for advice. kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer. It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time. So I changed my search and found this and It looks like my problem was with s2idle. After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone. This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

I also switched sleep to deep and set delay to 1 using kernelstub. After reboot works everything fine. Thanks :)

My config: Dell XPS 9570 Nvidia graphics Pop!Os 19.10 Without partition encryption

undefinednpc commented 4 years ago

Hi, thanks for advice. kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer. It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time. So I changed my search and found this and It looks like my problem was with s2idle. After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone. This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

I also switched sleep to deep and set delay to 1 using kernelstub. After reboot works everything fine. Thanks :)

My config: Dell XPS 9570 Nvidia graphics Pop!Os 19.10 Without partition encryption

worked for me as well, thank you

HatimLagzar commented 4 years ago

Hi, thanks for advice.

kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer.

It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time.

So I changed my search and found this and It looks like my problem was with s2idle.

After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone.

This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

Worked for me too, on dell XPS 9570 pop os 19.10 Thanks

bisgardo commented 4 years ago

The fixes above didn't work for me on my Lenovo X1 Carbon (7th gen) but led me, along with this, to a working fix:

# kernelstub -a snd_hda_intel.dmic_detect=0
# kernelstub -p
kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.10
    Root partition:....../dev/dm-1
    Root FS UUID:........21598a6c-f9fc-46ab-8fea-35b1356f6d7a
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.quiet systemd.show_status=false loglevel=0 splash snd_hda_intel.dmic_detect=0
    Kernel Image Path:.../boot/vmlinuz-5.3.0-7642-generic
    Initrd Image Path:.../boot/initrd.img-5.3.0-7642-generic
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3
# uname -a
Linux pop-os 5.3.0-7642-generic #34~1584408018~19.10~21df4b1-Ubuntu SMP Tue Mar 17 13:38:51 UTC  x86_64 x86_64 x86_64 GNU/Linux

Note that in the referenced reddit thread the fix is described as "temporary" and, as I understand it, has been fixed in newer kernels.

ivanstegic commented 4 years ago

I can confirm that this worked on my Lenovo ThinkPad X1 Carbon 7th Gen as well.

$ sudo kernelstub -p
kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.10
    Root partition:....../dev/dm-1
    Root FS UUID:........f7446fcb-9b5a-4565-9144-41d1f680ab85
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash snd_hda_intel.dmic_detect=0
    Kernel Image Path:.../boot/vmlinuz-5.3.0-7642-generic
    Initrd Image Path:.../boot/initrd.img-5.3.0-7642-generic
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

$ uname -a
Linux x1 5.3.0-7642-generic #34~1584408018~19.10~21df4b1-Ubuntu SMP Tue Mar 17 13:38:51 UTC  x86_64 x86_64 x86_64 GNU/Linux
jrjones34 commented 4 years ago

That's likely because we don't use GRUB. The correct change would be kernelstub -a rcutree.rcu_idle_gp_delay=1 to have kernelstub configure your systemd-boot loader entries.

I started having the issue outlined by OP after a recent update. This suggestion from @mmstick seems to have worked for me.

neofetch output:

OS: Pop!_OS 19.10 x86_64 
Host: Thelio Major thelio-major-b1 
Kernel: 5.3.0-7648-generic 
Uptime: 14 mins 
Packages: 2515 (dpkg), 8 (flatpak), 10 (snap) 
Shell: bash 5.0.3 
Resolution: 2560x1440, 2560x1440 
DE: GNOME 3.34.3 
WM: GNOME Shell 
WM Theme: Pop 
Theme: Pop [GTK2/3] 
Icons: Pop [GTK2/3] 
Terminal: tilix 
CPU: Intel i7-7820X (16) @ 4.300GHz 
GPU: AMD ATI Radeon RX 470/480/570/570X/580/580X/590 
Memory: 2747MiB / 31811MiB

kernelstub -p output:

kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.10
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........e0a45886-e0a1-4108-885d-755cf554dea1
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash rcutree.rcu_idle_gp_delay=1
    Kernel Image Path:.../boot/vmlinuz-5.3.0-7648-generic
    Initrd Image Path:.../boot/initrd.img-5.3.0-7648-generic
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3
Caligulaa commented 4 years ago

Hi, thanks for advice. kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer. It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time. So I changed my search and found this and It looks like my problem was with s2idle. After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone. This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

Worked for me too, on dell XPS 9570 pop os 19.10 Thanks

this worked for me to on a msi gs60 labtop... What the heck though seriously. My laptop almost caught fire in my bag today... Low bat suspend worked fine but heh.. thanks for the fix...!

alexphelps commented 3 years ago

snd_hda_intel.dmic_detect=0 worked for me! :grinning:

woook commented 3 years ago

I can't quite believe it but snd_hda_intel.dmic_detect=0 worked for me too! grinning

Lenovo Thinkpad on Pop!_OS 20.10, Kernel: 5.11.0-7612-generic

woook commented 3 years ago

I have to partially retract - it have solved it for me most of the time but every ~5th suspend - I get the same issue and it won't wake

hayetmd commented 3 years ago

Hello, My PC wouldn't wake up after suspend, everything just freezes. I am not using EFI so kernelstub is kinda useless for me. And I am not using grub either. I have dual-boot setup with windows, I usually use POP OS from boot menu each time and i prefer this way. Any suggestion would be appreciated. Thank You.

grep . /sys/bus/usb/devices/*/power/wakeup /sys/bus/usb/devices/1-1/power/wakeup:disabled /sys/bus/usb/devices/2-1/power/wakeup:disabled /sys/bus/usb/devices/3-6/power/wakeup:disabled /sys/bus/usb/devices/3-9/power/wakeup:enabled /sys/bus/usb/devices/usb1/power/wakeup:disabled /sys/bus/usb/devices/usb2/power/wakeup:disabled /sys/bus/usb/devices/usb3/power/wakeup:disabled /sys/bus/usb/devices/usb4/power/wakeup:disabled

arbitrary-dev commented 3 years ago

mem_sleep_default=deep

Setting this parameter (but to shallow) on my lemp10 resulted in sleep key issues #1678

Marivishnu commented 3 years ago

Hi, thanks for advice.

kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer.

It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time.

So I changed my search and found this and It looks like my problem was with s2idle.

After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone.

This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

Hello, even I am having this problem but even after changing using the kernelstub method, my fan is still running and the power LED is flashing. After opening the lid, the screen became black and I need to hard reboot to use my laptop again. Any suggestion? Pop_OS : 20.10 kernel : 5.11.0-7614-generic

Kernelstub output after changing:

kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 20.10
    Root partition:....../dev/sda8
    Root FS UUID:........c60d3125-0944-4bf1-a027-064129735aec
    ESP Path:............/boot/efi
    ESP Partition:......./dev/sda10
    ESP Partition #:.....0
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash mem_sleep_default=deep
    Kernel Image Path:.../boot/vmlinuz-5.11.0-7614-generic
    Initrd Image Path:.../boot/initrd.img-5.11.0-7614-generic
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

I have dual boot setup with my Windows 10 and I am not using grub.

NotAdi commented 3 years ago

Hi, thanks for advice. kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer. It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time. So I changed my search and found this and It looks like my problem was with s2idle. After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone. This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

Hello, even I am having this problem but even after changing using the kernelstub method, my fan is still running and the power LED is flashing. After opening the lid, the screen became black and I need to hard reboot to use my laptop again. Any suggestion? Pop_OS : 20.10 kernel : 5.11.0-7614-generic

Kernelstub output after changing:

kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 20.10
    Root partition:....../dev/sda8
    Root FS UUID:........c60d3125-0944-4bf1-a027-064129735aec
    ESP Path:............/boot/efi
    ESP Partition:......./dev/sda10
    ESP Partition #:.....0
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash mem_sleep_default=deep
    Kernel Image Path:.../boot/vmlinuz-5.11.0-7614-generic
    Initrd Image Path:.../boot/initrd.img-5.11.0-7614-generic
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

I have dual boot setup with my Windows 10 and I am not using grub.

I am facing the exact same issue. Tried all the possible solutions mentioned above but none worked. Here's what kernelstub -p shows

kernelstub.Config : INFO Looking for configuration... kernelstub : INFO System information: 

OS:..................Pop!_OS 20.10
Root partition:....../dev/sda3
Root FS UUID:........de9a28f6-3bce-41cd-a1b5-79aeb1c82381
ESP Path:............/boot/efi
ESP Partition:......./dev/sda2
ESP Partition #:.....2
NVRAM entry #:.......-1
Boot Variable #:.....0000
Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash rcutree.rcu_idle_gp_delay=1 mem_sleep_default=deep snd_hda_intel.dmic_detect=0
Kernel Image Path:.../boot/vmlinuz-5.11.0-7614-generic
Initrd Image Path:.../boot/initrd.img-5.11.0-7614-generic
Force-overwrite:.....False

kernelstub : INFO Configuration details:

ESP Location:................../boot/efi Management Mode:...............True Install Loader configuration:..True Configuration version:.........3

And here's what neofetch shows: https://imgur.com/c0yS6FS

The problem started out of the blue and it has become a huge pain because if i leave my laptop for sometime, it just becomes unusable unless I hard reboot it.

I am dual booting it with windows btw.

Marivishnu commented 3 years ago

Hi, thanks for advice. kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer. It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time. So I changed my search and found this and It looks like my problem was with s2idle. After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone. This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

Hello, even I am having this problem but even after changing using the kernelstub method, my fan is still running and the power LED is flashing. After opening the lid, the screen became black and I need to hard reboot to use my laptop again. Any suggestion? Pop_OS : 20.10 kernel : 5.11.0-7614-generic Kernelstub output after changing:

kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 20.10
    Root partition:....../dev/sda8
    Root FS UUID:........c60d3125-0944-4bf1-a027-064129735aec
    ESP Path:............/boot/efi
    ESP Partition:......./dev/sda10
    ESP Partition #:.....0
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash mem_sleep_default=deep
    Kernel Image Path:.../boot/vmlinuz-5.11.0-7614-generic
    Initrd Image Path:.../boot/initrd.img-5.11.0-7614-generic
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

I have dual boot setup with my Windows 10 and I am not using grub.

I am facing the exact same issue. Tried all the possible solutions mentioned above but none worked. Here's what kernelstub -p shows

kernelstub.Config : INFO Looking for configuration... kernelstub : INFO System information:

OS:..................Pop!_OS 20.10
Root partition:....../dev/sda3
Root FS UUID:........de9a28f6-3bce-41cd-a1b5-79aeb1c82381
ESP Path:............/boot/efi
ESP Partition:......./dev/sda2
ESP Partition #:.....2
NVRAM entry #:.......-1
Boot Variable #:.....0000
Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash rcutree.rcu_idle_gp_delay=1 mem_sleep_default=deep snd_hda_intel.dmic_detect=0
Kernel Image Path:.../boot/vmlinuz-5.11.0-7614-generic
Initrd Image Path:.../boot/initrd.img-5.11.0-7614-generic
Force-overwrite:.....False

kernelstub : INFO Configuration details:

ESP Location:................../boot/efi Management Mode:...............True Install Loader configuration:..True Configuration version:.........3

And here's what neofetch shows: https://imgur.com/c0yS6FS

The problem started out of the blue and it has become a huge pain because if i leave my laptop for sometime, it just becomes unusable unless I hard reboot it.

I am dual booting it with windows btw.

Hello, Are you using NVIDIA GPU?

NotAdi commented 3 years ago

Hello, Are you using NVIDIA GPU?

I have set GPU to integrated and it's been like that ever since I installed pop like 2 months ago.

Marivishnu commented 3 years ago

Hello, Are you using NVIDIA GPU?

I have set GPU to integrated and it's been like that ever since I installed pop like 2 months ago.

Thanks for your reply. I am using NVIDIA GPU and set It to hybrid. I found that after the recent update, my NVIDIA drivers were missing and that led to the problem of not suspending.

Here are the possible solutions:

  1. If you have NVIDIA GPU, try reinstalling NVIDIA drivers (first nvidia-driver 450 and install nvidia-driver 460 on top of it.). After a reboot, it solved the suspend problem.
  2. https://askubuntu.com/questions/840093/suspend-on-lid-close-doesnt-work-16-04?rq=1 Go to this forum post and try the methods suggested by Jesse van Dam. It too solved the problem. But if you have NVIDIA GPU then try the first method.

These methods solved my problem. :)

NotAdi commented 3 years ago

Hello, Are you using NVIDIA GPU?

I have set GPU to integrated and it's been like that ever since I installed pop like 2 months ago.

Thanks for your reply. I am using NVIDIA GPU and set It to hybrid. I found that after the recent update, my NVIDIA drivers were missing and that led to the problem of not suspending.

Here are the possible solutions:

  1. If you have NVIDIA GPU, try reinstalling NVIDIA drivers (first nvidia-driver 450 and install nvidia-driver 460 on top of it.). After a reboot, it solved the suspend problem.
  2. https://askubuntu.com/questions/840093/suspend-on-lid-close-doesnt-work-16-04?rq=1 Go to this forum post and try the methods suggested by Jesse van Dam. It too solved the problem. But if you have NVIDIA GPU then try the first method.

These methods solved my problem. :)

THANKS A TON!!!!!! I spent like 2 days trying to fix this stupid problem but nothing worked. Turns out it really was related to NVIDIA drivers. As you said, recent update somehow removed the drivers. After re-installing the drivers, in my initial testing, it looks like the problem's solved. Hopefully, when i wake up tomorrow, i don't have to hard reboot the system. Will let you know if i still encounter the issue

Marivishnu commented 3 years ago

Hello, Are you using NVIDIA GPU?

I have set GPU to integrated and it's been like that ever since I installed pop like 2 months ago.

Thanks for your reply. I am using NVIDIA GPU and set It to hybrid. I found that after the recent update, my NVIDIA drivers were missing and that led to the problem of not suspending. Here are the possible solutions:

  1. If you have NVIDIA GPU, try reinstalling NVIDIA drivers (first nvidia-driver 450 and install nvidia-driver 460 on top of it.). After a reboot, it solved the suspend problem.
  2. https://askubuntu.com/questions/840093/suspend-on-lid-close-doesnt-work-16-04?rq=1 Go to this forum post and try the methods suggested by Jesse van Dam. It too solved the problem. But if you have NVIDIA GPU then try the first method.

These methods solved my problem. :)

THANKS A TON!!!!!! I spent like 2 days trying to fix this stupid problem but nothing worked. Turns out it really was related to NVIDIA drivers. As you said, recent update somehow removed the drivers. After re-installing the drivers, in my initial testing, it looks like the problem's solved. Hopefully, when i wake up tomorrow, i don't have to hard reboot the system. Will let you know if i still encounter the issue

Thats fantastic to hear!

Bananas-Are-Yellow commented 3 years ago

I am having the same problem with my Oryx Pro laptop. It fails to suspend: the keyboard is still lit up and fans are still on. Have to long-press the power button and restart it.

Tried mem_sleep_default=deep and rcutree.rcu_idle_gp_delay=1 and rebooted but these did not fix it. The problem only started recently.

I am using integrated graphics.

Marivishnu commented 3 years ago

I am having the same problem with my Oryx Pro laptop. It fails to suspend: the keyboard is still lit up and fans are still on. Have to long-press the power button and restart it.

Tried mem_sleep_default=deep and rcutree.rcu_idle_gp_delay=1 and rebooted but these did not fix it. The problem only started recently.

I am using integrated graphics.

Does your laptop have NVIDIA GPU?

Bananas-Are-Yellow commented 3 years ago

I am having the same problem with my Oryx Pro laptop. It fails to suspend: the keyboard is still lit up and fans are still on. Have to long-press the power button and restart it. Tried mem_sleep_default=deep and rcutree.rcu_idle_gp_delay=1 and rebooted but these did not fix it. The problem only started recently. I am using integrated graphics.

Does your laptop have NVIDIA GPU?

Yes, I also have NVIDIA Graphics, but I usually use Integrated Graphics since it's quieter and lasts longer when on battery.

Marivishnu commented 3 years ago

I am having the same problem with my Oryx Pro laptop. It fails to suspend: the keyboard is still lit up and fans are still on. Have to long-press the power button and restart it. Tried mem_sleep_default=deep and rcutree.rcu_idle_gp_delay=1 and rebooted but these did not fix it. The problem only started recently. I am using integrated graphics.

Does your laptop have NVIDIA GPU?

Yes, I also have NVIDIA Graphics, but I usually use Integrated Graphics since it's quieter and lasts longer when on battery.

Ok. I found that after the recent update, my NVIDIA drivers were missing and that led to the problem of not suspending.

Try reinstalling NVIDIA drivers (first nvidia-driver 450 and install nvidia-driver 460 on top of it.). After a reboot, it will solve the suspend problem.

Bananas-Are-Yellow commented 3 years ago

I am having the same problem with my Oryx Pro laptop. It fails to suspend: the keyboard is still lit up and fans are still on. Have to long-press the power button and restart it. Tried mem_sleep_default=deep and rcutree.rcu_idle_gp_delay=1 and rebooted but these did not fix it. The problem only started recently. I am using integrated graphics.

Does your laptop have NVIDIA GPU?

Yes, I also have NVIDIA Graphics, but I usually use Integrated Graphics since it's quieter and lasts longer when on battery.

Ok. I found that after the recent update, my NVIDIA drivers were missing and that led to the problem of not suspending.

Try reinstalling NVIDIA drivers (first nvidia-driver 450 and install nvidia-driver 460 on top of it.). After a reboot, it will solve the suspend problem.

You are right!

I had seen your earlier comments about the NVIDIA drivers but I had ignored them thinking they were not relevant to me since I use Integrated Graphics rather than NVIDIA Graphics. Anyway, I opened Pop!_Shop and saw that nvidia-driver-460 was listed in the Drivers section. I installed it and restarted the laptop, and now it suspends correctly.

Many thanks.

MuseHorizon commented 3 years ago

Hi, thanks for advice.

kernelstub -a rcutree.rcu_idle_gp_delay=1 did not work for me but it led me to the right answer.

It looks like my problem was something different - I noticed that my pc did not finish shuting down into suspend mode - its fan was still running even after long time.

So I changed my search and found this and It looks like my problem was with s2idle.

After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone.

This is how my config now looks (visible with kernelstub -p):

kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 19.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........ce951317-3174-4f0e-b5da-e0350e7eabb0
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.loglevel=0 splash systemd.show_status=false quiet mem_sleep_default=deep
    Kernel Image Path:.../vmlinuz
    Initrd Image Path:.../initrd.img
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

After years of having this issue on every linux distro I've tried, this solution worked for me on HP ProBook 470 G2, Pop OS 20.10. Thanks! Can this fix become standard on Pop OS?

ilseroster commented 3 years ago

Hello everyone!

I am having this same issue on a Fujitsu U9311X running Pop 21.04, with single graphic (Intel Iris). None of the solutions above fully worked. The only one that partially works is rcutree.rcu_idle_gp_delay=1 BUT when the computer stays asleep for more than 15 minutes, it won't wake up. So the fix is OK for short sleeps, but not long ones.

I have tried all I can, but I am not able to work this out. I am not a programmer, and so my knowledge of how to solve this is very limited. Any help from any of your gracious minds will be highly appreciated! Thank you!

Michelle

kernelstub.Config : INFO Looking for configuration... kernelstub : INFO System information: 

OS:..................Pop!_OS 21.04
Root partition:....../dev/nvme0n1p3
Root FS UUID:........68a95a78-24b8-4ed5-bd1c-815a79ca0e33
ESP Path:............/boot/efi
ESP Partition:......./dev/nvme0n1p1
ESP Partition #:.....1
NVRAM entry #:.......4
Boot Variable #:.....0001
Kernel Boot Options:.quiet rcutree.rcu_idle_gp_delay=1 splash loglevel=0
Kernel Image Path:.../boot/vmlinuz-5.11.0-7620-generic
Initrd Image Path:.../boot/initrd.img-5.11.0-7620-generic
Force-overwrite:.....False

kernelstub : INFO Configuration details:

ESP Location:................../boot/efi Management Mode:...............False Install Loader configuration:..False Configuration version:.........3

lavarius commented 2 years ago

Hello, Are you using NVIDIA GPU?

I have set GPU to integrated and it's been like that ever since I installed pop like 2 months ago.

Thanks for your reply. I am using NVIDIA GPU and set It to hybrid. I found that after the recent update, my NVIDIA drivers were missing and that led to the problem of not suspending.

Here are the possible solutions:

1. If you have NVIDIA GPU, try reinstalling NVIDIA drivers (first nvidia-driver 450 and install nvidia-driver 460 on top of it.). After a reboot, it solved the suspend problem.

2. https://askubuntu.com/questions/840093/suspend-on-lid-close-doesnt-work-16-04?rq=1 Go to this forum post and try the methods suggested by **Jesse van Dam**. It too solved the problem. But if you have NVIDIA GPU then try the first method.

These methods solved my problem. :)

Thank you for this. I tried the above and was still left with a blank screen. Tried installing nvidia-driver 450 and nvidia-driver 460 on top, restarted, and tried suspension and this seems to fix it. I had nvidia-driver 470 prior.

Edit: nevermind, it still persists. I found that it could also be a bug with the kernel here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843

piotr-bujnowski commented 2 years ago

I solved this problem by unplugging CD ROM :P. I've never suspected this would work. None of the answers above did help.

MctomSpdo commented 2 years ago

I've tried all the opions from above, and there is still no result

I am using a Laptop (specs in a bit), and the screen will be black forever, after I close the lid If I close the lid when its locked tho, the screen will stay on and just hang, without ever coming back.

I am using a Acer Travel mate P4 with a i7-11850HE, 16GB or ram and 1 TB of ssd Note: I am also using a dual boot (for windows), and the drive is an OPTANE drive.

I have all the newest Installations and updates.

chyczewski-maciej commented 2 years ago

This helped for Lenovo Yoga 7 14ARE05 Slim (AMD Ryzen 7 4700U)

https://forums.lenovo.com/t5/Other-Linux-Discussions/Yoga-Slim-7-cannot-enter-deep-sleep-S3-state-aka-Suspend-to-RAM-on-Linux/m-p/5039060?page=2#5368743

raiblaze commented 2 years ago

My MSI laptop have GTX960M. Meet same issue.

_- After the suspension & wakeup, I wake up laptop display by reduce brightness of laptop a little and increase it again ( Use shortcut keys to reduce/increase brightness of laptop display, in my case is FN+arrow_down/arrow_up), somehow it trigger that laptop display back to normal._

fxrcode commented 2 years ago

Just resolved via sudo kernelstub -a "intel_iommu=off". Origin post: PSA: Intel Skylake (6th gen) and older CPUs VT-d issue still NOT fixed in 5.15.8: Link: https://www.reddit.com/r/pop_os/comments/rlajwq/psa_intel_skylake_6th_gen_and_older_cpus_vtd/

I'd tried all kernelstub fix, but nothing help. Here's the neofetch and kernelstub output:

             /////////////                fxrc@popos 
         /////////////////////            ---------- 
      ///////*767////////////////         OS: Pop!_OS 21.04 x86_64 
    //////7676767676*//////////////       Host: 20F9CTO1WW ThinkPad T460s 
   /////76767//7676767//////////////      Kernel: 5.15.8-76051508-generic 
  /////767676///*76767///////////////     Uptime: 4 mins 
 ///////767676///76767.///7676*///////    Packages: 3211 (dpkg), 42 (flatpak), 16 (snap) 
/////////767676//76767///767676////////   Shell: zsh 5.8 
//////////76767676767////76767/////////   Resolution: 3840x2160 
///////////76767676//////7676//////////   DE: GNOME 3.38.4 
////////////,7676,///////767///////////   WM: Mutter 
/////////////*7676///////76////////////   WM Theme: Pop 
///////////////7676////////////////////   Theme: Pop-dark [GTK2/3] 
 ///////////////7676///767////////////    Icons: Pop [GTK2/3] 
  //////////////////////'////////////     Terminal: gnome-terminal 
   //////.7676767676767676767,//////      CPU: Intel i7-6600U (4) @ 3.400GHz 
    /////767676767676767676767/////       GPU: Intel Skylake GT2 [HD Graphics 520] 
      ///////////////////////////         Memory: 5119MiB / 19866MiB 
         /////////////////////
             /////////////                                        
kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 21.04
    Root partition:....../dev/nvme0n1p3
    Root FS UUID:........01e1d62f-c196-4335-8850-59b84c93379b
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash rcutree.rcu_idle_gp_delay=1 mem_sleep_default=deep snd_hda_intel.dmic_detect=0
    Kernel Image Path:.../boot/vmlinuz-5.15.8-76051508-generic
    Initrd Image Path:.../boot/initrd.img-5.15.8-76051508-generic
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details: 

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3
ouvirativo commented 2 years ago

I had the same problem on Asus Vivobook X 513 EA

After running cat /sys/power/mem_sleep my console showed [s2idle] deep. Then I run sudo kernelstub -a mem_sleep_default=deep, rebooted and it changed previous command output to s2idle [deep] - and my problem with suspend is now gone.

Thanks very much!

sommerper commented 2 years ago

I'm having the same problem and I can't run kernelstub. I'm hoping someone can help me.

➜  / sudo kernelstub
kernelstub.Drive     : ERROR    Could not find a block device for the a partition. This is a critical error and we cannot continue.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 56, in __init__
    self.esp_fs = self.get_part_dev(self.esp_path)
  File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 94, in get_part_dev
    raise NoBlockDevError('Couldn\'t find the block device for %s' % path)
kernelstub.drive.NoBlockDevError: Couldn't find the block device for /boot/efi

I have a data disk, a windows install, and a PopOS install

➜  / lsblk -f     
NAME        FSTYPE   FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0       squashfs 4.0                                                        0   100% /snap/btop/368
loop1       squashfs 4.0                                                        0   100% /snap/btop/372
loop2       squashfs 4.0                                                        0   100% /snap/core/12821
loop3       squashfs 4.0                                                        0   100% /snap/imgcat/27
loop4       squashfs 4.0                                                        0   100% /snap/core/12725
loop5       squashfs 4.0                                                        0   100% /snap/core20/1376
loop6       squashfs 4.0                                                        0   100% /snap/snapd/14978
loop7       squashfs 4.0                                                        0   100% /snap/core20/1361
loop8       squashfs 4.0                                                        0   100% /snap/imgcat/32
loop9       squashfs 4.0                                                        0   100% /snap/snapd/15177
sda                                                                                      
├─sda1                                                                                   
└─sda2      ntfs           850EVO1TB DADCCAB6DCCA8C67                                    
nvme0n1                                                                                  
├─nvme0n1p1 ntfs           Recovery  7416286D16283292                                    
├─nvme0n1p2 vfat     FAT32           5C28-E73E                                           
├─nvme0n1p3                                                                              
├─nvme0n1p4 ntfs                     487029FE7029F2FC                                    
└─nvme0n1p5 ntfs                     DA8A5C868A5C60D5                                    
nvme1n1                                                                                  
├─nvme1n1p1 ext4     1.0   Pop OS    1950decb-75de-43ae-b4de-6ede0fd38133  259.1G    42% /run/timeshift/back
└─nvme1n1p2

my /etc/fstab looks like this 

UUID=1950decb-75de-43ae-b4de-6ede0fd38133  /  ext4  noatime,errors=remount-ro  0  0
/swapfile none swap discard 0 0
Marivishnu commented 2 years ago

I'm having the same problem and I can't run kernelstub. I'm hoping someone can help me.

➜  / sudo kernelstub
kernelstub.Drive     : ERROR    Could not find a block device for the a partition. This is a critical error and we cannot continue.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 56, in __init__
    self.esp_fs = self.get_part_dev(self.esp_path)
  File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 94, in get_part_dev
    raise NoBlockDevError('Couldn\'t find the block device for %s' % path)
kernelstub.drive.NoBlockDevError: Couldn't find the block device for /boot/efi

I have a data disk, a windows install, and a PopOS install

➜  / lsblk -f     
NAME        FSTYPE   FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0       squashfs 4.0                                                        0   100% /snap/btop/368
loop1       squashfs 4.0                                                        0   100% /snap/btop/372
loop2       squashfs 4.0                                                        0   100% /snap/core/12821
loop3       squashfs 4.0                                                        0   100% /snap/imgcat/27
loop4       squashfs 4.0                                                        0   100% /snap/core/12725
loop5       squashfs 4.0                                                        0   100% /snap/core20/1376
loop6       squashfs 4.0                                                        0   100% /snap/snapd/14978
loop7       squashfs 4.0                                                        0   100% /snap/core20/1361
loop8       squashfs 4.0                                                        0   100% /snap/imgcat/32
loop9       squashfs 4.0                                                        0   100% /snap/snapd/15177
sda                                                                                      
├─sda1                                                                                   
└─sda2      ntfs           850EVO1TB DADCCAB6DCCA8C67                                    
nvme0n1                                                                                  
├─nvme0n1p1 ntfs           Recovery  7416286D16283292                                    
├─nvme0n1p2 vfat     FAT32           5C28-E73E                                           
├─nvme0n1p3                                                                              
├─nvme0n1p4 ntfs                     487029FE7029F2FC                                    
└─nvme0n1p5 ntfs                     DA8A5C868A5C60D5                                    
nvme1n1                                                                                  
├─nvme1n1p1 ext4     1.0   Pop OS    1950decb-75de-43ae-b4de-6ede0fd38133  259.1G    42% /run/timeshift/back
└─nvme1n1p2

my /etc/fstab looks like this

UUID=1950decb-75de-43ae-b4de-6ede0fd38133  /  ext4  noatime,errors=remount-ro  0  0
/swapfile none swap discard 0 0

Did you checked this ?

sommerper commented 2 years ago

@Marivishnu thanks, but I have an AMD GPU.

jehadnasser commented 2 years ago

I have same issue now with Lenovo Legoin 5 pro i7-12700H & Nvidia 3070TI, non of the mentioned solutions worked for me.

chase11556 commented 1 year ago

I've tried all the opions from above, and there is still no result

I am using a Laptop (specs in a bit), and the screen will be black forever, after I close the lid

If I close the lid when its locked tho, the screen will stay on and just hang, without ever coming back.

I am using a Acer Travel mate P4 with a i7-11850HE, 16GB or ram and 1 TB of ssd

Note: I am also using a dual boot (for windows), and the drive is an OPTANE drive.

I have all the newest Installations and updates.

Have you found any fixes?

dms449 commented 1 year ago

System76 Gazelle Pop!_OS 22.04 LTS 11th Gen Intel Core i7-11800H GeForce RTX 3050

doesn't wake up (at least the displays don't) from sleep.

chase11556 commented 1 year ago

System76 Gazelle

Pop!_OS 22.04 LTS

11th Gen Intel Core i7-11800H

GeForce RTX 3050

doesn't wake up (at least the displays don't) from sleep.

From what I've read you need to do the bios update on the Acer website. I haven't tried it yet (waiting for my ssd to Install windows on) but it can't be done from pop (at least easily) and it's safer to update on windows.

I hope this helps! I did tons of searching trying to find this info!

dms449 commented 1 year ago

From what I've read you need to do the bios update on the Acer website. I haven't tried it yet (waiting for my ssd to Install windows on) but it can't be done from pop (at least easily) and it's safer to update on windows.

I hope this helps! I did tons of searching trying to find this info!

I'm not on an Acer (System 76 Gazelle) and I don't have (or want) windows installed.

NOTE This issue has come and gone with various updates for quite some time. It's really irritating and makes me never want to update.