[Fwd: XVideo Crash]
amomacias at gmail.com
Wed Aug 30 04:20:25 PDT 2006
-----BEGIN PGP SIGNED MESSAGE-----
Thanks Barry. I'm capturing a video right now with no problem.
Can you explain me a bit what have we changed adding these two lines
in xorg.conf? I don't understand very much about video internals :P
Does it affect the performance in any way?
1920x1088? I don't know why. Maybe my Panasonic NV GS27 does not fit
the standard at all or kino is crazy...no idea.
One more thing that i'm experiencing with kino, is that when i'm
capturing (not playing) DV, the window that supossedly shows the video
gets totally freezed and shows no video progress. If I put a window
above, and later I minimize that window, I see the current video
progress correctly for half second, and later it freezes again.
As I said, when no capture is being performed kino behaves ok showing
the DV contents.
Can anyone give me a clue of what's happening?
Thanks in advance and sorry for the "question pack".
Barry Scott wrote:
> alex wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> Hi everyone!
>> I have got the same problem, in the same hardware (well, a 915GM in my
>> laptop). I use debian (etch).
>> Changing to vesa temporarily acts as a good workaround (it has no
>> sense for me but works)
>> I think the i810 driver has got a problem trying to create video
>> overlays in some circunstances.
>> Maybe Adam is right and is a xvideo+i810 issue.
>> Important note: I use an apt-sourced and modified version of i810 in
>> order to remove the validatepci() call in the code of the xserver (see
>> http://lists.debian.org/debian-x/2006/06/msg00266.html for more
>> information, but surely the people using i915 knows what I'm talking
>> >> Trying XVideo at 720x576
>> >>> XvQueryAdaptors count: 1 Xv: Intel(R) Video Overlay:
>> ports 73 -
>> >>> 73 formats supported: 4 0x32595559 (YUY2) packed
>> >>> (YV12) planar 0x30323449 (I420) planar 0x59565955 (UYVY)
>> >>> 0: XV_IMAGE, 1920x1088 rate = 1/1
>> The program 'kino' received an X Window System error.
>> This probably reflects a bug in the program.
>> The error was 'BadAlloc (insufficient resources for operation)'.
>> (Details: serial 49521 error_code 11 request_code 141 minor_code 19)
>> (Note to programmers: normally, X errors are reported
>> that is, you will receive the error a while after causing it.
>> To debug your program, run it with the --sync command line
>> option to change this behavior. You can then get a meaningful
>> backtrace from your debugger if you break on the gdk_x_error()
> There is not enough graphics memory to allocate a 1920x1088 image.
> Add this new option to the device section:
> # enable HD XV playback
> Option "LinearAlloc" "6144"
> You may need to increase the value if you still get bad alloc.
> Oh and why is the image 1920x1088 when all the standards are
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the xorg