Created attachment 1019050 [details] dmesg for the failure scenario (using ctrl-alt-F5 for text mode login) Description of problem: After updating kernel from 3.18.9 to 3.19.3, the screen is garbled (looks like sync problem/too high resolution). The "F-logo fills up" display is OK, but when it switches resolution to display the login names, I only get "noise". From dmesg it looks like 3.18 used a "generic" driver, but 3.19 now has a specific driver (see below). Version-Release number of selected component (if applicable): Kernel 3.19.3, 3.19.4 How reproducible: Every time Steps to Reproduce: 1.Select kernel 3.19.3 or 3.19.4 from (text mode) start menu 2.Wait until login screen appears. Additional info: Graphics adapter: NVidia GT720 (lscpi output: 01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 720] (rev a1)) Result of "dmesg|grep nouveau": 3.18.9 (works): [ 2.485167] nouveau ![ DEVICE][0000:01:00.0] unknown Kepler chipset [ 2.485229] nouveau E[ DEVICE][0000:01:00.0] unknown chipset, 0xb06080b1 [ 2.485286] nouveau E[ DRM] failed to create 0x00000080, -22 [ 2.485563] nouveau: probe of 0000:01:00.0 failed with error -22 3.19.3 (fails): [ 2.434426] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0xb06080b1 [ 2.434428] nouveau [ DEVICE][0000:01:00.0] Chipset: GK208B (NV106) [ 2.434430] nouveau [ DEVICE][0000:01:00.0] Family : NVE0 [ 2.544040] nouveau [ VBIOS][0000:01:00.0] using image from PROM [ 2.544279] nouveau [ VBIOS][0000:01:00.0] BIT signature found [ 2.544282] nouveau [ VBIOS][0000:01:00.0] version 80.28.79.00.10 [ 2.544676] nouveau [ PMC][0000:01:00.0] MSI interrupts enabled [ 2.544720] nouveau [ PFB][0000:01:00.0] RAM type: DDR3 [ 2.544721] nouveau [ PFB][0000:01:00.0] RAM size: 2048 MiB [ 2.544723] nouveau [ PFB][0000:01:00.0] ZCOMP: 0 tags [ 2.545740] nouveau [ VOLT][0000:01:00.0] GPU voltage: 912500uv [ 3.206144] nouveau [ PTHERM][0000:01:00.0] FAN control: toggle [ 3.206158] nouveau [ PTHERM][0000:01:00.0] fan management: automatic [ 3.206193] nouveau [ PTHERM][0000:01:00.0] internal sensor: yes [ 3.206233] nouveau [ CLK][0000:01:00.0] 07: core 405 MHz memory 810 MHz [ 3.206335] nouveau [ CLK][0000:01:00.0] 0f: core 405-797 MHz memory 1600 MHz [ 3.206391] nouveau [ CLK][0000:01:00.0] --: core 405 MHz memory 810 MHz [ 3.211822] nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x500c30 [ IBUS ] [ 3.212386] nouveau [ DRM] VRAM: 2048 MiB [ 3.212387] nouveau [ DRM] GART: 1048576 MiB [ 3.212390] nouveau [ DRM] TMDS table version 2.0 [ 3.212392] nouveau [ DRM] DCB version 4.0 [ 3.212393] nouveau [ DRM] DCB outp 00: 01000f02 00020030 [ 3.212395] nouveau [ DRM] DCB outp 01: 02011f62 00020010 [ 3.212396] nouveau [ DRM] DCB outp 02: 02022f10 00000000 [ 3.212398] nouveau [ DRM] DCB conn 00: 00001031 [ 3.212399] nouveau [ DRM] DCB conn 01: 00002161 [ 3.212401] nouveau [ DRM] DCB conn 02: 00000200 [ 3.216365] nouveau [ DRM] MM: using COPY for buffer copies [ 3.330394] nouveau [ DRM] allocated 1680x1050 fb: 0x60000, bo ffff8804197f5000 [ 3.330513] fbcon: nouveaufb (fb0) is primary device [ 3.538545] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device [ 3.538546] nouveau 0000:01:00.0: registered panic notifier [ 3.541755] [drm] Initialized nouveau 1.2.1 20120801 for 0000:01:00.0 on minor 0 [ 13.570642] nouveau E[ PFIFO][0000:01:00.0] unsupported engines 0x00000000
After some investigations, net searches etc., I realized that the problem was missing detection of monitor capabilites (SyncMaster 226BW). I hacked up an xorg.conf file (attached) and got it to work -- sort of: The display looks fine, I even got dual monitor to work (which I had no success with with the old version of the driver), but after a while the system crashes. I will file the crash issue in a new bug.
Created attachment 1029428 [details] xorg.conf that solved the "display unreadable" problem. xorg.conf that works with the Syncmaster 226BW (but causes the system to crash after a while?)
Created bug #1224808 that describes the lockups I get after adding the xorg.conf file and updating.
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.