Len, Thanks for the quick response. Unfortunately, I think in this instance that the failure on resume IS related to the method of waking. Here are the results of testing as you imply below: Resume from S3 using power button -> 100% functional, both ttyS0 serial console and NVIDIA video card console Resume from S3 using WOL magic packet -> Fans run, disk activity, NO NVIDIA video card console response, NO ttyS0 serial console response, NO ping response Resume from S5 using power button -> Normal boot Resume from S5 using WOL magic packet -> Normal boot I haven't tried wake from S4 as I don't currently have a swap partition large enough to try it (1GB RAM). Regards, David. -----Original Message----- From: linux-acpi-owner@xxxxxxxxxxxxxxx [mailto:linux-acpi-owner@xxxxxxxxxxxxxxx]On Behalf Of Brown, Len Sent: Tuesday, 16 May 2006 4:35 PM To: David Giddy; linux-acpi@xxxxxxxxxxxxxxx Subject: RE: Help request on S3 resume problems I expect that the method to wake the system and the fact that resume from S3 fails are independent problems. Likely you can use WOL from S5 and the system will boot normally from poweroff. (same can be said for suspend-to-disk -- S4). Likely you can wake the system from S4/S5 via power or sleep button, and it will fail the same way as it fails via WOL. The way to debug an S3 resume with no video is to use a serial or a firewire console. -Len - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
