Laptop will not wake when lid is opened

geekazoid

I have Solus Budgie installed on a Dell Latitude 5490 with a 512 Gig SSD and 16 Gig of ram.

When I installed the OS I did a clean install with a swap partition.

When I open the lid the power button is illuminated but not the screen. I have tried pressing keys and swiping over the touchpad, agan no change. I have to shut the machine down using the power button and start again.

Also when the laptop times out, the screen goes black as you would expect and the light on the Caps Lock key flashes. Again I have to shut down using the power button and start again.

I have read many posts and articles on this issue but cannot seem to work through it on my computer.

Any help/advice would be much appreciated!

BuzzPCSOS

There really are a huge number of things that can cause this. To be fair sleep and wake are not always that reliable on Windows either.
It could be down to a hard drive that needs the file system to be repaired (Disks) or a faulty ram stick (Dells usually shop with a built in trouble shooter which includes a ram test, try F8 or F12 when booting) or it could be drivers or the kernel version you are on (try switching to LTSC and see if things work any better).

geekazoid

If I close the lid without powering down the laptop, my expectation (from using previous operating systems) is that when I then open the lid, I should see the login/lock screen.

I have spent hours trying all manner of solutions posted on the web but none have worked which is a pity because Solus is a superb os.

I will keep looking and trying.

Thank you for your input.

BuzzPCSOS

geekazoid my expectation (from using previous operating systems)

Different Linux OSs tend to run on different Kernels which could be the problem here as the version 6.17 that Solus is currently using might have problems with some hard-wares. Hopefully it will be fixed when we move onto 6.18.
You can wait until the Kernel gets updated to 6.18 or you can try the LTS Kernel which is currently on something like 6.12.
This link will give you instructions on how to do this.

geekazoid

Thanks again for your input, I have tried the switch to the LTS Kernel, again no change. I am also continuing my research online.

pomon

Solus leaves 2 kernels: The latest one after an update and the last one you used. If you installed the LTS kernel, you should have 3 kernel entries in the boot menu. When starting the system, repeatedly hit the spacebar to bring up the boot menu (on my Dell), and try all the kernels.

You need to look through the logs,after a hard reboot but don't paste the results here; put them on a pastebin service. Alternatively, upload them to some "know-it-all" (AI) for analysis.

My suggestions:

journalctl -b -1 -k | grep -i -E "PM:|suspend|resume|sleep"
journalctl -b -1 -k | grep -i -E "lid|acpi"
journalctl -b -1 -k -p err
journalctl -b -1 -k -e

Remember, if you are not part of the groups related to system logs (e.g., systemd-journal, adm, or wheel), you will need to use sudo.

geekazoid

pomon

Your response and time is appreciated, in relation to the kernel I followed your instructions. When booting I press the space bar, the boot menu gives 2 kernel options, the lts option which I am using and the previous kernel.

I continue using the LTS kernel.

I then closed the laptop lid. Opened the laptop lid and same thing, just the light on the power button illuminated. Hard reboot done.

The journalctl commands you suggest all gave the same result "Specifying boot ID or boot offset has no effect, no persistent journal was found"

The journalctl stuff is completely unknown territory to me so all i did was copy and paste each one into terminal.

Regards

pomon

geekazoid "Specifying boot ID or boot offset has no effect, no persistent journal was found"

First, please check if /var/log/journal exists.

If it doesn’t, it means persistent journaling is not enabled. Logs from the previous boot are lost, so journalctl -b -1 can’t show suspend/resume data after a hard reboot.

To enable persistent journaling:

sudo mkdir -p /var/log/journal
sudo systemctl restart systemd-journald

geekazoid

Thank you again for the response and your efforts to help me.

I could not find /var/log/journal and used the commands provided to rectify this.

I then went through the process of closing lid, opening lid and carrying out a hard reboot. I then entered the journalctl commands from your earlier post.

I got the same response from all commands 'No journal boot entry found for the specified boot (-1)'

Regards

geekazoid

I think I have managed to eliminate 'hardware issues' as the culprit.

I have done some distro hopping to see if what I expect to happen does indeed occur in other operating systems.

Works with Windows installed, Fedora workstation (gnome and cosmic) and Ubuntu desktop.

Ubuntu Budgie, Fedora Budgie, Ubuntu cinnamon and Zorin had the same result outlined in my original post.

I have also implemented a lot of the software/script solutions kindly provided by other linux users.

I have not managed to solve the issue.

Based on the research I have done it does appear to be pretty random.

I think I will have to suffer this in the hope a software or kernel update will resolve the matter.

geekazoid

So, as a sort of workaround (negates the need to keep doing hard reboots) I have managed to get the os to stay powered on when the screen is closed using this script:

"# systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target"

I wondered if there is a way of manipulating these parameters to solve my original issue but it would appear not.