Created attachment 406757 [details] Xorg log from F13-beta Description of problem: I have an Intel 965GM (Thinkpad X300) and the Multi-head-Test fails when my 19"-TFT (VGA) is connected. When it's connected during boot, both the screens get wrong resolutions (1024x768). Normally they have 1440x900 both. This is the output of 'xrandr' after a normal boot: [liveuser@localhost ~]$ xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 LVDS1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 287mm x 180mm 1440x900 60.0 + 50.0 1024x768 60.0* 800x600 60.3 56.2 640x480 59.9 VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x600 60.3 56.2 848x480 60.0 640x480 59.9 VGA1 doesn't even have 1440x900 listed. I can add the available 1440x900-mode to VGA1, that's ok. But when I activate it, it's not 1440x900 but 1186 x 851 or something, though xrandr reports 1440x900. So I have to add a new 1440x900-mode with a different name (fsc): xrandr --newmode fsc 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync xrandr --addmode VGA1 fsc xrandr --output LVDS1 --mode 1440x900 xrandr --output VGA1 --mode fsc --right-of LVDS1 I think the source may be an EDID (?) problem with the vga-tft and based on that information the driver somehow sets on _both_ displays wrong resolutions. the windows driver gets it right though Version-Release number of selected component (if applicable): F12, F13-beta How reproducible: always Steps to Reproduce: 1. boot with external VGA-Monitor attached 2. 3. Actual results: both screens have 1024x768 resolutions and show the same image (clone-mode) Expected results: both screens have 1440x900 resolutions and the external screen shows an extended desktop. Additional info: xorg log attached from F13-beta. in dmesg i see lots of this: [drm:drm_edid_is_valid] *ERROR* Raw EDID: <3>00 a0 00 a0 00 ff ff 00 1a b3 94 05 01 01 01 01 ................ <3>28 0f 00 a8 00 b4 00 2d 00 12 1f 04 b3 4b 9c 25 (......-.....K.% <3>12 50 54 bf ef 80 71 4f 81 c0 81 cf 81 80 95 00 .PT...qO........ <3>01 01 01 01 01 01 9a 29 a0 d0 51 84 2a 30 50 98 .......)..Q.*0P. <3>36 00 9a 00 11 00 00 1c 00 00 00 ff 00 59 45 47 6............YEG <3>55 30 32 35 30 35 34 0a 20 20 00 00 00 fd 00 38 U025054. .....8 <3>4b 1f 53 0e 00 0a 20 20 20 20 20 20 00 00 00 fc K.S... .... <3>00 57 31 39 2d 31 0a 20 20 20 20 20 20 20 00 a4 .W19-1. .. i915 0000:00:02.0: VGA-1: EDID invalid. the tft is called Fujitsu-Siemens (FSC) W19-1. It's a 19" widescreen tft with VGA and DVI connectors.
Monitor is broken, although, not _that_ broken. We should probably make the edid fixup threshold a kcmdline parameter.
A new version of the Intel driver, xorg-x11-drv-intel-2.11.0-1.fc13, has just been added: https://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.11.0-1.fc13 . Can you please test with this version and see if the bug is reproducible? If you have an installed Fedora 13, you can download and install the driver from the Koji link. If you are testing with live images, the nightly live images from 2010-04-17 (or possibly 2010-04-18) onwards should include this version: http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ . This comment is being added to all open Fedora 13 intel bugs, please ignore if it does not make sense in the context of your bug.
Hey Adam, is it now possible to specify the edid fixup per kcmdline parameter?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Still happens with F15. Did I miss the kcmdline parameter?
Bah, should have gotten back to this sooner. Patch posted upstream: http://lists.x.org/archives/dri-devel/2012-May/023631.html
I tried booting 3.4.2-1 (which has the fix backported) with edid_fixup=[2,4] but it didn't help.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.