Hide Forgot
We have a system using an NVidia Geforce GTX 570 card. Entering rescue mode or the install, anaconda appears to have crashed part way through the booting, showing systemd messages. However, Anaconda was actually running, but was not updating the screen - this was a tricky issue as we were using kickstart to do an automated install. The problem appears to be a nouveau bug. We worked around the problem by adding "nouveau.modeset=0 rdblacklist= nouveau" to the kernel boot configuration for the installation. Here is the affected hardware: 01:00.0 VGA compatible controller: nVidia Corporation GF110 [Geforce GTX 570] (rev a1) (prog-if 00 [VGA controller]) Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f9000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=128M] Memory at ee000000 (64-bit, prefetchable) [size=32M] I/O ports at cf00 [size=128] [virtual] Expansion ROM at e8000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nvidia Kernel modules: nvidia, nouveau, nvidiafb
Can you post the dmesg output from an attempt of using nouveau?
Created attachment 535867 [details] dmesg from anaconda startup with nouveau enabled Here's the dmesg from anaconda using nouveau. The system has two DVI-attached flat panels.
Hmm, yes, the display engine is quite unhappy apparently. Can I get the same again with "drm.debug=14 nouveau.reg_debug=0x600 log_buf_len=1M" appended to your kernel options? Thank you!
Created attachment 536377 [details] dmesg after adding drm.debug=14 nouveau.reg_debug=0x600 log_buf_len=1M
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.