suspend problems

[nwtmg]

The latest update has caused some problem with suspend I have toshiba satelitte with 2 gig of ram. Using the openbox window manager and prior to this resent update the suspend had worked ok

Code: Select all

uname -r
4.14.10-desktop-1.mga6


Used both the systemctl suspend and the qdbus command. Both work ok but will now not return after clicking the power on button.
Any help would be appreciated.

[wintpe]

id suggest boot into advanced mode and select previous kernel
then try suspend.

does it fix it.

you may want to remove the 4.14 kernel and related updates if it does fix it as a temporary fix.

to find out what was installed recently use

rpm -qa --last

you only need to remove the basic kernel package

the old kernels are always left in place.

regards peter

[nwtmg]

Thanks for the suggestion but I think I will keep the latest kernel. I feel that I am waiting for another update to take place that my update the suspend modules.

[doktor5000]

I feel that I am waiting for another update to take place that my update the suspend modules.

What suspend modules?

[zeebra]

blacklist moduleX, for some Acer models for example, there is a WMI driver that inhibits the correct behaviours regarding power management, keyboard lights, shortkeys and touchpad. For Acer machines it might in some cases be necessary to blacklist Acer WMI in the kernel for the power management functions to work correctly. Foe example, this was necessary previously to wake suspended machines by touch of a keyboard key.

Could you drop some dmesg and journalctl -b information here?

Just try to suspend the machine, then look in the logs.

Perhaps a custom Kernel will also fix the issue, it is ALWAYS worth trying a custom slim and nice Kernel, suited to your machine. You can always use the configuration file of an installation where you KNOW the suspend function works as you expect it to work.

[nwtmg]

Now using an older kernel version. Suspend working fine. Will retest with the next kernel release.