Bug 470777 - Screen resolution only goes up to 800x600
Summary: Screen resolution only goes up to 800x600
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nv
Version: 10
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-10 06:54 UTC by Amit Shah
Modified: 2018-04-11 07:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 06:48:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xorg.0.log (27.54 KB, text/plain)
2008-11-10 06:54 UTC, Amit Shah
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 14453 0 None None None Never

Description Amit Shah 2008-11-10 06:54:43 UTC
Created attachment 323042 [details]
xorg.0.log

Description of problem:
I'm trying out Fedora but running into a strange problem. I downloaded the i686 KDE Live spin and installed on my machine. The Live desktop as well as post-install desktop only had a resolution of 800x600 and it won't go up.

Strange thing is I can't find xorg.conf in /etc/X11 (or via locate). Where does Fedora store its X config? I remember having read about an empty xorg.conf working these days; is it also the case that an empty one is also not needed?

In my current Debian setup, I use the vesa driver to get a higher resolution.

smolt info for my comp:
http://www.smolts.org/client/show/pub_7fb559ea-f39f-4bb3-9db7-fbf74436f72f

xorg.0.log attached.

Comment 1 Matěj Cepl 2008-11-10 17:59:08 UTC
it should mostly without any /etc/X11/xorg.conf whatsoever -- could you please attach /var/log/Xorg.*.log as separate uncompressed attachments to this bug?

Comment 2 Amit Shah 2008-11-11 04:31:04 UTC
I've already attached /var/log/Xorg.0.log (the only I had -- this is a fresh install and boot).

Comment 3 Matěj Cepl 2008-11-11 23:49:36 UTC
I am sorry.

Comment 4 Orion Poplawski 2008-11-21 05:22:06 UTC
I've got the same issue.  6150LE chipset.  I'm using an Envision 2028 LCD.  Would be interested to know your monitor.  Vesa driver detects the monitor just fine.

Comment 5 Bug Zapper 2008-11-26 05:06:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Amit Shah 2009-07-16 06:11:25 UTC
Just for completenes:

https://bugzilla.redhat.com/show_bug.cgi?id=505829

That's a bug for the same monitor on an intel chipset. The monitor is

http://www.amazon.com/Samsung-SyncMaster-740N-17-inch-Monitor/dp/B000BT2PZS

Comment 7 Bug Zapper 2009-11-18 08:48:54 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2009-12-18 06:48:13 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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