Created attachment 882951 [details] Xorg log file Description of problem: Machine is a Gigabyte Brix GB-BXi7H-4500 (rev. 1.0), i.e. "Intel HD 4400" graphics. Monitor is a Dell U3014. They are connected by DisplayPort. I'm trying to use the native/max resolution 2560x1600. When I start X, the display appears for a second or three, then blinks out, and within a few seconds the monitor says it's going into power-save mode. Switching to a console VT everything comes back fine. The console seems to be using 2560x1600 mode and it never blinks or anything. A VT switch back to X sees the same behavior: displays fine for a second, and then blinks and goes to power-save. I forced the resolution down to 1920x1200 (using the Displays control panel thingy) and in that mode X is solid. The same monitor supports 2560x1600 fine via Displayport on two other machines (one of which is non-Fedora Linux on an older Intel integrated graphics "HD Graphics 4000", and the other is ChromeOS). Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.14.4-7.fc20.x86_64 xorg-x11-drv-intel-2.21.15-5.fc20.x86_64 kernel-3.13.8-200.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start X (log in via gdm, or log in on console and "startx"). 2. Look at screen for several seconds. 3. Actual results: Screen comes up right, then blinks and monitor goes into power-save. Expected results: Screen displays continually at this resolution. Additional info: I've attached the Xorg log file. This is from a run in which I plugged and unplugged the monitor many times, did many VT switches, changed resolution, etc.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.