When connecting an Acer X234w display to a 82Q35 graphics chip (8086:29b2, subsystem 8086:4f4a, rev 02) using the DVI connector, the native resolution of 1920x1200 works perfectly, but switching to any lower resolution such as 1024x768 results in the screen displaying the error message "Input not supported" (the error message is produced by the screen's firmware, not by any application running on the box). Log files etc. don't display anything unusual, Xorg seems to think everything is working fine even at the lower resolution. With ModeDebug enabled, this is what Xorg says about supported modes and EDID: (II) intel(0): EDID for output VGA1 (II) intel(0): EDID for output DVI1 (II) intel(0): Manufacturer: ACR Model: 0 Serial#: 1955596759 (II) intel(0): Year: 2007 Week: 49 (II) intel(0): EDID Version: 1.3 (II) intel(0): Digital Display Input (II) intel(0): Max Image Size [cm]: horiz.: 52 vert.: 32 (II) intel(0): Gamma: 2.20 (II) intel(0): DPMS capabilities: Off (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 (II) intel(0): First detailed timing is preferred mode (II) intel(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.608 (II) intel(0): blueX: 0.150 blueY: 0.060 whiteX: 0.313 whiteY: 0.329 (II) intel(0): Supported VESA Video Modes: (II) intel(0): 720x400@70Hz (II) intel(0): 640x480@60Hz (II) intel(0): 640x480@75Hz (II) intel(0): 800x600@60Hz (II) intel(0): 800x600@75Hz (II) intel(0): 1024x768@60Hz (II) intel(0): 1024x768@75Hz (II) intel(0): 1280x1024@75Hz (II) intel(0): Manufacturer's mask: 0 (II) intel(0): Supported Future Video Modes: (II) intel(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 (II) intel(0): #1: hsize: 1280 vsize 800 refresh: 60 vid: 129 (II) intel(0): #2: hsize: 1280 vsize 800 refresh: 75 vid: 3969 (II) intel(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149 (II) intel(0): #4: hsize: 1440 vsize 900 refresh: 75 vid: 3989 (II) intel(0): #5: hsize: 1600 vsize 1200 refresh: 60 vid: 16553 (II) intel(0): #6: hsize: 1680 vsize 1050 refresh: 60 vid: 179 (II) intel(0): Supported additional Video Mode: (II) intel(0): clock: 154.0 MHz Image Size: 518 x 324 mm (II) intel(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0 (II) intel(0): v_active: 1200 v_sync: 1203 v_sync_end 1209 v_blanking: 1235 v_border: 0 (II) intel(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 82 kHz, PixClock max 170 MHz (II) intel(0): Monitor name: Acer X243W (II) intel(0): Serial No: LAG040047210 (II) intel(0): EDID (in hex): (II) intel(0): 00ffffffffffff0004720000d7099074 (II) intel(0): 31110103803420782aef95a3544c9b26 (II) intel(0): 0f5054a54b0081808100810f9500950f (II) intel(0): a940b3000101283c80a070b023403020 (II) intel(0): 360006442100001a000000fd00384c1e (II) intel(0): 5211000a202020202020000000fc0041 (II) intel(0): 6365722058323433570a2020000000ff (II) intel(0): 004c41473034303034373231300a0036 (II) intel(0): EDID vendor "ACR", prod id 0 (II) intel(0): Using hsync ranges from config file (II) intel(0): Using vrefresh ranges from config file (II) intel(0): Printing DDC gathered Modelines: (II) intel(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz) (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz) (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz) (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz) (II) intel(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz) (II) intel(0): Modeline "1280x800"x0.0 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz) (II) intel(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz) (II) intel(0): Modeline "1440x900"x0.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz) (II) intel(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz) (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz) (II) intel(0): Printing probed modes for output DVI1 (II) intel(0): Modeline "1920x1200"x60.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz) (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz) (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz) Chances are the display is lying about the specifics of its supported modes and these values are slightly off what the display actually takes; Acer has a history of producing devices with atrocious BIOSes and firmwares. However, 1024x768 and 800x600 (and probably other lower resolutions) work when using the vesa driver as opposed to the intel driver. This happens with all semi-current versions of the intel driver (tried 2.8.0.901, 2.8.0, 2.7.1), but it used to work ages ago (probably around the time 2.4.x was current; and probably because old versions didn't rely as much on EDID as current ones do).
need more detailed description of your environment. such as your kernel version and dmesg. are you using Kernel Modesetting? also would you pls attach a intel_reg_dumper output when the the display resolution doesn't work? thanks.
kernel is 2.6.31-rc6, the problem happens both with kernel modesetting enabled and disabled, dmesg says [drm] TMDS-8: set mode 17 when switching to 1024x768, and [drm] TMDS-8: set mode 1a when switching back to 1920x1200
Created attachment 28889 [details] intel_reg_dumper output while in 1024x768
SDVO multiplier for pipe A is wrong...
What Michael said in comment #4 is right. When the system switches to the 1024x768 resolution, the SDVO multiplier should be 2. Hi, Bernhard Will you please add the modedebug option in xorg.conf and do the following test with the modesetting disabled? (add option "modedebug" "true" under the device section) a. switch to the native resolution b. switch to lower resolution(1024x768) After the test, please attach the Xorg.log. Thanks.
(In reply to comment #2) > kernel is 2.6.31-rc6, the problem happens both with kernel modesetting enabled > and disabled, dmesg says > > [drm] TMDS-8: set mode 17 > > when switching to 1024x768, and > > [drm] TMDS-8: set mode 1a > > when switching back to 1920x1200 > Will you please double check whether it can't work when the kernel modesetting is disabled? Will you please try the patch in https://bugs.freedesktop.org/show_bug.cgi?id=21417#C16 with modesetting enabled and see whether the issue still exists? Thanks.
As the box is based on Q35 platform and we have a fix for this platform, this bug will be marked as the duplicate of bug21417. If the problem still exists after trying the latest Eric's drm-intel-next tree, please reopen it again. thanks. *** This bug has been marked as a duplicate of bug 21417 ***
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.