Created attachment 504007 [details] dmesg output Description of problem: I am having some problems with the nouveau driver and my nvidia card. Nvidia card : lspci | grep VGA 40:00.0 VGA compatible controller: nVidia Corporation NV41GL [Quadro FX 1400] (rev a2) kernel: 2.6.38.7-30.fc15.x86_64 nouveau version xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15 I am having two issues. 1. When I boot I am not getting a nice Plymouth boot splash, it looks the same as when I boot the nvidia kmod (balck screen with a progress bar at the bottom). 2. I am getting seeming random lockups. I do not get these lockups when I use the nvidia kmod. When the system locks up it does not respond to keyboard or mouse input, although I can see and move the mouse cursor. I am attaching dmesg and my xorg log. Version-Release number of selected component (if applicable): How reproducible: It is an intermittent lockup. Steps to Reproduce: 1. Use the nouveau driver . 2. 3. Actual results: No Plymouth boot splash Intermittent lockups. Expected results: Plymouth boot splach no lockups. Additional info: Thank you in advance for looking into this.
Created attachment 504008 [details] Xorg.0.log
(In reply to comment #0) > Created attachment 504007 [details] > dmesg output > > Description of problem: > Firstly, thanks for creating this separate bug! It's much easier to track individual bugs than a heap of different ones in one report. > I am having some problems with the nouveau driver and my nvidia card. > > Nvidia card : > lspci | grep VGA > 40:00.0 VGA compatible controller: nVidia Corporation NV41GL [Quadro FX 1400] > (rev a2) > > kernel: 2.6.38.7-30.fc15.x86_64 > > nouveau version xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15 > > I am having two issues. > > 1. When I boot I am not getting a nice Plymouth boot splash, it looks the same > as when I boot the nvidia kmod (balck screen with a progress bar at the > bottom). Okay, nouveau is definitely being used as far as I can see from your kernel log. My guess is something's become messed up in your initrd etc after using the binary driver, causing nouveau to not get loaded until it's too late for plymouth to kick in. My initial suggestion here is to "yum reinstall kernel". > > 2. I am getting seeming random lockups. I do not get these lockups when I use > the nvidia kmod. > > When the system locks up it does not respond to keyboard or mouse input, > although I can see and move the mouse cursor. Do you have another machine you can ssh into the locked machine from? If so, dmesg and X log from while the system is hung would be very useful. Ben.
Alright, I will reinstall the kernel and shall try to ssh in if it locks up. I forgot to mention in the initial report, this is a regression, nouveau works on this card with Fedora 14.
reinstalling the kernel indeed resolved the Plymouth problem, so one down. It still locks, I have attached the requested information. Again, thank you for your time.
Created attachment 504109 [details] lockup dmesg
Created attachment 504111 [details] lockup Xorg.0.log
This problem persists with the new kernel 2.6.38.8-32.fc15.x86_64 The most reliable method to produce a lock up is to open activities by moving the mouse to the upper left hand corner. The click "Applications" The icons appear, but the system locks up. The mouse continues to move , but the system does not respond to mouse clicks or keyboard input. Thank you in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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