Bug 332791
| Summary: | refresh problems with ATI Radeon X1300 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Jay Berkenbilt <ejb> | ||||||||||||
| Component: | xorg-x11-drv-vesa | Assignee: | Dave Airlie <airlied> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 5.1 | CC: | ejb, imc, melnikovsky, xgl-maint | ||||||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||||||
| Target Release: | --- | Flags: | ejb:
needinfo-
|
||||||||||||
| Hardware: | i686 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2014-06-02 13:20:39 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: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Jay Berkenbilt
2007-10-15 16:18:10 UTC
Created attachment 227781 [details]
first screenshot
Created attachment 227791 [details]
second screenshot
I was able to reproduce this problem without any difficulty using a completely vanilla new user logging in with a default login. The problem could be reproduced by using ediff as long as the ediff control frame was moved down into the main part of the emacs frame so that it partially obscured part of one of the frames that was being diffed. This rules out my environment. 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) USING OPEN SOURCE DRIVERS ONLY 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. For instructions on have to be sure, that no binary drivers are present (and explanation why we are so hard against their use) see http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 228961 [details]
Xorg.0.log with no xorg.conf
This is the Xorg.0.log when starting X after removing the ATI proprietary
drivers and rebooting (to be sure the kernel module wasn't loaded).
Created attachment 228971 [details]
Xorg.0.log with xorg.conf generated by system-config-display
This is the Xorg.0.log when starting X from a config generated by
system-config-display (also attached) using only open source drivers. In this
case, the vesa driver was selected.
Created attachment 228981 [details]
system-conf-display-generated xorg.conf with free drivers
Here is the xorg.conf that was in use when Xorg.0.log-system-config-display was
generated.
I uninstalled the ATI proprietary drivers which I had only installed to see if they fixed the problem. I have attached the xorg.conf and the two log files you requested. Although I didn't run rpm -Va, I did run rpm -qa | grep GL | xargs rpm --verify rpm -qa | grep xorg | xargs rpm --verify I had installed the ATI drivers from rpms. I inspected the rpms to ensure that they didn't overwrite any standard libraries. (They install alternative libraries and create a file in ld.so.conf.d, which the removal of the rpm successfully removed.) I've got rpm -Va running now, and I'll reinstall any libraries that need to be reinstalled, but I know that this problem was definitely present before the proprietary drivers ever touched my system. I was able to reproduce the bug with both of the X configurations posted to this bug report and am in fact able to reproduce the bug now. The only advantage I gained from using the proprietary drivers was that DPMS worked. If I am not able to get DPMS working with the free drivers, I'll post that as a separate bug. fwiw, I reinstalled freeglut-2.4.0-11.fc7 glx-utils-6.5.2-10.fc7 mesa-libGL-devel-6.5.2-10.fc7 mesa-libGLU-6.5.2-10.fc7 which had some changes and it made no difference: the bug is still there. I should be back to a clean configuration now. this is a vesa driver issue, the ati driver doesn't support the X1300. Oh, geez. You're right. Even when I had the proprietary drivers installed, I was actually using the vesa driver. I guess I didn't look that carefully at the xorg.conf. Also, the DPMS problem was a red herring. I didn't have option DPMS "true" in xorg.conf. just reporting that this problem is still there with fedora 8. This is a completely clean install. Proprietary drivers have never touched the system. For what it's worth, I'm not sure this is really a vesa driver issue. After trying with the latest ATI proprietary drivers released 11/21/2007 and ensuring that I am actually using them, I still see the problem. So there is some code somewhere that is used both when the VESA drivers are in use and when the ATI drivers are in use. Perhaps this is lower level kernel VESA code or something. *** Bug 312751 has been marked as a duplicate of this bug. *** I have verified that this happens with Red Hat Enterprise Linux Workstation 5.1 as well as with Fedora 7 and 8. I also verified that the problem does NOT happen with the latest release of the radeonhd driver (1.2.1). Using radeonhd, my display behaves properly. I haven't tried anything that requires acceleration or dual monitors, so I can't comment on radeonhd's general suitability, but I definitely don't have this problem with that driver. This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug. I don't have this hardware anymore nor am I still running RHEL 5 anywhere. This can be closed at any time. Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support). |