Comment 108 for bug 568711

Revision history for this message
Michael Aeschbach (michael-aeschbach) wrote :

Check my comment #97 as well as it's link, too. My experiences with resume from suspend with Slackware were very weird. What I can say about my system is that the resume process did not start at all when I experienced the "black screen syndrom". Pm-suspend logs for successful and failed attempts are posted on LinuxQuestions.org (cf. #97). Furthermore: I did disable gnome-screensaver since I had problems with it when I resumed from hibernate. Another thing, since Ubuntu is Debian-based: suspend/resumed always worked well for me with Debian 5 (Lenny) but never with testing (Squeeze). Perhaps somebody could verify this on his system. If somebody would like me to send the full specs of my system (lspci), please let me know. Sorry that I'm not yet willing to install Ubuntu again; Fedora runs just to well and now even suspend to RAM works again. And last but not least: this behavior is not Ubuntu-specific. It affects every distro, I believe, since I saw it on Debian and its derivates (Debian, Ubuntu, LinuxMint, PeppermintOS) as well as on Slackware, SuSE, Fedora and a bit different on ArchLinux (there it was a problem with KMS and could at that time be solved by disabling KMS with kernel bootparameter modeset=0, which is, I think, not possible anymore, if you want to run the X window system).