Created attachment 633051 [details] Smolt profile Description of problem: I have two monitors attached to my single graphics card, one via VGA and one via DVI. This setup works fine with kernel 3.5 (3.5.6-1.fc17.x86_64), but after upgrading to 3.6.x, the DVI-attached screen goes blank as soon as the kernel loads (i.e. GRUB shows on it, but not the bootsplash or X). Booting to 3.5 continues to work as expected. Card is an integrated Intel 4 Series. It has an HDMI port, but not in use and I haven't tested it. Version-Release number of selected component (if applicable): 3.6.x (3.6.1-1.fc17.x86_64 and 3.6.1-1.fc17.x86_64) How reproducible: Every boot Steps to Reproduce: 1. Upgrade to 3.6.x kernel 2. Boot Actual results: Monitor attached to DVI port is blank Expected results: Both monitors displaying correct images Additional info: Will attach logs
Created attachment 633054 [details] dmesg and Xorg logs for both working and broken kernel versions I just realized that the Xorg logs say that the second monitor is connected to to HDMI1, even though it's actually connected to the DVI port. And both monitors are connected exactly the same way when using 3.6, even though it says only one is connected.
Same symptoms in kernel 3.6.3-1.fc17.x86_64.
Are you still seeing this with 3.7.9 or 3.8.2 in updates-testing?
Same issue here, I'm in: Linux localhost.localdomain 3.8.2-206.fc18.x86_64 #1 SMP Fri Mar 8 15:03:34 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.