> > > Probably not. I've no idea what's causing your problems. And no time > > > (sorry) to try and track it down. > > > > If I can be of any help there (running trial versions, 0.5.xx) let me > > know. > > Hmm... reverting to 0.4.0 did no good. I am now also experiensing hangups > with that version (no message log, sorry). > > Score so far: > > kernel 2.6.12 with ivtv 0.4.1 -> hangups > kernel 2.6.14 with ivtv 0.4.1 -> hangups > kernel 2.6.14 with ivtv 0.4.0 -> hangups > > Could it possibly be caused by a different version of the xdriver? I also > upgraded that from an older version. > Other firmware? That also got upgraded.
I decided to downgrade to 2.6.12 with ivtv 0.3.7 which I had running before. After watching video for about two hours, playback froze with the following entries in dmesg: ... ivtv: Decoder VBI RE-Insert start 0x0019ac00 size 0x0000be00 type 0 ivtv: Decoder VBI RE-Insert start 0x0019ac00 size 0x0000be00 type 0 ivtv: Decoder VBI RE-Insert start 0x0019ac00 size 0x0000be00 type 0 ivtv: Decoder VBI RE-Insert start 0x0019ac00 size 0x0000be00 type 0 ivtv: Decoder VBI RE-Insert start 0x0019ac00 size 0x0000be00 type 0 ivtv: Decoder VBI RE-Insert start 0x0019ac00 size 0x0000be00 type 0 ivtv: Decoder VBI RE-Insert start 0x0019ac00 size 0x0000be00 type 0 ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x00000015 with result 0xfffffff0 ivtv: DEC: couldnt read clock ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x0000000d with result 0xfffffff0 ivtv: DEC: error pausing ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x00000017 with result 0xfffffff0 ivtv: 100 ms time out waiting for firmware ivtv: Failed api call 0x00000002 with result 0xfffffff0 ivtv: Error stopping decoding ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x00000003 with result 0xfffffff0 ivtv: DEC: error changing speed ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x00000015 with result 0xfffffff0 ivtv: DEC: couldn't read clock ivtv: No Free Mailbox for cmd 0x00000015 after 100 tries! ivtv: Mailbox[0] 0x00000053 flags 0x00000003 ivtv: Mailbox[1] 0x00000053 flags 0x00000003 ivtv: Firmware UNRESPONSIVE when trying cmd 0x00000015!!! ivtv: DEC: couldn't read clock ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x00000015 with result 0xfffffff0 ivtv: DEC: couldn't read clock ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x00000015 with result 0xfffffff0 ivtv: DEC: couldn't read clock ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x00000015 with result 0xfffffff0 ivtv: DEC: couldn't read clock ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x00000044 with result 0xfffffff0 ivtv: 1000 ms time out waiting for firmware ivtv: Failed api call 0x0000004a with result 0xfffffff0 Could this be somehow related to the other problems I am experiencing? If so, does this shed any new light on the matter? Ronald. _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
