Ubuntu :: Thinkpad - No Suspend / Hibernate Or Resume
May 9, 2010
I've got a Thinkpad X31 with ATI M6 Ly card. Since Karmic, and Lucid, I get no suspend/hibernate/resume. If/when I select resume or close the lid, Lucid goes through the suspend cycle, and for approximately half a second it actually seems to go into suspend, then the screen comes back on, black, but definitely on, and absolutely no response to any keyboard input - have to hard-shutdown by holding down the power button. I've read that the problem is with the Ubuntu kernel, and that installing/compiling 2.6.33 fixes the issue, but causes other ones.
Slackware 13.1 installed clean on a new ThinkPad Edge (version 13 inch with AMD Processor and ATI graphics). I can get most of what I want working fine except for suspend and resume. I read somewhere that I should be using generic rather than huge kernel, so I have done that and scrapped ATI proprietary driver in case that was causing problems, but nothing so far has allowed me to suspend and resume with pm-suspend, acpitool suspend or with KDE suspend command. In all cases the screen blanks and the single ThinkPad red LED goes from on to blinking, but nothing seems to wake the machine up again. I had both suspend and hibernate working fine with Slack 13.1 on an older Lenovo laptop and ubuntu users report on their forums that this laptop does suspend and resume "out of the box" so I feel it must be possible.
My ThinkPad X32 doesn't shut off the backlight when I suspend it. It also doesn't resume properly. Shutdown works normally. I'm using OpenSuse 11.3 Gnome. Had the same issue with an install of Linux Mint Debian Edition (201101). It is a well-known Debian issue that has evidently trickled down through Ubuntu to Mint. It also exists in Fedora. In search of a distro that would handle suspend/resume without problems, I first tried Scientific Linux. Suspend/resume worked flawlessly, but I was not happy with the package manager in SL, which leaves it to the user to resolve dependency issues that are automatically handled by Synaptic in Mint/Ubuntu/Debian and by the Package Manager in OpenSuse.
OpenSuse 11.3 Gnome had the same problem - the backlight remained on upon suspend, and resume didn't work at all. I solved this issue by making a simple change in a start-up file in OpenSuse. I'm hoping the solution will work in Mint as well, as it is my favorite distro which I have used for three years. The solution:
1. With OpenSuse: open a terminal and type gnomesu gedit /etc/grub/menu.lst. When prompted, type your root password and click OK.
2. Gedit opens with the menu.lst file displayed. Down the page a bit, you'll see several sections that begin with "###Don't change this comment"
3. The first section gives details for the default boot operating system. Somewhere in this long spec, you'll find "vga=0x314" or vga=(something different for your system).
4. Just before or after this part, type "nomodeset" separated from the vga spec by a space.
5. Save the file and reboot. In OpenSuse, suspend/resume now works normally.
someone could let future readers know where the menu.lst file is located under Linux Mint. In the past, I've found it frustrating to try to edit the menu spec with Mint 10 versions, which use Grub2.
I installed the debian 6 on the tninkpad T42, use the Suspend,it can entry the suspend state，I type the key let it come back, it can exit the suspend state, But the screen always display "black",can't come back the X window.
I just got a Dell Inspiron 1764 and am dual booting it with Win7 and Ubuntu 9.10.Whenever I hibernate or suspend, it goes through everything fine, but then when I resume it just boots to a black screen and I have to do a hard shutdown. Is there a fix for this? I know it's a fairly common issue.
After I resume from hibernate with my cpu frequency manually set to the highest settings (2ghz) the network manager shows not wifi APs. "wlan0" shows under both ifconfig and iwconfig but "iwlist wlan0 scan" says no results. "sudo iwlist wlan0 scan" also says no results. I've tried rmmod then modprobe with no luck. Rebooting is the only way I can get WiFi working.
I can get wifi working again by: - rebooting - changing the cpu scaling to a lower setting then hibernate/resume - changing the cpu scaling to a lower setting then 'sudo rmmod ath9k; sudo modprobe ath9k;'
I am using Ubuntu 10.04 with Atheros ar5008 (AR5BXB72) using ath9k drives Code: $ lspci |grep Atheros 0e:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) Code: $ uname -r 2.6.32-24-generic
The good news: 11.4 seems to have much better support for my radeon graphics driver which makes many of my workarounds for 11.3 unnecessary
The bad news: whereas previously for 11.2, 11.3 using traditional ifup meant that I could easily restore internet (either wlan0 or eth0) with ifdown/ifup now this seems to have no effect. I haven't investigated further yet since without internet on hibernate or suspend 11.4 is not my grub of choice at the moment
There seem to be quite a few glitches with the 'stable' release of 11.4 but this seems to be the main problem for me. (Minimizing the beta 4 Firefox windows closing them is another...)
i dont know why my system dosnt resume from suspend sstate.i it goes in suspend state.it doesnt resume .i have to poweroff then restart it again.and when i get logged in it gives me Following Error: Resume problem: Your system did not appear to resume correctly from Suspend/Hibernate. This may be a driver problem or a hardware problem. Check the GNOME Power Manager Manual for common problems.
do you think it is because of batterry.i have a problem in my By Battery .IN DOS operating system.when i check my battery icon . A red Cross constantly blink on lower right side of the battery and it says (your Battery consider Replacing).i have notice one thing .And My battery timing hias become Decreased. Do you think this Resume problm is cause of battery problm.Or there is some problm in my Os software.
I am running Squeeze on an older Compaq EVO laptop with radeon graphics.
A few months ago, after an upgrade, suspend and hibernate stopped working. The suspend or hibernate worked fine, but the resume just hung with a black screen. I finally got around to looking into it and found a workaround.
The workaround is to disable Kernel Mode Setting for the radeon. This can be done by adding the boot parameter "radeon.modeset=0" or by editing /etc/modprobe.d/radeon-kms.conf so that it includes the line "options radeon modeset=0".
If you are interested in the details, you can search for problem reports related to radeon kernel mode setting.
Just got Ubuntu 9.10 and I'm liking it a lot, but my computer refuses to go into hibernate or suspend. I have a Dell M1530 but I don't really think it's a dell hardware issue because it's not just when I close the screen, it's also when I click suspend or hibernate from the menu.
I found this line in dmseg when I was checking out another problem. "[0.104467] ACPI Warning: Incorrect checksum in table [OEMB] - 03, should be FA 20090521 tbutils-246" Could this be why I have never been able to resume from hibernate on this machine?
I have ubuntu 10.04 installed on a 50 gb partition on my hard drive I have given a 3.5 gb partition for swap which is > 3gb ram i have. Druing the installation of ubuntu I had specified the swap partition and its hibernate was working fine sometimes before. But I had to delete the swap partition and recreate it because of some reasons so I did that and again created a 3.5 gb partition for swap space usig ubuntu live cd.
But after restart ubuntu no longer detected the swap partition it was ok as its uuid had changed so I specified the swap partition to be mounted automatically by adding an entry in /etc/fstab and then also added the same UUID in /etc/initramfs-tools/conf.d/resume so that it could resume. After restarting ubuntu after adding the entrly in /etc/fstab i got the option of hibernate but after hibernate everything goes well but after hibernate when i start laptop again ubuntu first tries to resume but it does not and without giving any message it shows the login screen.
I'm experiencing very slow resume from hibernation. Last one was nearly 3 minutes. Sure, there is 2GB of RAM to read from disk (no SSD) to memory but that long?What could I check/do?
My system cannot resume after hibernation. I have done all as described here [URL] ...
My have set up swap file "/swap_debian".
I have 3 partitions: sda1: windows boot partition. sda2: windows 8.1. sda3 : debian
I have the only linux distro installed: debian.
I have read lots of web pages. I have managed to set up suspend 2 disk. After dancing 2 days at the computer the system still cannot resume. I am getting "clearing orphaned inode" msgs while booting, and when booted to ram was not recovered.
Swap file is 4000 MB, RAM is 3860 something MB
My current grub is:
Code: Select all# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration'
[Code] ....
And yes, I did update-grub.
My current /etc/uswsusp.conf is:
Code: Select all# /etc/uswsusp.conf(5) -- Configuration file for s2disk/s2both resume device = /dev/sda3 compress = y early writeout = y image size = 1855258869 RSA key file = /etc/uswsusp.key shutdown method = platform resume offset = 31606784
My current /etc/fstab is:
Code: Select all# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5).
So I'm having this weird problem where my computer wants to continuously resume a session from hibernate no matter how I shut it down. I think it started when I tried to hibernate my computer with the battery really low. Somehow it messed it up. In any case, it can't resume properly, but gets stuck somewhere in the middle (I think when it's trying to sort out the resume image). Each time I power it on I have to boot it, restart in the middle of the boot so the boot menu comes up as it starts up again, edit commands before boot and add the "noresume" option so it will boot up normally.
I don't know if these are related, but I have had occasional lockups, where no input has any effect and then it shuts down, and am usually unable to resume from suspend on closing the lid.
Here are the specifics. Thinkpad x120e, AMD e-350, ATI radion 6310 graphics, Intel 320 series SSD 80 GB, no bluetooth.
The ethernet and wireless cards, as given in lspci, are
I'm using stock 32 bit current on a AAO D250 netbook. I'm running into a video issue after upgrade to the recent 2.6.35.7 kernel that doesn't exist after resume from suspend. The condition shows as a broken display that shows a black screen on the left with the KDE desktop partial exposed on the right side. Weird! My only fix so far is to blindly ctrl-alt-f6, login as root and reboot. The screen does not show the console screen during this reboot process
The pm-suspend logs show a clean hibernate and a clean thaw so that's no help. I've checked modprobe.d and don't have any alterations to any of the modules. The video module loaded is the intel_agp which sound right. I'm stumped at the moment.
I have some problems getting some of the buttons on my Thinkpad working properly. Volume buttons, thinklight, etc. work through tpb. It's the other buttons (sleep, hibernate, etc.) that are causing problems. The wireless radio button also works. I can hibernate and suspend successfully from the command-line using pm-suspend, etc. I have copied the 30-keymap-module-thinkpad-acpi.fdi file to /etc/hal/fdi/policy, where it sits alongside my UK keyboard layout policy (10-keymap.fdi). In this file, I have edited the 'radio' button to call a 'bluetooth' event instead, but it seems to be ignored and pressing Fn+F5 toggles both bluetooth and wlan radios and not just bluetooth... Is there something I have to do to merge the 2 files together? Or do I have to rename the thinkpad .fdi file so I have 10-keymap.fdi and 30-keymap.fdi?
I have the tpb daemon running but it's set not to block keystrokes and when I run xev and press the key combination for sleep, it reports 'xf86sleep' correctly, hibernate reports 'xf86suspend', etc., so I know the keys are getting recognized in some form... However, it seems that the HAL daemon is not picking up these events and running the corresponding commands. I am a member of the 'power' group, nevertheless, even running as root does not seem to make any difference. Finally, I am running wmii as a windowmanager with no desktop environment, and none of these buttons is configured in the window manager. hald should be picking up the events but it seems it isn't
I have problem with resuming after hibernate, it is about 50% chance that computer restart when I want resume, then it starts boot normally and all my work is lost. Acer aspire 3820tg Ubuntu 11.04 Builtin hibernate on partition I try uswsusp s2disk ... on resume it always stops in half of process. I used mainly hibernate, but I'm lost now.
My laptop won't resume after it suspends. It works fine under win 7 so it's not the hardware. The light says it's on and it's pretty much a blank screen. I'm not sure whether it's operational but the screen is off. It has exactly the same resault a waiting for the blank screen except it won't go back on.
I've just upgraded from 9.10 to 10.04 via the upgrade manager. Prior to the upgrade I was able to suspend and hibernate without any problems. Now that I have upgraded to 10.04, I can suspend however when I resume I am back at the gdm login prompt, logging in again with a new session.Having just done another test whilst writing this, it actually appears that if I select suspend from the top right I am suspended and can resume my session. If I close the lid on my laptop (which is supposed to suspend) I am logged out and suspended.Also, Hibernate doesn't work as well - sometimes it never actually hibernates (just sits on a black screen) and sometimes it doesn't resume (it's never hibernated and resumed correctly since the upgrade)
Whatever way I suspend my laptop (menu, keyboard shortcut, close lid), it seems to suspend just find (no panic lights, suspend LED indicator flashing as expected). However, when i try to resume, the laptop seems to begin the proper wakeup process (for example, the DVD-drive is tested), there's a lot of HDD activity for about 5 seconds, screen does not power on, and then the laptop just shuts off.
System setup: lucid beta 2, fully updated (just check now) LG E-500 laptop /w nvidia gforce mobile 8400G bios version 1.17 from June 2007 (not sure this is important)
Things I tried: * Completely remove anything to do with gpu drivers and installed nvidia-current driver. * Suspend stress test described here. this didn't work at all. The first test failed (with ac adapter attached) and the second test suspended but didn't automatically resume (see "the behavior" above). Also, when I booted up again, no apport bug report is created. I tried both with rtc set to utc=yes and utc=no. with utc=yes, the second test did automatically resume, but the same problem happened (laptop shutdown while resuming). * The debugging steps described here, but I couldn't get the "no_console_suspend" option to work. I tried adding both "no_console_suspend" and "no_console_suspend=1" (without quotes) to the boot script in the grub menu, but when I did pm-suspend in tty1, the laptop really did suspend. I would like to try to do this again if someone could explain how to add this option.
Notes: * Not sure this is relevant, but when I boot up after a failed resume attempt, wireless network is disabled (this only happens after a failed resume!!!). * I found a package called nvram-wakeup in synaptic that seems to be related to this. This package is not installed. Should I install it? In case this is relevant, forgot to mention I'm running ubuntu in dual-boot along side windows7.
I don't have any problems with 9.04 at all with suspend & resume just shutdown (wont power off usb saitek keyboard & razer mouse) but i don't care for that I prefer suspend & resume. However trying 9.10 suspend works while resume gets a black screen & locks up. Now on 10.04 it will suspend very fast but will not power up from resume keyboard & usb power is turned off thats what I can't figure out I have checked bios & changes settings after settings & nothing happens. I know in windows everything works but i do not want windows at all I prefer linux (ubuntu). In my asus eee pc 1001p suspend & resume works with both 9.10 & 10.04.
When I close my laptop lid (it goes into suspend mode). When I open it again, I can't see anything but a black screen. I have to reset the computer manually to accessUbuntu again.On a related note probably.. for 'some' screensavers, when I click to re-access my desktop, the screensaver freezes, but I can't see the unlock dialogue. I can however still type my password and it will unlock, I just can't see what I'm doing
in kubuntu how can i resume from suspend without password? it annoys the crap out of me i have been looking all over and cant find anything in settings to do this
Karmic 2.6.31-22-generic, Asus M3N78-EM, MCE remote with USB/IR dongle, latest Bios, Bios PM enable and set for suspend S3. IT will suspend but I need to depress case power button for it to resume. I want to use my remote control, I also can not get it to resume from Keyboard/mouse (See Note Below). Only suspend and power button work.
$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I am pretty new to Linux, but this can't be the way the system is supposed to operate.
Fedora 12 KDE 4.4 kernel 2.6.32.9-70.fc12.i686 Toshiba satellite L305D
As of updating KDE to 4.4 and a kernel update from two weekends ago hibernate/resume works perfectly. The problem is I feel that all terminals should be locked/logged out automatically upon suspend/hibernate. Through bug reporting at KDE found that an additional setting is required in KDE to lock the desktop before suspend/hibernate. But any of my other terminals that are logged in remain logged in upon resume. Is there an additional setting that I have to flip to secure the terminals? Would this be considered a security hole? Is there anything short of me manually logging out that I can do to automate locking/logging my terminals?
I am looking for a tool in fedora which can hibernate/standby and also resume after a few seconds automatically with a command. If we have that option by default in fedora.
I recently installed Ubuntu 10.04 Lucid Lynx. When I partitioned my HDD, I ran out of available partitions and so couldn't make a Swap Partition.I pushed on anyway, because I read here that you can create a Swap File instead of a partition that does the same thing. I've made the Swap File and it's activated (I know because during shutdown there's a message that flashes very quickly that says "Deactivating Swap [OK]".
But here's the real problem. My Ubuntu refuses to Suspend or Hibernate. The screen just goes black and the backlight stays on. Since one of the main functions of the swap file is to facilitate Suspend and Hibernate,I upgraded from 9.10 Karmic Koala, which suspended and hibernated normally.
When I suspend my computer and then resume later in the day my USB keyboard locks up. The only way I have found to reset the keyboard is to disconnect the USB cable from the USB port and then reconnect it.
