Created attachment 891918 [details] Xorg log file showing kernel 3.14.2-200.fc20.x86_64 failing nouveau Description of problem: After updating to kernel 3.14.2-200.fc20.x86_64 I was shocked to find my nice 27 inch screen capable of 2560x1440 resolution suddenly only showing XGA 1024x768. Version-Release number of selected component (if applicable): kernel 3.14.2-200.fc20.x86_64 How reproducible: Just sudo yum update to the latest kernel and reboot. Steps to Reproduce: 1. sudo yum update 2. sudo reboot 3. shock Actual results: Nouveau fails due to disabled KMS and falls back to VESA X driver resulting in XGA 1024x768 resolution. Expected results: Nouveau X driver with 2560x1440 resolution like before. Additional info: Attached Xorg log file showing new failing kernel 3.14.2-200.fc20.x86_64 configuration.
Created attachment 891931 [details] Xorg log file showing kernel 3.13.10-200.fc20.x86_64 working nouveau Attached Xorg log file showing previous working kernel 3.13.10-200.fc20.x86_64 configuration.
Digging a little bit through the previous and new dmesg output I found what is failing: [ 1.597775] nouveau [ VBIOS][0000:01:00.0] ... checksum invalid [ 1.597777] nouveau [ VBIOS][0000:01:00.0] checking ACPI for image... [ 1.597779] nouveau [ VBIOS][0000:01:00.0] ... signature not found [ 1.597780] nouveau [ VBIOS][0000:01:00.0] checking PCIROM for image... [ 1.597835] nouveau [ VBIOS][0000:01:00.0] ... appears to be valid [ 1.597836] nouveau [ VBIOS][0000:01:00.0] using image from PCIROM [ 1.597930] nouveau [ VBIOS][0000:01:00.0] BIT signature found [ 1.597932] nouveau [ VBIOS][0000:01:00.0] version 80.07.35.00.0b [ 1.598065] nouveau E[ VBIOS][0000:01:00.0] 0x75f2[ ]: unknown opcode 0xb9 [ 1.598142] nouveau E[ DEVINIT][0000:01:00.0] init failed, -22 [ 1.598209] nouveau E[ DRM] failed to create 0x80000080, -22 [ 1.598571] nouveau: probe of 0000:01:00.0 failed with error -22 Will attach both full dmesg outputs ASAP.
Created attachment 891932 [details] dmesg output of previous working configuration
Created attachment 891933 [details] dmesg output of new failing configuration
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.