Debian Configuration :: Laptop Does Not Resume From Suspend?
Jan 27, 2011
I have installed squeeze on a HP notebook. I have one small problem though.It does not resume from suspend. If I shutdown -> suspend, or close the the lid, or shut downs (suspends) as expected, but whenower it backup up, the screen just stays black.Hibernate is working fine.
output of lspci (if needed)
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
My Acer Aspire 7552 laptop is running Debian Testing (just the main repos, no contrib or non-free). For some reason, it takes over five minutes to resume from suspend, and an absurd period to come back from hibernate (well over half an hour). Has anyone encountered this problem before, or have any tips on how to fix it? For the time being, I'm completely powering off every time I close my laptop because it's faster that way.
Output of lspci in case it helps: 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
I'm running Debian Squeeze on a Dell Studio 1558 laptop, and I have my laptop set to suspend when my lid is closed. Resuming from suspend seems to work but the screen remains blank, forcing me to hard reboot every time. Upon reading this thread:
Tue Jun 21 23:07:12 AKDT 2011: performing suspend Tue Jun 21 23:07:28 AKDT 2011: Awake. Tue Jun 21 23:07:28 AKDT 2011: Running hooks for resume
I have just joined the Debian community, for the past 2 years I have been using Linux Mint (ubuntu), I am now using Linux Mint Debian 64. I have a Lenovo A700 ideacentre with a Broadcom 4313 WiFi card. I manage to get the card working, now I have a new problem. If I suspend the machine the WiFi will not connect on resume. Is there a simple command I can use to getting the connection restarted, or better yet a work around so it will restart on its own?
I'm having problems with resume after suspend to RAM. The machine starts to wake up, but the screens (multi mon VGA and DVI setup) are black and the keyboard doesn't light up. After ~20 seconds there's some brief disk activity and then the computer reboots. 100% repeatable with affected kernel versions. My test method is simple, I boot the machine on the kernel's recovery option, log on as root and run "PM_DEBUG=1 pm-suspend". I haven't found anything in the logs after a failed resume.
Here's the situation: I have a SSD disk. To get TRIM support I have to use kernel 2.6.33 or later, which means that the standard kernel in Squeeze is too old.I have Nvidia graphics, and there was a change in 2.6.34 that breaks older versions of xserver-xorg-video-nouveau (version 0.0.15, used in Squeeze), I can't use Debian Squeeze with a kernel newer than 2.6.33.x.My machine (XFX GeForce 9300 motherboard) won't resume from suspend to RAM if I use a kernel newer than 2.6.36. There are no BIOS updates available.
My options: Install newer kernel from Squeeze backports (2.6.38.2 last time I tried). <--- Not doable b/c of resume problems. Upgrade to Wheezy, which uses kernel 3.0.x. <--- Not doable b/c of resume problems.Compile a vanilla kernel. So basically I'm forced to compile my own vanilla kernel, 2.6.33.x on Squeeze or 2.6.35.x on Wheezy. I won't be stuck with an unsupported kernel version in the near future, but so far I've failed miserably.
I know that the latest kernel version where everything works is 2.6.36.x (no longer maintained), 2.6.37.0 and later cause resume problems (I've tried 2.6.37, 38, 39 and 3.0.0, .0.1). I've tried doing a git bisect on the kernel, but didn't succeed, ended up on 2.6.36-rc5 which is weird considering that 2.6.36.4 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
Lately I upraded my Debian using aptitude update/aptitude upgrade - including installing a new kernel (3.0). Since this upgrade I have strange problem with networking. When I suspend my computer and resume it, I do not have connectivity with network:
$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
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.
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 just upgraded to 9.10 (Karmic Koala) on a Dell laptop. Now when I close the laptop lid to suspend and then open it to resume, the audio disappears; have to reboot to get the audio back. I remember having this problem a while ago back on Hardy Heron and finding a kludge to fix it - a line inserted in a shell script that gets invoked on resume
I have recently updated my Ubuntu 9.10 install to Ubuntu 10.04 and the default kernel to 2.6.32-23 on my Acer Aspire 5738z laptop with 3 GB RAM and Intel GMA 4500m graphics card.
My problem is sometimes the laptop fails to resume after being Suspended to RAM. The problem is not consistent. Most of the time the system resumes properly but then some times it doesn't . It even doesn't respond to the Magic Keys. I am left with no other alternative but to keep the power button pressed till the laptop shuts down.
I'm running Debian Squeeze on a Dell Studio 1558 laptop, and I have my laptop set to suspend when my lid is closed. Resuming from suspend seems to work but the screen remains blank, forcing me to hard reboot every time. Upon reading this thread
Code: Tue Jun 21 23:07:12 AKDT 2011: performing suspend Tue Jun 21 23:07:28 AKDT 2011: Awake.
I have an issue with my Sony vaio fw31e not resuming from suspend. Reported this as a bug: [URL] The usual ways of suspending, from the kde 4 menu, from the power/battery widget or by lid closing always result in no resume. However, running pm-suspend from a root terminal suspends and resumes just fine. My question is, how does one delve into the way that the usual methods initiate suspend? Maybe if I could find out what each of these methods actually does, I may be able to see what is going wrong? I had been running squeeze on this lappy since July 2009 with no suspend issues until an update broke it sometime in January. The install is being fully upgraded every day at the moment.
I have a quite simple installation of Debian 8 Jessie XFCE and the resume from suspend is not working 9 out of 10 times. The system is single booted if that matters. I have found a few solutions to this problem but they were not suitable to my case as I don't have an Nvidia GPU but only Intel Onboard:
Code: Select all# lspci -v 00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02) Subsystem: Hewlett-Packard Company Device 2818 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0b <?> Kernel driver in use: agpgart-intel
When I try to resume, I can hear the system booting but I can't see anything on the screen and the keyboard is not working either (no light on Num Lock and Caps Lock). The only option is to press the power button for a few seconds to stop the machine and then push again to start booting again.
Up until a couple days ago, my computer had no problems suspending to ram. However, now when I suspend, and later hit a key on the keyboard (usually space) to resume, all I see is an illuminated black screen. I can't even open a tty via Ctrl+Alt+F1. I can however ssh into the machine.he only possibility I can think of is that I am no longer running kdm. I just use "startx" to star an openbox-session.
Fixing my chronic suspend/resume problems turned out to be easier under systemd, but like everything else lacks documentation.
To suspend rather than power off when pressing the power button, I edited /etc/systemd/login.conf
uncommenting this line and changing it to suspend: HandlePowerKey=suspend
and uncommenting the line HandleLidSwitch=suspend
Some services were lost on resume. This problem seems common. To run a command on resume, I believe you have to make your own script, and create a systemd file to run it.
My script is /home/james/.bin/james-resume.service, which contains:
#! /bin/sh /sbin/hdparm -B 255 /dev/sda
This must be executable. Ownership doesn't seem to matter.
To run it, I made a file in /etc/systemd/systen/suspend.target.wants The file name must match the script name: /etc/systemd/system/suspend.target.wants/james-resume.service
This contains:
[Unit] Description=Run James jobs at resume After=suspend.target After=hibernate.target After=hybrid-sleep.target
I'm running stock Debian 8.2 with GNOME DE on an Acer ES1-512 series laptop. Whenever I attempt to go into suspend, either by closing the laptop lid or holding ALT when clicking the power button in the top-left system menu on the desktop, my laptop briefly flashes the default GNOME lock screen, fades to black, and then hangs there. Usually, when my laptop would actually suspend, the power indicator light would change from blue to orange and slowly fade in and out. However, now it just sits on blue. There is no way to re-awaken the laptop from this state, and I have to force shutdown by holding the power button.
I have installed Debian a few days ago and when I close my laptop, it goes to suspend, everything is ok but when I try to awake the screen remains off.
I am using Asus X51RL laptop (made in 2007) and it is NOT a hardware problem, suspend works fine in Windows.
I have an Acer 1551 4755, with Debian Squeeze. Normally my Debian Squeeze installations and suspending work fine on my other 2 laptops. For some reason this one is troubled. I can put into sleep with "pm-suspend" or "pm-hibernate" but the thing is that my laptop never wakes up. I endup restarting.
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 like to suspend my laptop when I close the lid. I have squeeze installed. When I open the laptop lid all lights indicated that it coming out of suspend but the monitor stays black. It is worse since I install the ati drivers for the card instead of the xorg. It did it with both but worse with nonfree drivers. I can get it to come out by ctrl alt f2 and the ctrl alt f7. However yesterday that did not work but that was the first time. My laptop is an acer 5251-1513 amd processor v120, and hd 4250 radeon
it is a macbook pro (5,3) running sid.when i am using it, it is cool.however in suspend mode, it gets very hot.i have this running
Code: Select all/etc/init.d/macfanctld status ● macfanctld.service - LSB: Apple MacBook (Pro) fan control daemon Loaded: loaded (/etc/init.d/macfanctld)
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)
1. is it possible to schedule this command in the same manner as shutdown ? eg sudo shutdown -h 60
2. is it possible to schedule the laptop to come out of suspend ?
3. i have a usb sound card (xfi go). when waking from suspend, the internal sound card is selected. i have to manually select the external sound card & for whatever reason, also unmute it too
If I suspend my notebook it starts the usual slow orange blinking indicating the suspend mode got reached. There is also evidence in the various log files that this works. If I try to resume it hangs a for 3 seconds and then I get the hdd-password screen from my bios and the notebook boots from zero. I couldn't find anything in /var/log/messages nor dmesg. If I first boot to windows (grub 2nd partition) and then restart and boot to linux, all the suspend works fine
how do i disable the screen lock after i wake my computer from suspend? i would prefer to be able to just wake the computer up and have it go right to the desktop, without having to enter a password. i used to use ubuntu until today, and i remember having to run "gconf-editor" and then switching off on "lock_on_suspend" under apps/gnome-power-management from the menu that popped up. i tried to run "gconf-editor" in fedora 15, but that doesn't appear to exist. i've searched around and haven't been able to find an answer, so i'm wondering if anybody knows what to do?
I've upgraded 4 boxes (32- and 64-bit) from Suse 11.1 to 11.2 with no unresolvable issues. Now I'm stuck with my 5th box, a Dell Dimension 8400 desktop box (yes, an old brick, 32-bit). I can suspend to RAM ("suspend") and to disk ("hibernate") fine, but resume seems to fail. In Suse 11.1 I used kpowersave (GUI in the sys tray) to suspend to RAM. For some reason, it couldn't suspend to disk but that didn't bother me. kpowersave relies on the powersaved running.
Note I had upgraded my 11.1 installation to all shiny and new KDE 4.3 stuff, and while KDE 4.3 seems not to use powersaved (and thus kpowersave) all worked fine. Upgrading to 11.2 has removed kpowersave and powersaved. I don't mind switching to another way if only I could find documentation what's being used on KDE 4.3 (and/or Suse 11.2). All I find by googling is that the daemon used is powerdevil, and that I should use a GUI for suspending (this battery monitoring plasma app).
Well, if I do that on this box it simply does -- nothing. So I tried s2ram and a2disk directly:Running s2ram with the --force option works, but the box doesn't resume. Goes on, screen stays blank, mouse and keyboard don't work. s2disk complains about not being able to "stat the resume device file". I gave it the --resume_device /dev/sda6 option, and it hibernated fine. But it doesn't resume. Pressing the power on button just starts Suse anew (and recovers the file system journals, so I assume it thinks it has crashed before).
So I think I have 2 questions: What the heck does Suse 11.2 use for suspend/hibernate and resume? Is there any how-to available to learn what I need to configure? Why can't I resume from successful s2ram or s2disk operations? /var/log/pm-suspend-log or pm-powersave-log don't provide any clues.
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