Hybernate does not work on my laptop. I receive the following error in the log: Running hook /usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate:
INFO: checking for suspend-to-disk prerequisites...
ERROR: no resume parameter on kernel commandline, can not suspend
I'm running Debian 8.1 KDE on a 2007 dv6 laptop. Model number is worn off. lol but the specs:
Intel i3 first gen m 330
4GB RAM
Intel (ironlake) graphics
First off, closing the lid to my laptop doesn't trigger suspend, or anything no matter what I set it to in power options.
I can suspend using "systemctl" or suspend from the "Leave" menu, but upon turning my computer back on, my touchpad and keyboard don't work.
Sometimes, my touchpad will start working after about 15 seconds, but the keyboard doesn't come back. I have to hard reset.
I have a feeling it's something to do with systemd, but I'm not super proficient in linux. Just an end user who is friendly with a terminal.
The PC is a Toshiba laptop model# x205-s9359 running 11.2, KDE 4.3.5. Its video card is an nVidia 8700 GT. For two years now I've been plagued by random flashes, flickers and even missing scan lines on my screen when I use the nVidia drivers (up to and including 195.36.15), so lately I've been using the nv drivers. I miss the effects, etc. but I can live with that. At least I can get my work done, even if the display isn't as fancy as I'd like.
- When I run the nv drivers I can't suspend the PC to RAM or Disk. This means a lot of wasted time waiting for the machine to shut down and reboot every time I leave my desk for any length of time. If I try to suspend to RAM the only thing that happens is that the network connection disconnects then reconnects immediately. Here's the log file....
- If I try to suspend to Disk the PC appears to suspend as expected, but when it resumes it hangs before restarting X, and there's no keyboard or power button response. I have to use alt-prtsc-reisub to reboot. When the reboot is complete the screen shows all the windows, etc that were present before the suspend. Here's that log file....
-When I run the nVidia drivers the suspend/resume functions work perfectly, but I have to put up with all the problems described above. Here's the log file for Suspend to RAM with nVidia, and here's the one for Suspend to Disk.
I've spent hours searching for clues in these forums, on the openSUSE.org site in general, at KDE.org and with Google and I'm sorry to say that most of I've found is horribly out of date, and/or it's way over my head. or (worst of all) not even dated, so I've no idea whether it's current info relevant to my situation or so out of date that I might do real harm if I were to trust it. (RANT: Is it too hard to put a date on an article?... end of RANT) I'd be quite content to use the nv drivers if I could solve the power management issues, but I'd be equally happy to solve the flickering etc. with nVidia drivers.
i have noticed that if vista is not the active partition, hybernate does not work. it just goes black and then back to the user icon screen to log back in. another "slight" problem was that i was not able to apply a service pack. after restoring vistas dominance i was able to install the pack. is there any other work arounds for hybernate? even though you might not be interested in cleaning up after microsoft.
View 1 Replies View RelatedI'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.
got a suspend problem with OpenSuse 11.3. I configured the powersave module that whenever I close down the screen of my laptop it suspends to ram. Works fine so far except when the screensaver is active. It just stays on when I close down the lid.
View 5 Replies View RelatedMy computer have ATI X600 graphics card installed, and I installed CentOS5.3.
Every time I suspend my computer and then resume it, it seem the graphics card can't resume and the monitor says 'no signal', but the system still responses, I can use keyboard.
Is there any configuration I can't do to make it resume normally? I've searched a lot in Google but can't find out any one else run into the same problem.
Information about the card:
Quote:
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.
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)
[code]....
I've set up a media box for mythtv based on OpenSUSE 11.3 and LXDE. By default, the screen gets locked prior to a suspend. On resume, therefore, the screen is locked and requires a password to unlock. I need to disable this action. In KDE4, I can do that by going to the power management settings and un-selecting the appropriate check box. In LXDE, however, I can find no such settings. There must be a config file somewhere that I can tweak to turn off the screen lock prior to suspend, but I have no idea what it is.
View 5 Replies View RelatedMy 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.
When I resume my system after choosing the "Suspend to RAM" option, the login prompt appears but the keyboard doesn't work at all. (Caps/Num/Scroll don't light up either) The mouse, however, works fine and I'm able to click on the on-screen elements. Since I'm not able to login, I'm forced to reboot and abort the session. Note that this does NOT happen with the "Suspend to Disk" feature. (ie, it works fine).
System Specs:
openSUSE 11.2 KDE4.3 x86_64 (updated)
Sony VAIO VGN-CS17G
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've just started using OpenSuse 11.2 KDE. I have KDE4.4 installed. I had this issue with KDE 3.4 as well. My HP Multimedia DV3065 laptop is encountering an issue with suspend/restore. After restoring, the mouse is frozen. I have already tried a few things.
1. Dropping to init 1 and then back up to init 5 did not provide a temporary fix. So this is probably hardware related in some sense (kernel?)
2. I tried a grub option (cant remember what it is now). i8500-reset something like that. It made no difference.
3. I tried modifying my 99ZGrub file per another posts suggested solution. That actually locked up my laptop and I could not reboot (even after a cold boot). I pulled the battery and let it sit for a bit and it booted again
So I have several issues..
1. I would like suspend to restore my mouse.
2. I have not figured out how to program my Sleep button to Sleep. My menu bar icon has Log Out / Restart / Turn Off. The ALT+F1 menu tab Leave has those plus Sleep and Hibernate.
To workaround the kio_smb madness, I set up shares to be mounted via /etc/fstab. It works flawlessly until I suspend my laptop. Coming back from suspend, samba mounts are not being re-mounted automatically. Since I'm new to opensuse, I wish to ask you:
Is there a polished way to make this happen, in opensuse approach?
Or shall I just go and toy with scripts in the init.d (or what is it in suse)?
As much as I could figure, I checked in yast, and smbfs service is signed as "Yes".
It's documented in the howto's that you need to have the nomodeset kernel parameter specified if you want to run the proprietary Nvidia driver. But I read in certain posts that this is only required for "older" graphics cards.Can someone shed some light on this? Is the parameter ALWAYS required when running the nvidia driver, or only for certain graphic cards?
View 9 Replies View RelatedI'm trying to install Oracle DB on OpenSuse (is it smart, because it's not certified for that OS?)..and I've set oracle parameters using oracle script, but when I'm runnign through oracle installation, kernel parameters check reports that parametersa are 'n/a', like oracle OS account cannot access those parameters..
View 1 Replies View RelatedAfter setting the "nomodeset" kernel parameter, to install the nVidia proprietary driver in OpenSuSE 11.3 (I need to do CUDA development), my Sansa Clip+ is no longer recognized. When I turn the "nomodeset" option off, I can see it with $(fdisk -l).
View 1 Replies View RelatedThe OS is Lucid 64-bit . Before I begin I must say suspend/hibernate works fine with 3 other machines, so I'm trying to find out what's wrong with this one. I tried [URL].. and also I tried changing acpi-support. It currently is as this:
[code]....
First of all let me introduce myself. My name is Rasheed and i am from UAE, after not having any reply from a week in Fedora's official forum i came across the linuxquestions through google and hoping to help others and resolve my issues as well with the help of experts here. So here is my problem what i am currently having. I am going through a serious issue right now. My laptop crashes when SUSPEND/HIBERNATE or unplugging the laptop's charger.
View 14 Replies View RelatedI have Debian Squeeze x64 on ThinkPad T61p with standard 2.6.32-5-amd64 kernel. thinkpad_acpi loaded as module, suspend to RAM works fine from menu in KDE as well as by closing the lid, however machine doesn't appear to react on pressing Fn+F4 which should put it to sleep as well. I've read through thinkpad_acpi documentation and asked Google but so far can't find the solution. Can anyone, point me in correct direction?
View 6 Replies View RelatedI've tried ubuntu, kubuntu, fedora and linux mint. all 64 bit versions. I've also tried to suspend through applications like acpitool. But nothing works. When I click on Suspend, the screen goes blank but the computer is still running. The wireless network adaptor gets disabled for a second and then comes back on. All I have to do is press a key and I get the unlock screen prompt. Basically, suspend works like 'Lock Screen'. I have a HP Pavillion laptop. Core 2 Duo @ 2 GHz and 4 GB RAM.
View 12 Replies View RelatedI upgraded from 10.04 to 10.10 Worked fined, but suspend doesn't work anymore. When I click suspend, a tty1 terminal screen appears, exactly as you would hit ctrl+alt+F1, with the exception that no input is possible. I'm a newbie and an Ubuntu fan but I absolutely have no idea how to solve this...
View 5 Replies View RelatedI use KnetworkManager for wireless. Works great except that if laptopgoes into suspend the wireless does not work after resume anymore.NetworkManager log
Apr 27 20:24:42 linux-nfii NetworkManager[1433]: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Apr 27 20:24:42 linux-nfii NetworkManager[1433]: <info> Policy set 'Morran' (wlan0) as
[code]....
everything works perfect including reboot and shutdown but not the hibernate or suspend (sleep). Whenever i try to do Suspend, my caps lock starts blinking and the screen goes white
View 2 Replies View RelatedMy 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.
View 9 Replies View RelatedI'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)
View 9 Replies View RelatedI 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.
View 11 Replies View RelatedIt all works if I boot my self compiled vanilla 2.6.35-rc3 though. The environment
Sony vaio VGN-SR21M 4GBRAM P8400, ATI HD3400 mobility. I use
kernel-2.6.35.6-45.fc14.x86_64
xorg-x11-drv-ati.x86_64-6.13.1-0.3.20100705git37b348059.fc14
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?
View 3 Replies View Related