Bug 121548 - No 1280 x 800 resolution available during setup
Summary: No 1280 x 800 resolution available during setup
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: hwdata (Show other bugs)
(Show other bugs)
Version: 1
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-22 18:39 UTC by JB Barnes
Modified: 2014-03-17 02:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-28 22:48:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description JB Barnes 2004-04-22 18:39:45 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
During Anaconda setup, there is no 1280 x 800 resoution available 
when choosing a standard LCD (or any other monitor I can see). In 
case you're not familiar with this resolution, it's new, but is found 
in a significant percentage of new laptops. Most of the ones on the 
store shelves with the new wide format screens are 1280 x 800. (I 
have a Compaq X1000, but practically every manufacturer now has 
1280x800 laptops.)

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


How reproducible:
Always

Steps to Reproduce:
1. During Anaconda setup, choose standard LCD.
2. Try searching for the resolution in any listed monitor
3.
    

Additional info:

I've run into this on several machines. After installation, I have to 
modify XF86Config to add the correct resolution
Comment 1 Bill Nottingham 2004-05-19 21:53:42 UTC 
Added to MonitorsDB, will be in future builds for manual selection.
May not affect the available X modes, though.
Note You need to log in before you can comment on or make changes to this bug.