ZM incompatible with bttv 0.9.x ?

[matt_sf]

Hi all--

well all this time I thought I had been running bttv driver version 0.9.13 but the bulk kernel patch didn't apply properly so I was running a stock bttv 0.7.x version. When I finally got the bttv patches applied and rebuilt the kernel, it appears ZM will no longer open the video device:

Mar 14 13:49:57 chester zmc-d0[461]: INF [Debug Level = 0, Debug Log = ]
Mar 14 13:49:57 chester zmc-d0[461]: INF [Got 1 monitors]
Mar 14 13:49:57 chester zmc-d0[461]: INF [X:0]
Mar 14 13:49:57 chester zmc-d0[461]: INF [Y:0]
Mar 14 13:49:57 chester zmc-d0[461]: INF [W:320]
Mar 14 13:49:57 chester zmc-d0[461]: INF [H:240]
Mar 14 13:49:57 chester zmc-d0[461]: ERR [Failed to set window attributes: Invalid argument]

My shared memory settings are both at 100663296, this is on the 2.4.24 kernel, and an Osprey 200 card.
I have tried unloading and loading the bttv module, no luck. I tried recompiling and reinstalling ZM, still no luck. I also tried deleting the monitor entry from ZM and re-configuring it. meanwhile, both xawtv and videodog seem to have no problem grabbing live and static images, respectively. "zmc --device 0" also seems to attach and hold fine.

ah well after all this work i think it's time to downgrade :) Can anyone offer any debug advice? thanks!

-Matt

[zoneminder]

Hi Matt,

Have you unset 'STRICT_VIDEO_CONFIG' in the options?

Phil,

[matt_sf]

D'oh! I thought I had disabled that in my setup some time ago but I looked in the zmconfig.txt file and it was set to "YES" ... after going through the config the long way, it seemed to stick to "NO"... now that I've reinstalled it seems to be working. So save me some embarrassment and delete this thread ;-) thanks!

-Matt

[lazyleopard]

There might be a correlation between the initial values in the video_window and whether or not the "Failed to set window attributes" message is issued. If the original values of vid_win.x and vid_win.y are already zero then the error doesn't seem to happen. There may also be some connection with vid_win.flags (that's left un-touched). In cases where the error occurs I've noticed that the VIDEO_WINDOW_INTERLACE bit in vid_win.flags is set.

[lazyleopard]

My experiments suggest that, at least for BT848 and BT878 based cards, the "Failed to set window attributes" error from zm_local_camera.cpp might be solved by adding a line of code to reset the VIDEO_WINDOW_INTERLACE bit in vid_win.flags before the VIDIOCSWIN ioctl. Not had time to test this exhaustively yet though.