Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Created attachment 450920 [details]
Xorg log file

I'm using the Graphics Test Day LiveCD, which doesn't have a /etc/X11/xorg.conf file, but here's the Xorg log.

Created attachment 450921 [details]
/var/log/messages

Created attachment 450923 [details]
Output of dmesg

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I see this bug on two machines with f14; a dell dimension 530 desktop and a dell inspiron mini netbook. The desktop has a gma 3100 and the netbook has a gma 3150 (pineview).

netbook's lspci:
00:00.0 Host bridge: Intel Corporation N10 Family DMI Bridge
00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller
00:02.1 Display controller: Intel Corporation N10 Family Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02)
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
07:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

I'll boot with drm.debug=0x04 and post the results.

(In reply to comment #0)
> Description of problem:
> After the Plymouth progress animation completes the screen goes black and
> several seconds later the mouse cursor shows up over the black background.

Just to be sure, we are on the same page in terms of severity of the bug ... and after that the login manager jumps and everything works well? So, this is just a cosmetic issue about black screen in between plymouth and gdm?

(In reply to comment #7)
> (In reply to comment #0)
> > Description of problem:
> > After the Plymouth progress animation completes the screen goes black and
> > several seconds later the mouse cursor shows up over the black background.
> 
> Just to be sure, we are on the same page in terms of severity of the bug ...
> and after that the login manager jumps and everything works well? So, this is
> just a cosmetic issue about black screen in between plymouth and gdm?

In my case, yes. Everything works fine after the black screen, it just makes the boot process less polished. I'll attach the info requested in comment 1.

Created attachment 474507 [details]
Xorg log

Created attachment 474509 [details]
messages log

Created attachment 474510 [details]
dmesg output

It does manifest as a cosmetic bug in my case as well.  As the filer of the bug though, my concern was that it might be an indication of a larger problem.  Based on my understanding of KMS, one of its primary purposes is to eliminate unnecessary mode changes.  This cutting to a black screen would seem to imply that a mode change is happening anyway.

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. 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 '14' 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 14 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