Page 1 of 1

zmc_d0[8545]: ERR [Sync failure for frame 0: Interrupted ...

Posted: Sat May 07, 2005 8:26 pm
by angelhod
... system call]

slack 10.1, zm 1.21
all zm logs look good, no errors there but in syslog i got:
May 7 21:50:12 hod-desk zmc_d0[8545]: ERR [Sync failure for frame 0: Interrupted system call]
May 7 21:54:49 hod-desk zmc_d0[8643]: ERR [Sync failure for frame 3: Interrupted system call]
May 7 21:54:49 hod-desk zma_m1[8709]: ERR [Shared memory not initialised by capture daemon]
May 7 22:02:10 hod-desk kernel: bttv0: irq: SCERR risc_count=2eaab010
May 7 22:03:19 hod-desk kernel: bttv0: irq: SCERR risc_count=2eaab010

zm seems to be working but i got no streaming no frames captured - nothing

thank You for any help

it started to capture the frames.....

Posted: Sat May 07, 2005 8:59 pm
by angelhod
....
when it is set to MODECT function it is capturing the frames.... but cant see any streaming..... and the same is when it is set up to Monitor mode the colour is changed into orange and cant see any streaming.... just blank image

there is no erros in log files but syslog gives:
May 7 22:32:58 hod-desk zmc_d0[3401]: ERR [Sync failure for frame 2: Interrupted system call]
May 7 22:32:58 hod-desk zmc_d0[3613]: ERR [Can't shmget, probably not enough shared memory space free: Invalid argument]
May 7 22:32:58 hod-desk zmc_d0[3617]: ERR [Can't shmget, probably not enough shared memory space free: Invalid argument]
May 7 22:32:58 hod-desk zma_m1[3623]: ERR [Shared memory not initialised by capture daemon]
May 7 22:32:59 hod-desk zma_m1[3625]: ERR [Shared memory not initialised by capture daemon]
May 7 22:33:04 hod-desk zma_m1[3643]: ERR [Shared memory not initialised by capture daemon]
May 7 22:33:14 hod-desk zmc_d0[3644]: ERR [Sync failure for frame 1: Interrupted system call]
May 7 22:44:50 hod-desk zmc_d0[3658]: ERR [Sync failure for frame 2: Interrupted system call]
May 7 22:46:00 hod-desk zmc_d0[4114]: ERR [Sync failure for frame 0: Interrupted system call]
May 7 22:55:17 hod-desk zmc_d0[4232]: ERR [Sync failure for frame 2: Interrupted system call]


and messege log:

May 7 22:56:37 hod-desk zmc_d0[4596]: INF [Television: 4000 - Capturing at 50.00 fps]
May 7 22:56:57 hod-desk zmc_d0[4596]: INF [Television: 5000 - Capturing at 50.00 fps]
May 7 22:57:17 hod-desk zmc_d0[4596]: INF [Television: 6000 - Capturing at 50.00 fps]
May 7 22:57:37 hod-desk zmc_d0[4596]: INF [Television: 7000 - Capturing at 50.00 fps]
May 7 22:57:57 hod-desk zmc_d0[4596]: INF [Television: 8000 - Capturing at 50.00 fps]
May 7 22:58:17 hod-desk zmc_d0[4596]: INF [Television: 9000 - Capturing at 50.00 fps]



plz help

Posted: Sun May 08, 2005 10:11 am
by zoneminder
Sync failures usually indicate some mismatch between the bttv driver and the hardware. You may need to pass additional options to the driver to allow it to correctly identify your capture card.

Phil

.

Posted: Mon May 09, 2005 6:02 am
by angelhod
hmm but when i run xawtv it is quite well.....

Posted: Mon May 09, 2005 10:09 am
by zoneminder
That's probably because xawtv in it's normal mode is actually just mapping through the feed to your screen, the signal is just passing through and cannot be intercepted or analysed. ZM, and any other similar program, needs to use a slightly different interface and sync and grab individual frames. This is where you are seeing the error.

With xawtv you can sort of reproduce this by doing individual images grabs and you may well see the same error. If you don't then it's possible it may be just that the card cannot keep up with the speed that ZM asks for frames so you could try slowing it down by setting a lower Max FPS in the monitor configuration.

Phl

.

Posted: Wed May 11, 2005 11:47 am
by angelhod
when my driver bttv is loading syslog gives:

May 11 12:52:49 hod-desk kernel: bttv: readee error
May 11 12:52:49 hod-desk kernel: bttv0: using tuner=-1

Posted: Thu May 12, 2005 8:47 am
by zoneminder
This certainly sounds like your bttv card needs some additional configuration, probably in form of options passed to the module. What those options are depends on your card but if you search for your card type and bttv driver options you might be lucky.

Phil