<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Output to DVI-I (or DVI-D) is blank on Tonga (R9 285 and 380X) with multiple monitors" href="https://bugs.freedesktop.org/show_bug.cgi?id=91202#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Output to DVI-I (or DVI-D) is blank on Tonga (R9 285 and 380X) with multiple monitors" href="https://bugs.freedesktop.org/show_bug.cgi?id=91202">bug 91202</a> from <a class="email" href="mailto:freedesktop-bugs@digital-trauma.de" title="Thomas R. <freedesktop-bugs@digital-trauma.de>"> Thomas R.</a> <pre>Guido, does that mean that now it works for you, or simply that you can't say one way or the other because you didn't test with DAL actually running? I'm asking because I finally got around to compile amd-staging-4.7 (which only works with a certain set of kernel options, BTW), and with DAL enabled and both the last commit and f67b5d74 you mentioned, I still see this bug. So now I'm confused - am I doing something wrong, or was the fix a victim of the numerous DAL cleanups along the way, or maybe the freesync changes? I got "[drm] DAL is enabled" in my kernel log at any rate, and freesync.c dumps stack traces in warn_slowpath_null, which I guess is just a development help and nothing serious. If I'd find a branch with both a working and non-working revision in it I'd be willing to bisect, but going back in staging-4.7 removes DAL completely, and staging-4.6 doesn't even compile for me, which was when I gave up yesterday. It's a shame because apart from this, 4.7 works really, really well. So if there is anything I can do to properly triangulate this problem, I'd be very eager to help.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>