<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - 2560x1440 @144Hz graphic glitches and bad refresh rate" href="https://bugs.freedesktop.org/show_bug.cgi?id=93826#c38">Comment # 38</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 2560x1440 @144Hz graphic glitches and bad refresh rate" href="https://bugs.freedesktop.org/show_bug.cgi?id=93826">bug 93826</a> from <a class="email" href="mailto:yves.weber@yahoo.de" title="Yves W. <yves.weber@yahoo.de>"> Yves W.</a> <pre>(In reply to Jan Niklas Hasse from <a href="show_bug.cgi?id=93826#c37">comment #37</a>) > > Sorry, but I don't know what you mean by "using bitsect". > > Changes to the source code of the driver are controlled via Git as commits. > Assuming it once worked 144 Hz it's possible to use Git to find out which > commit caused the flickering. This is done by identifying any commit which > worked (good, in your case 4.4) and a commit which doesn't work (bad, 4.8). > Bisecting will then help you find the first bad commit faster (by sectioning > the pool of possible first bad commits in two sections repeatedly). > > I'm not sure though that this good commit exists though. Flickering also > happens with 4.4 for me. means i have to try manually each step and recompile kernel? But that will take ages :) I don't have that much time. btw mint 18 kernel updated to 4.4.0-43-generic It's still working like charm with 144hz @ 1440p - no flickering .. :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>