Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Approximately 50%-60% of the time I am able to resume from suspend. Suspend seems to mainly fail most always on the second suspend attempt on any given uptime.
I have about the same problem with the same kernel on an older p4 with 19 Tara.
Is there an area I could/should be more focused on to try to resolve this issue?
Thank You,
Last edited by panorain; 12-12-2018 at 11:26 PM.
Reason: Wording
I've updated the installation here of Mint 19.1 Beta to 19.1 Tessa and still having intermittent suspend/resume problems. I am a noob so I am not certain about just yet how to attempt to use systemd to suspend and resume. Thanks for the help though.
Last edited by panorain; 12-24-2018 at 11:33 PM.
Reason: Wording
I believe with this particular terminal that BIOS ACPI settings have some play in the suspend issue I have been dealing with. Terminal seems to suspend and unsuspend in general without failure when BIOS ACPI settings is set to auto instead of ACPI S1 or ACPI S3.
Bios ACPI settings are one issue, but if the terminal does it OK, that seems to clear the BIOS.
What you're left with is the power manager (or lack thereof) in whatever WM you happen to be using. Often it's simply badly configured. I once got this issue that if I went to hibernate, it would hibernate, reboot, and hibernate again immediately. It was in fact doing it twice - once via bios and once via power manager. It could even be loading the wrong drivers.
Another useful trick is to restart acpid with a -l option. You can then tail syslog and hit bios hot keys, and they will report them in syslog. They link to scripts (all under /etc/acpi). Of course, if systemd has stuck it's nose into that, you're up the creek without a paddle from this poster at any rate.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.