Connexant cx25821 help
I have a PCI-E capture card with two connexant cx25821 chips. 04:00.0 Multimedia video controller: Conexant Systems, Inc. Device 8210 05:00.0 Multimedia video controller: Conexant Systems, Inc. Device 8210 There is a staging driver in latest linux kernels. Looks like it uses v4l2 api. I tried to use precompiled module cx25821 provided with Ubuntu 10.10 beta (2.6.35-19-generic #28-Ubuntu SMP Sun Aug 29 06:36:51 UTC 2010 i686 GNU/Linux). # modprobe cx25821 The module looks like to be loaded successfully. # lsmod | grep cx cx25821 108646 0 v4l2_common17329 1 cx25821 videodev 43098 2 cx25821,v4l2_common videobuf_dma_sg 9806 1 cx25821 videobuf_core 16907 2 cx25821,videobuf_dma_sg btcx_risc 3636 1 cx25821 tveeprom 11178 1 cx25821 dmesg says: [ 1980.986232] Linux video capture interface: v2.00 [ 1980.989245] cx25821: module is from the staging directory, the quality is unknown, you have been warned. [ 1980.993152] cx25821 driver version 0.0.106 loaded And now I can not see any /dev/video0-7 devices to get input from the card. I'l greatly appreciate if someone could tell me about additional actions to make this work. Thank you. Roman -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: cx88_alsa - getting loud white noise with capture card.
Just revisiting this again after close to 2 years - still experiencing the same. Loud static like sound. Tried a few CX23881 cards and it seems the same :( I'm doing: arecord -D hw:1,0 -f dat test.wav I tried it for all the CX8801 audio sources (8 chip DVR card), here are the output wav files and waveforms: http://itstar.co.uk/CX8801_Audio Any ideas at all? Roman On 11 November 2009 09:12, Roman Gaufman wrote: > > It sounds like I've not tuned the channel, but there is no channel - > it's a capture card with 8 inputs. When I try to change channels with > mplayer 'h' key, the sound changes slightly and I can hear it turn > sound off and turn it back on. > > Is there a specific frequency I need to set? - I tried all channels > available in mplayer and all I hear is loud static/white noise. > > Anyone? > > 2009/11/10 Roman Gaufman : > > Tried this again on 2.6.31-14 and still not able to get audio working. > > Using this command: > > > > mplayer -vo null tv:// -tv > > driver=v4l2:device=/dev/video1:alsa:adevice=hw.2,0:amode=1:audiorate=48000:forceaudio:volume=100:immediatemode=0:norm=PAL-BG:fps=25:input=0 > > > > Video works but getting nothing but loud static on audio. Please help :( > > > > > > 2008/8/3 Roman Gaufman : > >> Hi, > >> > >> I have an 8 audio + 8 video PCI-Express Conexant 23881 DVR Card I'm > >> trying to get working in Linux. > >> > >> The video channels all work flawlessly and the audio is recognized, > >> but I just get very loud white noise no matter what I try. > >> > >> I tried the following commands and been googling for days to no avail: > >> > >> for i in 0 1 2 3 4 5 6 7; do /usr/bin/mencoder tv:// -tv > >> driver=v4l2:device=/dev/video$i:alsa:adevice=hw.$i,0:amode=0:audiorate=32000:volume=100:immediatemode=0:norm=PAL-DK:input=0:width=720:height=576:outfmt=yuy2 > >> -oac mp3lame -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=5000 -frames > >> 300 -o test$i.avi & done > >> > >> for i in 0 1 2 3 4 5 6 7; do arecord -d 10 -D hw:$i,0 -c 2 -f S16_LE > >> --period-size=65536 --buffer-size=524288 -r 48000 test$i.wav & done > >> > >> I had to boot the kernel with acpi=off irqpoll for video not to give > >> me input/output errors, but audio still gives me loud white noise. > >> > >> The only error messages I see are: > >> > >> [ 3758.546252] cx88[4]/1: IRQ loop detected, disabling interrupts > >> [ 3758.546323] cx88[4]: irq aud [0x1000] dn_sync* > >> [ 3758.546329] cx88[4]: irq aud [0x1001] dn_risci1* dn_sync* > >> > >> My bios Plug & Play OS setting is set to no. > >> > >> This is what arecord -l returns: > >> > >> List of CAPTURE Hardware Devices > >> card 0: CX8801_1 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > >> Subdevices: 1/1 > >> Subdevice #0: subdevice #0 > >> card 1: CX8801 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > >> Subdevices: 1/1 > >> Subdevice #0: subdevice #0 > >> card 2: CX8801_2 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > >> Subdevices: 1/1 > >> Subdevice #0: subdevice #0 > >> card 3: CX8801_3 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > >> Subdevices: 1/1 > >> Subdevice #0: subdevice #0 > >> card 4: CX8801_4 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > >> Subdevices: 1/1 > >> Subdevice #0: subdevice #0 > >> card 5: CX8801_5 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > >> Subdevices: 1/1 > >> Subdevice #0: subdevice #0 > >> card 6: CX8801_6 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > >> Subdevices: 1/1 > >> Subdevice #0: subdevice #0 > >> card 7: CX8801_7 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > >> Subdevices: 1/1 > >> Subdevice #0: subdevice #0 > >> > >> This is what lspci -v returns (both with and without -n) > >> > >> - [ ] 04:07.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI > >> Video and Audio Decoder (rev 05) > >> Subsystem: Unknown device c180:c980 > >> Flags: bus master, medium devsel, latency 64, IRQ 19 > >> Memory at d000 (32-bit, non-prefetchable) [size=16M] > >> Capabilities: [44] Vital Product Data > >> Capabilities: [4c] Power Management version 2 > >> - [ ] 04:07.0 0400: 14f1:8800 (rev 05) > >> Subsystem: c
Re: Connexant cx25821 help
I figured as much, but what can I do now? Should I take some high resolution pictures of the board? Any other details I can provide to help developers add support for this board? Is there anyone in particularly I should contact? Anywhere I can post any information I collect on this board? I'm happy to donate this board if someone wants to help add support for it. On 22 May 2011 02:37, Devin Heitmueller wrote: > > Just because there is a driver for whatever chipset your board happens > to have, doesn't mean that your board is actually supported. The > definition of a product is more than just the chips that are on it. > >> # modprobe cx25821 > > You should *never* have to manually modprobe. If you ran modprobe, > then that means the driver does not know about the PCI ID for your > board. > >> The module looks like to be loaded successfully. > >> And now I can not see any /dev/video0-7 devices to get input from the card. >> I'l greatly appreciate if someone could tell me about additional actions to >> make this work. > > The /dev/video devices will not be created if the driver did not > associate with the card. Basically what you did is the equivalent of > modprobing any driver in the system regardless of whether or not it > has anything to do with the actual hardware you happen to have. > > Somebody would likely have to do work to modify the driver to support > your board. This would mean a driver developer who actually cared > enough to do the work would have to have one of the boards, which > doesn't appear to be the case at this point. > > Hope that helps (or at least it makes clear that this board will not > just start to magically work just because you have a card which > contains the chips involved). > > Devin > > -- > Devin J. Heitmueller - Kernel Labs > http://www.kernellabs.com > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Connexant cx25821 help
On 22 May 2011 04:11, Devin Heitmueller wrote: > On Sat, May 21, 2011 at 10:25 PM, Roman Gaufman wrote: >> I figured as much, but what can I do now? > > Your options at this point are: > > 1. Find some developer who cares enough to take a free board just for > the fun of making it work. Any suggestions where? > 2. If you're a commercial entity, hire somebody to do the work > (Kernel Labs does this sort of work) I have a small company that consists of just me and I'm broke, heh, but I'll check out kernel labs thanks! > 3. Learn enough about driver development to add the support yourself. Any suggestions where/how to start? - are there any guides/tutorials that show how to go from start to finish getting a board to work? > > The reality is that the LinuxTV project is grossly understaffed > already, and if you're a regular user who wants a working product, > your best bet is to just buy something that is already supported. All > other options require either a considerable investment in money (to > pay someone to do the work), or time (to learn how to do it yourself). Do you have any recommendations for a DVR card that has 8 or 16 audio+video inputs that's already supported by linux available for sale? The problem is I can't find anything that's already supported, so I'm just trying random cards. I bought one with SAA7134 chips that happened to work, but they stopped making it. The problem is I can't find anything supported that's available for sale. It seems quite the opposite, only rare obscure cards that are no longer sold are supported :/ > > Developers who care enough to contribute to the project typically have > no shortage of boards at their disposal, and they tend to focus their > energy on where you get the most bang for the buck. This tends to > favor products that are more popular, which is why the cx25821 driver > has gotten almost zero attention (since there are almost no actual > products using it other than Conexant reference designs). > >> Should I take some high resolution pictures of the board? >> Any other details I can provide to help developers add support for this >> board? >> Is there anyone in particularly I should contact? >> Anywhere I can post any information I collect on this board? > > You can create an entry on the LinuxTV wiki with the board details. > Of course no guarantee that anybody will do anything with it (in fact, > the less popular the board, the less likely for this to be the case). This is a board from http://securitycamera2000.com and is one of the few boards that pop up when looking for a DVR card on google and ebay. I will create an entry on the LinuxTV wiki, thanks! > > Devin > > -- > Devin J. Heitmueller - Kernel Labs > http://www.kernellabs.com > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Connexant cx25821 help
On 22 May 2011 12:21, Andy Walls wrote: > > Bluecherry might have a product that meet your needs: > > http://store.bluecherry.net/products/PV%252d155-%252d-16-port-video-capture-card-%28120FPS%29.html > > I have no actual experience with their products myself. I'm interested first and foremost in audio inputs. That card has no audio at all :( > > Regards, > Andy > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: cx88_alsa - getting loud white noise with capture card.
I found out cards like BlueCherry set the format wrong because of a limitation in Alsa. The audio input is G723 but the format is set as 8khz PCM - maybe something like this is happening here? Anyone able to get usable audio out of a CX88 or CX23881 card? I'm getting something, but it sounds like pink noise just like out of the BlueCherry card. Roman On 22 May 2011 03:21, Roman Gaufman wrote: > > Just revisiting this again after close to 2 years - still experiencing > the same. Loud static like sound. Tried a few CX23881 cards and it > seems the same :( > > I'm doing: arecord -D hw:1,0 -f dat test.wav > > I tried it for all the CX8801 audio sources (8 chip DVR card), here > are the output wav files and waveforms: > http://itstar.co.uk/CX8801_Audio > > Any ideas at all? > > Roman > > > On 11 November 2009 09:12, Roman Gaufman wrote: > > > > It sounds like I've not tuned the channel, but there is no channel - > > it's a capture card with 8 inputs. When I try to change channels with > > mplayer 'h' key, the sound changes slightly and I can hear it turn > > sound off and turn it back on. > > > > Is there a specific frequency I need to set? - I tried all channels > > available in mplayer and all I hear is loud static/white noise. > > > > Anyone? > > > > 2009/11/10 Roman Gaufman : > > > Tried this again on 2.6.31-14 and still not able to get audio working. > > > Using this command: > > > > > > mplayer -vo null tv:// -tv > > > driver=v4l2:device=/dev/video1:alsa:adevice=hw.2,0:amode=1:audiorate=48000:forceaudio:volume=100:immediatemode=0:norm=PAL-BG:fps=25:input=0 > > > > > > Video works but getting nothing but loud static on audio. Please help :( > > > > > > > > > 2008/8/3 Roman Gaufman : > > >> Hi, > > >> > > >> I have an 8 audio + 8 video PCI-Express Conexant 23881 DVR Card I'm > > >> trying to get working in Linux. > > >> > > >> The video channels all work flawlessly and the audio is recognized, > > >> but I just get very loud white noise no matter what I try. > > >> > > >> I tried the following commands and been googling for days to no avail: > > >> > > >> for i in 0 1 2 3 4 5 6 7; do /usr/bin/mencoder tv:// -tv > > >> driver=v4l2:device=/dev/video$i:alsa:adevice=hw.$i,0:amode=0:audiorate=32000:volume=100:immediatemode=0:norm=PAL-DK:input=0:width=720:height=576:outfmt=yuy2 > > >> -oac mp3lame -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=5000 -frames > > >> 300 -o test$i.avi & done > > >> > > >> for i in 0 1 2 3 4 5 6 7; do arecord -d 10 -D hw:$i,0 -c 2 -f S16_LE > > >> --period-size=65536 --buffer-size=524288 -r 48000 test$i.wav & done > > >> > > >> I had to boot the kernel with acpi=off irqpoll for video not to give > > >> me input/output errors, but audio still gives me loud white noise. > > >> > > >> The only error messages I see are: > > >> > > >> [ 3758.546252] cx88[4]/1: IRQ loop detected, disabling interrupts > > >> [ 3758.546323] cx88[4]: irq aud [0x1000] dn_sync* > > >> [ 3758.546329] cx88[4]: irq aud [0x1001] dn_risci1* dn_sync* > > >> > > >> My bios Plug & Play OS setting is set to no. > > >> > > >> This is what arecord -l returns: > > >> > > >> List of CAPTURE Hardware Devices > > >> card 0: CX8801_1 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > > >> Subdevices: 1/1 > > >> Subdevice #0: subdevice #0 > > >> card 1: CX8801 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > > >> Subdevices: 1/1 > > >> Subdevice #0: subdevice #0 > > >> card 2: CX8801_2 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > > >> Subdevices: 1/1 > > >> Subdevice #0: subdevice #0 > > >> card 3: CX8801_3 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > > >> Subdevices: 1/1 > > >> Subdevice #0: subdevice #0 > > >> card 4: CX8801_4 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > > >> Subdevices: 1/1 > > >> Subdevice #0: subdevice #0 > > >> card 5: CX8801_5 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > > >> Subdevices: 1/1 > > >> Subdevice #0: subdevice #0 > > >> card 6: CX8801_6 [Conexant CX8801], device 0: CX88 Digital [CX88 Digital] > > >> Subdevices: 1/1 > > &
TW68 Driver
There is a really great driver for the thousands of capture cards floating around ebay called TW68. It is available here: http://gitorious.org/tw68 I'm not a developer but I have been using it for a number of years and it's a shame it's still not included in the kernel. Is anyone interested in making this happen? -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
tw68-v2/tw68-i2c.c:145: error: unknown field ‘clie nt_register’ specified in initializer
Hey, I'm trying to compile tw68 and I'm getting the following: make -C /lib/modules/2.6.31-14-generic/build M=/root/tw68-v2 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic' CC [M] /root/tw68-v2/tw68-core.o CC [M] /root/tw68-v2/tw68-cards.o CC [M] /root/tw68-v2/tw68-i2c.o /root/tw68-v2/tw68-i2c.c:145: error: unknown field ‘client_register’ specified in initializer /root/tw68-v2/tw68-i2c.c:145: warning: missing braces around initializer /root/tw68-v2/tw68-i2c.c:145: warning: (near initialization for ‘tw68_adap_sw_template.dev_released’) /root/tw68-v2/tw68-i2c.c:145: warning: initialization makes integer from pointer without a cast /root/tw68-v2/tw68-i2c.c:145: error: initializer element is not computable at load time /root/tw68-v2/tw68-i2c.c:145: error: (near initialization for ‘tw68_adap_sw_template.dev_released.done’) make[2]: *** [/root/tw68-v2/tw68-i2c.o] Error 1 make[1]: *** [_module_/root/tw68-v2] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic' make: *** [all] Error 2 Any ideas? -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: tw68-v2/tw68-i2c.c:145: error: unknown field ‘ client_register’ specified in initializer
Thanks, managed to compile but getting -1 Unknown symbol in module now - any ideas? # make make -C /lib/modules/2.6.31-14-generic/build M=/root/tw68-v2 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic' CC [M] /root/tw68-v2/tw68-core.o CC [M] /root/tw68-v2/tw68-cards.o CC [M] /root/tw68-v2/tw68-video.o CC [M] /root/tw68-v2/tw68-controls.o CC [M] /root/tw68-v2/tw68-fileops.o CC [M] /root/tw68-v2/tw68-ioctls.o CC [M] /root/tw68-v2/tw68-vbi.o CC [M] /root/tw68-v2/tw68-ts.o CC [M] /root/tw68-v2/tw68-risc.o CC [M] /root/tw68-v2/tw68-input.o CC [M] /root/tw68-v2/tw68-tvaudio.o LD [M] /root/tw68-v2/tw68.o Building modules, stage 2. MODPOST 1 modules CC /root/tw68-v2/tw68.mod.o LD [M] /root/tw68-v2/tw68.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic' # insmod tw68.ko insmod: error inserting 'tw68.ko': -1 Unknown symbol in module # uname -a Linux xanview-dev 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux 2009/11/10 Domenico Andreoli : > Hi, > > On Tue, Nov 10, 2009 at 1:19 PM, Roman Gaufman wrote: >> Hey, I'm trying to compile tw68 and I'm getting the following: >> >> make -C /lib/modules/2.6.31-14-generic/build M=/root/tw68-v2 modules >> make[1]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic' >> CC [M] /root/tw68-v2/tw68-core.o >> CC [M] /root/tw68-v2/tw68-cards.o >> CC [M] /root/tw68-v2/tw68-i2c.o >> /root/tw68-v2/tw68-i2c.c:145: error: unknown field ‘client_register’ >> specified in initializer >> /root/tw68-v2/tw68-i2c.c:145: warning: missing braces around initializer >> /root/tw68-v2/tw68-i2c.c:145: warning: (near initialization for >> ‘tw68_adap_sw_template.dev_released’) >> /root/tw68-v2/tw68-i2c.c:145: warning: initialization makes integer >> from pointer without a cast >> /root/tw68-v2/tw68-i2c.c:145: error: initializer element is not >> computable at load time >> /root/tw68-v2/tw68-i2c.c:145: error: (near initialization for >> ‘tw68_adap_sw_template.dev_released.done’) >> make[2]: *** [/root/tw68-v2/tw68-i2c.o] Error 1 >> make[1]: *** [_module_/root/tw68-v2] Error 2 >> make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic' >> make: *** [all] Error 2 >> >> Any ideas? > > yes, the i2c part got outdated by some kernel change. anyway it is still > not used so you can safely remove tw68-i2c.c from Makefile. > > regards, > Domenico > > -[ Domenico Andreoli, aka cavok > --[ http://www.dandreoli.com/gpgkey.asc > ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: tw68-v2/tw68-i2c.c:145: error: unknown field ‘ client_register’ specified in initializer
Thank you, managed to modprobe the module. However now when I try to open the device with mplayer, the system just freezes. No error messages, just freezes and I have to hold the power button for 5 seconds. Any ideas? This is what I get in dmesg when I insmod tw68.ko: [ 94.913695] tw68: v4l2 driver version 0.0.1 loaded [ 94.913744] tw68 :03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 94.913750] tw6804[0]: found at :03:00.0, rev: 16, irq: 16, latency: 32, mmio: 0xfbdff000 [ 94.913755] tw6804[0]: subsystem: :, board: GENERIC [card=0,autodetected] [ 94.913774] tw6804[0]: Unable to determine board type, using generic values [ 95.020034] IRQ 16/tw6804[0]: IRQF_DISABLED is not guaranteed on shared IRQs [ 95.020074] tw6804[0]: registered device video1 [v4l2] [ 95.020084] tw6804[0]: registered device vbi0 [ 95.020253] tw68 :03:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 95.020258] tw6804[1]: found at :03:01.0, rev: 16, irq: 17, latency: 32, mmio: 0xfbdfd000 [ 95.020263] tw6804[1]: subsystem: :, board: GENERIC [card=0,autodetected] [ 95.020610] tw6804[1]: Unable to determine board type, using generic values [ 95.129871] IRQ 17/tw6804[1]: IRQF_DISABLED is not guaranteed on shared IRQs [ 95.129899] tw6804[1]: registered device video2 [v4l2] [ 95.129910] tw6804[1]: registered device vbi1 [ 95.130075] tw68 :03:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 95.130081] tw6804[2]: found at :03:02.0, rev: 16, irq: 18, latency: 32, mmio: 0xfbdfb000 [ 95.130086] tw6804[2]: subsystem: :, board: GENERIC [card=0,autodetected] [ 95.130093] tw6804[2]: Unable to determine board type, using generic values [ 95.239712] IRQ 18/tw6804[2]: IRQF_DISABLED is not guaranteed on shared IRQs [ 95.239740] tw6804[2]: registered device video3 [v4l2] [ 95.239752] tw6804[2]: registered device vbi2 [ 95.239901] tw68 :03:03.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 95.239907] tw6804[3]: found at :03:03.0, rev: 16, irq: 19, latency: 32, mmio: 0xfbdf9000 [ 95.239912] tw6804[3]: subsystem: :, board: GENERIC [card=0,autodetected] [ 95.239919] tw6804[3]: Unable to determine board type, using generic values [ 95.349553] IRQ 19/tw6804[3]: IRQF_DISABLED is not guaranteed on shared IRQs [ 95.349581] tw6804[3]: registered device video4 [v4l2] [ 95.349592] tw6804[3]: registered device vbi3 [ 95.349733] tw68 :03:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 95.349738] tw6804[4]: found at :03:04.0, rev: 16, irq: 16, latency: 32, mmio: 0xfbdf7000 [ 95.349743] tw6804[4]: subsystem: :, board: GENERIC [card=0,autodetected] [ 95.349751] tw6804[4]: Unable to determine board type, using generic values [ 95.459394] IRQ 16/tw6804[4]: IRQF_DISABLED is not guaranteed on shared IRQs [ 95.459423] tw6804[4]: registered device video5 [v4l2] [ 95.459435] tw6804[4]: registered device vbi4 [ 95.459578] tw68 :03:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 95.459583] tw6804[5]: found at :03:05.0, rev: 16, irq: 17, latency: 32, mmio: 0xfbdf5000 [ 95.459588] tw6804[5]: subsystem: :, board: GENERIC [card=0,autodetected] [ 95.459595] tw6804[5]: Unable to determine board type, using generic values [ 95.569236] IRQ 17/tw6804[5]: IRQF_DISABLED is not guaranteed on shared IRQs [ 95.569263] tw6804[5]: registered device video6 [v4l2] [ 95.569274] tw6804[5]: registered device vbi5 [ 95.569417] tw68 :03:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 95.569422] tw6804[6]: found at :03:06.0, rev: 16, irq: 18, latency: 32, mmio: 0xfbdf3000 [ 95.569427] tw6804[6]: subsystem: 1797:6804, board: GENERIC [card=0,autodetected] [ 95.569434] tw6804[6]: Unable to determine board type, using generic values [ 95.679077] IRQ 18/tw6804[6]: IRQF_DISABLED is not guaranteed on shared IRQs [ 95.679105] tw6804[6]: registered device video7 [v4l2] [ 95.679117] tw6804[6]: registered device vbi6 [ 95.679263] tw68 :03:07.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 95.679268] tw6804[7]: found at :03:07.0, rev: 16, irq: 19, latency: 32, mmio: 0xfbdf1000 [ 95.679273] tw6804[7]: subsystem: :, board: GENERIC [card=0,autodetected] [ 95.679280] tw6804[7]: Unable to determine board type, using generic values [ 95.788918] IRQ 19/tw6804[7]: IRQF_DISABLED is not guaranteed on shared IRQs [ 95.788946] tw6804[7]: registered device video8 [v4l2] [ 95.788957] tw6804[7]: registered device vbi7 2009/11/10 Domenico Andreoli : > Hi > > On Tue, Nov 10, 2009 at 1:40 PM, Roman Gaufman wrote: >> Thanks, managed to compile but getting -1 Unknown symbol in module now >> - any ideas? >> >> # make >> make -C /lib/modules/2.6.31-14-generic/build M=/root/tw68-v2 modules >> make[1]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic' >> CC [M] /root/tw6
Re: tw68-v2/tw68-i2c.c:145: error: unknown field ‘ client_register’ specified in initializer
I swapped my graphics card and techwell DVR card places and now it works, thanks you!!! Only 1 question, the readme says there is no audio yet - any ideas when/if audio will be available? :) Thanks again! Roman 2009/11/10 Roman Gaufman : > Thank you, managed to modprobe the module. > > However now when I try to open the device with mplayer, the system > just freezes. No error messages, just freezes and I have to hold the > power button for 5 seconds. Any ideas? > > This is what I get in dmesg when I insmod tw68.ko: > > [ 94.913695] tw68: v4l2 driver version 0.0.1 loaded > [ 94.913744] tw68 :03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [ 94.913750] tw6804[0]: found at :03:00.0, rev: 16, irq: 16, > latency: 32, mmio: 0xfbdff000 > [ 94.913755] tw6804[0]: subsystem: :, board: GENERIC > [card=0,autodetected] > [ 94.913774] tw6804[0]: Unable to determine board type, using generic values > [ 95.020034] IRQ 16/tw6804[0]: IRQF_DISABLED is not guaranteed on shared > IRQs > [ 95.020074] tw6804[0]: registered device video1 [v4l2] > [ 95.020084] tw6804[0]: registered device vbi0 > [ 95.020253] tw68 :03:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > [ 95.020258] tw6804[1]: found at :03:01.0, rev: 16, irq: 17, > latency: 32, mmio: 0xfbdfd000 > [ 95.020263] tw6804[1]: subsystem: :, board: GENERIC > [card=0,autodetected] > [ 95.020610] tw6804[1]: Unable to determine board type, using generic values > [ 95.129871] IRQ 17/tw6804[1]: IRQF_DISABLED is not guaranteed on shared > IRQs > [ 95.129899] tw6804[1]: registered device video2 [v4l2] > [ 95.129910] tw6804[1]: registered device vbi1 > [ 95.130075] tw68 :03:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 > [ 95.130081] tw6804[2]: found at :03:02.0, rev: 16, irq: 18, > latency: 32, mmio: 0xfbdfb000 > [ 95.130086] tw6804[2]: subsystem: :, board: GENERIC > [card=0,autodetected] > [ 95.130093] tw6804[2]: Unable to determine board type, using generic values > [ 95.239712] IRQ 18/tw6804[2]: IRQF_DISABLED is not guaranteed on shared > IRQs > [ 95.239740] tw6804[2]: registered device video3 [v4l2] > [ 95.239752] tw6804[2]: registered device vbi2 > [ 95.239901] tw68 :03:03.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > [ 95.239907] tw6804[3]: found at :03:03.0, rev: 16, irq: 19, > latency: 32, mmio: 0xfbdf9000 > [ 95.239912] tw6804[3]: subsystem: :, board: GENERIC > [card=0,autodetected] > [ 95.239919] tw6804[3]: Unable to determine board type, using generic values > [ 95.349553] IRQ 19/tw6804[3]: IRQF_DISABLED is not guaranteed on shared > IRQs > [ 95.349581] tw6804[3]: registered device video4 [v4l2] > [ 95.349592] tw6804[3]: registered device vbi3 > [ 95.349733] tw68 :03:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [ 95.349738] tw6804[4]: found at :03:04.0, rev: 16, irq: 16, > latency: 32, mmio: 0xfbdf7000 > [ 95.349743] tw6804[4]: subsystem: :, board: GENERIC > [card=0,autodetected] > [ 95.349751] tw6804[4]: Unable to determine board type, using generic values > [ 95.459394] IRQ 16/tw6804[4]: IRQF_DISABLED is not guaranteed on shared > IRQs > [ 95.459423] tw6804[4]: registered device video5 [v4l2] > [ 95.459435] tw6804[4]: registered device vbi4 > [ 95.459578] tw68 :03:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > [ 95.459583] tw6804[5]: found at :03:05.0, rev: 16, irq: 17, > latency: 32, mmio: 0xfbdf5000 > [ 95.459588] tw6804[5]: subsystem: :, board: GENERIC > [card=0,autodetected] > [ 95.459595] tw6804[5]: Unable to determine board type, using generic values > [ 95.569236] IRQ 17/tw6804[5]: IRQF_DISABLED is not guaranteed on shared > IRQs > [ 95.569263] tw6804[5]: registered device video6 [v4l2] > [ 95.569274] tw6804[5]: registered device vbi5 > [ 95.569417] tw68 :03:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 > [ 95.569422] tw6804[6]: found at :03:06.0, rev: 16, irq: 18, > latency: 32, mmio: 0xfbdf3000 > [ 95.569427] tw6804[6]: subsystem: 1797:6804, board: GENERIC > [card=0,autodetected] > [ 95.569434] tw6804[6]: Unable to determine board type, using generic values > [ 95.679077] IRQ 18/tw6804[6]: IRQF_DISABLED is not guaranteed on shared > IRQs > [ 95.679105] tw6804[6]: registered device video7 [v4l2] > [ 95.679117] tw6804[6]: registered device vbi6 > [ 95.679263] tw68 :03:07.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > [ 95.679268] tw6804[7]: found at :03:07.0, rev: 16, irq: 19, > latency: 32, mmio: 0xfbdf1000 > [ 95.679273] tw6804[7]: subsystem: :, board: GENERIC > [card=0,autodetected] > [ 95.679280]
Re: tw68-v2/tw68-i2c.c:145: error: unknown field ???client_register??? specified in initializer
2009/11/10 Domenico Andreoli : > On Tue, Nov 10, 2009 at 01:48:43PM +0000, Roman Gaufman wrote: >> I swapped my graphics card and techwell DVR card places and now it >> works, thanks you!!! > > have you a PCI-E techwell board? Yep, it's PCI-E 8 audio/video dvr card. > > i'm taking the driver out of the freezer trying to get rid of > the IRQF_DISABLED warning flag. i'm interested in seeing your > /proc/interrupts, if possible, before and after the boards swap. Both with the patch: After the swap (working): CPU0 CPU1 CPU2 CPU3 0: 22 0 0 40 IO-APIC-edge timer 1: 0 0 0 2 IO-APIC-edge i8042 4: 0 0 0 2 IO-APIC-edge 8: 0 0 0 1 IO-APIC-edge rtc0 9: 0 0 0 0 IO-APIC-fasteoi acpi 16: 0 0 0 543773 IO-APIC-fasteoi ahci, uhci_hcd:usb3, uhci_hcd:usb9, tw6804[0], tw6804[4] 17: 0 0 0 40297 IO-APIC-fasteoi pata_jmicron, ohci1394, tw6804[1], tw6804[5] 18: 0 0 0 24680 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb5, uhci_hcd:usb8, tw6804[2], tw6804[6] 19: 0 0 40184 0 IO-APIC-fasteoi uhci_hcd:usb7, tw6804[3], tw6804[7] 21: 0 0 0 0 IO-APIC-fasteoi uhci_hcd:usb4 22: 0218 0 0 IO-APIC-fasteoi HDA Intel 23: 0 0 0108 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb6 24: 934040 0 0 0 HPET_MSI-edge hpet2 25: 0 390326 0 0 HPET_MSI-edge hpet3 26: 0 0 590635 0 HPET_MSI-edge hpet4 27: 0 0 0 845999 HPET_MSI-edge hpet5 33: 0 0 0 0 PCI-MSI-edge ahci 34: 812442 0 0 0 PCI-MSI-edge eth1 NMI: 0 0 0 0 Non-maskable interrupts LOC: 54 38 23 8 Local timer interrupts SPU: 0 0 0 0 Spurious interrupts CNT: 0 0 0 0 Performance counter interrupts PND: 0 0 0 0 Performance pending work RES: 4027 5400 6102 6462 Rescheduling interrupts CAL:124139137 44 Function call interrupts TLB: 27517 22022 23155 17498 TLB shootdowns TRM: 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 Threshold APIC interrupts MCE: 0 0 0 0 Machine check exceptions MCP: 41 41 41 41 Machine check polls ERR: 0 MIS: 0 Before swap (system freezes as soon as I try to open video device): # cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 0: 22 0 0 1 IO-APIC-edge timer 1: 0 0 0 2 IO-APIC-edge i8042 4: 0 0 0 2 IO-APIC-edge 8: 0 0 0 1 IO-APIC-edge rtc0 9: 0 0 0 0 IO-APIC-fasteoi acpi 16: 0 0 0 9090 IO-APIC-fasteoi ahci, uhci_hcd:usb3, uhci_hcd:usb9, tw6804[0], tw6804[4] 17: 0 0 0 3 IO-APIC-fasteoi pata_jmicron, ohci1394, tw6804[1], tw6804[5] 18: 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb5, uhci_hcd:usb8, tw6804[2], tw6804[6] 19: 0 0 0 0 IO-APIC-fasteoi uhci_hcd:usb7, tw6804[3], tw6804[7] 21: 0 0 0 0 IO-APIC-fasteoi uhci_hcd:usb4 22: 0218 0 0 IO-APIC-fasteoi HDA Intel 23: 0 0 0103 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb6 24: 3102 0 0 0 HPET_MSI-edge hpet2 25: 0 2403 0 0 HPET_MSI-edge hpet3 26: 0 0 1899 0 HPET_MSI-edge hpet4 27: 0 0 0 2835 HPET_MSI-edge hpet5 33: 0 0 0 0 PCI-MSI-edge ahci 34:816 0 0 0 PCI-MSI-edge eth1 NMI: 0 0 0 0 Non-maskable interrupts LOC: 54 38 23 8 Local timer interrupts SPU: 0 0 0 0 Spurious interrupts CNT:
