Hide Forgot
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.
Btw, not sure if this is related to ancient Bug 144010.
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.
Should have been:"Monitor _type_ is autoconfigured" in s-c-d menu.
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.
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.
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.
Created attachment 242071 [details] Initial setup log when s-c-d ran without config
Created attachment 242081 [details] xorg.conf that is created the same every time
Created attachment 242091 [details] Initial setup log when s-c-d ran without config
Created attachment 242101 [details] X log after start X after initial config
Created attachment 242111 [details] X log after starting X again and running s-c-d under X
Comment on attachment 242091 [details] Initial setup log when s-c-d ran without config Duplicate attachment.
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.
I still see this with F9.
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
Still seeing this with F10Beta. Not sure how relevant this is now as xorg.conf is not created/used by default anymore.
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
This is still present with F10 final.
Well, what I have stated in Comment #2 some 2.5 years ago still applies for F11ß.
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
This is still an issue with Fedora 12 Beta.
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.