Bug 753519 - Firstboot broken with Nvidia Quadro FX 380 (nouveau driver) on Fedora 16 x86_64
Summary: Firstboot broken with Nvidia Quadro FX 380 (nouveau driver) on Fedora 16 x86_64
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: 16
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Martin Sivák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-13 03:27 UTC by alexp
Modified: 2013-02-13 19:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 19:14:03 UTC
Type: ---


Attachments (Terms of Use)
lspci (4.62 KB, text/plain)
2011-11-13 03:27 UTC, alexp
no flags Details
/var/log/messages (82.95 KB, text/plain)
2011-11-13 03:27 UTC, alexp
no flags Details
/var/log/Xorg.9.log (44.58 KB, text/plain)
2011-11-13 03:50 UTC, alexp
no flags Details

Description alexp 2011-11-13 03:27:28 UTC
Created attachment 533324 [details]
lspci

Description of problem:
The livecd worked good. I was using gnome-shell. The install went smooth. After a reboot, Plymouth bootloader came up with the Fedora logo just fine. After that I just saw a blank screen and could move the mouse pointer. I don't think firstboot was working.

Version-Release number of selected component (if applicable):
Fedora 16 x86_64

GFX Hardware:
0f:00.0 VGA compatible controller: nVidia Corporation G96 [Quadro FX 380] (rev a1)

The following output in /var/log/messages looked suspicious:
Nov 13 00:03:07 fedora firstboot[1245]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xc00031 (firstboot)
Nov 13 00:03:07 fedora firstboot[1245]: Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

Comment 1 alexp 2011-11-13 03:27:56 UTC
Created attachment 533325 [details]
/var/log/messages

Comment 2 alexp 2011-11-13 03:50:08 UTC
Created attachment 533326 [details]
/var/log/Xorg.9.log

Comment 3 Sammy 2011-11-13 14:48:08 UTC
Do you have an initramfs file in /boot? In my case this was missing 
and let to panic during the boot.

Comment 4 alexp 2011-11-13 15:40:57 UTC
@Sammy

Yes, there is initramfs-3.1.0-7.fc16.x86_64.img under /boot.

In fact, the system can start up just fine. I can log in as root on a VT.

The problem is that the /usr/sbin/firstboot just shows a blank screen with a mouse pointer.

Comment 5 alexp 2011-12-08 20:01:07 UTC
I now believe that firstboot does not support my graphics card using the nouveau driver.

I know that nouveau works because the LiveCD comes up with gnome-shell just fine without falling back to classic mode. It is usable and I can install Fedora using it.

Another reason I know that nouveau works just fine is that when firstboot comes up and the screen goes blank, pressing CTRL+BACKSPACE kills firstboot and actually brings up gdm. The gdm works without any problems and looks fine.

After some work, I have developed a workaround.

1) I first boot up with "rdblacklist=nouveau nomodeset" in the grub configuration. This allows firstboot to appear. I can then set proceed with post-installation Fedora configuration.

2) After firstboot is complete, I remove the added terms from the grub configuration, allowing the nouveau driver to work as normal.

Comment 6 Fedora End Of Life 2013-01-16 15:58:34 UTC
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

Comment 7 Fedora End Of Life 2013-02-13 19:14:07 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.