Created attachment 406243 [details] X server log with drm.debug=15 Description of problem: The graphical boot process stops after the Fedora logo is filled. Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-0.0.16-2.20100218git2964702.fc13.x86_64 How reproducible: two times out of two Steps to Reproduce: http://fedoraproject.org/wiki/QA:Testcase_nouveau_basic Actual results: The Fedora logo gets filled from lower left to upper right, a halo appears and fades, and then nothing more happens on the screen. I can access the system by SSH though. Only the graphics is broken. Expected results: a login screen Additional info: It has worked before. This problem started after I installed a huge bunch of updates in preparation for the Nouveau test day. Smolt profile: http://www.smolts.org/client/show/pub_88cd7ab2-c7c0-46b9-9a91-e7687128a21c There are files in /etc/xorg.conf.d but no xorg.conf.
Created attachment 406245 [details] /var/log/messages with drm.debug=15
Created attachment 406246 [details] /var/log/dmesg with drm.debug=15
Created attachment 406248 [details] /var/log/Xorg.0.log with nomodeset With nomodeset I get a login screen but with a lower resolution than it should be.
If I don't add "nomodeset" but instead remove "rhgb", then the system boots OK with the correct resolution.
I'm wondering if you're seeing an issue I seen after some recent updates. If you boot with unmodified default boot options, except for an appended "3", and the login at the graphical console and run "init 5", do things work as expected?
Assuming s/graphical/text/, that works except that keypresses aren't echoed on tty1 so I have to type the username blindly and "Password:" is printed to the right of "login:" instead of below. After I've logged in keypresses are echoed as usual. On tty2 I don't see this quirk. Anyway, yes, "init 5" works as expected.
Ok. Can you check https://bugzilla.redhat.com/show_bug.cgi?id=577789, I'd say it's likely the same issue.
gdm-2.29.92-6.fc13 fixed this. I filed bug 583025 about the problem with "nomodeset". *** This bug has been marked as a duplicate of bug 577789 ***