Bug 492527 - Openchrome -wrong screen size at install
Summary: Openchrome -wrong screen size at install
Keywords:
Status: CLOSED DUPLICATE of bug 450845
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-openchrome
Version: rawhide
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Xavier Bachelot
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-27 09:13 UTC by Martin Thain
Modified: 2009-03-27 12:09 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-03-27 12:09:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Log file (79.60 KB, text/plain)
2009-03-27 09:15 UTC, Martin Thain
no flags Details
Hardware information from lspci (2.01 KB, text/plain)
2009-03-27 09:16 UTC, Martin Thain
no flags Details

Description Martin Thain 2009-03-27 09:13:59 UTC
Description of problem:

I installed Fedora 11 Rawhide from a live CD on a laptop with chrome built in graphics. 
The screen was far too large and I could only see the top left two thirds.

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

xorg-x11-drv-openchrome-0.2.903-9.fc11.i586

How reproducible:

Very!

Steps to Reproduce:
1. Boot lap top from Fedora 11 CD
2. Screen Display size is wrong
3. Login by selecting default user.
  
Actual results:
Gnome starts and screen size is set to 1600x1200

Expected results:
Should be 1024x768 for my laptop (or if a default has to be chosen 640x480 would be sensible)

Additional info:
From GNOME I luckily can set the screen size from System -> Prference -> Display to correct it to 1024x768

Comment 1 Martin Thain 2009-03-27 09:15:05 UTC
Created attachment 336980 [details]
Log file

Comment 2 Martin Thain 2009-03-27 09:16:26 UTC
Created attachment 336981 [details]
Hardware information from lspci

Comment 3 Xavier Bachelot 2009-03-27 12:09:34 UTC
Sorry, not much can be done about that until upstream implement native panel modesetting for your chipset.

*** This bug has been marked as a duplicate of bug 450845 ***


Note You need to log in before you can comment on or make changes to this bug.