Suspend/Resume issues

Aero9000

Hi all,

After the latest update of last weekend suspend/resume no longer works flawlessly. I suspend the computer and upon resume (after 10 mins or so) the desktop shows up but not the password window, nor a mouse pointer. Also, it is not possible to change to a virtual terminal (e.g. CTRL-ALT-F2) and the caps lock light no longer responds. Final solution, I have to power down the box and reboot. :-(

Perhaps the new kernel (6.3.4-237.current) doesn't play well on my box. So I booted the previous kernel and still same issue. This led me to believe perhaps some config file was modified.

To make absolutely sure I reinstalled Solus Budgie 4.3 and made sure not to install any updates or make any modifications. Then I reattempted multiple suspend/resume cycles and the box behaved perfectly. Then I updated the system to latest version of Solus, rebooted and tried suspend/resume again. Well, guess what. No resume. In a final attempt I booted with the old 5.x kernel and retried and again the system failed to resume.

So it almost certainly has to be a configuration issue. Maybe this info can help the devs?

Aero9000

Perhaps my question was not unambiguous :-)

Can someone perhaps point me to where I can find suspend and resume logs? Of if someone can tell me where I can find suspend/resume config files?

nolan

Perhaps that error was introduced with the inclusion of xwayland, i have some problems with the screen (backlight not working properly and I have not tested for more info).

Just to be sure, could you show the content of fstab with cat /etc/fstab if the swap partition is not present there (should be: UUID=something none swap sw 0 0), that could be the problem.

Aero9000

# /etc/fstab: static file system information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>

# /dev/ROOT / ext3 noatime 0 1
# /dev/SWAP none swap sw 0 0
# /dev/fd0 /mnt/floppy auto noauto 0 0
none /proc proc nosuid,noexec 0 0
none /dev/shm tmpfs defaults 0 0
# /dev/sdb5 at time of installation
UUID=5a7a73f1-3a9c-4bcb-bdce-09feffd50902 /home ext4 rw,relatime,errors=remount-ro 0 2
# /dev/sda5 at time of installation
UUID=42fad20c-bf68-451d-8d30-19ffda009f9b / ext4 rw,relatime,errors=remount-ro 0 1

As you can see I have no swap set up. But since my box has 16 Gigs of RAM I don't really need swap. Thus far Solus has never used more than 4 Gigs of RAM.

Just to be clear, my problem relates to suspend to RAM. I don't hibernate the box.

nolan

well, I'll be waiting then, seems interesting.

Aero9000

The issue is resolved is per Solus 4.4