<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#c28">Comment # 28</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:stanislav.lisovskiy@intel.com" title="Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>"> Stanislav Lisovskiy</a> <pre> > > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>