Description of problem: Intel video w/ iiyama vision master 450 monitor selects a video mode (1600x1200x96hz) that the monitor cannot handle. It does take 1280x1024x75hz nicely. "xrandr -display :0 --output VGA1 --mode 1280x1024 --rate 75" makes a visible display, but it does not live across a logout. (II) intel(0): Integrated Graphics Chipset: Intel(R) G33 (--) intel(0): Chipset: "G33" (II) intel(0): Output VGA1 has no monitor section (II) intel(0): EDID for output VGA1 (II) intel(0): Manufacturer: IVM Model: 1900 Serial#: 0 xrandr -display :0 -q Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096 VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 54mm x 3688mm 1600x1200 96.3 1280x1024 75.0* 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 Is there a workaround to forcibly disable that 1600x1200x96hz mode? Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.9.1-1.fc12.i686 F12 with latest updates, no xorg.conf file. How reproducible: always Steps to Reproduce: 1. boot with iiyama monitor attached to VGA output. 2. 3. Actual results: nothing visible - monitor thinks there is no signal. Expected results: visible display Additional info:
Can you attach the output of 'xrandr --props' from this monitor? I'd like to get the EDID block so I can see what resolutions it's advertising.
xrandr -display :0 --properties Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096 VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 54mm x 3688mm EDID: 00ffffffffffff0026cd001900000000 0a0801010f241b8be80e64a057489926 10484c3ffffca9540101010101010101 0101010101019065403062b0324040c0 130036680e11001f000000fe00000000 00000000000000000000000000fe0000 000000000000000000000000000000fe 000000000000000000000000000000fa 1600x1200 96.3 1280x1024 75.0* 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0
Well, that's special. It really is advertising a 96Hz 1600x1200 mode, although, kind of a weird one: Detailed mode: Clock 260.000 MHz, 54 mm x 3688 mm 1600 1664 1856 2160 hborder 17 1200 1201 1204 1250 vborder 0 +hsync +vsync That physical size is clearly wrong, and we don't actually handle borders in any sensible way, so we should probably ignore it. For that matter I'm not really convinced intel hardware can actually do 260MHz on VGA and look remotely acceptable. It's also advertising a 1600x1200 80Hz mode, but the kernel isn't finding it for some reason. Hmm.
xorg-x11-drv-intel-2.11.0-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.11.0-2.fc13
xorg-x11-drv-intel-2.11.0-2.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-intel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.11.0-2.fc13
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.