Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
Distribution: Ubuntu 9.04 X86_64 Desktop, 8.04 X86 Server
Posts: 33
Rep:
Strange Suspend Issues
I have a Dell Latitude D830, running Ubuntu 9.04 64-bit. It used to suspend and hibernate fine, without any issues, but all of a sudden (I'm not sure when), it stopped waking up from both suspend and hibernate. When I "power" the computer back on, all I get (after the initial Dell screen) is a white flashing cursor in the top left corner of my screen.
I searched around pretty much everywhere and tried every fix I could find. Nothing works except (this is the strange part) when I enable suspend to ram "tracing." When I enable this option, suspend works perfectly...other than the side effect of my date/time being completely wrong at boot, so I have no way of logging what exactly is going wrong.
In case someone doesnt know, the "tracing" writes dmesg to the memory chip that keeps time/date so it can be saved when the system reboots.
This grabs a terminal and logs everything. Start with hibernate. I never bothered to get suspend sorted. You need resume= pointing to your swop partition (e.g. resume=/dev/sda9)
sync; echo -n > /sys/power/state
There is also a kernel bopot option for console debug 'no_ocnsole_suspend'
Add that to your boot line
Distribution: Ubuntu 9.04 X86_64 Desktop, 8.04 X86 Server
Posts: 33
Original Poster
Rep:
Thanks, I got hibernate working.
Suspend is still the same. It appears that no_console_suspend doesn't anything, I still get the flashing dash when I try to resume.
"/usr/sbin/acpid -d"
returns: "acpid: can't open /proc/acpi/event: Device or resource busy"
and I'm not sure what you mean by "sync; echo -n > /sys/power/state" Should I be echoing something into that file?
Thanks, I got hibernate working.
Suspend is still the same. It appears that no_console_suspend doesn't anything, I still get the flashing dash when I try to resume.
Try in the logs, or google for it. I mentioned it because it appears after a successful suspend. Never used it myself
Quote:
Originally Posted by swordphsh
"/usr/sbin/acpid -d"
returns: "acpid: can't open /proc/acpi/event: Device or resource busy"
That's because acpid is already running. stop the service first.
Quote:
Originally Posted by swordphsh
and I'm not sure what you mean by "sync; echo -n > /sys/power/state" Should I be echoing something into that file?
Distribution: Ubuntu 9.04 X86_64 Desktop, 8.04 X86 Server
Posts: 33
Original Poster
Rep:
I did a bit more searching around and added "acpi_sleep=s4_nohwsig" (in addition to no_console_suspend) and also removed "quiet" and "splash", to see if it would show what it was doing and that fixed it. I tried replacing quiet and splash, but it will not work with them in the boot parameters. I have no idea why that would make a difference, but it works and doesn't mess anything up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.