<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED MOVED - [NV17] nouveau driver fails to restore screen content / video mode after resume from s2ram" href="https://bugs.freedesktop.org/show_bug.cgi?id=55450#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED MOVED - [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:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> Emil Velikov</a> <pre>(In reply to <a href="show_bug.cgi?id=55450#c14">comment #14</a>) > Well the problem was that nouveau has gone into my initrd. A simple > NO_KMS_IN_INITRD="yes" followed by an mkinitrd did the trick. >From my POV kms drivers in initrd is a very bad idea. > just gained test results are not encouraging: > * echo mem >/sys/power/state without nouveau -> bluescreen > * echo mem >/sys/power/state without nouveau and with vga=0 -> funny text > screen flicker > I'm suspecting that those two are different (possibly related) issues. Although once we can get a non-lockup system after s2r we can look into the (alleged) nouveau issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>