<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Unable to detect monitor modes connected to a TB16 Dell dock" href="https://bugs.freedesktop.org/show_bug.cgi?id=111507#c29">Comment # 29</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Unable to detect monitor modes connected to a TB16 Dell dock" href="https://bugs.freedesktop.org/show_bug.cgi?id=111507">bug 111507</a> from <a class="email" href="mailto:lionel.g.landwerlin@linux.intel.com" title="Lionel Landwerlin <lionel.g.landwerlin@linux.intel.com>"> Lionel Landwerlin</a> <pre>(In reply to Stanislav Lisovskiy from <a href="show_bug.cgi?id=111507#c28">comment #28</a>) > > > > Like I wrote earlier, the bisect was wrong. Sometimes the monitor will > > manage to work and that screwed up the bisect. > > > > Reverting that one patch doesn't actually help. > > Ok, then we are dealing with something else. However if the console mode > works all the time it is quite likely that it is userspace again. > > I have seen similar issue quite a lot when it was simply a userspace issue. > > Also you can try to force a modeset using xrandr. I don't think I can when using a gnome-shell wayland session.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>