Bug 138761
Summary: | Installer sets invalid sync rate for X server on ATI Radeon X300/Viewsonic VX-900-2 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Colohan <colohan+redhat> | ||||
Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4 | CC: | knox | ||||
Target Milestone: | --- | Keywords: | Regression, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-09-28 00:43:03 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 150221 | ||||||
Attachments: |
|
Description
Chris Colohan
2004-11-11 00:44:59 UTC
I have noticed some related bugs appearing. In particular, see the following bugs: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136108 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139023 I encountered a similar problem installing FC3 x86_64 with my Radeon 9800 Pro and Syncmaster 191+. With the Monitor connected via the DVI interface, the screen blanks and the install fails because an invalid sync rate. Changing to a VGA connection (exact same video card and monitor) allowed the install to complete without problem. After the post-install reboot and configure, switching back to the DVI connection works just fine. FC3 test 3 did not have this problem. Only FC3 final. Install in text mode if you haven't gotten the OS installed already, then afterward, log in as root, and run: system-config-display --reconfig Try to start up X, and if it does not work, please attach your X server log file, and config file to the bug report using the attachment feature below. Also, please file a bug report in the X.Org project bugzilla at http://bugs.freedesktop.org in the "xorg" component, as this will maximize the likelyhood of this issue being fixed sooner and made available as an update for Fedora Core. Once you've filed your bug report in X.Org bugzilla, paste the URL here and we will track the issue in the upstream bugzilla. Setting status to "NEEDINFO", awaiting upstream bug URL and file attachments as requested above. 6 months have elapsed since the last feedback from this issue, and there has not been any feedback to my request in comment #3, so I assume the issue is resolved in the current updates released for Fedora Core 3. If the problem is still an issue with all Fedora updates applied however, file a bug report to X.Org as requested above, and if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates. Setting status to "RAWHIDE" Unfortunately, I do not have a spare computer to reinstall the operating system on from scratch for testing purposes. :-( I switched to a text console on my working and fully-up-to-date system, and ran "system-config-display --reconfig", and was rewarded with a blank screen (due to it starting up an X server with an invalid sync rate). I had to kill the invisible X server with ctrl-alt-backspace. No files were touched in /etc/X11 by doing this, so I have no failing config file to attach. If you can tell me where this command might leave a log file I can go looking for it. :-) I did a search for similar bugs in the X.Org bugzilla, and although I didn't find one exactly like this one, I did figure out that they would like exact X server invocation and configuration information in their bugreports. Since the redhat configure scripts do not give me this information (and I sadly don't have the time to read all of the redhat scripts to figure this out), I can't file a bugreport which would be useful to them. If you can tell me: a) where to find any log files which are generated by the X server started up by "system-config-display --reconfig", and b) how to find out what command line invocation of X is performed by this command then I will happily give you the information you desire. Now that FC4 is out, I was able to try it again. It still doesn't work, so I am reopening the bug. If you can give me instructions on how to generate the log file you need, I would be happy to provide it. As requested in comment #3 above, please file a bug report in the X.Org project bugzilla at http://bugs.freedesktop.org in the "xorg" component in order for Xorg developers to be made aware of the issue. The X server log file is automatically put into the system wide log directory /var/log. Attach the X server log file and config file to the X.org bug report you file, so that Xorg developers have enough detail to be able to diagnose the problem. Once you've filed your bug report in X.Org bugzilla, paste the URL here and we will track the issue in the upstream bugzilla. Setting status to "NEEDINFO", awaiting upstream bug URL. Created attachment 115979 [details]
X.org log file generated when running system-config-display
Comment on attachment 115979 [details]
X.org log file generated when running system-config-display
I attempted to run "system-config-display --reconfig" on my FC4 system, and it
displayed a blank screen (invalid sync rate). So it never got as far as
generating a new configuration file for me to try.
Attached is the error log from the system-config-display command. I will open
an x.org bug momentarily...
FYI -- I have not attached the config file for Xorg since either there was none, or system-config-display erased it faster than I was able to make a copy of it in /tmp.... Bug 3627 created in xorg is here: https://bugs.freedesktop.org/show_bug.cgi?id=3627 Tracking in upstream master X.Org bug report: https://bugs.freedesktop.org/show_bug.cgi?id=1129 |