Bug 110111
| Summary: | Mobility FireGL 7800 M7 doesn't clone well, weird drawing on external display | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Keith T. Garner <kgarner> |
| Component: | XFree86 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-10-12 06:30:35 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: | |||
|
Description
Keith T. Garner
2003-11-14 21:37:04 UTC
All bug reports need to be filed as one bug being reported per bug report, so that individual issues can be tracked, and once they're resolved, they can be closed one at a time without having to wait for the whole group to be closed out. For issue #1: Can't help you with that problem as I don't have any ATI Radeon Mobility hardware at all. You'll have to report that issue to XFree86.org bugzilla at http://bugs.xfree86.org for someone who has the hardware to investigate. Using special hotkeys on a laptop does not invoke X server features or functionality, it invokes BIOS features, and may conflict with the video driver. I can't really do anything about this either way however, as I don't have the hardware at all. Issue #2: I can't picture this to know what could be the cause. Make sure acceleration is not disabled, and that you're using the Red Hat kernel and MTRR is working properly. I can try to reproduce this on desktop hardware sometime, but you'll need to file a separate bug report for me to track that one issue. You should also file that report to XFree86.org so that it isn't a problem in 4.4.0 if it is indeed an XFree86 bug. Issue #3: Radeon hardware supports only a single video overlay, and that overlay can only be on one CRT or the other at a time, so it is not possible to have an Xvideo overlay on both windows simultaneously. XFree86 4.5.0 (or whatever is after 4.4.0) will have a new special mode for the Radeon called MergedFB mode which allows both screens to share the same framebuffer. When MergedFB is available, the video overlay works across screens, but that wont be for a long time. All of these 3 problems really require physical access to the specific hardware in order for a developer to be able to investigate them. I do not have Radeon Mobility hardware, and so I wont likely be able to do anything about these problems other than review patches that others provide, or backport known fixes from XFree86 CVS that people claim fixes the problem for them. My recommendation is to test the current XFree86 CVS head Radeon support, and if the problems persist, to file these 3 issues as separate bug reports in XFree86 bugzilla, so they can be tracked by the entire range of developers working on the XFree86 radeon driver, of whom one or more might perhaps have Radeon Mobility access. You might also want to post about these problems on the XFree86 mailing list xfree86 and see what turns up. If you file bug reports upstream, please include the bug URL(s) here so I can track the issues upstream and investigate potential inclusion of any fixes that show up. Thanks in advance. Hmm, I just reread #2... Are you saying your mouse cursor is
being corrupted? If so, try using:
Option "swcursor"
in the device section of the config file.
This happens with the 'text' cursor in a konsole as well. Unless that is done at the hardware level as well.... I'll give swcursor a try. Also, I'll be good and file seperate reports for the other issues. Can you take screenshots of the corruption? That might help quite a bit perhaps. If the problem doesn't show up in a screenshot, can you take some high-res digital pictures with no flash? Preferably .png as they have no lossy compression... unless the camera's native format is .jpg (mine is, bleah) Sometimes a picture is worth a thousand words. ;o) I haven't had a chance to get those screenshots yet. However, on a whim, I booted into X without the external monitor attached. After X was up, I attached the external monitor, and behaviour above worked as expected (for all three items, yes, I need seperate bugs files for two of them.) Since this bugzilla report was filed, there have been several major updates to the X Window System, which may resolve this issue. Users who have experienced this problem are encouraged to upgrade to the latest version of Fedora Core, which can be obtained from: If this issue turns out to still be reproduceable in the latest version of Fedora Core, please file a bug report in the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, 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. |