looking for hardware reasons why suspend and hibernation don't work
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.
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.
looking for hardware reasons why suspend and hibernation don't work
My suspend-to-disk and suspend-to-RAM stopped working months ago. I've grasped at straws about why ever since, but I really don't think it's a software problem, because I've reinstalled my system (MEPIS) repeatedly. What sort of hardware failures could cause this? What should I be looking for?
I notice that at boot, Linux always says "no resume image found," even if I left the system in suspension or hibernation. I can post parts of the dmesg if someone tells me what to look for; I can't display the whole thing because it's too long to fit here.
suspend and hibernate are handled with acpi. So look for
dmesg | grep acpi
some laptops need extra kernel options for acpi to work properly
Did suspend/wake fail after an upgrade by chance?
man initramfs-tools :
resume
On install initramfs-tools tries to autodetect the resume parti‐
tion. On success the RESUME variable is written to
/etc/initramfs-tools/conf.d/resume. The boot variable noresume
overrides it
sudo nano /etc/initramfs-tools/conf.d/resume
make sure line:
RESUME=XXXXx-XXX-XXXX-XXXX
points at your swap partition uuid. save and exit, then:
It might have been after some piece of software was upgraded that the suspend/wake failed, but I don't think so, because if I reinstall the entire system from my liveCD so that those upgrades are gone, I still can't suspend.
I discovered that the problem seems to be my network adapter. This is how I found out. I wanted to see whether this would happen on another distro, so I installed one (Kubuntu, because I've been looking at it) on another partition, and tried both types of suspend from there. Suspend-to-RAM didn't work there either--the computer shuts down, but can't find any image when rebooting, but something interesting happened when I tried suspending to disk. It did shut down, but for a second, I saw a message to the effect that "rt61" was interfering with the suspend-to-disk. Rt61 is the driver of my wireless network adapter. (It's a Linksys WMP54G.)
Well, this seems a difficult problem. This is my second model of wireless adapter; after the first, a Linksys WUSB54G, broke, I bought a PCI card instead so I would have less cable clutter. I really can't spend money on a different network adapter (perhaps another WUSB54G, since I know it works), so unless someone has a solution for network adapters interfering with suspend/hibernate functionality, I'm probably stuck.
you can tell acpi to remove your wireless driver when it suspends - check with lsmod -r rt61 just before doing a suspend. If that works then you can either remember to do this every time or add it to a suspend script.
I have been distracted from this problem, mostly by school, until now. (I was just surviving without hibernation.) When I enter "lsmod -r rt61," the terminal says "usage: lsmod." That's odd--why wouldn't lsmod know that parameter?
Last edited by newbiesforever; 07-09-2010 at 05:08 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.