No Suspend Only Hibernate

[jimbou]

Hello All,

I have installed and fully updated Fedora 8 on a Dell Precision M60. The user would like to use suspend as opposed to hibernate. But the suspend option does not exist anywhere, only hibernate.

The pm-utils package is installed.

Hibernate works.

I ran pm-suspend from command line and it suspended, but will not wake back. Or at least the video does not come back. Using the xorg "nv" driver.

No quirks in use.

lshal | grep -i hardware shows:
===
system.hardware.primary_video.product = 796 (0x31c) (int)
system.hardware.primary_video.vendor = 4318 (0x10de) (int)
system.hardware.product = 'Precision M60' (string)
system.hardware.serial = 'BHS3J61' (string)
system.hardware.uuid = '44454C4C-4800-1053-8033-C2C04F4A3631' (string)
system.hardware.vendor = 'Dell Computer Corporation' (string)
laptop_panel.brightness_in_hardware = false (bool)
===

Ideas / Suggestions?

TIA

[markjb]

Quick look at the hal sleep quirks

http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html

shows a vbestate restore is probably needed for the M60, anyway site above might help.

[jimbou]

Excellent site. I went there and used the quirk-checker script. It reported no problems and I should be able to suspend properly. So this time I pressed <Fn>-<Suspend> keys and the machine does indeed suspend. Pressing the power button does get it back awake again.

Now I am really befuddled as to why there is no longer a suspend option in the gnome menu system or the gnome power manager choices.

I checked my Fedora 8 desktop and the suspend options no longer exist in the menus there either.

I know some will want to be able to close their laptop lid and get suspend and not hibernate.

I have done several yum --list commands to see if I maybe need to install a package but can't come up with anything yet.

Thanks again.

Ideas?

TIA

[markjb]

does

lshal | grep suspend_to_ram

return
power_management.can_suspend_to_ram = true (bool)

If gnome-power-manager doesn't want to play ball, you can alternatively have the acpid service deal with suspending to ram on a lid close event (amongst others).
For example
create /ect/acpi/events/lidclose.conf

event=button[ /]lid
action=/usr/sbin/pm-suspend

and restart the acpid service

[GrayFox]

Now I am really befuddled as to why there is no longer a suspend option in the gnome menu system or the gnome power manager choices.

I checked my Fedora 8 desktop and the suspend options no longer exist in the menus there either.

I know some will want to be able to close their laptop lid and get suspend and not hibernate.

I have done several yum --list commands to see if I maybe need to install a package but can't come up with anything yet.

Thanks again.

Ideas?

TIA

Heh, heh I asked the same question: The suspend menu item is in the Shutdown... menu item in
the system menu.

Jerry

[Sidrian]

Same problem here. Suspend in f7 worked perfectly, but now after installing f8 i dont have "Suspend" option in menu "System" and computer dont wake up after using pm-suspend command.
Does anyone solwed this problem?
Conf: Asus p5b deluxe (p965), geforce 7900gs

[jimbou]

No. Fortunately, the guy that uses the laptop I was having trouble with, prefers to suspend with the Fn keys. Although on an IBM T43 laptop I was working with, the suspend option is there. It has some strange behaviour though. After the machine is booted and logged in I could close the lid and it would suspend. But after that it will not suspend unless the lid is closed twice?? Seems like it worked flawlessly with the kernel that is supplied with the install. But once it is upgraded then the problem appears.

Hmmmmm.

[Sidrian]

Am i retarted or? Today install f8 on work and one more time no "Suspend" button i "System" menu. Motherboard with integrated intel (some 945 series). Only FOSS drivers. Maybe im stupid and fedora developers just placed that damn button to some other place?!

PS. sorry for floodin in Laptop section, all this PC are dekstops. Didnt want to start similar thread.

[jimbou]

Te suspen option in the menu system should be under System -> Shutdown. Then you can select suspend if it is available.

HTH

[Sidrian]

In f7 "Suspend" button was in system menu. In shutdown menu i can only select hibernate.

[Mack]

Hi Jimbou,

I have the same close-twice-to-suspend problem with a Toshiba M105-S3041 (similar innards to your T43, as I recall). This has got to mean something to someone! There's no clue in the logs, either.

The other gnome-power-manager problem that I'm having is that when I disconnect the AC it (almost always...) suspends.

[RJFUatHOME]

I'm still using Fedora 7 but have any of you checked the options available in the gconf editor under /apps/gnome-power-manager?

It may be different in version 8 but there are some button display options in there for suspend and hibernate. You may have to log out and back in to see changes.

[Mack]

Hi RJFUatHome,

Thanks for the suggestion---that's a good question. I had looked through the settings for gnome-power-manager and they look fine.

What's weird is that no event is logged every other lid close. Nevertheless, gnome-power-manager is aware in some way that the lid is closed, because on the lid-closings in which it doesn't suspend, it does blank the screen, as it's configured to do when running on AC.

I tried turning on acpid and it catches every lid closing. I may end up using acpid rather than gnome-power-manager, as suggested in post #4 above. I had to do this after I an update to FC5 wrecked HAL/udev. At least then it was a nuisance because gnome-screensaver refused to play nicely with acpid, and PAM was standoffish at best.

I don't know anything about ConsoleKit and how session switching works, but I wonder if it's relevant. I noticed that /var/log/messages sometimes contains messages like "gnome-power-manager: (UserOtherThanMe) suspend failed" after I've successfully suspended. This is even though no session other than my own has been opened since the last reboot. "ps -e" shows that there's only one gnome-power-manager running, too. Maybe gnome-power-manager is getting confused about potentially getting acpi events from more than one session?

[RJFUatHOME]

I was really pointing to the settings in there that affect the display of the ability to suspend or hibernate for user accounts in Gnome and how it displays on the shutdown dialog. I didn't mean to imply there was anything in there that might fix the lid issue, sorry.

I get the impression that power management and ACPI is really a difficult moving target with a ton of different implementations in BIOS. I have an old toshiba laptop that does the exact same thing with Windows98, I have to close it twice to force a suspend.

I wonder what other options the acpid service can handle? It sounds like a pain to create a custom acpi conf file to replace or supplement the gnome-power-manager, especially when they seem to be working on power management so agressively lately in Gnome.

[jimbou]

That's pretty funny. I discovered the unplug from AC and suspend problem last night. As others are mentioning, the acpi / bios relationship seems to be a nightmare. Not sure why something that worked flawlessly in FC6 has become an issue in FC7 and now Fedora 8.

But at least using the Fn key is working out ok for the T43 I am working on.

[Mack]

Last night I found a bug report on the redhat bugzilla (bug 354841) regarding suspend-on-unplug-from-AC and added my two bits. I didn't see anything about close-twice-to-suspend.

RJFUatHOME, that's interesting that Windows98 does the same thing. That sure runs counter to my theory that session switching is to blame!

Using acpid to suspend-on-lid-close isn't hard. I haven't ever figured out how to get acpid to run gnome-screensaver, since it necessisarily calls it as root. But xscreensaver works fine.

Xscreensaver isn't installed by default in F8. If you don't have it, then

yum install xscreensaver

will get it. After it's installed, run

xscreensaver-demo

to configure it. Like gnome-screensaver, it needs to be running as a daemon process before you can use it. For now, you can start it with simply

xscreensaver &

To have it running whenever you need it, click on system -> preferences -> personal -> sessions and add xscreensaver as a program to always run.

Create a file /etc/acpi/events/lid.conf:

event=button/lid.*
action=/etc/acpi/actions/suspend.sh


Create a file /etc/acpi/actions/suspend.sh:

#!/bin/bash
#
# /etc/acpi/actions/suspend.sh
#
# Script to suspend via acpi
#
/usr/bin/xscreensaver-command -lock 2>/dev/nul
sleep 1
/usr/sbin/pm-suspend
/usr/bin/xscreensaver-command -deactivate 2>/dev/nul


Be sure to make this second file executable and start acpid:

chmod a+x suspend.sh
service acpid start


So that this survives the next reboot, turn acpid on permanently:

chkconfig acpid on

Since acpid is going to be taking care of lid closing events, it's probably a bad idea to have gnome-power-manager trying to do the same (at least every other time).
Go to system -> preferences -> system -> power management. Under the Battery tab, set gnome-power-manager to do nothing on lid-closing.

I've suspended and resumed many many times with nary a hang---with either the traditionally troublesome ipw3945 kernel module or with the open source (!) iwl3945. Let's just say I'm pleased.

If you close the lid and open it up in less than a minute or two, xscreensaver skips the authentication dialog.