Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 454276 - glxgears video corruption on radeon x1050 dualhead dual dvi
Summary: glxgears video corruption on radeon x1050 dualhead dual dvi
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 9
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-07 13:03 UTC by Benjamin S. Scarlet
Modified: 2009-07-14 17:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-14 17:32:12 UTC

Attachments (Terms of Use)
Example corruption (deleted)
2008-07-07 13:03 UTC, Benjamin S. Scarlet
no flags Details
xorg.conf file (deleted)
2008-07-07 13:04 UTC, Benjamin S. Scarlet
no flags Details
Xorg.0.log (deleted)
2008-07-07 13:05 UTC, Benjamin S. Scarlet
no flags Details
glxinfo output (deleted)
2008-07-07 13:07 UTC, Benjamin S. Scarlet
no flags Details
xorg.conf (deleted)
2009-02-21 11:09 UTC, Benjamin S. Scarlet
no flags Details
Xorg.0.log (deleted)
2009-02-21 11:10 UTC, Benjamin S. Scarlet
no flags Details

Description Benjamin S. Scarlet 2008-07-07 13:03:15 UTC
Description of problem:
Running glxgears on a dualhead setup, everything looks great until I move the
glxgears window into the right side of the right monitor. Any part of the
glxgears window overlapping that area area (past about column 1050 - both
displays being 1600x1200) displays as corrupt (see attached png if you care -
xwd caught the corruption).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run glxgears
2. drag glxgears to the right side of the right monitor
Actual results:
Corrupt image where window overlaps the (approximately) right third of the right

Expected results:
nifty spinning gears like everywhere else on the monitor.

Additional info:

Comment 1 Benjamin S. Scarlet 2008-07-07 13:03:15 UTC
Created attachment 311142 [details]
Example corruption

Comment 2 Benjamin S. Scarlet 2008-07-07 13:04:17 UTC
Created attachment 311143 [details]
xorg.conf file

Comment 3 Benjamin S. Scarlet 2008-07-07 13:05:58 UTC
Created attachment 311145 [details]

Comment 4 Benjamin S. Scarlet 2008-07-07 13:07:25 UTC
Created attachment 311146 [details]
glxinfo output

Comment 5 François Cami 2009-02-20 19:51:02 UTC

DRI is disabled as soon as you enable Xinerama.
Please use the xrandr-style xorg.conf (or no xorg.conf at all) to get DRI.

The corruption you experience is probably due to your video card not having enough memory.

Please confirm that the attached log is from your video card (9200SE 128MB according to the log, not X1050).

Fedora Bugzappers volunteer triage team

Comment 6 Benjamin S. Scarlet 2009-02-21 11:09:33 UTC
Created attachment 332815 [details]

second try

Comment 7 Benjamin S. Scarlet 2009-02-21 11:10:33 UTC
Created attachment 332816 [details]

second try

Comment 8 Benjamin S. Scarlet 2009-02-21 11:20:23 UTC
Firstly, thank you for looking at my bug.

Secondly, I must apologize. I somehow managed to post incorrect Xorg.0.log and xorg.conf files - files which correspond to my previous dual-head solution, which used two cards and Xinerema, and thus did not support DRI or glx. Something in Fedora 9 broke that solution (I seem to recall Xinerama didn't work), and so I got my current card - sold under the name X1050, but showing up in lspci as "ATI Technologies Inc RV350 AR [Radeon 9600]" (which seems to make sense according to wikipedia). I've attached new Xorg.0.log and xorg.conf files.

If the problem is simply that the card has insufficient memory, is there somewhere I can see that in these log files? Also, how can I calculate how much memory I need for 3d support at a given resolution?

Thanks again,
Ben Scarlet

Comment 9 François Cami 2009-02-21 11:56:20 UTC

Thanks for updating the logs.

For maintainer : I can reproduce the corruption using a FireGL V3100 (128MB) but not on my V7100 (256MB) (3200x1200 on both cases).

Fedora Bugzappers volunteer triage team

Comment 10 Bug Zapper 2009-06-10 01:57:51 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here:

Comment 11 Bug Zapper 2009-07-14 17:32:12 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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