<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bisected] kernel 3.7.0-rc1 breaks 6950 (CAYMAN)" href="https://bugs.freedesktop.org/show_bug.cgi?id=56139#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bisected] kernel 3.7.0-rc1 breaks 6950 (CAYMAN)" href="https://bugs.freedesktop.org/show_bug.cgi?id=56139">bug 56139</a> from <a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> Alexandre Demers</a> <pre>(In reply to <a href="show_bug.cgi?id=56139#c21">comment #21</a>) > (In reply to <a href="show_bug.cgi?id=56139#c19">comment #19</a>) > > If I followed you correctly, setting bit 24 to "1" disables memory but keeps > > the CRTC state as it is (hopefully in sync with the monitor). However, what > > I see when grub2 kicks in with the "gfxpayload=keep" is an unsynced monitor. > > Sometimes the display will be black, other times it will only appear in the > > first couple of vertical lines, in others it will be vertically synced but > > shifted to the right at half or at two third of the screen. In other words, > > this really seems to be a sync problem. Should I try to combine patch 69113 > > and patch 69370 with the others? > > Are you saying the monitor gets messed up when grub kicks in? I.e., before > the OS loads? If so, that sounds like a grub issue. I'll take some pictures or record a small video of what's going on. That will be easier to understand. But yes, I'm beginning to think Grub2 is playing a bad trick somewhere in there and is not playing nicely when handling the framebuffer.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>