Created attachment 443204 [details] dmesg after getting blank screen. Call trace starting at line 763. Description of problem: X server fails to start. I see the light bulb change to a the letter f, then the screen goes blank instead of giving the login screen. By using CTRL-F2, I can get a terminal session that allowed me to to obtain dmesg and Xorg.log.0 files to document the problem. Version-Release number of selected component (if applicable): Next reboot after downloading updates of Sep 5, 2010. How reproducible: Always. Steps to Reproduce: 1. Normal startup Actual results: Blank screen Expected results: Login screen Additional info: I got around the problem by adding the nodeset parameter suggested in bug 496504. Fortunately, I'm not stuck with the 3-second wait. Perhaps this is a duplicate of bug 557296. dmesg file shows a call trace. See first attachment.
Created attachment 443205 [details] Xorg.0.log with blank screen
Created attachment 443206 [details] dmesg after appending "nomodeset" to kernel line in /boot/grub/grub.conf
Created attachment 443207 [details] Xorg.0.log with nomodeset in startup
The extra parameter mentioned in comment 1 should be "nomodeset". Sorry about the typo.
Looks like a nouveau bug: idr_remove called for id=0 which is not allocated. Pid: 135, comm: plymouthd Not tainted 2.6.34.6-47.fc13.i686.PAE #1 Call Trace: [<c07a0651>] ? printk+0x14/0x1b [<c05ad7bb>] idr_remove+0xe1/0x146 [<f7eb1f2b>] drm_mode_object_put+0x29/0x35 [drm] [<f7eb20b1>] drm_mode_destroy+0x13/0x1d [drm] [<f7f93e13>] nouveau_connector_get_modes+0x33/0x28b [nouveau] [<c060f7ed>] ? acpi_lid_open+0x27/0x41 [<f7f9499a>] ? nouveau_connector_detect_lvds+0x16c/0x176 [nouveau] [<f7ee469c>] drm_helper_probe_single_connector_modes+0xe6/0x23e [drm_kms_helper] [<f7eb3aa4>] drm_mode_getconnector+0xd2/0x2b9 [drm] [<c04c64a7>] ? blk_queue_bounce+0x23a/0x241 [<f7eaabd4>] drm_ioctl+0x26d/0x359 [drm] [<f7eb39d2>] ? drm_mode_getconnector+0x0/0x2b9 [drm] [<c04c64a7>] ? blk_queue_bounce+0x23a/0x241 [<c05b482e>] ? copy_to_user+0x34/0x10a [<c062c335>] ? vt_ioctl+0x0/0x1697 [<c057f3f4>] ? file_has_perm+0x8c/0xa6 [<c04c64a7>] ? blk_queue_bounce+0x23a/0x241 [<c04e4b2d>] vfs_ioctl+0x2c/0x96 [<f7eaa967>] ? drm_ioctl+0x0/0x359 [drm] [<c04e50c3>] do_vfs_ioctl+0x488/0x4c6 [<c04c64a7>] ? blk_queue_bounce+0x23a/0x241 [<c057f698>] ? selinux_file_ioctl+0x43/0x46 [<c04c64a7>] ? blk_queue_bounce+0x23a/0x241 [<c04e5147>] sys_ioctl+0x46/0x66 [<c04c64a7>] ? blk_queue_bounce+0x23a/0x241 [<c07a2614>] syscall_call+0x7/0xb [<c04c64a7>] ? blk_queue_bounce+0x23a/0x241 [<c04c64a7>] ? blk_queue_bounce+0x23a/0x241
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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
Bug not seen since upgrading to version 14. Closing.