Comment 9 for bug 64927

Exactly the same problem with the linux-2.6.20-3-generic package (version 2.6.20-3.4) from feisty (and everything else from today's feisty, too).

I messed around with the s2ram program from suspend.sf.net a bit (running from single-user text console, to eliminate interactions with HAL and/or X), and I couldn't find any of its -f submodes that would make the screen turn back on. More worrisome still is that after resume (both from the normal suspend button and from s2ram) the keyboard is completely unresponsive, which makes me think the kernel never quite comes back up properly :(

zw