Bug 476418 - XVideo overlay doesn't work with radeon driver, uses Textured Video by default
Summary: XVideo overlay doesn't work with radeon driver, uses Textured Video by default
Keywords:
Status: CLOSED DUPLICATE of bug 505152
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 10
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-14 13:53 UTC by Florian Fahr
Modified: 2018-04-11 09:21 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
: 505152 (view as bug list)
Environment:
Last Closed: 2009-09-14 22:44:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xorg.conf-less X.Org log (59.84 KB, text/plain)
2008-12-20 00:08 UTC, Florian Fahr
no flags Details
dmesg output (32.08 KB, text/plain)
2009-02-06 21:54 UTC, Florian Fahr
no flags Details

Description Florian Fahr 2008-12-14 13:53:23 UTC
Description of problem:
After upgrading (and lately doing a complete fresh install) to Fedora 10, XVideo doesn't use Overlay mode anymore, but seems to default to Textured Video, instead. However, this mode seems to be significantly slower than Overlay causing massive page tearing and frame drops, especially when playing full-screen video.

Version-Release number of selected component (if applicable):
6.9.0-61.fc10

How reproducible:
Always

Steps to Reproduce:
1. Enable Xv in any application playing video (e.g. VLC).
2. Play a video.
3. Observe.
  
Actual results:
Video plays using textured video.

Expected results:
Video should play using overlay.

Additional info:
I wasn't able to find anything in the man file about these two modes. If there is anything to change this behavior, it might be a good idea to add it to the man file.

Comment 1 Matěj Cepl 2008-12-18 00:26:49 UTC
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, if available) 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 (if you have one) 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.

Comment 2 Florian Fahr 2008-12-20 00:08:01 UTC
Created attachment 327507 [details]
xorg.conf-less X.Org log

I don't have any xorg.conf. Fedora didn't create any.

Comment 3 François Cami 2009-02-06 21:30:28 UTC
Florian,
Could you attach your dmesg output as uncompressed text attachment as well ?
Could you try the latest 6.10 driver (available in Fedora 10 updates) and report ?
Does booting with the nomodeset option help ?

Comment 4 Florian Fahr 2009-02-06 21:54:59 UTC
Created attachment 331169 [details]
dmesg output

This is the output of dmesg. I guess that my driver is at the version number you described. Yum just caught itself inside an endless loop, so I can't check at the moment. I, however, will check the nomodeset option you hinted at. Overlay is still not working, by the way.

Comment 5 Florian Fahr 2009-02-07 09:55:38 UTC
You, sir, are a genius.

Yes, booting with the 'nomodeset' option brought video overlay back. Didn't notice it at first, because it has somehow become really responsive to window movements.

Are there any fixes in the works to make video overlays compatible with kernel mode setting? Cuz I like that Plymouth eye candy ^^

Oh, and the driver is at version 6.10, by the way.

Comment 6 François Cami 2009-02-08 23:37:34 UTC
Florian,
Thanks for testing, definitely a Radeon KMS bug.
Switching component to xorg-x11-drv-ati.

Comment 7 Martin Decky 2009-05-15 14:05:19 UTC
If you look on a patch radeon-modeset.patch (which is in xorg-x11-drv-ati-6.12.2-13.fc11.src.rpm), you can see commit f0c761fe645a00fb109dd265371e94ff2829a796. The commit log says

radeon: disable overlay for modesetting for now

Thus disabling the overlay while using KMS was intentional. The important question is: Can somebody with the knowledge of Radeon and KMS bring the overlay functionality back?

The overlay is usually the only way how to support video playback in dual-head configurations with R200 boards (where the textured video is limited to the framebuffer size of 2048x2048 which can be easily exceeded in dual-head configurations).

Why is the access to the PLL registers not possible while using KMS? Can somebody please look on this?

Comment 8 Jérôme Glisse 2009-09-14 10:18:16 UTC
I don't think we will implement overlay under KMS as we don't think it brings any real improvement over textured video beside avoiding the size limit. Also i am quite surprise that people use such old hardware to drive new screen with such big resolution when 9200Pro came out i am pretty sure 1280x1024 was among the biggest resolution you could think of, this also reflect in the hw as i am pretty sure that beyond 2048x2048 you are reaching hw bandwidth limit. If one can come up with a clean patch which add overlay support to KMS we might consider adding it.

Comment 9 Florian Fahr 2009-09-14 10:46:13 UTC
How does Textured Video compare to Overlay? I am using a mobilityRadeon 9700 and last time I checked the performance was more or less abysmal with tearing and frame drops and stuff when playing a HD trailer on www.gametrailers.com, for instance. Therefore I vote for inclusion ;)

Comment 10 Matěj Cepl 2009-09-14 22:44:17 UTC

*** This bug has been marked as a duplicate of bug 505152 ***


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