Hide Forgot
Description of problem: After initial installation, laptop gets stuck at "Starting firstboot configuration program (graphical mode)". Console on other virtual terminals is available but installation remains incomplete. Version-Release number of selected component (if applicable): xorg-x11-drv-vesa-2.3.0-7.fc15.i686 How reproducible: Everytime Steps to Reproduce: 1. Install from media-verified DVD 2. Perform Initial reboot 3. Sticks at console message "Starting firstboot configuration program (graphical mode)" Actual results: Sticks at console message "Starting firstboot configuration program (graphical mode)". Expected results: Completion of FirstBoot process. Additional info: Additional x11 log indicates "Screen(s) found, but none have a usable configuration."
Created attachment 504002 [details] log files
Created attachment 504061 [details] glxinfo.txt from the archive
Created attachment 504062 [details] smolt.txt from the archive
Created attachment 504063 [details] Xorg.0.log from the archive
Created attachment 504064 [details] Xorg.1.log from the archive
Created attachment 504065 [details] Xorg.2.log from the archive
Created attachment 504066 [details] Xorg.3.log from the archive
Created attachment 504067 [details] Xorg.4.log from the archive
Created attachment 504068 [details] Xorg.5.log from the archive
Created attachment 504070 [details] Xorg.9.log from the archive
Oh, I see now. You got hit by GMA500 [aka Poulsbo] chip. Unfortunately, there is no good FLOSS support for this chip available. There are attempts to make it working on Fedora somehow (probably the best source is http://www.happyassassin.net/index.php?s=Poulsbo, but he seems to gave up on the project lately; you may Google for the continuation of the story, if there is any). Passing this bug to developers.
(In reply to comment #11) > Oh, I see now. You got hit by GMA500 [aka Poulsbo] chip. Unfortunately, there > is no good FLOSS support for this chip available. I am having the same problem with fresh-install of F15 (do you need additional logs?). F14 did work, running the poulsbo chip in a slow, standard, vga-style configuration, but it did at least work. I was then able to use the URL in comment 11 to get a better functioning display (and it still does, as I am dual-booting). I note that a kernel module in F15 is named poulsbo: $ lsmod | egrep poulsbo poulsbo 952 0 video 10793 1 poulsbo so it seems that F15 is trying to support poulsbo in some fashion.
F17 has a gma500 driver.
... and F15 is EOL.