Bug 11444

Summary: Dual head not working on 965G
Product: xorg Reporter: Eric Dorland <eric>
Component: Driver/intelAssignee: Eric Anholt <eric>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: eric
Version: 7.2 (2007.02)Keywords: NEEDINFO
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
i915 platform: i915 features:
Description Flags
my xorg.conf
Xorg.0.log after all my machinations none

Description Eric Dorland 2007-07-01 21:52:59 UTC

I've recently purchased an Intel DG965WH motherboard with an integrated 965G graphics chip. I'm trying to get dual head, Xinerama style working on my two monitors. On is a Hyundai L90D+ (19" LCD) and the other is a Samsung SyncMaster 226BW (22" widescreen LCD). I have Silicon Image Orion ADD2-N SDVO card to drive the Samsung display, and the Hyundai is just plugged in to the motherboard's VGA port. I'm trying to drive them both at their highest resolutions (1680x1050 for the Samsung and 1280x1024 for the Hyundai). I'm running the latest intel driver from Debian, xserver-xorg-video-intel 2.0.0-5, server 1.3.

After starting X the Hyundai's resolution seems stretched (as if it were running at 1680x1050) and only part of the Samsung's monitor has content which appears to be fitting in a 1280x1024 subset of the display. I run:

$ xrandr --output TMDS-1 --right-of VGA
$ xrandr --output VGA --auto

Now, oddly, the Hyundai on the left looks ok, but the Samsung has the 1/3 of it's screen looking ok (I can move windows into it), but the rest of the screen is black with some random multi colored lines in it. I can move the mouse over this and it renders correctly. In fact I can move windows over it but they get obscured by the black square. Sorry for no screenshot. Here the output from xrandr after the two operations above:

Screen 0: minimum 320 x 200, current 2960 x 1050, maximum 2960 x 1050
VGA connected 1280x1024+0+0 (normal left inverted right) 376mm x 301mm
   1280x800       60.0  
   1280x768       60.0  
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9  
TMDS-1 connected 1680x1050+1280+0 (normal left inverted right) 474mm x 296mm
   1680x1050      59.9*+   60.0  
   1280x1024      75.0     59.9  
   1280x960       59.9  
   1152x864       75.0     74.8  
   1024x768       75.1     70.1     60.0  
   832x624        74.6  
   800x600        72.2     75.0     60.3     56.2  
   640x480        75.0     72.8     66.7     60.0  
   720x400        70.1  

I'll attach my xorg.conf and the X log as soon as bugzilla will let me. If there's anything else you need to help diagnose the problem please let me know.
Comment 1 Eric Dorland 2007-07-01 21:53:53 UTC
Created attachment 10542 [details]
my xorg.conf
Comment 2 Eric Dorland 2007-07-01 21:55:06 UTC
Created attachment 10543 [details]
Xorg.0.log after all my machinations
Comment 3 Jesse Barnes 2007-08-09 11:57:19 UTC
Are you running a 3D window manager like compiz or beryl?  If so, try with just twm, metacity, or kwin instead.  The 3D window managers have some known problems with large, cross monitor displays.

Also, try disabling page flipping and triple buffering, and see if the issue occurs with both EXA and XAA AccelMethods.
Comment 4 Gordon Jin 2007-09-11 22:26:45 UTC
Dorland, could you try Jesse's suggestion?
Comment 5 Gordon Jin 2007-10-08 19:54:34 UTC
Feedback time out. Please reopen if you can still reproduce with suggestions in comment#3.
Comment 6 Eric Dorland 2008-09-01 16:02:04 UTC
I apologize for letting the feedback timeout, but I am still most definitely having this problem, at least the resolution part. Both monitors start up in 1280x1024 and I have to run xrandr --output TDMS-1 --mode 1680x1050 every time I restart X.

Let me know what sort of additional information would be useful and I will provide it.
Comment 7 Gordon Jin 2008-09-12 00:14:26 UTC
It has been over 1 year. So please first try the latest driver (2.4.2 release or 2.5-branch). Then provide the information requested in comment#3.
Comment 8 Gordon Jin 2008-10-12 22:44:06 UTC
Dorland, are you able to try newer driver?
Comment 9 Michael Fu 2008-11-11 17:11:00 UTC
timeout for reporter's response. reject.

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.