<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - LG 5K Ultrafine display (tiled DP) is not detected correctly" href="https://bugs.freedesktop.org/show_bug.cgi?id=105198#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - LG 5K Ultrafine display (tiled DP) is not detected correctly" href="https://bugs.freedesktop.org/show_bug.cgi?id=105198">bug 105198</a> from <a class="email" href="mailto:bugs@bzatek.net" title="Tomas Bzatek <bugs@bzatek.net>"> Tomas Bzatek</a> <pre>(In reply to Jose Roberto de Souza from <a href="show_bug.cgi?id=105198#c17">comment #17</a>) > Tomas Bzatek did you setup xrandr after apply the patch? > See here: <a href="https://github.com/i3/i3/issues/1799#issuecomment-233900476">https://github.com/i3/i3/issues/1799#issuecomment-233900476</a> I did something similar and I can see the newly created monitor in the `xrandr --listmonitors` output. No difference in mode setting and no change from the windowmanager side either. I understand the WM needs to be aware of this logical monitor setup but would it make a difference in KMS, i.e. would it magically cause the outputs to get synchronized? Also, is there a difference in DDX driver used? I'm using the legacy intel driver as modesetting+glamor is noticeably slower. I've tried both anyway with exactly the same results (tiles out of sync), the only difference was in display output naming. That said I'm still seeing hardware sync issues where the panel is perhaps unable to find and synchronize the first scanlines of the frame. It's probably specific to the panel controller with perhaps only little delay tolerance between the inputs. Other panels may allow more tolerance at the expense of larger input lag.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>