Bug 638134 - incorrect screen resolution ser
Summary: incorrect screen resolution ser
Keywords:
Status: CLOSED DUPLICATE of bug 638174
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-28 11:16 UTC by tiredman
Modified: 2010-09-29 01:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-29 01:04:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Xorg.0.log (66.97 KB, application/octet-stream)
2010-09-28 11:34 UTC, tiredman 		no flags Details
smolt profile (6.90 KB, text/plain)
2010-09-28 11:37 UTC, tiredman 		no flags Details
dmesg output (126.20 KB, application/octet-stream)
2010-09-28 11:39 UTC, tiredman 		no flags Details
/var/log/messages (158.12 KB, application/octet-stream)
2010-09-28 11:42 UTC, tiredman 		no flags Details
View All

Description tiredman 2010-09-28 11:16:47 UTC 
Description of problem:
Fedora incorrectly sets my sreen resolution to 1280 x 1024. The correct resolution for my monitor is 1440x900


Version-Release number of selected component (if applicable):
Test Day:2010-09-28 Nouveau x86_64 live cd

How reproducible:


Steps to Reproduce:
1. boot from live cd

  
Actual results:
screen is set to 1280 x 1024 resolution. system->prefererces->monitors only lists 1280 x1024, 1024 x 768, 800 x 600, and 640 x 480


Expected results:
screen is set to 1440x900


Additional info:
Comment 1 tiredman 2010-09-28 11:34:45 UTC 
Created attachment 450151 [details]
Xorg.0.log
Comment 2 tiredman 2010-09-28 11:37:42 UTC 
Created attachment 450152 [details]
smolt profile
Comment 3 tiredman 2010-09-28 11:39:27 UTC 
Created attachment 450153 [details]
dmesg output
Comment 4 tiredman 2010-09-28 11:42:38 UTC 
Created attachment 450155 [details]
/var/log/messages
Comment 5 Ben Skeggs 2010-09-29 01:04:37 UTC 

*** This bug has been marked as a duplicate of bug 638174 ***
Note You need to log in before you can comment on or make changes to this bug.