After default Fedora 7 installation on my Acer Aspire 1692 I suspended my machine from System->Suspend. Everything seemed to went fine, machine was stopped ok. But after hitting a button machine is powered on but nothing seems to happen even if waiting like 10 minutes. The system does not react to any attempts from keyboard (such as ctrl+alt+bs or ctrl+alt+del). Only thing in /var/log/messages is: Jun 1 19:17:04 localhost gnome-power-manager: (dqarras) Suspending computer because user clicked suspend from tray menu
Actually, when suspending from console with echo -n mem > /sys/power/state system is suspended ok and resume fails again but now the system responds to ctrl+alt+del or the command reboot. So the problem is that the display stays disconnected. This is probably related to Bug 236223.
Does 'pm-suspend --quirk-vbe-post' (or any other option from pm-suspend --help) from console help? If so I can help you create a patch for hal-info.
btw: Get pm-utils-0.99.3-6.fc8.i386.rpm from koji.fedoraproject.org and install that (rpm -Uhv pm-utils-0.99.3-6.fc8.i386.rpm), the f7 package has no vbetool (should be fixed soon I think).
Created attachment 155916 [details] hal-info patch for Acer Aspire 1692 suspend
Fantastic, 'pm-suspend --quirk-vbe-post' works perfectly! I've attached a patch to hal-info that works for Acer Aspire 1692. It uses just the same quirks as Acer Aspire 1690. Thanks!
Oh, it should be noted that I was using the RPM from http://koji.fedoraproject.org/packages/pm-utils/0.99.3/6.fc8/i386/pm-utils-0.99.3-6.fc8.i386.rpm The default Fedora 7 RPM did not work. Thanks.
Actually, I noticed that only the RPM upgrade is needed as lshal reports: root@localhost:~# lshal | grep Aspire smbios.system.product = 'Aspire 1690' (string) system.hardware.product = 'Aspire 1690' (string) system.product = 'Aspire 1690 Not Applicable' (string) So, the patch is withdrawn, do not apply. And if you can, please close this bug as only the RPM upgrade is needed.
I have the same problem. I have F7 on a Dell Inspiron B130 and everything suspends correctly, but when I bring it back up, I get this message on the screen and goes no further: audit(1181402594.472:9): avc: denied {search} for pid=3136 comm="alsactl" name="root" dev=sda1 ino=9035137 scontext=system_u: system_r: alsa_t:s0 tcontext=system_u: object_r: default:s0 tclass=dir stopping tasks... done. shrinking memory... done. freed 74028 kbytes in 0.17 seconds (435.45 MB/s) Suspending console(s) I have disabled SElinux and still get the same result. I have not tried to kill "alsactl" before suspending, so that might be an easy fix. Will report back with result at a later time.
(In reply to comment #8) > I have the same problem. I have F7 on a Dell Inspiron ... > audit(1181402594.472:9): avc: denied {search} for pid=3136 comm="alsactl" > name="root" dev=sda1 ino=9035137 scontext=system_u: system_r: alsa_t:s0 > tcontext=system_u: object_r: default:s0 tclass=dir ... > I have disabled SElinux and still get the same result. I have not tried to kill > "alsactl" before suspending, so that might be an easy fix. Will report back > with result at a later time. You can not kill alsactl, it's started to restore the sound card settings (not a daemon). Do you have SELinux disabled or in permissive mode (/etc/sysconfig/selinux)?
(In reply to comment #9) > (In reply to comment #8) > > I have the same problem. I have F7 on a Dell Inspiron > ... > > audit(1181402594.472:9): avc: denied {search} for pid=3136 comm="alsactl" > > name="root" dev=sda1 ino=9035137 scontext=system_u: system_r: alsa_t:s0 > > tcontext=system_u: object_r: default:s0 tclass=dir > ... > > I have disabled SElinux and still get the same result. I have not tried to > kill > > "alsactl" before suspending, so that might be an easy fix. Will report back > > with result at a later time. > > You can not kill alsactl, it's started to restore the sound card settings (not > a daemon). Do you have SELinux disabled or in permissive mode > (/etc/sysconfig/selinux)? Resume from hibernate works for me once I set SELinux to either permissive mode or disabled. Once I put it back in enforce mode, I get the same message as before. Don't know why I didn't think of doing that before, but thanks for the help anyhow.
I can confirm again that this is fixed in F8T3 & Rawhide. Feel free to close this one.