<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [NV17] nouveau driver fails to restore screen content / video mode after resume from s2ram" href="https://bugs.freedesktop.org/show_bug.cgi?id=55450#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [NV17] nouveau driver fails to restore screen content / video mode after resume from s2ram" href="https://bugs.freedesktop.org/show_bug.cgi?id=55450">bug 55450</a> from <a class="email" href="mailto:estellnb@elstel.org" title="Elmar Stellnberger <estellnb@elstel.org>"> Elmar Stellnberger</a> <pre>In deed, it is now a kernel issue (... and I doubt that it previously was)! I have tried to s2ram from init=/bin/bash with mount -t sysfs none /sys: * s2ram result: colorful stars; sysrq-keys are no more working * s2ram -nofbsuspend result: bluescreen; sysrq-keys are not working * nouveau.modeset=0; s2ram result: text console is restored and almost readable; however sysrq-keys are still not working. kernel-3.11.3-1.1-default (I would wonder if you still needed libdrm, Mesa version by now; there will be no pm-suspend dmesg on init=/bin/bash). Should I re-post on kernel.org?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>