William Dutcher wrote:
Hi Graeme. Thanks for looking at this. The verbose/debug output of dispwin and xrandr follows. - William
Failed to get EDID for display
That's a bit of a hint. Normally the EDID should be a property of each output.
% xrandr --verbose Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1280 DFP2 connected 1280x1024+0+0 (0x8d) normal (normal left inverted right x axis y axis) 376mm x 301mm Identifier: 0x89 Timestamp: 891369 Subpixel: unknownClones: CRTC: 0CRTCs: 0 1 Panning: 0x0+0+0 Tracking: 0x0+0+0 Border: 0/0/0/0 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
And there are no other properties listed here, which is a bit suspicious. It's hard to know from this though whether it's a bug or limitation in the X server/display driver, a change in the XRANDR protocol that trips up dispwin, or what. What does xrandr --version report ? What graphics card is it, and what card driver and version of the X server is it ? cheers, Graeme Gill.