Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The Suspend function does not work for me as it should. One would expect that recovering from Suspend is accomplished by moving the mouse or pressing a key.
I have a super Fedora Core 6 system except for one bug-- recovering from Suspend. My Suspend works somewhat like a black hole-- once I enter the Suspended state, I am trapped. I can only get out of that state by hitting the Reset button--not a good practice.
When I click on Suspend, my display instantly goes blank and the CPU power is turned off. That's good. My system probably enters an S3 (suspend to RAM) state. Afterwards, I can't get out of the Suspended state. Pressing any keys or the power button does not awaken my system. Only the Reset button rescues me.
Here is some additional information:
- My Intel BIOS supports ACPI. Two states are available, S1 and S3. I use S3.
- apm service is off
- acpid service is enabled
- Linux command (in root) acpi results in "Command not found"
- Linux command (in root) acpid results in "Can't open /proc/acpi/event: Device or resource busy"
In my present Award bios and in my previos mobos (some had the other big bios maker --Phoenix(?)-- not sure) there is a seperate set of control flags to set to tell the bios what will bring it out of hibernation/suspend. It has : PSA keyboard (bunch of entrys for key combos), PCI, and a few others. I would try a few differnt ones there and see if you can find a setting your setup responds to.