Slackware :: 13.1 - Suspend / Resume With 2 Different Laptops
May 29, 2010
Laptop 1 is an acer aspire 5570. closing and opening the lid works a few times, after editing acpi_handler.sh, and battery life reporting is ok during this time. then, for no apparent reason, the laptop no longer responds to the lid closing, and no longer seems to be able to read the battery charge state. once this has occurred, the computer will also no longer restart, it tries a few times, with lights flashing and the hd making ugly noises. the only way to extricate the computer from this state is to pull and reinsert the battery.
Laptop 2 is a gateway nv18. suspend/resume with the lid are ok, mostly. the issure here is no display at all in x. but the computer does respond to ctrl-alt-backspace to kill x, with the command prompt returning. still not good. I'm trying a fresh install on the gateway, to see if this was just an installation glitch.
Both laptops performed flawlessly in 13 otherwise.
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.
I can still play sound through other programs, but ncmpcpp and sonata both stay stuck on 'paused'.I can kill mpd, then restart it, and verbose logging indicates success, but restarting either client results in the same behavior.'rc.alsa restart' has no effect, and modprobe -r snd* results in 'fatal * module in use' despite that i have no sound applications running but sound still works fine in audacity and other programs.
I have a Dell latitude D620, suspended to ram and resumed and when I move the mouse the display goes crazy. It looks like an old TV with the horizontal hold messed up. IIRC this runs an intel video card, I'll double check when I get home.
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)
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.
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.
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've been trying to find an answer to the following problem : whenever my PC is put in Suspend/Hibernate mode, it fails to recover when pushing the power button. This happens both with automatic suspend or manual suspend. I've been reading this problem, and mine is quite similar, but no solution is given.
uname -rmi 2.6.18-194.11.4.el5 x86_64 x86_64 PS: this computer is not connected to Internet, no update possible.
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.
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)
Starting with kernels 2.6.29.x and above (which includes 2.6.30.x and 2.6.31.x),whether obtained from "kernel.org" of from the "FC11 repository", none of theseresume properly after putting the computer to sleep (suspend)... in my case, via"pm-suspend".When I press the "On" button, I hear the fan, but get no video. And the fan neverreturns to the normal resumed, slower speed -- which it normally does after aroper resume.Eventually I have to issue "Ctrl + Alt + Delete" to reboot. So the computeris resumed to some degree (to have been able to accept that sequence), butnot all the way - no video (and who knows what else)Any ideas -- I've searched high and low. Are there new kernel parametersI have to be aware of when I do a "make oldconfig", and go from there?
I am having a problem with suspend in F15. While the computer enters and resumes from suspend extremely fast (basically instantaneous), the whole system seems sluggish and unresponsive afterwards. The mouse cursor is lagging and some key strokes are omitted when typing. The animations in Gnome 3 are also very non-fluid compared to how they were before suspend. The only way I have found to return to normal operation is to reboot the computer. I have tried 32 and 64-bit versions of Fedora 15 with the problem existing in both. I also tried the latest version of openSuse (Gnome 2.32) just to see if this problem persisted and I can confirm that it did. Perhaps this indicates a kernel-related problem that should be reported as a bug somewhere else?
lspci: Code: 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11) 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11) 00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11) 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11) 00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11) 00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11) .....
There is an intermittent problem with resuming from s2ram. Occasionally, the power button is pressed to resume, the screensaver comes on but the animation is frozen along with the mouse and KB. Sometimes the desktop will show although with the same frozen condition. My swap parition is 2GB. I read in the forums that a small swap partition may cause a somewhat similar condition. I also read a recommendation to disable powersaving and screensaver, again not for my exact symptoms. I would like to find the root cause even if it takes some doing. Otherwise, the system rocks (except Amarok never worked but Kaffeine works for sound). Here are the system specs:
openSUSE 11.3 x86_64 KDE 4.4.4. rel 3 HP xw9400 Workstation AMD 64 Opteron OCZ Vertex 60GB (dedicated system drive-single boot)
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.
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.
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.
I was trying to get this feature: wake up my htpc from s3 with my remote control and the solution is to modify /proc/acpi/wakeup and a descriptor in /sys. Here are the details: I'm using a Microsoft IR receiver for MCE remote that appears as dev 2 of bus 2 in lsusb
root@htpc:~# lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 045e:0714 Microsoft Corp. Bus 001 Device 005: ID 045e:0715 Microsoft Corp. Bus 001 Device 004: ID 045e:0707 Microsoft Corp. Wireless Laser Mouse 8000 Bus 001 Device 003: ID 045e:070c Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub....
That's USB0 I have to enabled, why not usb 1 or 2 (bus 2 in lsusb)? Moreover why are all the disabled/enabled preceded with a star and S4 and not S3 mentioned? Nevertheless that wasn't enough to get it work. I looked in gconf-editor in apps/gnome-power-manager/general but I have no can-suspend or something similar... (I'm running on 10.10, with 10.04 I could suspend only once, afterwards the computer didn't go to suspend, just black screen then login screen). So I looked in /sys/ and found that 'cat /sys/bus/usb/devices/2-1/power/wakeup' (notice the 2.1 as bus 2 device 2 (0,1,...) gave 'disabled' so a echo enabled > /sys/bus/usb/devices/2-1/power/wakeup and now I can wake-up with the remote when I want.
What I don't understand: Why USB0 in /proc/acpi/wakeup ? Why have to change in /proc and /sys ? Is it possible to automate this to get it work even if I change the usb port the receiver is plugged in ?
I want to suspend/resume a thread. The library I am using is pthread.h.I am also running my application on linux.Is there any function in pthread. let me suspend a thread temporary?I have read a document in which it was mentioned thatthread does not support suspend/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.
I have a new, fully updated installation of F12 which won't resume from suspend (to RAM) on my hardware. I also have the Ubuntu Karmic Live CD which does suspend/resume perfectly on the same box. So, I'd like to try and find out what Ubuntu is doing to make it work and configure my F12 to do the same.
