Jurgen Goedbloed writes:

Ian wrote,
>> - X server crashes after changing the screen settings in mythtv (GUID
>> width, heigth and offset). I don't know what mythtv is telling the X
>> server then.
>
> Read the README in the ivtv-1.0.1 archive:
>
> NOTE: users of MythTV who use the PVR350 for mpeg decoding need to
> specify the option osd_compat=1 when loading the ivtv-fb module. This
> is not required when using the default Xv output.
>
> I think you need to set this.

Tried that, but then X won't start. I get

(EE) IVTVDEV(0): FBIOPUT_VSCREENINFO: Invalid argument
(EE) IVTVDEV(0): Mode init failed

Without the osd_compat=1 X starts fine.

If you didn't use the osd_compat option before, you shouldn't need it now.

What are the *full* contents of the X log after the crash ?

Backtrace:
0: X(xf86SigHandler+0x81) [0x80c2d21]
1: [0x110420]
2:
/usr/lib/xorg/modules/extensions//libGLcore.so(xmesa_check_and_update_buffer_size+0x32)
[0x6e9cf2]
3: /usr/lib/xorg/modules/extensions//libGLcore.so(XMesaResizeBuffers+0x29)
[0x6ec489]
4: /usr/lib/xorg/modules/extensions//libGLcore.so [0x6ec810]
5: /usr/lib/xorg/modules/extensions//libglx.so [0x1a63ba]
6: X(compPositionWindow+0x59) [0x8105599]
7: X(ReparentWindow+0x1ac) [0x8077b6c]
8: X(ProcReparentWindow+0xd5) [0x8089425]
9: X [0x81523c1]
10: X(Dispatch+0x1aa) [0x80899fa]
11: X(main+0x495) [0x8071735]
12: /lib/libc.so.6(__libc_start_main+0xe0) [0x272f70]
13: X(FontFileCompleteXLFD+0x1e9) [0x8070a21]

Fatal server error:
Caught signal 11.  Server aborting

This looks like a bug in Mesa. Nothing to do with X driver.

Attachment: pgp48lNuTHuxS.pgp
Description: PGP signature

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to