Description of problem: xvideo works OK for smaller videos, but 1920x1080 videos played by mplayer are jerky and there is a lot of shearing, and additionally when I quit mplayer, there is a five second delay before it actually quits, during which it displays two latest frames of the video repeatedly. Jerkiness if not because of inadequate CPU power. 2.2.1-14 version of the driver works OK. Version-Release number of selected component (if applicable): 2.3.2-2 How reproducible: always Steps to Reproduce: 1. mplayer -vo xv somemovie 2. 3. Actual results: as described Expected results: smooth play Additional info: I have965Q chipset, motherboard DQ965GF. 1600x1200@75Hz mode. xvinfo for v2.3.2-2: X-Video Extension version 2.2 screen #0 Adaptor #0: "Intel(R) Textured Video" number of ports: 16 port base: 118 operations supported: PutImage supported visuals: depth 24, visualID 0x21 number of attributes: 2 "XV_BRIGHTNESS" (range -128 to 127) client settable attribute client gettable attribute (current value is 0) "XV_CONTRAST" (range 0 to 255) client settable attribute client gettable attribute (current value is 0) maximum XvImage size: 1920 x 1088 Number of image formats: 5 id: 0x32595559 (YUY2) guid: 59555932-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) 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: 0x59565955 (UYVY) guid: 55595659-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x434d5658 (XVMC) guid: 58564d43-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) Adaptor #1: "Intel(R) Video Overlay" number of ports: 1 port base: 134 operations supported: PutImage supported visuals: depth 24, visualID 0x21 number of attributes: 12 "XV_COLORKEY" (range 0 to 16777215) client settable attribute client gettable attribute (current value is 66046) "XV_BRIGHTNESS" (range -128 to 127) client settable attribute client gettable attribute (current value is -19) "XV_CONTRAST" (range 0 to 255) client settable attribute client gettable attribute (current value is 75) "XV_SATURATION" (range 0 to 1023) client settable attribute client gettable attribute (current value is 146) "XV_DOUBLE_BUFFER" (range 0 to 1) client settable attribute client gettable attribute (current value is 1) "XV_PIPE" (range -1 to 1) client settable attribute client gettable attribute (current value is -1) "XV_GAMMA0" (range 0 to 16777215) client settable attribute client gettable attribute (current value is 526344) "XV_GAMMA1" (range 0 to 16777215) client settable attribute client gettable attribute (current value is 1052688) "XV_GAMMA2" (range 0 to 16777215) client settable attribute client gettable attribute (current value is 2105376) "XV_GAMMA3" (range 0 to 16777215) client settable attribute client gettable attribute (current value is 4210752) "XV_GAMMA4" (range 0 to 16777215) client settable attribute client gettable attribute (current value is 8421504) "XV_GAMMA5" (range 0 to 16777215) client settable attribute client gettable attribute (current value is 12632256) maximum XvImage size: 1920 x 1088 Number of image formats: 5 id: 0x32595559 (YUY2) guid: 59555932-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) 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: 0x59565955 (UYVY) guid: 55595659-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x434d5658 (XVMC) guid: 58564d43-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar)
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) 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 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.
Created attachment 312374 [details] xorg.conf
Created attachment 312375 [details] Xorg.0.log
Did not make any difference when I tried without /etc/X11/xorg.conf.
Created attachment 313080 [details] Xorg.0.log no xorg.conf
I tried 2.4.0-1, Xorg did not start up because you had that intel-master.patch. (EE) LoadModule: Module intel does not have a intelModuleData data object. No clue what that patch was supposed to fix, but I removed that patch and 2.4.0-1 now works nicely with xvideo.
I can also see the error message in my Xorg log now: LoadModule: Module intel does not have a intelModuleData data object. xorg-x11-drv-i810-2.4.0-1.fc10.x86_64
Newer versions of the driver load fine. Do you still see the problem with the newer driver?
No.
Closing per comments 6 and 9.