From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: Hardware: Toshiba Satellite A30 Laptop Software: Fedora Core 3 with latest updates With kernel enabled with ACPI: Grub config: "kernel /boot/vmlinuz-2.6.9-1.681_FC3 ro root=LABEL=/ acpi=on rhgb quiet" Good: Good reliable power management when running. Bad: Suspend to disk doesn't work when shutting lid on laptop. Ugly: Suspend to RAM works but will not resume properly (screen is blank) after pressing power button. Note: When using the 'echo 4 > /proc/acpi/sleep' or 'echo 4 > /sys/power/state' commands (to get the laptop to suspend to disk) no response is heard or seen. According to the boot up configurations the acpid daemon is running but that is all I know. Version-Release number of selected component (if applicable): acpid-1.0.3-2 How reproducible: Always Steps to Reproduce: 1. Shut laptop lid. 2. Wait 3. Laptop does not turn off. Actual Results: The laptop did not suspend to disk. Expected Results: The laptop should suspend to disk Additional info:
This is quite common. If you care enough, you'll probably want to patch the kernel to get the standard 2.6 software suspend feature working again, or use <http://softwaresuspend.berlios.de/>. Either way, it 'ain't gonna be easy. Oh, and even if you manage to get suspend working, you may find that some of the hardware doesn't like resuming - especially things like video and networking.
to fix suspend to RAM try passing "acpi_sleep=s3_bios" to kernel bootline
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
This bug has been automatically closed as part of a mass update. It had been in NEEDINFO state since July 2005. If this bug still exists in current errata kernels, please reopen this bug. There are a large number of inactive bugs in the database, and this is the only way to purge them. Thank you.