FedoraThis forum is for the discussion of the Fedora Project.
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.
I'm running Fedora Core 4, which has ACPI enabled in the kernel. I've managed to get it to a state where I can successfully suspend to S3 sleep (suspend-to-RAM), after stopping a couple of services and removing the odd driver. However, I'm having problems getting it to resume properly.
I'm fairly sure it went into sleep properly, because I can use the keyboard to wake the computer; however, instead of resuming to where I was, it just goes through the normal boot process. What I suspect is happening is that it is coming across some fatal error during the resume process and automatically rebooting before the screen wakes up.
Can anyone shed any light on this? Has anyone encountered the same problem, and has anyone been able to get this to work successfully?
I'm running the FC4 out-of-the-box kernel (kernel-2.6.11-1.1369_FC4) with standard FC4.
This may not be the problem you're having, but if you have acpid installed, it has a default configuration that will cause a shutdown right after restarting from suspend. To work around this, remove /etc/acpi/events/sample.conf (or edit the file and comment out the lines that look like:
Code:
#event=button/power.*
#action=/sbin/shutdown -h now
Ah. I do remember something like that in the acpid.conf file. I don't know whether that's what is causing my problem, but I'll certainly try taking that out and seeing if it changes anything. The nice thing about that default config is that I can hit the power button on the front of the box and it shuts itself down cleanly, which is quite nice. Not that I can ever be bothered to get up and walk across the room to actually do it!
I tried what you suggested. I don't have an acpid.conf file, but there was a sample.conf file in /etc/acpid/events/ which had the entries in you mentioned. I commented them out, but still no luck, it does exactly the same.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.