BT878 card doesn't show up in ZM

Forum for questions and support relating to the 1.24.x releases only.
Locked
speedamaster
Posts: 25
Joined: Wed Dec 30, 2009 11:29 am

BT878 card doesn't show up in ZM

Post by speedamaster »

I installed a pico2000 card having 4BNC connectors

added the following to bttv.conf
options bttv gbuffers=32 card=77 tuner=4 radio=0 coring=1 full_luma_range=1 chroma_agc=1 combfilter=1 autoload=0 triton1=0 vsfx=0
after a reboot the dmesg shows
bttv: driver version 0.9.16 loaded
bttv: using 32 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 0000:05:04.0, irq: 82, latency: 32, mmio: 0xe8200000
bttv0: using: GrandTec Multi Capture Card (Bt878) [card=77,insmod option]
bttv0: gpio: en=00000000, out=00000000 in=00f360ff [init]
bttv0: using tuner=4
bttv0: registered device video2
bttv0: registered device vbi2
bttv0: PLL: 28636363 => 35468950 .. ok
bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
bt878_probe: card id=[0x0],[ <NULL> ] has DVB functions.
bt878(0): Bt878 (rev 17) at 05:04.1, irq: 82, latency: 32, memory: 0xe8201000
in the ZM console I selected a new monitor with the pre-settings for BTTV video PAL 320x240 but the source in ZM console is shown ORANGE. If I select some other pre-settings from BTTV it turns RED. And NO picture at all.

What else could I check to verify?
whatboy
Posts: 304
Joined: Mon Aug 31, 2009 10:31 pm

Post by whatboy »

What if you set those settings on /etc/modprobe.conf or /etc/modprobe.d/modprobe.conf???
speedamaster
Posts: 25
Joined: Wed Dec 30, 2009 11:29 am

Post by speedamaster »

I'll dump the details tonight for both cases, but I played around a lot and at least did try the "/etc/modprobe.conf" one which didn't solve the issue.

Is there a way to check whether even /dev/videoX does something senseful? I am using ClearOS (CentOS based) so I might not have all packages installed....
speedamaster
Posts: 25
Joined: Wed Dec 30, 2009 11:29 am

Post by speedamaster »

BTW a probe while creating a new monitor results in
Unable to probe local cameras, status is '255'
Locked