<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - intel-virtual-output offers wrong screen resolution for VIRTUAL screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=73816#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - intel-virtual-output offers wrong screen resolution for VIRTUAL screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=73816">bug 73816</a> from <a class="email" href="mailto:admin@schwarzwald-falke.de" title="Christoph Bessei <admin@schwarzwald-falke.de>"> Christoph Bessei</a> <pre>Finally I found a solution to solve the problem. As you expected the problem was the EDID of the monitor. Earlier NVIDIA drivers ignored the EDID and allowed own ModeLines in the xorg.conf or added via xrandr. But since 304 (I think, not sure) NVIDIA uses the EDID and reject every self created ModeLine. So I changed now a few lines in my /etc/bumblebee/xorg.conf.nvidia (Monitor Section) file: HorizSync 35-81 VertRefresh 35-76 Option "ModeValidation" "AllowNonEdidModes" Option "ModeValidation" "NoDFPNativeResolutionCheck” The HorizSync and VertRefresh was needed in my case because NVIDIA didn't allow 60Hz without these lines. The "ModeValidation" lines are telling the NVIDIA driver that it should accept self created ModeLines even if they are not appear in the EDID. I think it's possible to delete some lines in my xorg.conf.nvidia file and still get the same effect, but I haven't tested this. @Chris: Thanks for your help and the fast patch for xrandr ModeLines!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>