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.
I have managed to successfully track down and reproduce with accuracy a problem I have for some time now when I go from suspend to ram to resume, on my slackware box (slackware 13 right now in fact...).
The issue goes on like this:
I am using a notebook computer.
1. I suspend to ram with the power cord plugged in(from xfce, but should not matter, it uses pm-utils triggered by specific hal scripts as far as I see)
2. I remove the power cord after suspend to ram is compelete.
3. I wait like 10s, then resume by pressing the power button briefly
4. All I got is a blank screen with an unresponsive computer, all I can do is powering down by pressing and holding the power button pressed for a few seconds (hard shutdown).
Now, I suspect the problem is generated by the fact the computer resumes from standby and udev (most likely) or hal has a device list database that does not correspond to the real facts anymore. I have tried to log udev and hald messages (with debug logging activated) to syslog, but after the hard reboot I can see there is not even one syslog message at from time I resumed from suspend, so not sure what and at what level locks the machine.
Any ideas which could shed some light on this issue are much appreciated.