Help with checkerboard error effect

[mrkroket]

Hello all:

First, thanks for this wonderful software, it works great!.
But I'm having some problems on my setup, I can't get it working correctly.

It happens that my images randomly (and very often) change to a checkerboard effect. This wrecks everything, and the motion detection gets confused.

See what I'm talking about:


As soon as I change some property on v4l, it fixes the error. I.e. if I run the command: v4lctl -c /dev/video0 bright 126 the image gets normal.


My Setup:
Intel(R) Pentium(R) 4 CPU 2.80GHz and 1GB RAM

lspci

Code: Select all

01:07.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)
01:08.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
01:0a.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)

So I have 3 video inputs.

Zoneminder logs usually gets lost signal of the camera (could be, they are cheap and they have a long cable run), but only on 2 out of 3 video inputs (video0 and video2). /dev/video1 doesn't have any ZM error and stills appears the checker effect:

Code: Select all

Mar 23 09:31:53 LINUX zmc_dvideo2[15804]: ERR [Failed to capture image from monitor 2 (0/1)]
Mar 23 09:31:53 LINUX zmdc[14746]: ERR ['zmc -d /dev/video2' exited abnormally, exit status 255]
Mar 23 09:35:06 LINUX zmc_dvideo0[15767]: ERR [Failed to capture image from monitor 3 (0/1)]
Mar 23 09:35:06 LINUX zmdc[14746]: ERR ['zmc -d /dev/video0' exited abnormally, exit status 255]

dmesg shows an error on each capture card, but it seems a common OpenSuse error related to ACPI on ioremap.c:

Code: Select all

vendor=8086 device=244e
saa7134 0000:01:0a.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
saa7133[2]: found at 0000:01:0a.0, rev: 209, irq: 19, latency: 64, mmio: 0xfeadf800
saa7133[2]: subsystem: 1043:4845, board: ASUSTeK P7131 Analog [card=146,insmod option]
resource map sanity check conflict  0xfeadf800 0xfeae07ff 0xfeadf800 0xfeadffff 0000:01:0a.0
------------[ cut here ]------------
WARNING: at arch/x86/mm/ioremap.c:156 __ioremap_caller+0x89/0x39a()
Modules linked in: tda827x tda8290 tuner saa7134(+) ir_common rtc_cmos rtc_core dcdbas(X) videodev rtc_lib v4l1_compat compat_ioctl32 v4l2_common videobuf_dma_sg e1000 videobuf_core tveeprom iTCO_wdt iTCO_vendor_support shpchp sg i2c_i801 intel_agp button pci_hotplug serio_raw i2c_core agpgart pcspkr sd_mod crc_t10dif ehci_hcd uhci_hcd usbcore edd ext3 mbcache jbd fan ide_pci_generic piix ide_core ata_generic ata_piix libata scsi_mod dock thermal processor thermal_sys hwmon
Supported: Yes, External
Pid: 699, comm: modprobe Tainted: G        W 2.6.27.7-9-pae #1
 [<c0106570>] dump_trace+0x6b/0x249
 [<c01070a5>] show_trace+0x20/0x39
 [<c035175f>] dump_stack+0x71/0x76
 [<c012ddf8>] warn_on_slowpath+0x4d/0x70
 [<c0119cfc>] __ioremap_caller+0x89/0x39a
 [<c011a11f>] ioremap_nocache+0x18/0x1c
 [<f8b97f19>] saa7134_initdev+0x490/0x8ec [saa7134]
 [<c0243622>] pci_device_probe+0xa3/0xe4
 [<c02afe96>] really_probe+0xd7/0x1de
 [<c02b0072>] __driver_attach+0x37/0x55
 [<c02af751>] bus_for_each_dev+0x31/0x57
 [<c02afc48>] driver_attach+0x16/0x18
 [<c02af14a>] bus_add_driver+0xec/0x21b
 [<c02b01e5>] driver_register+0x85/0xe2
 [<c024384a>] __pci_register_driver+0x3c/0x6a
 [<c010112b>] _stext+0x3b/0x127
 [<c015001a>] sys_init_module+0x8a/0x19e
 [<c0104c9b>] sysenter_do_call+0x12/0x2f
 [<ffffe430>] 0xffffe430
 =======================
---[ end trace b205ecb8a8180e1b ]---
saa7133[2]: board init: gpio is 0
tuner' 3-004b: chip found @ 0x96 (saa7133[2])
saa7133[2]: i2c eeprom 00: 43 10 45 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[2]: i2c eeprom 10: 00 ff e2 0f ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 88 ff ff ff ff
saa7133[2]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 40: ff 22 00 c2 96 ff 02 30 15 ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[2]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
tda829x 3-004b: setting tuner address to 61
tda829x 3-004b: type set to tda8290+75a
saa7133[2]: registered device video2 [v4l2]
saa7133[2]: registered device vbi2
saa7133[2]: registered device radio2

Any thoughts???

Thanks in advance

[whatboy]

Are you using Baluns??? if not, try them...

[mrkroket]

I'm using this kind of balums:

http://www.eirsec.ie/blog/?p=22



Both 3 cameras are having this behaviour, no matter how far (20m, 40m, 70m). It's random, but it happens 95% of the whole time.

Thanks!

[whatboy]

Power supply stable???

[mrkroket]

I think not. The PC is located on a Warehouse out of the city, so power supply is so so.

Besides that checkerboard problem, I have another one that only happens on the farthest camera (about 80m). It is like an out of sync.

It get really bad on workhours. Out of workhours it shows less distortion.

I suppose this is related to some energy problem, but the checkerboard effect happens to me on any camera!!

The checkerboard effect could bet related to PS?

[mastertheknife]

Yes, power supply and interference can definitely cause such an issue.