Created attachment 430162 [details] dmesg output Description of problem: Upgrade from F11 to F12 will not display with nouveau driver. Have to force use of nv driver. I am seeing the following in the dmesg log: [drm] nouveau 0000:01:05.0: Detected an NV 0 generation card (0x20154000) [drm] nouveau 0000:01:05.0: Attempting to load BIOS image from PROM [drm] nouveau 0000:01:05.0: ... appears to be valid : [drm] nouveau 0000:01:05.0: 64 MiB GART (aperture) [drm] nouveau 0000:01:05.0: Allocating FIFO number 0 [TTM] AGP Bind memory failed. [TTM] Couldn't bind backend. [drm] nouveau 0000:01:05.0: error allocating DMA push buffer: -22 [drm] nouveau 0000:01:05.0: pushbuf -12 [drm] nouveau 0000:01:05.0: nouveau_channel_free: freeing fifo 0 [TTM] Zone kernel: Used memory at exit: 0 kiB. nouveau 0000:01:05.0: PCI INT A disabled nouveau: probe of 0000:01:05.0 failed with error -12 Seeing this in the Xorg.log: (EE) [drm] drmOpen failed. (EE) NOUVEAU(0): [drm] error opening the drm (EE) NOUVEAU(0): 879: (II) UnloadModule: "nouveau" (II) UnloadModule: "dri" (II) UnloadModule: "int10" (II) Unloading /usr/lib/xorg/modules/libint10.so (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Will attach full logs Version-Release number of selected component (if applicable): AGP is nVidia NV5 RIVA TNT2/TNT2 Pro rev 21 uname -a: Linux walden4 2.6.32.14-127.fc12.i686 #1 SMP Fri May 28 05:04:10 UTC 2010 i686 athlon i386 GNU/Linux Older AMD processor athlon 800MHz How reproducible: Happens everytime I boot Steps to Reproduce: 1. Boot the system Actual results: System boots but no rhgb display or Xorg graphical login screen. I can ssh from another system and examine log files. Expected results: rhgb is visible, Xorg login screen appears. Additional info:
Created attachment 430163 [details] Xorg.0.log
Adding lspci -vv output for AGP 01:05.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 15) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. AGP-V3800 SDRAM Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 11 Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at fc000000 (32-bit, prefetchable) [size=32M] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel modules: nouveau, nvidiafb, rivafb
Created attachment 430913 [details] lspci -vv output
Created attachment 430914 [details] lsmod output Note this output is while the system is using the nv driver.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.