Robert P. J. Day wrote, On 11/16/2008 10:26 PM:
The reason X failed is probably in /var/log/Xorg.0.log - can you get it somehow? Perhaps by booting a livecd?thought of that, but don't have a live CD at the moment. perhaps i can restart, wait until the instant of the X server failure, then switch to a virtual console and see if that's informative.And, have you tried booting with "nomodeset"? Does that work?will try that shortly, thanks. can i assume, then, that others have seen this symptom?
F10 kernels defaults to use "modeset" which is nice, but unfortunately it is still work in progress. Disabling it sometimes/often helps.
http://docs.fedoraproject.org/release-notes/f10preview/en_US/What_is_New_for_Installation_and_Live_Images.html#sn-Fedora_10_boot-time
why, yes ... yes, it does. and i'm not too proud to ask ... what exactly did that accomplish? (i verified a graphical install only to the extent of getting that first screen -- i'm assuming things will continue to work as i progress through the rest of the install.)
That gives you a possible workaround. You can add it to /etc/grub.conf.It will also help Fedora developers when you file it in bugzilla, together with /var/log/Xorg.0.log and /var/log/dmesg - both from a failing session without nomodeset. Or even better: perhaps you can find an existing similar bug in bugzilla.
/Mads
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
