Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
If I make a brand new install of Ubuntu 12.04 64-bit, update it fully, and run the command pm-suspend, then the time for it to resume from sleep is 4 seconds with an Atom/Ion platform and 17 secs with AMD Fusion E-350. But systems report in syslog that resume took 2.5 secs.
I have looked through logs syslog, Xorg.0.log, pm-powersave.log, pm-suspend.log, kern.log, dmesg, boot and boot.log and compared them for the 2 systems. I can't spot any exciting differences (apart from in pm-powersave.log seeing one occurrance of "Setting Host Bridge 0000:00:00.0 to on" for Atom and 8 such lines for E-350, for addresses 0000:00:18.0 to 0000:00:18.7).
A peculiar thing in syslog is that all events for suspend and subsequent resume are logged during the same second, i e all suspend and resume events have the same time stamp, which if it was true would mean that all of the suspend process, all of my 10 minute coffe break in between, and all of the resume process took place during < 1 second. Either that or the clock is standing still.
One thing I REALLY would have use for is a log with proper time stamps for each event during resume, so that I could see what is going on: Is it "locked" for several seconds, or in a loop, or waiting for something, etc. But the logs I found don't have that. And that it reports that resume took 2.5 secs in the log to me could indicate that whatever causes the extra 13 sec delay happens before the log starts or something?
With fglrx it is even slower, but I haven's tested that in great detail. I understand graphics driver has an influence on ACPI somehow even though ACPI has its own drivers. It also isn't faster with Linux Mint.