<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - intel-virtual-output shows different resolutions under certain conditions" href="https://bugs.freedesktop.org/show_bug.cgi?id=74800#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - intel-virtual-output shows different resolutions under certain conditions" href="https://bugs.freedesktop.org/show_bug.cgi?id=74800">bug 74800</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=74800#c11">comment #11</a>) > I understand what you are saying. > > Wouldn't this changes reflect in "xrandr -d :8" ? > It never showed up a 1920x1080 mode there. I think if you rewrote xrandr to monitor notifications, then you would also see it occur. It's certainly odd. The only thing I am confident about is that those modes are being generated on the remote :8 display and reported on HDMI-0. I have no idea why, and they also occur on the first read of modes. One thing that does occur, is that i-v-o uses the equivalent of xrandr --current (which does not force a reprobe of the outputs). > Another interesting thing. > If I remove the HDMI connector, nvidia fallsback to a 800x600 only mode (the > same happens when bumblebee starts with no heads). > The VIRTUAL1 display shouldn't fall to 800x600 also? No. Aiui, the fallback mode is just a mode set on no outputs, it is just the framebuffer size set when nothing is connected. (In -intel, we also provide a similar fallback.) Since there is nothing connected on any output, i-v-o reports nothing connected. (Checking xrandr -d :0/:8 should confirm that.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>