Bug#425814: xserver-xorg-video-ati: Xv broken on Mach64 3D Rage LT Pro AGP-133
On Sun, 2007-06-24 at 02:22 +0200, Brice Goglin wrote:
> Hi Svante,
>
> Is there anything new about XV being broken on your mach64 board? Did
> you by chance look at Michel's earlier questions? (see
> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;bug=425814)
>
> It looks like we'll have to reassign this bug to the server core
> (xserver-xorg-core) since downgrading it to 1.1.1 fixed the problem
> while changing xserver-xorg-video-ati's version did not apparently help.
>
> Thanks,
> Brice
Sorry for not replying until now, been busy with other things.
Reassign: xserver-xorg-core
Version: 2:1.3.0.0.dfsg-6
Loaded modules:
pcidata, dbe, ddc, extmod,freetype, glx, int10, record, type1, vbe, dri,
ati, kbd, mouse, atimisc, fb, ramdac, xaa, i2c, GLcore
I think you can reasssign to xserver-xorg-core, since upgarding the ati driver did not help.
The colorkeys differ at one point, the client gettable attribute: (current value is 0/1)
2:1.1.1-21
"XV_AUTOPAINT_COLORKEY" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 0)
--
"XV_COLORKEY" (range 0 to 16777215)
client settable attribute
client gettable attribute (current value is 3137)
--
"XV_COLORKEY_MASK" (range 0 to 16777215)
client settable attribute
client gettable attribute (current value is 65535)
2:1.3.0.0.dfsg-6:
xvinfo|grep -A2 COLORKEY
"XV_AUTOPAINT_COLORKEY" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 1)
--
"XV_COLORKEY" (range 0 to 16777215)
client settable attribute
client gettable attribute (current value is 3137)
--
"XV_COLORKEY_MASK" (range 0 to 16777215)
client settable attribute
client gettable attribute (current value is 65535)
Taking screenshots does not reveal anything, at least using mplayer or
vlc, the problems seem to occur when a sequence of images is displayed.
When pausing the dotted contours are visible, but not on the
screenshots. Unfortunately, I don't have a digital camera available
right now.
Reply to: