Bug 22973 - Mesa3D does not support multimonitor setups correctly
Summary: Mesa3D does not support multimonitor setups correctly
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-27 14:46 UTC by JasonErickson
Modified: 2018-04-25 04:48 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Original Multi-monitor setup (653.98 KB, image/png)
2009-07-27 14:46 UTC, JasonErickson
Details
Mesa3D running dual monitor graphics. (216.03 KB, image/png)
2009-07-27 14:46 UTC, JasonErickson
Details
Video modes used (3.24 KB, image/png)
2009-07-27 14:47 UTC, JasonErickson
Details

Description JasonErickson 2009-07-27 14:46:01 UTC
Created attachment 28047 [details]
Original Multi-monitor setup

I got the approval from my company to provide these screen shots.  The three screen shots are as follows.

1) The original running on the standard windows XP OpenGL driver using a Nvidia Quadro FX 3700.  You can clearly see the dual monitor support with the screenshot.
2) The Mesa3D version running in a virtual machine running windows XP and Mesa3D OpenGL driver.
3) Video modes used in the virtual machine environment.

As you can see in #2 the graphics for the first screen are on top of the graphics for the second screen.  I emphasized this by shrinking the first screen which in turn shrank the rendered graphics on the second screen.

The graphic issues you see in #2 will be filed as a separate bug as I believe it is a separate issue than the multi-monitor issue.
Comment 1 JasonErickson 2009-07-27 14:46:48 UTC
Created attachment 28048 [details]
Mesa3D running dual monitor graphics.
Comment 2 JasonErickson 2009-07-27 14:47:05 UTC
Created attachment 28049 [details]
Video modes used
Comment 3 Timothy Arceri 2018-04-25 04:48:11 UTC
Mesa isn't where this type of thing is handled. You were probably having an issue in X somewhere. Given the age of this bug I'm just going to close it rather than reassigning.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.