Created attachment 23772 [details] xorg log Using nouveau drm and xorg driver from git 20090303, with GeForce 8600M GT card (in a laptop). I cannot play anything using the xv driver. With mplayer, it loops and I get no image : X11 error: BadMatch (invalid parameter attributes)?% ??% ??,?% 0 0 X11 error: BadMatch (invalid parameter attributes)?% ??% ??,?% 0 0 X11 error: BadMatch (invalid parameter attributes)?% ??% ??,?% 0 0 X11 error: BadMatch (invalid parameter attributes)?% ??% ??,?% 0 0 X11 error: BadMatch (invalid parameter attributes)?% ??% ??,?% 0 0 X11 error: BadMatch (invalid parameter attributes)?% ??% ??,?% 0 0 ... With xine, it just crashes : X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 132 (XVideo) Minor opcode of failed request: 19 () Serial number of failed request: 2021 Current serial number in output stream: 2022 xvinfo output : X-Video Extension version 2.2 screen #0 Adaptor #0: "Nouveau GeForce 8/9 Textured Video" number of ports: 32 port base: 63 operations supported: PutImage supported visuals: depth 24, visualID 0x21 depth 24, visualID 0x22 no port attributes defined maximum XvImage size: 4096 x 4096 Number of image formats: 3 id: 0x32315659 (YV12) guid: 59563132-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x30323449 (I420) guid: 49343230-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x32595559 (YUY2) guid: 59555932-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed)
Created attachment 23773 [details] I just noticed many errors in dmesg, attaching the relevant part.
Unfortunately this is the current expected behaviour. If you run an XRENDER base composite manager (xcompmgr is fine) Xv will work. Hopefully we'll be able to remove this limitation in the future. The errors you mentioned are also expected, and harmless. We're looking at what's going wrong there however :)
(In reply to comment #2) > Unfortunately this is the current expected behaviour. If you run an XRENDER > base composite manager (xcompmgr is fine) Xv will work. Hopefully we'll be > able to remove this limitation in the future. > > The errors you mentioned are also expected, and harmless. We're looking at > what's going wrong there however :) > I just enabled composite in xorg.conf (not enabled by default), and started xcompmgr -a, and xv works perfectly now, thanks! However I could not find anything when searching for this issue, is it mentioned somewhere? I did not find existing bug reports, and maybe this limitation could also be mentioned on the main page ( http://nouveau.freedesktop.org/wiki/ ) since there is a decent workaround.
(In reply to comment #3) > However I could not find anything when searching for this issue, is it > mentioned somewhere? > I did not find existing bug reports, and maybe this limitation could also be > mentioned on the main page ( http://nouveau.freedesktop.org/wiki/ ) since there > is a decent workaround. > I've updated the wiki on the two relevent pages I know about (FeatureMatrix and XVideoStatus) to note this issue.
(In reply to comment #4) > (In reply to comment #3) > > However I could not find anything when searching for this issue, is it > > mentioned somewhere? > > I did not find existing bug reports, and maybe this limitation could also be > > mentioned on the main page ( http://nouveau.freedesktop.org/wiki/ ) since there > > is a decent workaround. > > > > I've updated the wiki on the two relevent pages I know about (FeatureMatrix and > XVideoStatus) to note this issue. > Looks good, thanks.
this has been resolved ages ago.
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.