Bug 330761 - s-c-d started from console limited to 800x600 with a 1280x800 LCD display
Summary: s-c-d started from console limited to 800x600 with a 1280x800 LCD display
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-display
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-13 17:05 UTC by Daniel Qarras
Modified: 2018-04-11 17:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-28 23:06:47 UTC


Attachments (Terms of Use)
Initial setup log when s-c-d ran without config (1.78 KB, text/plain)
2007-10-29 17:00 UTC, Daniel Qarras
no flags Details
xorg.conf that is created the same every time (823 bytes, text/plain)
2007-10-29 17:01 UTC, Daniel Qarras
no flags Details
Initial setup log when s-c-d ran without config (1.78 KB, text/plain)
2007-10-29 17:01 UTC, Daniel Qarras
no flags Details
X log after start X after initial config (63.86 KB, text/plain)
2007-10-29 17:04 UTC, Daniel Qarras
no flags Details
X log after starting X again and running s-c-d under X (73.06 KB, text/plain)
2007-10-29 17:05 UTC, Daniel Qarras
no flags Details

Description Daniel Qarras 2007-10-13 17:05:16 UTC
Description of problem:
With system-config-display-1.0.51-4.fc8 and xorg-x11-drv-ati-6.7.195-2.fc8
system-config-display gives default maximum resolution only of 800x600 even if
my laptop has a 1280x800 display. My laptop model is Acer Aspire 1690 with ATI
Mobility Radeon X700.

Version-Release number of selected component (if applicable):
system-config-display-1.0.51-4.fc8
xorg-x11-drv-ati-6.7.195-2.fc8

How reproducible:
Always.

Steps to Reproduce:
1. rm -f /etc/X11/xorg.conf
2. system-config-display
3. notice how 800x600 is the default maximum
  
Actual results:
One needs to manually change display type to LCD 1280x800.

Expected results:
Automatic detection.

Additional info:
This is harmful also during installation as 800x600 mode is used.

Comment 1 Daniel Qarras 2007-10-13 17:05:50 UTC
Btw, not sure if this is related to ancient Bug 144010.

Comment 2 Daniel Qarras 2007-10-19 18:41:35 UTC
Some additional information: when starting system-config-display with
xorg-x11-drv-ati-6.7.195-3.fc8 and without /etc/X11/xorg.conf, resolution
proposed is 800x600 and no higher resolutions are available in the menu although
the display in 1200x800 at that very moment! Monitor is autoconfigured. When
accepting the defaults the created xorg.conf contains correctly DisplayDepth 24
and no Monitor/Modes settings. Then starting X gives nicely 1200x800.

So it seems that the driver and autodetection is working correctly but s-c-d is
not getting the correct information leading to this unintuitive situation.

Comment 3 Daniel Qarras 2007-10-19 18:43:01 UTC
Should have been:"Monitor _type_ is autoconfigured" in s-c-d menu.

Comment 4 Daniel Qarras 2007-10-25 13:43:55 UTC
Yet more information: system-config-display works correctly if started when
running X/GNOME already, then 1200x800 resolution is available as the default value.

So the problem in s-c-d is there only when started from console.

Comment 5 Matěj Cepl 2007-10-29 14:05:01 UTC
Thanks for the bug report.  We have reviewed the information you have provided 
above, and there is some additional information we require that will be 
helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) and X server log 
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file 
attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and 
let X11 autodetect your display and video card? Attach to this 
bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this 
information.

Thanks in advance.


Comment 6 Daniel Qarras 2007-10-29 16:59:19 UTC
I started by removing all configs and logs, then running system-config-display,
saving config & log, starting X, running system-config-display and saving log.
I'll attach the files now.

Comment 7 Daniel Qarras 2007-10-29 17:00:03 UTC
Created attachment 242071 [details]
Initial setup log when s-c-d ran without config

Comment 8 Daniel Qarras 2007-10-29 17:01:00 UTC
Created attachment 242081 [details]
xorg.conf that is created the same every time

Comment 9 Daniel Qarras 2007-10-29 17:01:52 UTC
Created attachment 242091 [details]
Initial setup log when s-c-d ran without config

Comment 10 Daniel Qarras 2007-10-29 17:04:44 UTC
Created attachment 242101 [details]
X log after start X after initial config

Comment 11 Daniel Qarras 2007-10-29 17:05:22 UTC
Created attachment 242111 [details]
X log after starting X again and running s-c-d under X

Comment 12 Daniel Qarras 2007-10-29 17:05:57 UTC
Comment on attachment 242091 [details]
Initial setup log when s-c-d ran without config

Duplicate attachment.

Comment 13 Bug Zapper 2008-04-04 14:04:48 UTC
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
rawhide.
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 14 Daniel Qarras 2008-05-05 23:05:03 UTC
I still see this with F9.

Comment 15 Bug Zapper 2008-05-14 03:22:43 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 16 Daniel Qarras 2008-10-04 09:56:01 UTC
Still seeing this with F10Beta. Not sure how relevant this is now as xorg.conf is not created/used by default anymore.

Comment 17 Bug Zapper 2008-11-26 02:00:27 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 18 Daniel Qarras 2008-12-14 15:27:51 UTC
This is still present with F10 final.

Comment 19 Daniel Qarras 2009-04-03 15:32:48 UTC
Well, what I have stated in Comment #2 some 2.5 years ago still applies for F11ß.

Comment 20 Bug Zapper 2009-06-09 09:18:49 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

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

Comment 21 Daniel Qarras 2009-10-23 19:29:58 UTC
This is still an issue with Fedora 12 Beta.

Comment 22 Daniel Qarras 2009-10-28 23:06:47 UTC
Actually, this works when run under X! I was testing on console where _pyrandr is not usable.

Ideally, of course, this would work from console, too, but since no resolution is added to xorg.conf I think it is safe to close this one.


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