Linux Mint 20.1 doesn't wake up from suspend

[sami1592]

• Title says it all. Once it goes to suspend mode, it does not wake up. I can see the light in the power button but pressing the button does not work. I need to push it for few seconds to force shut down.

• Sometimes it works. I was able to figure out when it does and when it does not

• Lid is not closed in these cases

• According it my "Power Management", my laptop should not even go to Suspend if on power. But it does :/ Picture included

If you could help me, I would be grateful.

System info :

Code: Select all

System:    Kernel: 5.4.0-73-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.8.6 
           Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: Dell product: Latitude 7480 v: N/A serial: <filter> 
           Mobo: Dell model: 0CXWHP v: A01 serial: <filter> UEFI: Dell v: 1.17.1 date: 05/06/2020 
Battery:   ID-1: BAT0 charge: 49.2 Wh condition: 49.2/60.0 Wh (82%) model: BYD DELL KG7VF06 status: Full 
CPU:       Topology: Dual Core model: Intel Core i7-7600U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23199 
           Speed: 700 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 700 2: 699 3: 700 4: 699 
Graphics:  Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.2.6 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k5.4.0-73-generic 
Network:   Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 
           IF: enp0s31f6 state: up speed: 10 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: f040 bus ID: 02:00.0 
           IF: wlp2s0 state: down mac: <filter> 
Drives:    Local Storage: total: 953.87 GiB used: 199.99 GiB (21.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: PM961 NVMe 1024GB size: 953.87 GiB 
Partition: ID-1: / size: 52.51 GiB used: 16.15 GiB (30.8%) fs: ext4 dev: /dev/nvme0n1p6 
           ID-2: /home size: 511.28 GiB used: 183.80 GiB (35.9%) fs: ext4 dev: /dev/nvme0n1p8 
           ID-3: swap-1 size: 9.54 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p7 
Sensors:   System Temperatures: cpu: 40.5 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 274 Uptime: 39m Memory: 15.52 GiB used: 2.46 GiB (15.8%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
           Shell: bash v: 5.0.17 inxi: 3.0.38 
5.4.0-73-generic

Power Management Settings

[Pjotr]

Try this:
Update Manager - panel: View - Linux kernels
Install the latest kernel of the 5.8 series. Then reboot.

Reason: very new hardware often needs a very new kernel series.

[sami1592]

Hey, thanks for replying. One confusion, my hardware is at least 3 years old. Should I still try to change the kernel?

Also, is this the right category for my problem? Or should I post it in a different category?

[Pjotr]

my hardware is at least 3 years old. Should I still try to change the kernel?

Yes, certainly worth a try. Easy to revert, by the way.

[ocor]

Hi sami1592, I am experiencing the same problem. Did installing the latest kernel fix the problem for you? Or did you otherwise find a solution at all?

Thanks!

Grtz.,
Ocor

[SMG]

• Sometimes it works. I was able to figure out when it does and when it does not

• Lid is not closed in these cases

Lid is not closed in what cases? Are you saying it works if the lid is not closed or is the reverse true?

The lid closure switch is a physical hardware switch. If it is sending (or not sending) a signal when it should, that would be a hardware issue rather than an operating system issue.

One other place to check settings is the Screensaver app. Sometimes there is interference between it and Power Management.

[sami1592]

Hi sami1592, I am experiencing the same problem. Did installing the latest kernel fix the problem for you? Or did you otherwise find a solution at all?

Thanks!

Grtz.,
Ocor

Hey Ocor, right now it is working properly again. I did not do anything. And after sometime, it might not. This has been happening for a while now.

[sami1592]

• Sometimes it works. I was able to figure out when it does and when it does not

• Lid is not closed in these cases

Lid is not closed in what cases? Are you saying it works if the lid is not closed or is the reverse true?

The lid closure switch is a physical hardware switch. If it is sending (or not sending) a signal when it should, that would be a hardware issue rather than an operating system issue.

One other place to check settings is the Screensaver app. Sometimes there is interference between it and Power Management.

1. Lid : For my laptop the Lid is always open. That is what I wanted to say. In that way we can eliminate different possibilities.
2. Screensaver App : What settings should I look for?

[SMG]

• Sometimes it works. I was able to figure out when it does and when it does not

This seems to indicate you know what the difference might be when it works and when it does not work. However, I have not noticed where you explained what this difference is.

Or maybe you do not know the difference, but just know that sometimes it works and sometimes it does not?

Are you sometimes using a docking station and sometimes not? Or maybe sometimes have external hardware (mouse, keyboard, speakers) attached and sometimes not? Maybe one of those is a factor in whether or not it works?

2. Screensaver App : What settings should I look for?

Just check to see if the settings you have in the Screensaver app do not seem to contradict the ones you use in the Power Management app. I personally do not use the Screensaver app, but I have heard there can sometimes be underlying code conflicts with how Mint uses the Screensaver and Power Management apps.