Created attachment 1043712 [details] journalctl --boot=-1 Description of problem: Primary monitor shows "Input signal unusable" after booting to kernel-4.0.5-200.fc21.x86_64. Version-Release number of selected component (if applicable): kernel-4.0.5-200.fc21.x86_64 How reproducible: 100% Steps to Reproduce: 1. Select kernel-4.0.5-200.fc21.x86_64 in GRUB 2. Wait for system to boot Actual results: My Primary monitor shows "Input signal unusable". Expected results: My monitor would show the login screen, like it always has, all the way up through and including 4.0.4-202.fc21.x86_64. Additional info: Video Card: Radeon HD 7850 @ 1920x1080
Created attachment 1043713 [details] lshw output (from working 4.0.4-202 kernel)
Updated to Fedora 22 and 4.0.7-300.fc22.x86_64, and the problem is still present. I have to boot into the 4.0.4-202 kernel to see anything on my primary monitor. Is there any particular troubleshooting I can do to help find the root cause of this problem?
With an xterm open on my secondary monitor, I confirmed that my primary monitor is connected, detected, and the card is supposedly outputting its preferred mode, 1920x1080: $ xrandr Screen 0: minimum 320 x 200, current 3360 x 1080, maximum 16384 x 16384 DisplayPort-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+1440+0 (normal left inverted right x axis y axis) 510mm x 287mm 1920x1080 60.00*+ 50.00 59.94 1920x1080i 60.00 50.00 59.94 1280x1024 75.02 60.02 1280x960 60.00 ... DVI-0 disconnected (normal left inverted right x axis y axis) DVI-1 connected 1440x900+0+48 (normal left inverted right x axis y axis) 410mm x 257mm 1280x1024 75.02 60.02 1440x900 74.98* 60.07 1280x960 60.00 ... I was able to successfully change to resolutions lower than 1920x1080 and see output. But both the 1080 and 1080i resolutions caused "Input Not Supported" to show up on the primary monitor. Of course, everything works as expected when booting the 4.0.4-202.fc21 kernel. I also compared the journalctl output to that of the working 4.0.4-202.fc21 kernel, and saw no relevant differences. Interestingly, on 4.0.7-300.fc22.x86_64, I'm able to see the login screen, and log in. It's not until after I log in (and the monitors flash, indicating a mode switch or something) that the "Input Not Supported" returns. I'm fairly confident (but can't confirm) that when I first reported this bug, I wasn't even able to get to the login screen. Also, if I select "GNOME on Wayland" at the login screen, the output seems to work successfully. I'm having a hard time narrowing this down.
This bug is still present on kernel-4.1.3-200.fc22.x86_64.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.