TW6805 card - xawtv OK - zmu OK - ZM does not display images

Post here to ask any questions about hardware suitability, configuration in ZoneMinder, or experiences. If you just want to know if something works with ZoneMinder or not, please check the Hardware Compatibility sections in the forum, and the Wiki first. Also search this topic as well.
marnold
Posts: 4
Joined: Thu Feb 25, 2010 11:55 pm

Re: Cant get the Linux driver compiled

Post by marnold »

Hi Steve,

I just noticed that I am having the same errors as what you posted

I am running fedora 12 and updated my kernel today via yum to 2.6.32.12-115.fc12.i686.PAE
When I updated the kernel I also made sure I installed the latest tw68-v2 driver and I also run the latest v4l-dvb linux code to support my tv tuner cards.

I am hoping that thinggs will be fixed soon :-)


Cheers, Mark
steve1611 wrote:I have fedora 12 with kernel 2.6.32.11 and downloaded the modules from gitorious

It seems that i was trying to load the tw68000 driver which failed

i have now compiled the tw68-tw68-v2 driver with no errors.

Driver will not load - can anyone suggest next steps i can take to get it working?

error from dmesg

tw68: v4l2 driver version 0.0.4 loaded
tw6804[0]: found at 0000:00:0a.0, rev: 16, irq: 9, latency: 32, mmio: 0xeb002000
tw6804[0]: subsystem: 0000:0000, board: GENERIC [card=0,autodetected]
tw6804[0]: Unable to determine board type, using generic values
IRQ 9/tw6804[0]: IRQF_DISABLED is not guaranteed on shared IRQs
------------[ cut here ]------------
WARNING: at /usr/local/src/v4l-dvb-16ade09022d9/v4l/v4l2-dev.c:458 __video_register_device+0x48/0x3f5 [videodev]()
Hardware name: P4X266-8233
Modules linked in: snd_seq snd_pcm tw68(+) i2c_viapro snd_timer snd_page_alloc via_ircc snd_mpu401_uart v4l2_common 8139too videodev irda i2c_voodoo3 8139cp v4l1_compat i2c_algo_bit snd_rawmidi videobuf_dma_sg mii i2c_core videobuf_core snd_seq_device snd soundcore crc_ccitt btcx_risc ata_generic pata_acpi pata_via [last unloaded: scsi_wait_scan]
Pid: 291, comm: modprobe Not tainted 2.6.32.11-99.fc12.i686 #1
Call Trace:
[<c043a479>] warn_slowpath_common+0x6a/0x81
[<e0bfa3b4>] ? __video_register_device+0x48/0x3f5 [videodev]
[<c043a4a2>] warn_slowpath_null+0x12/0x15
[<e0bfa3b4>] __video_register_device+0x48/0x3f5 [videodev]
[<e0bfa781>] video_register_device+0xf/0x11 [videodev]
[<e0833cf7>] tw68_initdev+0x963/0xaf3 [tw68]
[<c05ca2cc>] local_pci_probe+0x13/0x15
[<c05cad4d>] pci_device_probe+0x48/0x6b
[<c064f57d>] driver_probe_device+0xca/0x1d2
[<c064f6cd>] __driver_attach+0x48/0x64
[<c064eb8d>] bus_for_each_dev+0x42/0x6c
[<c064f36d>] driver_attach+0x19/0x1b
[<c064f685>] ? __driver_attach+0x0/0x64
[<c064f051>] bus_add_driver+0xd0/0x217
[<c05b8b30>] ? kset_find_obj+0x23/0x4f
[<c064f933>] driver_register+0x7e/0xe5
[<c05caf0f>] __pci_register_driver+0x3d/0x9a
[<e083056d>] ? tw68_init+0x0/0x5d [tw68]
[<e08305c8>] tw68_init+0x5b/0x5d [tw68]
[<c0401143>] do_one_initcall+0x51/0x13f
[<c0469fbc>] sys_init_module+0xac/0x1e0
[<c040365c>] syscall_call+0x7/0xb
---[ end trace 811d1b7ca46eb5b8 ]---
tw6804[0]: can't register video device
tw68: probe of 0000:00:0a.0 failed with error -22

any help appreciated.
agatek
Posts: 6
Joined: Thu May 06, 2010 11:55 pm

Re: tw68 driver updated

Post by agatek »

wbrack wrote:I found another control register on the TW68xx which has a big effect on the resynchronization after switching the chip's input, and I adjusted the initialisation of that register. The updated source is on gitorious.org/tw68.

For multiple cameras per chip, it will be necessary to set the variable CAPTURES_PER_FRAME (on the "config" tag under "options") to at least 2. I think this is because, on the TW68xx chip, the changing of the input takes place immediately, which could easily be in the middle of a frame (I say "I think", because the chip's datasheet isn't clear on this).
Hi Bill, I've been trying to get 6805a working with more than one camera. The card works fine with xawtv when switching the channels manually and with zm but only with a single camera. As soon as another one for the same chip is added both channels are affected and this is not a small interference like I can see from pics of this thread. It is a total out of sync mess. Sometimes I can even observe that the capture channels are swapped so what was channel0 disappears somehow and receives the cam attached to composite1. At the same time a monitor with the channel1 show out of sync mess. I tried different values of CAPTURES_PER_FRAME (up to 8 ) with no apparent effect. Any ideas?
vol4enok
Posts: 1
Joined: Tue Jul 13, 2010 7:12 am

Post by vol4enok »

Forgive for my English. Please prompt in what a problem of such distortions at object movement in a shot. In advance thanks. The chip tw6805a

ImageImage

OS Ubuntu 9.10
moorsey
Posts: 53
Joined: Sun Jan 03, 2010 8:56 am

Post by moorsey »

from my limited knowledge, this is called interlacing, one full frame is made up from every 2 frames, so only alternate lines are captured every frame. Any movement during this process causes interlacing and the effect you are seeing. This is a limitation of PAL/NTSC

PAL resolution is 720x576, so you can only use half that to get rid of the effect - 360x288.

I believe there is a way of de-interlacing the video at the cost of extra CPU usage, I half not looked into this though, but would like to if it is easy enough
agatek
Posts: 6
Joined: Thu May 06, 2010 11:55 pm

Re: tw68 driver updated

Post by agatek »

agatek wrote:I've been trying to get 6805a working with more than one camera. The card works fine with xawtv when switching the channels manually and with zm but only with a single camera. As soon as another one for the same chip is added both channels are affected and this is not a small interference like I can see from pics of this thread. It is a total out of sync mess. Sometimes I can even observe that the capture channels are swapped so what was channel0 disappears somehow and receives the cam attached to composite1. At the same time a monitor with the channel1 show out of sync mess. I tried different values of CAPTURES_PER_FRAME (up to 8 ) with no apparent effect. Any ideas?
Replying to my own post: problem seems to be solved. What helped was to specify the resolution of the imgs of the individual cameras as a multiplier of VGA resolution (i.e. 640x480, 320x240, 480x360 etc.) rather than the actual resolutions of the cameras.
Nik4444
Posts: 2
Joined: Tue Jul 13, 2010 9:52 pm

Post by Nik4444 »

Hi all and thanks for the work you put in this driver!
I've got a TW6864 based pci-e card, and I've tried to compile the driver in Ubuntu 10.04. Everything seems to be fine, 'make install' builds and loads the module tw68.ko in the kernel, as seen by using lsmod. BUT.... No /dev/video0 has been created, so I'm very stuck, what should I do now?
Looking at the driver source I've seen no direct references to TW6864 chipset, only 6800 and few others, even if somewhere I saw something like TW68XX that makes me think that MAYBE there is some kind of support for unknown TW's devices (like TW6864). So my question is: am I doing something wrong in compiling or the lack of /dev/video0 is caused by my unsupported chipset?
luisbriones
Posts: 3
Joined: Tue Aug 17, 2010 7:33 pm

Post by luisbriones »

Hi,

I´m new in Linux and Zone Minder

I try to install the program in a Duron 1Ghz with 256mb of RAM

SO: Ubuntu server 10.04

My video card is this:

Image

with this chipset:

Image

I run this:

make insmod

Code: Select all

eroclub@Video:~/tw68-v2$ make insmod
make -C /lib/modules/2.6.32-24-generic/build M=/home/aeroclub/tw68-v2 modules
make[1]: se ingresa al directorio `/usr/src/linux-headers-2.6.32-24-generic'
  CC [M]  /home/aeroclub/tw68-v2/tw68-core.o
  CC [M]  /home/aeroclub/tw68-v2/tw68-cards.o
  CC [M]  /home/aeroclub/tw68-v2/tw68-video.o
  CC [M]  /home/aeroclub/tw68-v2/tw68-vbi.o
  CC [M]  /home/aeroclub/tw68-v2/tw68-ts.o
  CC [M]  /home/aeroclub/tw68-v2/tw68-risc.o
  CC [M]  /home/aeroclub/tw68-v2/tw68-tvaudio.o
  LD [M]  /home/aeroclub/tw68-v2/tw68.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/aeroclub/tw68-v2/tw68.mod.o
  LD [M]  /home/aeroclub/tw68-v2/tw68.ko
make[1]: se sale del directorio `/usr/src/linux-headers-2.6.32-24-generic'
lspci

Code: Select all

aeroclub@Video:~/tw68-v2$ lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02)
00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 82)
00:01.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 07)
00:01.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 07)
00:01.4 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS PCI Audio Accelerator (rev 02)
00:01.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0)
00:02.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:09.0 Multimedia video controller: Techwell Inc. TW6802 multimedia video card (rev 10)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 630/730 PCI/AGP VGA Display Adapter (rev 31)
lspci | grep 68

Code: Select all

aeroclub@Video:~/tw68-v2$ lspci | grep 68
00:09.0 Multimedia video controller: Techwell Inc. TW6802 multimedia video card (rev 10)
lspci -n

Code: Select all

aeroclub@Video:~/tw68-v2$ lspci -n
00:00.0 0600: 1039:0730 (rev 02)
00:00.1 0101: 1039:5513 (rev d0)
00:01.0 0601: 1039:0018
00:01.1 0200: 1039:0900 (rev 82)
00:01.2 0c03: 1039:7001 (rev 07)
00:01.3 0c03: 1039:7001 (rev 07)
00:01.4 0401: 1039:7018 (rev 02)
00:01.6 0703: 1039:7013 (rev a0)
00:02.0 0604: 1039:0001
00:09.0 0400: 1797:6801 (rev 10)
01:00.0 0300: 1039:6300 (rev 31)
I understant that the driver is not working.

Anybody can help me?

Regards,

Luis
Nik4444
Posts: 2
Joined: Tue Jul 13, 2010 9:52 pm

Post by Nik4444 »

@ luisbriones,

after "make insmod" try "make run" and look if mplayer starts to capture from your board. With another card i also tried "make install" and after then it worked (it was tw6805A chipset).

Also look with "lsmod" if tw68 is loaded as a module.


In my case (TW6868 - TW6864) nothing happens and mplayer exit whith an error, because no /video0 - 1 - 2... devices were generated, even if the module builds fine and installs with no errors.

Looking better with lspci i found that my board is "seen" by the system as "unknown non-vga device" (or something like this...), probably this is the real problem for me.

Aloha
micwong88
Posts: 1
Joined: Tue Aug 31, 2010 1:11 pm

My experience on TW6805A

Post by micwong88 »

Just want to share my experience on a TW6805A chipset capture card.
I buy the card in here.
http://cgi.ebay.com.au/H-264-4Ch-DVR-PC ... 777wt_1110
The chipset actually is TW6805A.

01:00.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
01:00.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)

I setup a Ubuntu 10.04 with latest patch, 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:12:52 UTC 2010 i686 GNU/Linux
My PC is a Pentium 4 with 1G ram
I use tw68-v2 driver from git://gitorious.org/tw68/tw68-v2.git (Version as of 22 June 2010) and complied and install it using "make install". Then I reboot the linux afterward.
I use the ubuntu respository to install zoneminder with default setting.
Then, I follow the instruction http://www.zoneminder.com/wiki/index.ph ... rom_a_.deb to do patching. (Xawtv and mplayer is working but zmu is not until I do this patching.)
For video setup, here is my setting.
Device Path: /dev/video0
Capture Method: Video for Linux version 1
Device Channel: 0 (0-3 for all 4 channels)
Device Format: AUTO
Capture Palette: RGB24
Capture Width (pixels): 720
Capture Height (pixels): 576
Preserve Aspect Ratio : Not Checked
Orientation : Normal

I have tried to use Video for Linux version 2 with the same setting as other and never make it video as I can see the video but "interlace" 2 video image each other even I lowed the resolution to 384x288 and still interlace.
For 720x576 in V4L, it is the highest resolution I get. Anything higher than that, (I have try 721x576) the image start "sloping". If change the width to higher, the images "interlace" again.

For Palette, I have tried any YUV palette and it make the video keep circulate all video inputs. For any RGB palette, it works prefect.

For other setting, I haven't changed at all. For proving my setting, I have format the linux box and reinstall everything again with my setting and procedure and it work fine again.

Also, there is 1 more tip. If the capture card do not work, try to put it on other PCI slot.

Hopefully, it can help anyone.
veritech
Posts: 4
Joined: Fri Jul 11, 2008 4:47 pm

Green Screen

Post by veritech »

I have a Q-See card with the tw6800 (4 channel)

I am running Ubuntu 10, downloaded the driver from git://gitorious.org/tw68/tw68-v2.git, ran make; make install

/dev/video0 is now present. but when I run
test -x /usr/bin/mplayer && mplayer tv:// -tv device=/dev/video0:outfmt=yuy2:normid=3:width=640:height=480

mplayer shows a green screen. Zoneminder shows source /dev/video0(0) in red.

any suggestions?

Thanks
veritech
Posts: 4
Joined: Fri Jul 11, 2008 4:47 pm

I got further

Post by veritech »

I did a fresh install of Ubuntu 10 and followed the instructions for zoneminder at http://viktorpetersson.com/2010/05/23/h ... ts-server/

I downloaded and made the tw68-v2 drivers.

during the testing I discovered that if I set the camera to NTSC/YUYV I get a green screen. Even under mplayer. I change it to PAL, I get an image.

Seems to be an issue with the driver.

I also added www-data to video and kmem groups and changed the SHM_KEY in options to 0x4b450000

it seems to be working, even though the bottom 10% of the image is interlaced or just black. (probably a PAL/NTSC issue, but colour is fine)

Code: Select all

zmu -d /dev/video0 -q -v
Video Device: /dev/video0
General Capabilities
  Driver: tw68
  Card: GENERIC
  Bus: PCI:0000:02:07.0
  Version: 0.0.4
  Type: 0x5000011
    Supports video capture (X)
    Does not support video output
    Does not support frame buffer overlay
    Supports VBI capture
    Does not support VBI output
    Does not support sliced VBI capture
    Does not support sliced VBI output
    Does not support video output overlay
    Does not have tuner
    Does not have audio in and/or out
    Does not have radio
    Supports read/write i/o (X)
    Does not support async i/o
    Supports streaming i/o (X)
    Standards:
      NTSC
      NTSC-M
      NTSC-M-JP
      NTSC-M-KR
      NTSC-443
      PAL
      PAL-BG
      PAL-H
      PAL-I
      PAL-DK
      PAL-M
      PAL-N
      PAL-Nc
      PAL-60
      SECAM
      SECAM-B
      SECAM-G
      SECAM-H
      SECAM-DK
      SECAM-L
      SECAM-Lc
  Formats:
    15 bpp RGB, le (RGBO)
    15 bpp RGB, be (RGBQ)
    16 bpp RGB, le (RGBP)
    16 bpp RGB, be (RGBR)
    24 bpp RGB, le (BGR3)
    24 bpp RGB, be (RGB3)
    32 bpp RGB, le (BGR4)
    32 bpp RGB, be (RGB4)
    4:2:2 packed, YUYV (YUYV)
    4:2:2 packed, UYVY (UYVY)
Crop Capabilities
  Bounds: 720 x 288
  Default: 720 x 288
  Current: 720 x 288
Inputs: 4
  Input 0
    Name: Composite1
    Type: Camera
    Audioset: 00000001
    Standards: 0xffffff
    Power on  (X)
    Signal detected  (X)
    Colour Signal detected
    Horizontal Lock not detected
  Input 1
    Name: Composite2
    Type: Camera
    Audioset: 00000001
    Standards: 0xffffff
    Power on  (X)
    Signal detected  (X)
    Colour Signal detected
    Horizontal Lock detected
  Input 2
    Name: Composite3
    Type: Camera
    Audioset: 00000001
    Standards: 0xffffff
    Power on  (X)
    Signal detected  (X)
    Colour Signal detected
    Horizontal Lock detected
  Input 3
    Name: Composite4
    Type: Camera
    Audioset: 00000001
    Standards: 0xffffff
    Power on  (X)
    Signal detected  (X)
    Colour Signal detected
    Horizontal Lock detected
[/code]
wdeninger
Posts: 5
Joined: Mon Nov 08, 2010 12:21 am

Techwell 6805 card (OWL-6832)

Post by wdeninger »

I've been considering purchacing the a Techwell 6805 16 channel 480fps card in comparison to the ISIS1642 8 channel card, but I'm finding the marketing literature a little vague when it comes to recording resolution.

The ISIS1642 claims: Resolution: 640*480,640*240,320*240 for ntsc 768*576, 768*288,384*288 for pal

http://www.anykeeper.com/isis-1624-16-c ... 00fps.html

and the Techwell card says: Resolution: 160X120 / 240X180 / 320X240 / 352X288 / 480X360 / 640X480

http://www.cctvcamera.martbase.com/Tech ... s_P105077/

But neither state whether the "resolution" is recording or playback. And the resolutions specified for the Techwell card seem a bit odd.

Does anyone here have any strong opinions regarding these two cards?

-W

jasper314
Posts: 1
Joined: Mon Dec 27, 2010 11:31 pm

tw6816

Post by jasper314 »

Hi,
I have a Techwell pci card based on the 6816 chipset. I have managed to make it work partially (The card has 8 video inputs, I can get 4 to work).
I had to change the source code of the tw68 driver a bit for this. (I know C, but I don't really know anything about Linux kernel drivers. The change is pretty trivial, which is the reason I was able to do this...)

I thought I'd share my experience as it might be helpful for others with the same card, or a similar one. Obviously, I would be interested if anyone has any idea on how to get the remaining 4 inputs to work.

I am running debian squeeze with kernel
Linux cam 2.6.32-5-686 #1 SMP Fri Dec 10 16:12:40 UTC 2010 i686 GNU/Linux

Doing a
lspci -n | grep 1797
shows this (the grep is just to filter out non-related hardware)

Code: Select all

02:08.0 0400: 1797:6810 (rev 10)
02:08.1 0400: 1797:6811 (rev 10)
02:08.2 0400: 1797:6812 (rev 10)
02:08.3 0400: 1797:6813 (rev 10)
02:08.4 0480: 1797:6814 (rev 10)
02:08.5 0480: 1797:6815 (rev 10)
02:08.6 0480: 1797:6816 (rev 10)
02:08.7 0480: 1797:6817 (rev 10)
The tw68 driver does not recognize these pci devices, but it turns out it will work fine with the first 4 devices if it would recognize them. We can make the driver recognize the devices by modifying the source code a bit. In the file tw68-cards.c, look for the line

Code: Select all

struct pci_device_id tw68_pci_tbl[] = {
Below that you'll see definitions for the 6800, 6801 and 6804 cards. Copy and paste 4 times one such definition, and change the number to 6810, 6811, 6812 and 6813.
Then, in the tw68.h file, look up the line

Code: Select all

#define PCI_DEVICE_ID_6804      0x6804
cope and paste 4 times, and change the number again to 6810, 6811, 6812 and 6813.
Now do a make and make install, and reboot. With some luck, you should have the /dev/video0 to /dev/video3 devices.

About my attempts to make the other 4 inputs work:
Adding any of the remaining pci ids 6814, 6815, 6816 and 6817 in the same way does not create a new /dev/video device, and produces some error messages in dmesg. Even removing the 6810 to 6813 ones, and only include 6814 does not work (so it is a problem with the device, not the fact that it is the 5th one). The 4 remaining devices are a bit different in that they don't come with audio inputs on the card. I also noted that the lspci lists them with the number 0480 instead of 0400, although I don't know what that number means. Below is part of my dmesg, created with 5 devices defined in the source. It shows 6810 to 6813 loading fine, and the problems with loading 6814.
Anyone any ideas?

Code: Select all

[    8.844884] Linux video capture interface: v2.00
[    8.891688] tw68: v4l2 driver version 0.0.4 loaded
[    8.891739] tw68 0000:02:08.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    8.891747] tw6810[0]: found at 0000:02:08.0, rev: 16, irq: 17, latency: 64, mmio: 0xfcfdf000
[    8.891755] tw6810[0]: subsystem: 1797:6810, board: GENERIC [card=0,autodetected]
[    8.891783] tw6810[0]: Unable to determine board type, using generic values
[    8.992029] IRQ 17/tw6810[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[    8.992616] tw6810[0]: registered device video0 [v4l2]
[    8.993100] tw6810[0]: registered device vbi0
[    8.993134] tw68 0000:02:08.1: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    8.993142] tw6811[1]: found at 0000:02:08.1, rev: 16, irq: 17, latency: 64, mmio: 0xfcfdf400
[    8.993149] tw6811[1]: subsystem: 1797:6811, board: GENERIC [card=0,autodetected]
[    8.993187] tw6811[1]: Unable to determine board type, using generic values
[    9.096027] IRQ 17/tw6811[1]: IRQF_DISABLED is not guaranteed on shared IRQs
[    9.096581] tw6811[1]: registered device video1 [v4l2]
[    9.097059] tw6811[1]: registered device vbi1
[    9.097095] tw68 0000:02:08.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    9.097102] tw6812[2]: found at 0000:02:08.2, rev: 16, irq: 17, latency: 64, mmio: 0xfcfdf800
[    9.097110] tw6812[2]: subsystem: 1797:6812, board: GENERIC [card=0,autodetected]
[    9.097147] tw6812[2]: Unable to determine board type, using generic values
[    9.192618] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[    9.200038] IRQ 17/tw6812[2]: IRQF_DISABLED is not guaranteed on shared IRQs
[    9.200129] tw6812[2]: registered device video2 [v4l2]
[    9.200165] tw6812[2]: registered device vbi2
[    9.200193] tw68 0000:02:08.3: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    9.200201] tw6813[3]: found at 0000:02:08.3, rev: 16, irq: 17, latency: 64, mmio: 0xfcfdfc00
[    9.200208] tw6813[3]: subsystem: 1797:6813, board: GENERIC [card=0,autodetected]
[    9.200243] tw6813[3]: Unable to determine board type, using generic values
[    9.260148] [drm] Initialized drm 1.1.0 20060810
[    9.304032] IRQ 17/tw6813[3]: IRQF_DISABLED is not guaranteed on shared IRQs
[    9.304134] tw6813[3]: registered device video3 [v4l2]
[    9.304165] tw6813[3]: registered device vbi3
[    9.304196] tw68 0000:02:08.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    9.304204] tw6814[4]: found at 0000:02:08.4, rev: 16, irq: 17, latency: 64, mmio: 0xfcfdee00
[    9.304211] tw6814[4]: subsystem: 1797:6814, board: GENERIC [card=0,autodetected]
[    9.304249] tw6814[4]: Unable to determine board type, using generic values
[    9.304266] BUG: unable to handle kernel paging request at f8385018
[    9.304392] IP: [<f82b263a>] tw68_initdev+0x53b/0xba6 [tw68]
[    9.304486] *pde = 36f93067 *pte = 00000000 
[    9.304607] Oops: 0002 [#1] SMP 
[    9.304726] last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:02:08.2/video4linux/vbi2/index
[    9.304778] Modules linked in: drm i2c_i801 i2c_algo_bit tw68(+) v4l2_common videodev v4l1_compat i2c_core videobuf_dma_sg videobuf_core btcx_risc parport_pc parport rng_core pcspkr dcdbas evdev psmouse processor button shpchp pci_hotplug serio_raw ext3 jbd mbcache sg sr_mod cdrom sd_mod crc_t10dif usbhid hid ata_generic uhci_hcd ata_piix thermal ehci_hcd floppy e1000 libata thermal_sys scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan]
[    9.306664] 
[    9.306707] Pid: 442, comm: modprobe Not tainted (2.6.32-5-686 #1) OptiPlex GX270               
[    9.306758] EIP: 0060:[<f82b263a>] EFLAGS: 00010286 CPU: 0
[    9.306809] EIP is at tw68_initdev+0x53b/0xba6 [tw68]
[    9.306855] EAX: f8385018 EBX: 00000080 ECX: f65e5eb8 EDX: f8384e00
[    9.306903] ESI: 00000800 EDI: 00000000 EBP: f6640000 ESP: f65e5ec4
[    9.306959]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[    9.307016] Process modprobe (pid: 442, ti=f65e4000 task=f661aec0 task.ti=f65e4000)
[    9.307083] Stack:
[    9.307134]  f6cb2000 f6640030 00000000 f6640120 f82b47e4 f6cb2000 f82b47b4 f82b47e4
[    9.307460] <0> c1145dbd c1146707 f82b47b4 f6cb2000 f82b5244 f6cb205c ffffffed f82b47e4
[    9.307872] <0> c11b2bf2 f6cb205c f82b47e4 f6cb2090 c11b2cc6 f82b47b4 00000000 c13a1584
[    9.308003] Call Trace:
[    9.308003]  [<c1145dbd>] ? local_pci_probe+0xb/0xc
[    9.308003]  [<c1146707>] ? pci_device_probe+0x41/0x63
[    9.308003]  [<c11b2bf2>] ? driver_probe_device+0x8a/0x11e
[    9.308003]  [<c11b2cc6>] ? __driver_attach+0x40/0x5b
[    9.308003]  [<c11b2635>] ? bus_for_each_dev+0x37/0x5f
[    9.308003]  [<c11b2ac5>] ? driver_attach+0x11/0x13
[    9.308003]  [<c11b2c86>] ? __driver_attach+0x0/0x5b
[    9.308003]  [<c11b20fd>] ? bus_add_driver+0x99/0x1c5
[    9.308003]  [<c11b2ef7>] ? driver_register+0x87/0xe0
[    9.308003]  [<f82af549>] ? tw68_init+0x0/0x56 [tw68]
[    9.308003]  [<c11468d8>] ? __pci_register_driver+0x33/0x89
[    9.308003]  [<f82af549>] ? tw68_init+0x0/0x56 [tw68]
[    9.308003]  [<c100113e>] ? do_one_initcall+0x55/0x155
[    9.308003]  [<c1057375>] ? sys_init_module+0xa7/0x1d7
[    9.308003]  [<c10030fb>] ? sysenter_do_call+0x12/0x28
[    9.308003] Code: 20 89 38 8b 85 4c 01 00 00 83 ca ff 83 c0 1c 89 10 b8 00 16 00 00 8b 95 4c 01 00 00 89 02 8b 85 50 01 00 00 b3 80 05 18 02 00 00 <88> 18 b8 64 00 00 00 e8 f7 88 d8 c8 8b 85 50 01 00 00 b2 40 05 
[    9.308003] EIP: [<f82b263a>] tw68_initdev+0x53b/0xba6 [tw68] SS:ESP 0068:f65e5ec4
[    9.308003] CR2: 00000000f8385018
[    9.308003] ---[ end trace 5998a93b50cbdc13 ]---
yurys
Posts: 6
Joined: Mon Dec 06, 2010 8:41 am

Post by yurys »

Good afternoon!
I have card techwell 6805 with 32 channels.

http://www.techwellinc.com/products/bro ... TW6805.pdf
http://www.orientrus.ru/shop/UID_472.html

lspci | grep 68
02:04.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
02:04.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)
02:05.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
02:05.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)
02:06.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
02:06.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)
02:07.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
02:07.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)
02:08.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
02:08.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)
02:09.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
02:09.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)
02:0a.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
02:0a.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)
02:0b.0 Multimedia video controller: Techwell Inc. Device 6804 (rev 10)
02:0b.1 Multimedia controller: Techwell Inc. Device 6805 (rev 10)

ls/dev/video*
/dev/video0/dev/video2/dev/video4/dev/video6
/dev/video1/dev/video3/dev/video5/dev/video7

By experiences I have come to following options zoneminder to best quality:
CAPTURES_PER_FRAME 4
Maximum FPS 4
Device Format NTSC
Capture Palette BGR24
Capture Width (pixels) 320
Capture Height (pixels) 240

If 4 cameras on the chip, the image black-and-white, State work: Idle - 1.54 fps.

If 2 cameras on the chip, the image colour/black-and-white, State: Idle - 3.27 fps.

Also 32 devices work not all, some show the black screen.

I need to connect 23 cameras.

Somebody solved such problem?
Such 2 cards on one computer will work?
c0nf
Posts: 2
Joined: Thu Mar 10, 2011 10:59 am

Post by c0nf »

im running ubuntu 10.10 server, and when i try to make driver for my tw6805, this is what happened.


root@server:~/tw68-v2# make
make -C /lib/modules/2.6.35-27-generic-pae/build M=/root/tw68-v2 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.35-27-generic-pae'
CC [M] /root/tw68-v2/tw68-core.o
/root/tw68-v2/tw68-core.c: In function ‘tw68_dma_free’:
/root/tw68-v2/tw68-core.c:113: warning: passing argument 1 of ‘videobuf_waiton’ from incompatible pointer type
include/media/videobuf-core.h:172: note: expected ‘struct videobuf_buffer *’ but argument is of type ‘struct videobuf_queue *’
/root/tw68-v2/tw68-core.c:113: warning: passing argument 2 of ‘videobuf_waiton’ makes integer from pointer without a cast
include/media/videobuf-core.h:172: note: expected ‘int’ but argument is of type ‘struct videobuf_buffer *’
/root/tw68-v2/tw68-core.c:113: error: too many arguments to function ‘videobuf_waiton’
make[2]: *** [/root/tw68-v2/tw68-core.o] Error 1
make[1]: *** [_module_/root/tw68-v2] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.35-27-generic-pae'
make: *** [all] Error 2

can anyone help me with this error ?
Post Reply