Bug 97886

Summary: radeon r300 vdpau broken
Product: Mesa Reporter: Branko <bagzy92>
Component: Drivers/Gallium/r300Assignee: Default DRI bug account <dri-devel>
Status: CLOSED WONTFIX QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium    
Version: 12.0   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Screenshot Dreamworks Logo "Boy on Moon"

Description Branko 2016-09-21 08:48:46 UTC
I have upgraded to mesa 12.0.1 in my Gentoo linux and now Mplayer and VLC video playback don't work. Mplayer can't play anything, in VLC I only get sound and black screen.

Here is MPlayer output which showing that vdpau is broken: https://bpaste.net/show/41ec1aaf26b6

Here is vdpauinfo output: https://bpaste.net/show/1681cbeee499

VDPAU works good with mesa 11.2.2.
Comment 1 Branko 2016-09-22 20:07:43 UTC
vdpau_display vout display error: presentation queue display failure: An invalid handle value was provided. Either the handle does not exist at all, or refers to an object of an incorrect type.
Comment 2 Ilia Mirkin 2016-09-22 20:09:49 UTC
Probably lack of PIPE_BIND_LINEAR support. Probably fixed by https://patchwork.freedesktop.org/patch/110569/
Comment 3 Matt Turner 2017-06-09 17:41:22 UTC
Don't use pastebins in place of attachments.
Comment 4 GHPS 2018-01-07 22:44:14 UTC
Created attachment 136605 [details]
Screenshot Dreamworks Logo "Boy on Moon"
Comment 5 GHPS 2018-01-07 22:45:48 UTC
I can confirm this bug and can see that it exists at least up to Mesa 17.2.4.

Background: Switching from Kubuntu 14.04 to 16.04 I had the problem that
DVD playback in VLC was broken (see screenshot of the Dreamworks Logo "Boy on Moon"). After digging a bit deeper I was able to locate the bug in 
libvdpau, precisely its MPEG1/MPEG2* decoder capabilities 
[full background story with hardware/software specs:1]. 
This results in the blocky artifacts of vdpau in Mesa 12.0.6 
on a Radeon of the r300 family.

Upgrading my Kubuntu 16.04 system to Mesa 17.2.4 didn't fix the problem.

Tests with Kubuntu 17.10 (released with Mesa 17.2.2) show that here the same problem is present.

1: https://ubuntuforums.org/showthread.php?t=2312060&page=2&p=13520479#post13520479
Comment 6 Christian König 2018-01-08 07:50:45 UTC
We no longer support the VDPAU backend for r300.

It never was anything more than pure display and shader based MPEG2 decoding, so not really useful except for testing.
Comment 7 GHPS 2018-01-18 16:42:24 UTC
> We no longer support the VDPAU backend for r300.
I see the point that at some moment in time the support for 
an old platform has to be ceased.

As for myself I've been using my trusty old Thinkpad T60 
since 10 years with various operating systems and drivers.
While starting with Win XP and the proprietary ATI drivers the
system became slower with every iteration of Windows rendering
it ultimately useless under Windows 10. Switching to Kubuntu 14.04
not only made the old hardware usable again but showed the surprising
effect that the machine becomes faster with every release cycle of kernel
and drivers. 

That my Thinkpad now is more usable than it ever was is
in parts a result of the great work of the Mesa team. They - You! - 
developed a driver that is much better than ATI’s original work.

Therefore I regret that the r300 platform is no longer supported.

More so since the vdpau driver seemed to be working fine in previous
versions, the initial bug report is from September 2016 and a patch
was submitted to fix the problem.

And the bug bites every user who is trying to play back mpeg1/mpeg2 content 
- DVDs - since VLC and other players silently rely on vpdau.

So it would be very kind if a developer would take a second look at the problem.
Comment 8 Christian König 2018-01-18 17:56:39 UTC
Sorry, but the vdpau backend for r300 never did anything else than displaying the playback content. There actually never was any decoding acceleration.

So you should be able to actually use Xv just the same way.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.