xf86-video-intel 2.0.0 and DVI

[Hamish Moffatt]

On Tue, May 29, 2007 at 10:13:55AM -0700, Keith Packard wrote:
> On Tue, 2007-05-29 at 23:32 +1000, Hamish Moffatt wrote:
> 
> > (II) intel(0): Modeline "1280x1024"x75.0  135.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
> > (II) intel(0): Modeline "1280x1024"x75.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
> 
> Not quite identical; as you can see, the hsync start timing is earlier
> in the second mode. You wouldn't think this would matter, would you. The

Thanks, I missed that.

> second one is the VESA standard timing for this mode, the first appears
> to be an EDID-specified mode.
> 
> Please use xrandr --verbose to see which of these two modes actually
> works; if the EDID mode works, then there's a bug in the mode preference
> code. If the VESA mode works, your EDID data is buggy and we can add a
> quirk to the server to repair it automatically.

Here's the xrandr output; I'm not sure how to interpet it.  How can one
tell which mode is actually in use from this format?

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1280
VGA disconnected (normal left inverted right)
	Identifier: 0x5c
	Timestamp:  -580238011
	Subpixel:   unknown
	Clones:     
	CRTCs:      0 1
TMDS-1 connected 1280x1024+0+0 normal (normal left inverted right) 338mm x 270mm
	Identifier: 0x5d
	Timestamp:  -580238011
	Subpixel:   horizontal rgb
	Clones:     
	CRTC:       0
	CRTCs:      0 1
	EDID_DATA:
		00ffffffffffff0034a1720142020000
		230d010380221b78eac4f6a3574a9c23
		114f54bfef80714f81908180818b0101
		010101010101bc34009851002a403070
		1300520e1100001ed50980a0205e6310
		1060520830e41000001a000000fd0038
		4b1f510e000a202020202020000000fc
		004d45412044563137320a20202000d1
  1280x1024 (0x5f)  135.0MHz
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock   80.0KHz
        v: height 1024 start 1025 end 1028 total 1066           clock   75.0Hz
  1280x1024 (0x60)  140.8MHz
        h: width  1280 start 1368 end 1504 total 1728 skew    0 clock   81.5KHz
        v: height 1024 start 1027 end 1034 total 1072           clock   76.0Hz
  1280x1024 (0x61)  135.0MHz
        h: width  1280 start 1296 end 1440 total 1688 skew    0 clock   80.0KHz
        v: height 1024 start 1025 end 1028 total 1066           clock   75.0Hz
  1280x1024 (0x62)  131.0MHz
        h: width  1280 start 1368 end 1504 total 1728 skew    0 clock   75.8KHz
        v: height 1024 start 1027 end 1034 total 1069           clock   70.9Hz
  1280x1024 (0x63)  109.0MHz
        h: width  1280 start 1368 end 1496 total 1712 skew    0 clock   63.7KHz
        v: height 1024 start 1027 end 1034 total 1063           clock   59.9Hz
[other resolutions]

The non-verbose output is:

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1280
VGA disconnected (normal left inverted right)
TMDS-1 connected 1280x1024+0+0 (normal left inverted right) 338mm x 270mm
   1280x1024      75.0*+   76.0     75.0     70.9     59.9  
[..]

Once I convinced it to switch to the other 75.0 Hz mode, which worked.
(Went via the 76Hz mode I think.) I can't reproduce that now.

> For now, you can add the working mode to your config file and it will be
> used in preference to either EDID or built-in VESA modes. Give it a
> unique name to ensure the server matches that.
> 
> And, yes, the 'modes' list in the config will likely be ignored; use 
> 
>   Option "PreferredMode" "MyWorkingMode"
> 
> in the appropriate Monitor section to control the starting mode.

Thanks, that works.

Apparently neither of the 75Hz modes works :-| 76Hz does.

thanks,
Hamish
-- 
Hamish Moffatt VK3SB <hamish at debian.org> <hamish at cloud.net.au>