Bug 712249

Summary: [Poulsbo] Laptop doesn't start graphics at all
Product: [Fedora] Fedora Reporter: Julian Tosh <redhat.com>
Component: xorg-x11-drv-vesaAssignee: Adam Jackson <ajax>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: ajax, mcepl, phil.pishioneri, xgl-maint
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: [cat:others]
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-29 17:59:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
log files
none
glxinfo.txt from the archive
none
smolt.txt from the archive
none
Xorg.0.log from the archive
none
Xorg.1.log from the archive
none
Xorg.2.log from the archive
none
Xorg.3.log from the archive
none
Xorg.4.log from the archive
none
Xorg.5.log from the archive
none
Xorg.9.log from the archive none

Description Julian Tosh 2011-06-09 22:43:25 UTC
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."

Comment 1 Julian Tosh 2011-06-09 22:44:04 UTC
Created attachment 504002 [details]
log files

Comment 2 Matěj Cepl 2011-06-10 09:58:06 UTC
Created attachment 504061 [details]
glxinfo.txt from the archive

Comment 3 Matěj Cepl 2011-06-10 09:58:15 UTC
Created attachment 504062 [details]
smolt.txt from the archive

Comment 4 Matěj Cepl 2011-06-10 09:58:23 UTC
Created attachment 504063 [details]
Xorg.0.log from the archive

Comment 5 Matěj Cepl 2011-06-10 09:58:30 UTC
Created attachment 504064 [details]
Xorg.1.log from the archive

Comment 6 Matěj Cepl 2011-06-10 09:58:38 UTC
Created attachment 504065 [details]
Xorg.2.log from the archive

Comment 7 Matěj Cepl 2011-06-10 09:58:45 UTC
Created attachment 504066 [details]
Xorg.3.log from the archive

Comment 8 Matěj Cepl 2011-06-10 09:58:54 UTC
Created attachment 504067 [details]
Xorg.4.log from the archive

Comment 9 Matěj Cepl 2011-06-10 09:59:04 UTC
Created attachment 504068 [details]
Xorg.5.log from the archive

Comment 10 Matěj Cepl 2011-06-10 09:59:12 UTC
Created attachment 504070 [details]
Xorg.9.log from the archive

Comment 11 Matěj Cepl 2011-06-10 10:43:16 UTC
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.

Comment 12 Phil Pishioneri 2011-06-13 18:38:23 UTC
(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.

Comment 13 Phil Pishioneri 2012-06-26 00:32:31 UTC
F17 has a gma500 driver.

Comment 14 Adam Jackson 2012-08-29 17:59:31 UTC
... and F15 is EOL.