Bug 440996 - X failed to start on laptop Panasonic Toughbook CF-52
Summary: X failed to start on laptop Panasonic Toughbook CF-52
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 8
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-04 21:07 UTC by Alain Portal
Modified: 2008-05-07 07:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-07 07:33:15 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
xorg.conf (806 bytes, text/plain)
2008-04-04 21:07 UTC, Alain Portal 		no flags Details
Xorg.0.log (1.60 KB, text/plain)
2008-04-04 21:09 UTC, Alain Portal 		no flags Details
messages (86.11 KB, text/plain)
2008-04-04 21:11 UTC, Alain Portal 		no flags Details
View All

Description Alain Portal 2008-04-04 21:07:09 UTC 
Description of problem:

When X seems to start, there is nothing on the screen. Screen seems off.
Ctrl+F? and Ctrl-Alt+Back are unavailable. To restart, the is no other way 
than unplugged the laptop.

Version-Release number of selected component (if applicable):

6.8.0-1.fc8

How reproducible:

Always

Steps to Reproduce:
1. Buy a Panasonic Toughbook CF-52AJCBUB9
2. Install F8 or last F8 Respin in text mode (graphical install fails)
3. Start X
  
Actual results:

Screen freezed

Expected results:

A graphical session

Additional info:

Should this bug been duplicated of 
https://bugzilla.redhat.com/show_bug.cgi?id=440468 ?
Comment 1 Alain Portal 2008-04-04 21:07:09 UTC 
Created attachment 301343 [details]
xorg.conf
Comment 2 Alain Portal 2008-04-04 21:09:44 UTC 
Created attachment 301345 [details]
Xorg.0.log

After unplugging and restarting the laptop
Comment 3 Alain Portal 2008-04-04 21:11:26 UTC 
Created attachment 301346 [details]
messages

After unplugging and restarting the laptop
Comment 4 Alain Portal 2008-04-06 17:31:09 UTC 
As the xorg.conf file shows it, this bug isn't ati driver specific as there is 
the same result with the "vesa" driver.
Note You need to log in before you can comment on or make changes to this bug.