From Michael.McQuay@wcg.com Thu, 1 Nov 2001 09:34:28 -0600 Date: Thu, 1 Nov 2001 09:34:28 -0600 From: McQuay, Michael Michael.McQuay@wcg.com Subject: [cpia] Re: can't compile on RH7.1 I'm having the exact same problem/errors as you described below. Have you found a solution, yet? If I find a solution, I'll post it. ---Original message--- Greetings, I tried compiling on my RH7.1 machine and got errors trying to compile cpia.c Any help would be appreciated here is the build log. gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-f rame-pointer -pipe -fno-strength-reduce -m486 -malign-loops =2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-fram e-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VI DEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA cpia.c cpia.c: In function `cpia_write_proc': cpia.c:652: warning: `val' might be used uninitialized in this function cpia.c: At top level: cpia.c:3906: warning: initialization from incompatible pointer type cpia.c:3907: warning: missing braces around initializer cpia.c:3907: warning: (near initialization for `cpia_template.name') cpia.c:3909: warning: initialization makes integer from pointer without a cast cpia.c:3909: initializer element is not computable at load time cpia.c:3909: (near initialization for `cpia_template.name[2]') cpia.c:3910: warning: initialization makes integer from pointer without a cast cpia.c:3910: initializer element is not computable at load time cpia.c:3910: (near initialization for `cpia_template.name[3]') cpia.c:3911: warning: initialization makes integer from pointer without a cast cpia.c:3911: initializer element is not computable at load time cpia.c:3911: (near initialization for `cpia_template.name[4]') cpia.c:3912: warning: initialization makes integer from pointer without a cast cpia.c:3913: warning: initialization makes integer from pointer without a cast cpia.c:3914: warning: initialization makes integer from pointer without a cast cpia.c:3914: initializer element is not computable at load time cpia.c:3914: (near initialization for `cpia_template.name[7]') cpia.c:3915: warning: initialization makes integer from pointer without a cast cpia.c:3915: initializer element is not computable at load time cpia.c:3915: (near initialization for `cpia_template.name[8]') cpia.c:3916: warning: initialization makes integer from pointer without a cast cpia.c:3916: initializer element is not computable at load time cpia.c:3916: (near initialization for `cpia_template.name[9]') cpia.c:3917: warning: initialization makes integer from pointer without a cast make: *** [cpia.o] Error 1 From Michael.McQuay@wcg.com Thu, 1 Nov 2001 09:51:32 -0600 Date: Thu, 1 Nov 2001 09:51:32 -0600 From: McQuay, Michael Michael.McQuay@wcg.com Subject: [cpia] Re: can't compile on RH7.1 Oops, except that mine also has the following lines at the bottom. cpia.c:3917: warning: initialization makes integer from pointer without a cast cpia.c: In function `cpia_register_camera': cpia.c:4079: too few arguments to function `video_register_device' make: *** [cpia.o] Error 1 -----Original Message----- From: McQuay, Michael To: 'cpia@risc.uni-linz.ac.at' Cc: 'diodice@dgitech.com' Sent: 11/1/2001 9:34 AM Subject: [cpia] Re: can't compile on RH7.1 I'm having the exact same problem/errors as you described below. Have you found a solution, yet? If I find a solution, I'll post it. ---Original message--- Greetings, I tried compiling on my RH7.1 machine and got errors trying to compile cpia.c Any help would be appreciated here is the build log. gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-f rame-pointer -pipe -fno-strength-reduce -m486 -malign-loops =2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-fram e-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VI DEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA cpia.c cpia.c: In function `cpia_write_proc': cpia.c:652: warning: `val' might be used uninitialized in this function cpia.c: At top level: cpia.c:3906: warning: initialization from incompatible pointer type cpia.c:3907: warning: missing braces around initializer cpia.c:3907: warning: (near initialization for `cpia_template.name') cpia.c:3909: warning: initialization makes integer from pointer without a cast cpia.c:3909: initializer element is not computable at load time cpia.c:3909: (near initialization for `cpia_template.name[2]') cpia.c:3910: warning: initialization makes integer from pointer without a cast cpia.c:3910: initializer element is not computable at load time cpia.c:3910: (near initialization for `cpia_template.name[3]') cpia.c:3911: warning: initialization makes integer from pointer without a cast cpia.c:3911: initializer element is not computable at load time cpia.c:3911: (near initialization for `cpia_template.name[4]') cpia.c:3912: warning: initialization makes integer from pointer without a cast cpia.c:3913: warning: initialization makes integer from pointer without a cast cpia.c:3914: warning: initialization makes integer from pointer without a cast cpia.c:3914: initializer element is not computable at load time cpia.c:3914: (near initialization for `cpia_template.name[7]') cpia.c:3915: warning: initialization makes integer from pointer without a cast cpia.c:3915: initializer element is not computable at load time cpia.c:3915: (near initialization for `cpia_template.name[8]') cpia.c:3916: warning: initialization makes integer from pointer without a cast cpia.c:3916: initializer element is not computable at load time cpia.c:3916: (near initialization for `cpia_template.name[9]') cpia.c:3917: warning: initialization makes integer from pointer without a cast make: *** [cpia.o] Error 1 _______________________________________________ cpia mailing list - cpia@risc.uni-linz.ac.at http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From Nick.Holloway@pyrites.org.uk 1 Nov 2001 22:21:55 -0000 Date: 1 Nov 2001 22:21:55 -0000 From: Nick Holloway Nick.Holloway@pyrites.org.uk Subject: [cpia] Using cpia with a 2.4.13 kernel As I discovered that the setting of cpia parameters had been disabled (as it was insecure) in the 2.4 kernel stream, I decided to drop the current CVS code from sourceforge into the kernel source. At the end is a patch required to get it to compile with 2.4.13. I now have the camera working on a 486 DX2/50 plugged into a TRISTATE parallel port, with images being captured by "motion" (motion.sourceforge.net). I must confess I've hardly exhaustively tested the parameter settings, as the only setting I have changed is the compression mode. Are there plans to feed a patch for cpia into the 2.4 kernel? Index: cpia_pp.c =================================================================== RCS file: /cvsroot/webcam/cpia/module/cpia_pp.c,v retrieving revision 1.3 diff -u -r1.3 cpia_pp.c --- cpia_pp.c 2001/09/16 12:15:17 1.3 +++ cpia_pp.c 2001/11/01 22:12:50 @@ -1651,7 +1651,7 @@ #endif /* kernel version >= 2.3.0 */ cam_list = NULL; - spinlock_init( cam_list_lock_pp ); + spin_lock_init( cam_list_lock_pp ); return 0; } -- `O O' | Nick.Holloway@pyrites.org.uk // ^ \\ | http://www.pyrites.org.uk/ From aaron_800@yahoo.com Thu, 1 Nov 2001 16:10:32 -0800 (PST) Date: Thu, 1 Nov 2001 16:10:32 -0800 (PST) From: Aaron Littich aaron_800@yahoo.com Subject: [cpia] Stereo cpia cams Hello, I bought two ezonics webcams, and when i use one, they work using the cpia driver. I'm wondering how I would go about setting it up so that I could use two at once, since the reason I bought two was to investigate stereo vision research for autonomous robotic navigation. Thanks, Aaron __________________________________________________ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com From Michael.McQuay@wcg.com Fri, 2 Nov 2001 11:22:08 -0600 Date: Fri, 2 Nov 2001 11:22:08 -0600 From: McQuay, Michael Michael.McQuay@wcg.com Subject: [cpia] Re: can't compile on RH7.1 I had noticed that same thing about the video_device structure changing and was hacking around on the cpia driver, trying to get it to work, when I saw your email. I just compiled 2.4.13 and, you're right, the cpia drivers that are included with it work properly now. I've said it before and I'll say it again, THIS DRIVER ROCKS! Thanks to all of you who've provided a way for me to use my webcam in linux. -----Original Message----- From: David Iodice To: McQuay, Michael Sent: 11/2/2001 6:26 AM Subject: RE: [cpia] Re: can't compile on RH7.1 The problem I have is that the /usr/src/linux/include/linux/videodev.h file defined the video_device structure. And that structure differs from what the code expects. The solution is to rebuild the kernel and select cpia drivers at that time. Then the camera works. Make sure you also select the usb options that are listed in the cpia docs. This appears to work -- friends of mine did this, I haven't gotten that far yet :-) Good luck. David -----Original Message----- From: McQuay, Michael [mailto:Michael.McQuay@wcg.com] Sent: Thursday, November 01, 2001 10:52 AM To: ''cpia@risc.uni-linz.ac.at' ' Cc: ''diodice@dgitech.com' ' Subject: RE: [cpia] Re: can't compile on RH7.1 Oops, except that mine also has the following lines at the bottom. cpia.c:3917: warning: initialization makes integer from pointer without a cast cpia.c: In function `cpia_register_camera': cpia.c:4079: too few arguments to function `video_register_device' make: *** [cpia.o] Error 1 -----Original Message----- From: McQuay, Michael To: 'cpia@risc.uni-linz.ac.at' Cc: 'diodice@dgitech.com' Sent: 11/1/2001 9:34 AM Subject: [cpia] Re: can't compile on RH7.1 I'm having the exact same problem/errors as you described below. Have you found a solution, yet? If I find a solution, I'll post it. ---Original message--- Greetings, I tried compiling on my RH7.1 machine and got errors trying to compile cpia.c Any help would be appreciated here is the build log. gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-f rame-pointer -pipe -fno-strength-reduce -m486 -malign-loops =2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-fram e-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VI DEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA cpia.c cpia.c: In function `cpia_write_proc': cpia.c:652: warning: `val' might be used uninitialized in this function cpia.c: At top level: cpia.c:3906: warning: initialization from incompatible pointer type cpia.c:3907: warning: missing braces around initializer cpia.c:3907: warning: (near initialization for `cpia_template.name') cpia.c:3909: warning: initialization makes integer from pointer without a cast cpia.c:3909: initializer element is not computable at load time cpia.c:3909: (near initialization for `cpia_template.name[2]') cpia.c:3910: warning: initialization makes integer from pointer without a cast cpia.c:3910: initializer element is not computable at load time cpia.c:3910: (near initialization for `cpia_template.name[3]') cpia.c:3911: warning: initialization makes integer from pointer without a cast cpia.c:3911: initializer element is not computable at load time cpia.c:3911: (near initialization for `cpia_template.name[4]') cpia.c:3912: warning: initialization makes integer from pointer without a cast cpia.c:3913: warning: initialization makes integer from pointer without a cast cpia.c:3914: warning: initialization makes integer from pointer without a cast cpia.c:3914: initializer element is not computable at load time cpia.c:3914: (near initialization for `cpia_template.name[7]') cpia.c:3915: warning: initialization makes integer from pointer without a cast cpia.c:3915: initializer element is not computable at load time cpia.c:3915: (near initialization for `cpia_template.name[8]') cpia.c:3916: warning: initialization makes integer from pointer without a cast cpia.c:3916: initializer element is not computable at load time cpia.c:3916: (near initialization for `cpia_template.name[9]') cpia.c:3917: warning: initialization makes integer from pointer without a cast make: *** [cpia.o] Error 1 _______________________________________________ cpia mailing list - cpia@risc.uni-linz.ac.at http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/ cpia From lists@killinghand.org Tue, 13 Nov 2001 21:51:28 -0600 Date: Tue, 13 Nov 2001 21:51:28 -0600 From: Axe lists@killinghand.org Subject: [cpia] Device is Busy Anyone have a problem with attempting to drop pictures from a CPIA camera, and it randomly locking /dev/video*? For a few drops, it will work properly, but then poof... heh...it breaks.. Even though the program exits (I use gqcam), /dev/video* stays 'busy', and you can't drop anymore frames. When I try to unload the modules, I can unload cpia_usb, cpia_pp, and parport. But cpia and videodev won't unload due to getting a 'device is busy' error. The only way I can get this "fixed" is by rebooting the machine. I'm using RH7.2 kernel version 2.4.9-13 (This has happened with RH7.0 and 7.1 also). If anyone has any ideas, or needs more info, I'd be glad to hear it. This is the output from the messages file when I unload the three above-mentioned modules: Nov 13 21:42:05 gothic kernel: usb.c: deregistering driver cpia Nov 13 21:42:05 gothic kernel: cpia.c:cpia_unregister_camera_Rc7cb4e91(3243):/dev/video0 removed while open, deferring video_unregister_device Nov 13 21:42:05 gothic kernel: Unable to handle kernel paging request at virtual address c888e65a Nov 13 21:42:05 gothic kernel: printing eip: Nov 13 21:42:05 gothic kernel: c888e65a Nov 13 21:42:05 gothic kernel: *pde = 014a9067 Nov 13 21:42:05 gothic kernel: *pte = 00000000 Nov 13 21:42:05 gothic kernel: Oops: 0000 Nov 13 21:42:05 gothic kernel: CPU: 0 Nov 13 21:42:05 gothic kernel: EIP: 0010:[sound:num_midis_Ra1eae7cf+243282/98532974] Not tainted Nov 13 21:42:05 gothic kernel: EIP: 0010:[] Not tainted Nov 13 21:42:05 gothic kernel: EFLAGS: 00010286 Nov 13 21:42:05 gothic kernel: eax: c70d94bc ebx: c78f2200 ecx: 00000000 edx: c70d94bc Nov 13 21:42:05 gothic kernel: esi: c70d94b0 edi: c89c0000 ebp: c1cac000 esp: c1cadf10 Nov 13 21:42:05 gothic kernel: ds: 0018 es: 0018 ss: 0018 Nov 13 21:42:05 gothic kernel: Process gqcam (pid: 1626, stackpage=c1cad000) Nov 13 21:42:05 gothic kernel: Stack: c78f2200 000b170a c887f707 c70d94b0 c89c0000 00000000 00000000 c78f2208 Nov 13 21:42:05 gothic kernel: c78f2200 0004a400 40467008 c887ff0b c78f2200 c1cac000 40467008 00000001 Nov 13 21:42:05 gothic kernel: 0004b000 c15d6250 ffffffea 00000000 0004a400 c887a091 c78f22c0 40467008 Nov 13 21:42:05 gothic kernel: Call Trace: [sound:num_midis_Ra1eae7cf+182015/98594241] __insmod_cpia_S.text_L16504 [cpia] 0x26a7 Nov 13 21:42:05 gothic kernel: Call Trace: [] __insmod_cpia_S.text_L16504 [cpia] 0x26a7 Nov 13 21:42:05 gothic kernel: [sound:num_midis_Ra1eae7cf+184067/98592189] __insmod_cpia_S.text_L16504 [cpia] 0x2eab Nov 13 21:42:05 gothic kernel: [] __insmod_cpia_S.text_L16504 [cpia] 0x2eab Nov 13 21:42:05 gothic kernel: [sound:num_midis_Ra1eae7cf+159881/98616375] __insmod_videodev_S.text_L2148 [videodev] 0x31 Nov 13 21:42:05 gothic kernel: [] __insmod_videodev_S.text_L2148 [videodev] 0x31 Nov 13 21:42:05 gothic kernel: [sys_read+149/204] sys_read [kernel] 0x95 Nov 13 21:42:05 gothic kernel: [] sys_read [kernel] 0x95 Nov 13 21:42:05 gothic kernel: [sys_mremap+50/76] sys_mremap [kernel] 0x32 Nov 13 21:42:05 gothic kernel: [] sys_mremap [kernel] 0x32 Nov 13 21:42:05 gothic kernel: [sys_mremap+66/76] sys_mremap [kernel] 0x42 Nov 13 21:42:05 gothic kernel: [] sys_mremap [kernel] 0x42 Nov 13 21:42:05 gothic kernel: [system_call+51/56] system_call [kernel] 0x33 Nov 13 21:42:06 gothic kernel: [] system_call [kernel] 0x33 Nov 13 21:42:06 gothic kernel: Nov 13 21:42:06 gothic kernel: Nov 13 21:42:06 gothic kernel: Code: Bad EIP value. From gstalusan@uwaterloo.ca 14 Nov 2001 01:33:30 -0500 Date: 14 Nov 2001 01:33:30 -0500 From: George Talusan gstalusan@uwaterloo.ca Subject: [cpia] Device is Busy I have had the same problem as well for a long time now. Unplugging the camera and then plugging it back in seems to do the trick, except from /dev/video{n} to /dev/video{n+1} each time. Debian. Kernel 2.4.14 or cvs driver. gqcam. ABit BP6 2x466MHz. On Tue, 2001-11-13 at 22:51, Axe wrote: > Anyone have a problem with attempting to drop pictures from a CPIA camera, > and it randomly locking /dev/video*? > For a few drops, it will work properly, but then poof... heh...it breaks.. > Even though the program exits (I use gqcam), /dev/video* stays 'busy', and > you can't drop anymore frames. > When I try to unload the modules, I can unload cpia_usb, cpia_pp, and > parport. But cpia and videodev won't unload due to getting a 'device is > busy' error. The only way I can get this "fixed" is by rebooting the > machine. > I'm using RH7.2 kernel version 2.4.9-13 (This has happened with RH7.0 and > 7.1 also). > If anyone has any ideas, or needs more info, I'd be glad to hear it. > > > This is the output from the messages file when I unload the three > above-mentioned modules: > > Nov 13 21:42:05 gothic kernel: usb.c: deregistering driver cpia > Nov 13 21:42:05 gothic kernel: > cpia.c:cpia_unregister_camera_Rc7cb4e91(3243):/dev/video0 removed while > open, deferring video_unregister_device > Nov 13 21:42:05 gothic kernel: Unable to handle kernel paging request at > virtual address c888e65a > Nov 13 21:42:05 gothic kernel: printing eip: > Nov 13 21:42:05 gothic kernel: c888e65a > Nov 13 21:42:05 gothic kernel: *pde = 014a9067 > Nov 13 21:42:05 gothic kernel: *pte = 00000000 > Nov 13 21:42:05 gothic kernel: Oops: 0000 > Nov 13 21:42:05 gothic kernel: CPU: 0 > Nov 13 21:42:05 gothic kernel: EIP: > 0010:[sound:num_midis_Ra1eae7cf+243282/98532974] Not tainted > Nov 13 21:42:05 gothic kernel: EIP: 0010:[] Not tainted > Nov 13 21:42:05 gothic kernel: EFLAGS: 00010286 > Nov 13 21:42:05 gothic kernel: eax: c70d94bc ebx: c78f2200 ecx: 00000000 > edx: c70d94bc > Nov 13 21:42:05 gothic kernel: esi: c70d94b0 edi: c89c0000 ebp: c1cac000 > esp: c1cadf10 > Nov 13 21:42:05 gothic kernel: ds: 0018 es: 0018 ss: 0018 > Nov 13 21:42:05 gothic kernel: Process gqcam (pid: 1626, stackpage=c1cad000) > Nov 13 21:42:05 gothic kernel: Stack: c78f2200 000b170a c887f707 c70d94b0 > c89c0000 00000000 00000000 c78f2208 > Nov 13 21:42:05 gothic kernel: c78f2200 0004a400 40467008 c887ff0b > c78f2200 c1cac000 40467008 00000001 > Nov 13 21:42:05 gothic kernel: 0004b000 c15d6250 ffffffea 00000000 > 0004a400 c887a091 c78f22c0 40467008 > Nov 13 21:42:05 gothic kernel: Call Trace: > [sound:num_midis_Ra1eae7cf+182015/98594241] __insmod_cpia_S.text_L16504 > [cpia] 0x26a7 > Nov 13 21:42:05 gothic kernel: Call Trace: [] > __insmod_cpia_S.text_L16504 [cpia] 0x26a7 > Nov 13 21:42:05 gothic kernel: [sound:num_midis_Ra1eae7cf+184067/98592189] > __insmod_cpia_S.text_L16504 [cpia] 0x2eab > Nov 13 21:42:05 gothic kernel: [] __insmod_cpia_S.text_L16504 > [cpia] 0x2eab > Nov 13 21:42:05 gothic kernel: [sound:num_midis_Ra1eae7cf+159881/98616375] > __insmod_videodev_S.text_L2148 [videodev] 0x31 > Nov 13 21:42:05 gothic kernel: [] __insmod_videodev_S.text_L2148 > [videodev] 0x31 > Nov 13 21:42:05 gothic kernel: [sys_read+149/204] sys_read [kernel] 0x95 > Nov 13 21:42:05 gothic kernel: [] sys_read [kernel] 0x95 > Nov 13 21:42:05 gothic kernel: [sys_mremap+50/76] sys_mremap [kernel] 0x32 > Nov 13 21:42:05 gothic kernel: [] sys_mremap [kernel] 0x32 > Nov 13 21:42:05 gothic kernel: [sys_mremap+66/76] sys_mremap [kernel] 0x42 > Nov 13 21:42:05 gothic kernel: [] sys_mremap [kernel] 0x42 > Nov 13 21:42:05 gothic kernel: [system_call+51/56] system_call [kernel] 0x33 > Nov 13 21:42:06 gothic kernel: [] system_call [kernel] 0x33 > Nov 13 21:42:06 gothic kernel: > Nov 13 21:42:06 gothic kernel: > Nov 13 21:42:06 gothic kernel: Code: Bad EIP value. > > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > zhttp://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From rvt@dds.nl Wed, 14 Nov 2001 18:00:11 +0100 Date: Wed, 14 Nov 2001 18:00:11 +0100 From: Ries van twisk rvt@dds.nl Subject: [cpia] driver for kodac ez-200? Well the subject line says it all! Is there a driver? if no is there a driver in deveopment? If no where to start to write the driver for the EZ-200, possible be referce engineer the protocl used by kodac. Ries From axe@killinghand.org Wed, 14 Nov 2001 20:08:23 -0600 Date: Wed, 14 Nov 2001 20:08:23 -0600 From: Axe axe@killinghand.org Subject: [cpia] Device is Busy When you disconnect it from the computer, and plug it back in are you able to reuse the device? If I unplug it, I still get the 'device is busy' errors... (I forgot to mention, this is a USB cam) ----- Original Message ----- From: "George Talusan" To: "Axe" Cc: Sent: Wednesday, November 14, 2001 12:33 AM Subject: Re: [cpia] Device is Busy > I have had the same problem as well for a long time now. Unplugging the > camera and then plugging it back in seems to do the trick, except from > /dev/video{n} to /dev/video{n+1} each time. > > Debian. Kernel 2.4.14 or cvs driver. gqcam. ABit BP6 2x466MHz. > > > > On Tue, 2001-11-13 at 22:51, Axe wrote: > > Anyone have a problem with attempting to drop pictures from a CPIA camera, > > and it randomly locking /dev/video*? > > For a few drops, it will work properly, but then poof... heh...it breaks.. > > Even though the program exits (I use gqcam), /dev/video* stays 'busy', and > > you can't drop anymore frames. > > When I try to unload the modules, I can unload cpia_usb, cpia_pp, and > > parport. But cpia and videodev won't unload due to getting a 'device is > > busy' error. The only way I can get this "fixed" is by rebooting the > > machine. > > I'm using RH7.2 kernel version 2.4.9-13 (This has happened with RH7.0 and > > 7.1 also). > > If anyone has any ideas, or needs more info, I'd be glad to hear it. > > > > > > This is the output from the messages file when I unload the three > > above-mentioned modules: > > > > Nov 13 21:42:05 gothic kernel: usb.c: deregistering driver cpia > > Nov 13 21:42:05 gothic kernel: > > cpia.c:cpia_unregister_camera_Rc7cb4e91(3243):/dev/video0 removed while > > open, deferring video_unregister_device > > Nov 13 21:42:05 gothic kernel: Unable to handle kernel paging request at > > virtual address c888e65a > > Nov 13 21:42:05 gothic kernel: printing eip: > > Nov 13 21:42:05 gothic kernel: c888e65a > > Nov 13 21:42:05 gothic kernel: *pde = 014a9067 > > Nov 13 21:42:05 gothic kernel: *pte = 00000000 > > Nov 13 21:42:05 gothic kernel: Oops: 0000 > > Nov 13 21:42:05 gothic kernel: CPU: 0 > > Nov 13 21:42:05 gothic kernel: EIP: > > 0010:[sound:num_midis_Ra1eae7cf+243282/98532974] Not tainted > > Nov 13 21:42:05 gothic kernel: EIP: 0010:[] Not tainted > > Nov 13 21:42:05 gothic kernel: EFLAGS: 00010286 > > Nov 13 21:42:05 gothic kernel: eax: c70d94bc ebx: c78f2200 ecx: 00000000 > > edx: c70d94bc > > Nov 13 21:42:05 gothic kernel: esi: c70d94b0 edi: c89c0000 ebp: c1cac000 > > esp: c1cadf10 > > Nov 13 21:42:05 gothic kernel: ds: 0018 es: 0018 ss: 0018 > > Nov 13 21:42:05 gothic kernel: Process gqcam (pid: 1626, stackpage=c1cad000) > > Nov 13 21:42:05 gothic kernel: Stack: c78f2200 000b170a c887f707 c70d94b0 > > c89c0000 00000000 00000000 c78f2208 > > Nov 13 21:42:05 gothic kernel: c78f2200 0004a400 40467008 c887ff0b > > c78f2200 c1cac000 40467008 00000001 > > Nov 13 21:42:05 gothic kernel: 0004b000 c15d6250 ffffffea 00000000 > > 0004a400 c887a091 c78f22c0 40467008 > > Nov 13 21:42:05 gothic kernel: Call Trace: > > [sound:num_midis_Ra1eae7cf+182015/98594241] __insmod_cpia_S.text_L16504 > > [cpia] 0x26a7 > > Nov 13 21:42:05 gothic kernel: Call Trace: [] > > __insmod_cpia_S.text_L16504 [cpia] 0x26a7 > > Nov 13 21:42:05 gothic kernel: [sound:num_midis_Ra1eae7cf+184067/98592189] > > __insmod_cpia_S.text_L16504 [cpia] 0x2eab > > Nov 13 21:42:05 gothic kernel: [] __insmod_cpia_S.text_L16504 > > [cpia] 0x2eab > > Nov 13 21:42:05 gothic kernel: [sound:num_midis_Ra1eae7cf+159881/98616375] > > __insmod_videodev_S.text_L2148 [videodev] 0x31 > > Nov 13 21:42:05 gothic kernel: [] __insmod_videodev_S.text_L2148 > > [videodev] 0x31 > > Nov 13 21:42:05 gothic kernel: [sys_read+149/204] sys_read [kernel] 0x95 > > Nov 13 21:42:05 gothic kernel: [] sys_read [kernel] 0x95 > > Nov 13 21:42:05 gothic kernel: [sys_mremap+50/76] sys_mremap [kernel] 0x32 > > Nov 13 21:42:05 gothic kernel: [] sys_mremap [kernel] 0x32 > > Nov 13 21:42:05 gothic kernel: [sys_mremap+66/76] sys_mremap [kernel] 0x42 > > Nov 13 21:42:05 gothic kernel: [] sys_mremap [kernel] 0x42 > > Nov 13 21:42:05 gothic kernel: [system_call+51/56] system_call [kernel] 0x33 > > Nov 13 21:42:06 gothic kernel: [] system_call [kernel] 0x33 > > Nov 13 21:42:06 gothic kernel: > > Nov 13 21:42:06 gothic kernel: > > Nov 13 21:42:06 gothic kernel: Code: Bad EIP value. > > > > > > _______________________________________________ > > cpia mailing list - cpia@risc.uni-linz.ac.at > > zhttp://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > From gstalusan@uwaterloo.ca 14 Nov 2001 21:11:30 -0500 Date: 14 Nov 2001 21:11:30 -0500 From: George Talusan gstalusan@uwaterloo.ca Subject: [cpia] Device is Busy Yes. If the camera stops responding on /dev/video1, and I unplug-then-plug, the camera then lives on /dev/video2. On Wed, 2001-11-14 at 21:08, Axe wrote: > When you disconnect it from the computer, and plug it back in are you able > to reuse the device? If I unplug it, I still get the 'device is busy' > errors... > (I forgot to mention, this is a USB cam) > > > > ----- Original Message ----- > From: "George Talusan" > To: "Axe" > Cc: > Sent: Wednesday, November 14, 2001 12:33 AM > Subject: Re: [cpia] Device is Busy > > > > I have had the same problem as well for a long time now. Unplugging the > > camera and then plugging it back in seems to do the trick, except from > > /dev/video{n} to /dev/video{n+1} each time. > > > > Debian. Kernel 2.4.14 or cvs driver. gqcam. ABit BP6 2x466MHz. > > > > > > > > On Tue, 2001-11-13 at 22:51, Axe wrote: > > > Anyone have a problem with attempting to drop pictures from a CPIA > camera, > > > and it randomly locking /dev/video*? > > > For a few drops, it will work properly, but then poof... heh...it > breaks.. > > > Even though the program exits (I use gqcam), /dev/video* stays 'busy', > and > > > you can't drop anymore frames. > > > When I try to unload the modules, I can unload cpia_usb, cpia_pp, and > > > parport. But cpia and videodev won't unload due to getting a 'device is > > > busy' error. The only way I can get this "fixed" is by rebooting the > > > machine. > > > I'm using RH7.2 kernel version 2.4.9-13 (This has happened with RH7.0 > and > > > 7.1 also). > > > If anyone has any ideas, or needs more info, I'd be glad to hear it. > > > > > > > > > This is the output from the messages file when I unload the three > > > above-mentioned modules: > > > > > > Nov 13 21:42:05 gothic kernel: usb.c: deregistering driver cpia > > > Nov 13 21:42:05 gothic kernel: > > > cpia.c:cpia_unregister_camera_Rc7cb4e91(3243):/dev/video0 removed while > > > open, deferring video_unregister_device > > > Nov 13 21:42:05 gothic kernel: Unable to handle kernel paging request at > > > virtual address c888e65a > > > Nov 13 21:42:05 gothic kernel: printing eip: > > > Nov 13 21:42:05 gothic kernel: c888e65a > > > Nov 13 21:42:05 gothic kernel: *pde = 014a9067 > > > Nov 13 21:42:05 gothic kernel: *pte = 00000000 > > > Nov 13 21:42:05 gothic kernel: Oops: 0000 > > > Nov 13 21:42:05 gothic kernel: CPU: 0 > > > Nov 13 21:42:05 gothic kernel: EIP: > > > 0010:[sound:num_midis_Ra1eae7cf+243282/98532974] Not tainted > > > Nov 13 21:42:05 gothic kernel: EIP: 0010:[] Not tainted > > > Nov 13 21:42:05 gothic kernel: EFLAGS: 00010286 > > > Nov 13 21:42:05 gothic kernel: eax: c70d94bc ebx: c78f2200 ecx: > 00000000 > > > edx: c70d94bc > > > Nov 13 21:42:05 gothic kernel: esi: c70d94b0 edi: c89c0000 ebp: > c1cac000 > > > esp: c1cadf10 > > > Nov 13 21:42:05 gothic kernel: ds: 0018 es: 0018 ss: 0018 > > > Nov 13 21:42:05 gothic kernel: Process gqcam (pid: 1626, > stackpage=c1cad000) > > > Nov 13 21:42:05 gothic kernel: Stack: c78f2200 000b170a c887f707 > c70d94b0 > > > c89c0000 00000000 00000000 c78f2208 > > > Nov 13 21:42:05 gothic kernel: c78f2200 0004a400 40467008 > c887ff0b > > > c78f2200 c1cac000 40467008 00000001 > > > Nov 13 21:42:05 gothic kernel: 0004b000 c15d6250 ffffffea > 00000000 > > > 0004a400 c887a091 c78f22c0 40467008 > > > Nov 13 21:42:05 gothic kernel: Call Trace: > > > [sound:num_midis_Ra1eae7cf+182015/98594241] __insmod_cpia_S.text_L16504 > > > [cpia] 0x26a7 > > > Nov 13 21:42:05 gothic kernel: Call Trace: [] > > > __insmod_cpia_S.text_L16504 [cpia] 0x26a7 > > > Nov 13 21:42:05 gothic kernel: > [sound:num_midis_Ra1eae7cf+184067/98592189] > > > __insmod_cpia_S.text_L16504 [cpia] 0x2eab > > > Nov 13 21:42:05 gothic kernel: [] __insmod_cpia_S.text_L16504 > > > [cpia] 0x2eab > > > Nov 13 21:42:05 gothic kernel: > [sound:num_midis_Ra1eae7cf+159881/98616375] > > > __insmod_videodev_S.text_L2148 [videodev] 0x31 > > > Nov 13 21:42:05 gothic kernel: [] > __insmod_videodev_S.text_L2148 > > > [videodev] 0x31 > > > Nov 13 21:42:05 gothic kernel: [sys_read+149/204] sys_read [kernel] 0x95 > > > Nov 13 21:42:05 gothic kernel: [] sys_read [kernel] 0x95 > > > Nov 13 21:42:05 gothic kernel: [sys_mremap+50/76] sys_mremap [kernel] > 0x32 > > > Nov 13 21:42:05 gothic kernel: [] sys_mremap [kernel] 0x32 > > > Nov 13 21:42:05 gothic kernel: [sys_mremap+66/76] sys_mremap [kernel] > 0x42 > > > Nov 13 21:42:05 gothic kernel: [] sys_mremap [kernel] 0x42 > > > Nov 13 21:42:05 gothic kernel: [system_call+51/56] system_call [kernel] > 0x33 > > > Nov 13 21:42:06 gothic kernel: [] system_call [kernel] 0x33 > > > Nov 13 21:42:06 gothic kernel: > > > Nov 13 21:42:06 gothic kernel: > > > Nov 13 21:42:06 gothic kernel: Code: Bad EIP value. > > > > > > > > > _______________________________________________ > > > cpia mailing list - cpia@risc.uni-linz.ac.at > > > zhttp://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > > > From brandon288@lycos.com Thu, 15 Nov 2001 06:44:44 +0100 Date: Thu, 15 Nov 2001 06:44:44 +0100 From: lau tau tin brandon288@lycos.com Subject: [cpia] cpia webcam 30fps?? miss/mister : i want to run video conferencing over ipv6 on linux's platform, i almost crazy to find out which brand of the webcam can run video conferencing until 30 frames/second. anyone know which brand of the webcam use the cpia driver and the performance quite good (30 fps)?? my system is : a) processor i686, speed 733MHz, RAM 256Mbps b) redhat kernel 2.4.6 (enable ipv6) c) usb-controller UHCI d) driver cpia or ov511 from Prof Dr Brandon Faculty FTSM From jpc1@doc.ic.ac.uk Thu, 15 Nov 2001 12:08:54 +0000 (GMT) Date: Thu, 15 Nov 2001 12:08:54 +0000 (GMT) From: Justin Cormack jpc1@doc.ic.ac.uk Subject: [cpia] cpia webcam 30fps?? > > miss/mister : > > i want to run video conferencing over ipv6 on linux's platform, i almost crazy to find out which brand of the webcam can run video conferencing until 30 frames/second. anyone know which brand of the webcam use the cpia driver and the performance quite good (30 fps)?? my system is : > > a) processor i686, speed 733MHz, RAM 256Mbps > b) redhat kernel 2.4.6 (enable ipv6) > c) usb-controller UHCI > d) driver cpia or ov511 I wouldnt use a USB camera if you want high frame rate. Unless you only want tiny resolution. Even then 30fps is pretty unlikely. I dont know what bandwidth you have, therefore how much compression you need. Or what resolution you require, so I cant give any definite recommendations. Justin From mrenzmann@web.de Thu, 15 Nov 2001 13:43:55 +0100 Date: Thu, 15 Nov 2001 13:43:55 +0100 From: Michael Renzmann mrenzmann@web.de Subject: [cpia] cpia webcam 30fps?? Hi. Justin Cormack wrote: >> i want to run video conferencing over ipv6 on linux's platform, i >> almost crazy to find out which brand of the webcam can run video >> conferencing until 30 frames/second. anyone know which brand of >> the webcam use the cpia driver and the performance quite good (30 >> fps)?? my system is : How about the VC V.Net Network cameras? The new C30U is able of capturing 30fps as MPEG1-Stream. I'm currently working on a library that gives access to the V.Net cam functions. But you should be aware that these cams are not as cheap as webcams ;) If there is interest, I can establish a contact between any person and JVC Professional. Bye, Mike From jpc1@doc.ic.ac.uk Thu, 15 Nov 2001 12:56:16 +0000 (GMT) Date: Thu, 15 Nov 2001 12:56:16 +0000 (GMT) From: Justin Cormack jpc1@doc.ic.ac.uk Subject: [cpia] cpia webcam 30fps?? > > Hi. > > Justin Cormack wrote: > > >> i want to run video conferencing over ipv6 on linux's platform, i > >> almost crazy to find out which brand of the webcam can run video > >> conferencing until 30 frames/second. anyone know which brand of > >> the webcam use the cpia driver and the performance quite good (30 > >> fps)?? my system is : > > How about the VC V.Net Network cameras? The new C30U is able of > capturing 30fps as MPEG1-Stream. I'm currently working on a library that > gives access to the V.Net cam functions. But you should be aware that > these cams are not as cheap as webcams ;) > > If there is interest, I can establish a contact between any person and > JVC Professional. These look quite nice actually, I might be interested (pan and tilt is very useful for some apps). How much are they? The other network camera that you could use is the axis one (www.axis.se). They are about $250, so quite cost effective. Neither would support ipv6 natively, though as the axis ones run Linux, you could in principle upgrade it (it would be quite hard as it runs 2.0 kernel, so you would have to upgrade and might run into space problems, or have to backport ipv6 to 2.0). Either way you could bridge ipv4 to ipv6. There are some other fun solutions if you have plenty of bandwidth, eg buy a dv or mpeg camera with firewire and tunnel the firewire stream over the network. As someone is writing a dv1394 driver that you can just cat into and out of to a camera, you should just be able to run a videoconference with netcat in a single line of shell code... Justin From mrenzmann@web.de Thu, 15 Nov 2001 15:25:27 +0100 Date: Thu, 15 Nov 2001 15:25:27 +0100 From: Michael Renzmann mrenzmann@web.de Subject: [cpia] cpia webcam 30fps?? Hi. Justin Cormack wrote: >>How about the VC V.Net Network cameras? The new C30U is able of >>capturing 30fps as MPEG1-Stream. I'm currently working on a library that >>gives access to the V.Net cam functions. But you should be aware that >>these cams are not as cheap as webcams ;) >>If there is interest, I can establish a contact between any person and >>JVC Professional. > These look quite nice actually, I might be interested (pan and tilt is very > useful for some apps). How much are they? > The other network camera that you could use is the axis one (www.axis.se). > They are about $250, so quite cost effective. The V.Net cams are a bit more expensive compared to the axis cams, but axis does not have tilt/pan heads, afaik. I'm very convinced of these cams by now. > There are some other fun solutions if you have plenty of bandwidth, eg > buy a dv or mpeg camera with firewire and tunnel the firewire stream over > the network. As someone is writing a dv1394 driver that you can just cat > into and out of to a camera, you should just be able to run a videoconference > with netcat in a single line of shell code... That sounds too easy, doesn't it? ;)) Bye, Mike From Michael.McQuay@wcg.com Thu, 15 Nov 2001 09:11:06 -0600 Date: Thu, 15 Nov 2001 09:11:06 -0600 From: McQuay, Michael Michael.McQuay@wcg.com Subject: [cpia] cpia webcam 30fps?? As some of the other responses mentioned, 30 frames/second may not be reliably achieveable with a webcam. However, if you're looking for a decent, cheap webcam, I like the Ezonics EZCam USB. I've tried 3 different webcams, and I like the Ezonics the best. The other two were the IBM PC Camera (which I didn't like at all, very jerky) and a Kensington webcam (which I haven't thoroughly played with, yet). Anyway, of these 3 the Ezonics is the only one that works with the linux cpia driver. -----Original Message----- From: lau tau tin To: cpia@risc.uni-linz.ac.at Sent: 11/14/2001 11:44 PM Subject: [cpia] cpia webcam 30fps?? miss/mister : i want to run video conferencing over ipv6 on linux's platform, i almost crazy to find out which brand of the webcam can run video conferencing until 30 frames/second. anyone know which brand of the webcam use the cpia driver and the performance quite good (30 fps)?? my system is : a) processor i686, speed 733MHz, RAM 256Mbps b) redhat kernel 2.4.6 (enable ipv6) c) usb-controller UHCI d) driver cpia or ov511 from Prof Dr Brandon Faculty FTSM _______________________________________________ cpia mailing list - cpia@risc.uni-linz.ac.at http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From bronson@rinspin.com Thu, 15 Nov 2001 10:21:22 -0800 (PST) Date: Thu, 15 Nov 2001 10:21:22 -0800 (PST) From: Scott Bronson bronson@rinspin.com Subject: [cpia] cpia webcam 30fps?? http://www.cdw.com/shop/products/default.asp?EDC=201935 Another option: Hauppauge boards can be had for less than $60. Plug in a camcorder and get capture speeds limited only by your hard drive. I use one on my Linux box right now. - Scott > As some of the other responses mentioned, 30 frames/second may not be > reliably achieveable with a webcam. However, if you're looking for a > decent, cheap webcam, I like the Ezonics EZCam USB. > > I've tried 3 different webcams, and I like the Ezonics the best. > > The other two were the IBM PC Camera (which I didn't like at all, very > jerky) and a Kensington webcam (which I haven't thoroughly played with, > yet). > > Anyway, of these 3 the Ezonics is the only one that works with the > linux cpia driver. > > > > -----Original Message----- > From: lau tau tin > To: cpia@risc.uni-linz.ac.at > Sent: 11/14/2001 11:44 PM > Subject: [cpia] cpia webcam 30fps?? > > miss/mister : > > i want to run video conferencing over ipv6 on linux's platform, i > almost crazy to find out which brand of the webcam can run video > conferencing until 30 frames/second. anyone know which brand of the > webcam use the cpia driver and the performance quite good (30 fps)?? my > system is : > > a) processor i686, speed 733MHz, RAM 256Mbps > b) redhat kernel 2.4.6 (enable ipv6) > c) usb-controller UHCI > d) driver cpia or ov511 > > from Prof Dr Brandon > Faculty FTSM > > > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From hart@physics.arizona.edu Fri, 16 Nov 2001 09:45:27 -0700 (MST) Date: Fri, 16 Nov 2001 09:45:27 -0700 (MST) From: Sam Hart hart@physics.arizona.edu Subject: [cpia] IntelPlay QX3 problems I actually sent this information to Peter.Pregler@risc.uni-linz.ac.at, but I have some new information and I figured posting to this list would probably be a Good Idea(tm) as well... I have an IntelPlay QX3 microscope that I am trying to get running under Linux. The camera seems to work fine (I can view the feed in xawtv) but I also need to be able to use the lamps on the device. When I run cpia-control 0.3.3 (which is supposed to support the IntelPlay QX3) I get the following error: Ooops: probably you got a floating exception. If the error below is about a 'float() literal too large' you have encountered a python-gtk bug. Either upgrade to version 0.6.3 or greater or unset the locale settings (environment variables LANG and LC_*) and restart the application. In any other case please send me a bug report. empty string for float() The relevent packages I have installed are: python-1.5.2-35 pygtk-0.6.8-3 pygtk-libglade-0.6.8-3 python-devel-1.5.2-35 pygnome-1.4.1-3 gtk+-1.2.10-11 gtk+-devel-1.2.10-11 I originally tried this on a Red Hat 7.2 machine (at work, where I am trying to set this up) with Kernel 2.4.7, but I have also verified that I get the exact same error on my Debian machine at home (with Kernels 2.4.9 & 2.4.12). It looks like from the code the app is just writing data to /proc/cpia/video0 , but when I try to do the same from the command prompt, I get no change in any of the states for the QX3. Is there any advice anyone can give me what I should be doing? We are looking to replace a buggy Win95 machine in a undergrad Physics lab with a Linux box, but we need some sort of reasonable way to control/use this QX3 there. Thx in advance. -- Sam Hart University/Work addr. Personal addr. From Michael.McQuay@wcg.com Fri, 16 Nov 2001 11:07:50 -0600 Date: Fri, 16 Nov 2001 11:07:50 -0600 From: McQuay, Michael Michael.McQuay@wcg.com Subject: [cpia] IntelPlay QX3 problems I'm getting the same error when trying to use cpia-control 0.3.3. I'll be interested to any ideas/suggestions as well. P.S. It used to work for me when I was using a 2.2.X kernel. My kernel now is 2.4.13. -----Original Message----- From: Sam Hart To: cpia@risc.uni-linz.ac.at Sent: 11/16/2001 10:45 AM Subject: [cpia] IntelPlay QX3 problems I actually sent this information to Peter.Pregler@risc.uni-linz.ac.at, but I have some new information and I figured posting to this list would probably be a Good Idea(tm) as well... I have an IntelPlay QX3 microscope that I am trying to get running under Linux. The camera seems to work fine (I can view the feed in xawtv) but I also need to be able to use the lamps on the device. When I run cpia-control 0.3.3 (which is supposed to support the IntelPlay QX3) I get the following error: Ooops: probably you got a floating exception. If the error below is about a 'float() literal too large' you have encountered a python-gtk bug. Either upgrade to version 0.6.3 or greater or unset the locale settings (environment variables LANG and LC_*) and restart the application. In any other case please send me a bug report. empty string for float() The relevent packages I have installed are: python-1.5.2-35 pygtk-0.6.8-3 pygtk-libglade-0.6.8-3 python-devel-1.5.2-35 pygnome-1.4.1-3 gtk+-1.2.10-11 gtk+-devel-1.2.10-11 I originally tried this on a Red Hat 7.2 machine (at work, where I am trying to set this up) with Kernel 2.4.7, but I have also verified that I get the exact same error on my Debian machine at home (with Kernels 2.4.9 & 2.4.12). It looks like from the code the app is just writing data to /proc/cpia/video0 , but when I try to do the same from the command prompt, I get no change in any of the states for the QX3. Is there any advice anyone can give me what I should be doing? We are looking to replace a buggy Win95 machine in a undergrad Physics lab with a Linux box, but we need some sort of reasonable way to control/use this QX3 there. Thx in advance. -- Sam Hart University/Work addr. Personal addr. _______________________________________________ cpia mailing list - cpia@risc.uni-linz.ac.at http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From hart@physics.arizona.edu Fri, 16 Nov 2001 10:18:28 -0700 (MST) Date: Fri, 16 Nov 2001 10:18:28 -0700 (MST) From: Sam Hart hart@physics.arizona.edu Subject: [cpia] IntelPlay QX3 problems On Fri, 16 Nov 2001, McQuay, Michael wrote: > I'm getting the same error when trying to use cpia-control 0.3.3. I'll be > interested to any ideas/suggestions as well. > > P.S. It used to work for me when I was using a 2.2.X kernel. My kernel now > is 2.4.13. Okay, so is this a kernel thing, or some problem with cpia-control and/or one of it's components (such as the newer versions of pygtk)? I.e., can you (or anyone) control the QX3's lamps by reproducing the sequences cpi-control is supposed to send to /proc/cpia/video0 manually? I'd be more than happy to hack together my own custom little GUI for use in our labs if I can just get these lamps to work on my own. Problem is, I know very little about cpia, this device, or what is needed to make it all work. -- Sam Hart University/Work addr. Personal addr. > Ooops: probably you got a floating exception. If the error below > is about a 'float() literal too large' you have encountered a > python-gtk bug. Either upgrade to version 0.6.3 or greater or > unset the locale settings (environment variables LANG and LC_*) > and restart the application. In any other case please send me > a bug report. > > empty string for float() From gleicon@uol.com.br Fri, 16 Nov 2001 16:01:56 -0200 Date: Fri, 16 Nov 2001 16:01:56 -0200 From: Gleicon S. Moraes gleicon@uol.com.br Subject: [cpia] IntelPlay QX3 problems Hi. I dont own one of those qx3, but I got some links that I hope help you to hack your own solution. The spec ( and commands ) http://webcam.sourceforge.net/docs/qx3_cmd.pdf and a post that can help you.. http://mailman.risc.uni-linz.ac.at/pipermail/cpia/2000-January/000377.html regards -- Gleicon S. Moraes -- gleicon@terra.com.br - gleicon@uol.com.br http://videodog.cjb.net http://planeta.terra.com.br/informatica/gleicon/ ----- Original Message ----- From: "Sam Hart" To: Sent: Friday, November 16, 2001 3:18 PM Subject: RE: [cpia] IntelPlay QX3 problems > On Fri, 16 Nov 2001, McQuay, Michael wrote: > > > I'm getting the same error when trying to use cpia-control 0.3.3. I'll be > > interested to any ideas/suggestions as well. > > > > P.S. It used to work for me when I was using a 2.2.X kernel. My kernel now > > is 2.4.13. > > Okay, so is this a kernel thing, or some problem with cpia-control and/or > one of it's components (such as the newer versions of pygtk)? > > I.e., can you (or anyone) control the QX3's lamps by reproducing the > sequences cpi-control is supposed to send to /proc/cpia/video0 manually? > > I'd be more than happy to hack together my own custom little GUI for use > in our labs if I can just get these lamps to work on my own. Problem is, I > know very little about cpia, this device, or what is needed to make it all > work. > > -- > Sam Hart > University/Work addr. > Personal addr. > > > Ooops: probably you got a floating exception. If the error below > > is about a 'float() literal too large' you have encountered a > > python-gtk bug. Either upgrade to version 0.6.3 or greater or > > unset the locale settings (environment variables LANG and LC_*) > > and restart the application. In any other case please send me > > a bug report. > > > > empty string for float() > > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > From Nick.Holloway@pyrites.org.uk 17 Nov 2001 13:03:15 -0000 Date: 17 Nov 2001 13:03:15 -0000 From: Nick Holloway Nick.Holloway@pyrites.org.uk Subject: [cpia] IntelPlay QX3 problems hart@physics.arizona.edu (Sam Hart) writes: > It looks like from the code the app is just writing data to > /proc/cpia/video0 , but when I try to do the same from the command prompt, > I get no change in any of the states for the QX3. The kernel version of the cpia code has had the /proc code disabled, as it was possible to construct badly formed writes which would cause overwrites. Have a look for the "#if 0" in cpia_write_proc in cpia.c. The CVS on SourceForge has rewritten the cpia_write_proc to prevent this problem, but this hasn't been fed back into the official kernel yet. It isn't available as a download either. To get my fully functioning cpia driver in a 2.4 kernel, I took my fresh 2.4.13 kernel, replaced the cpia*.[ch] files from the sourceforge CVS, replaced "spinlock_init" with "spin_lock_init" in cpia_pp.c (typo?), and it now works. -- `O O' | Nick.Holloway@pyrites.org.uk // ^ \\ | http://www.pyrites.org.uk/ From joeja@mindspring.com Sat, 17 Nov 2001 22:17:42 -0800 Date: Sat, 17 Nov 2001 22:17:42 -0800 From: Joseph Acosta joeja@mindspring.com Subject: [cpia] webcam II does not work... Hey I am using kernel 2.4.14 and the webcam II is not working. It seems to work fine with Redhats default kernel 2.4.7, but with 2.4.14 stock kernel it does not work at all. It complains could not open /dev/video0: no such device. However I do have /dev/video0 to 63. I have both parallel port and cpia drivers in the kernel and there is a /proc/cpia/video0 file that says: read-only ----------------------- V4L Driver version: 0.7.4 CPIA Version: 0.00 (0.0) CPIA PnP-ID: 0000:0000:0000 VP-Version: 0.0 0000 system_state: 0x00 grab_state: 0x00 stream_state: 0x00 fatal_error: 0x00 cmd_error: 0x00 debug_flags: 0x00 vp_status: 0x00 error_code: 0x00 video_size: CIF sub_sample: 422 yuv_order: YUYV roi: ( 0, 0) to (352, 288) actual_fps: 0 transfer_rate: 0kB/s read-write ----------------------- current min max default comment brightness: 50 0 100 50 contrast: 48 0 96 48 steps of 8 saturation: 50 0 100 50 sensor_fps: 15.000 3 30 15 stream_start_line: 240 0 288 240 ecp_timing: normal slow normal normal color_balance_mode: auto manual auto auto red_gain: 32 0 212 32 green_gain: 6 0 212 6 blue_gain: 92 0 212 92 max_gain: 2 1,2,4,8 2 exposure_mode: auto manual auto auto centre_weight: on off on on gain: 1 1 max_gain 1 1,2,4,8 possiblefine_exp: 0 0 511 0 coarse_exp: 185 0 65535 185 red_comp: 220 220 255 220 green1_comp: 214 214 255 214 green2_comp: 214 214 255 214 blue_comp: 230 230 255 230 apcor_gain1: 0x1c 0x0 0xff 0x1c apcor_gain2: 0x1a 0x0 0xff 0x1a apcor_gain4: 0x2d 0x0 0xff 0x2d apcor_gain8: 0x2a 0x0 0xff 0x2a vl_offset_gain1: 24 0 255 24 vl_offset_gain2: 28 0 255 28 vl_offset_gain4: 30 0 255 30 vl_offset_gain8: 30 0 255 30 flicker_control: off off on off mains_frequency: 50 50 60 50 only 50/60 allowable_overexposure: 0 0 255 0 compression_mode: auto none,auto,manual auto decimation_enable: off off off off compression_target: quality framerate quality quality target_framerate: 7 0 30 7 target_quality: 10 0 255 10 y_threshold: 15 0 31 15 uv_threshold: 15 0 31 15 hysteresis: 3 0 255 3 threshold_max: 11 0 255 11 small_step: 1 0 255 1 large_step: 3 0 255 3 decimation_hysteresis: 2 0 255 2 fr_diff_step_thresh: 5 0 255 5 q_diff_step_thresh: 3 0 255 3 decimation_thresh_mod: 2 0 255 2 and also a /proc/video/dev/video0 file: name : CPiA Camera type : VID_TYPE_CAPTURE hardware : 0x18 from dmesg: parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] parport0: cpp_daisy: aa5500ff(10) parport0: assign_addrs: aa5500ff(10) parport0: Multimedia device, VLSI Vision Ltd PPC2 Camera parport_pc: Via 686A parallel port: io=0x378 Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.7.4 Parallel port driver for Vision CPiA based cameras v0.7.4 Any ideas what is going on here???? Thanks Joe From c_rrl@yahoo.com Mon, 19 Nov 2001 15:20:58 -0400 Date: Mon, 19 Nov 2001 15:20:58 -0400 From: C R R L c_rrl@yahoo.com Subject: [cpia] EZcam II USB This is a multi-part message in MIME format. ------=_NextPart_000_0011_01C1710D.CA3096A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have a EZcam II USB and encounter does not modulate to make it work in = linux. I want to know if you would haran that EZcam II USB is compatible = with new versions of cpia? Cam which they are supported by cpia many is = to me dificult to find in my pais. To also some already this a little = old. single worked cpia with camold? where they were left new cam?=20 ------=_NextPart_000_0011_01C1710D.CA3096A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have a EZcam II USB and encounter = does not=20 modulate to make it work in linux. I want to know if you would haran = that EZcam=20 II USB is compatible with new versions of cpia? Cam which they are = supported by=20 cpia many is to me dificult to find in my pais. To also some already = this a=20 little old. single worked cpia with camold? where they were left new = cam?=20
------=_NextPart_000_0011_01C1710D.CA3096A0-- _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From jjeskeli@cs.uku.fi Tue, 20 Nov 2001 01:13:47 +0200 Date: Tue, 20 Nov 2001 01:13:47 +0200 From: Jari Eskelinen jjeskeli@cs.uku.fi Subject: [cpia] TerraCam USB not working Hi! I just bought Terratec's TerraCam USB and tried to get it work with Linux, but without success. In Windows cam works without problems, but I bought TerraCam only because it was only cam available with possible Linux-support. I have Debian GNU/Linux with kernel 2.4.14. I compiled USB-support as modules (usbcore, usb-uchi) as well as cpia-drivers and v4l (cpia, cpia_usb, videodev). USB-drivers are loaded without problems. Cpia drivers are loaded, but no camera are found. No files appers in /proc/cpia and /dev/video* won't work. This is very confusing, because thee are no error messages to begin with, so I'm unable to solve this problem. Can anybody tell any ideas to this problem? I'd be grateful. I noticed that cpia-version in kernel is only 0.7.4, and newest package is 1.2.0. So I grabbed latest sources and tried to compile. No success, first error-message was this: cpia.c:4079: too few arguments to function `video_register_device'. I grepped kernel-sources and it seems to be that video_register_device needs one more function, which seemed to be -1 in every video-driver :O So I added it. Then there was errors about struct called video_device cpia_template. Struct format seemed to have changed and I modified struct like some guy had done in one message found in cpia-archives (added NULL to beginning and -1 to end). No success still. root@cannon:~# modprobe usb-uhci usb.c: registered new driver hub usb-uhci.c: $Revision: 1.268 $ time 20:02:38 Nov 19 2001 usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 11 for device 00:07.2 PCI: Sharing IRQ 11 with 00:07.3 PCI: Sharing IRQ 11 with 00:08.0 usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 11 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 11 for device 00:07.3 PCI: Sharing IRQ 11 with 00:07.2 PCI: Sharing IRQ 11 with 00:08.0 usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 11 usb-uhci.c: Detected 2 ports hub.c: USB new device connect on bus1/1, assigned device number 2 usb.c: new USB bus registered, assigned bus number 2 usb.c: USB device 2 (vend/prod 0x5a9/0xa511) is not claimed by any active driver. hub.c: USB hub found hub.c: 2 ports detected usb-uhci.c: v1.268:USB Universal Host Controller Interface driver root@cannon:~# modprobe cpia_usb Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.7.4 usb.c: registered new driver cpia root@cannon:~# cat /dev/video /proc/cpia/* cat: /dev/video: No such device cat: /proc/cpia/*: No such file or directory Even led won't light up in TerraCam. So thanks in advance if somebody can help. -- Jari Eskelinen * http://jarpatus.cjb.net/ * jjeskeli@cs.uku.fi From jjeskeli@cs.uku.fi Tue, 20 Nov 2001 17:35:26 +0200 Date: Tue, 20 Nov 2001 17:35:26 +0200 From: Jari Eskelinen jjeskeli@cs.uku.fi Subject: [cpia] TerraCam USB not working, something changed in hardware? Hi again! Yesterday I wondered why my TerraCam USB won't work with Linux. I explored ome web-sites and it seems my TerraCam is not exactly like original - I noticed now that in box there are sticker which says "New! Now with snapshot button and FaceMail test versio!". Indeed there are button on top of camera, which takes snapshot in Windows. Don't know any other hardware changes though. Does anybody know if this camera could be made to work with cpia-drivers or have the chip changed (to what)? Some minor tweaking? I' no coder, but if I can help somehow with that camera, tell. Thanks for your time! -- Jari Eskelinen * http://jarpatus.cjb.net/ * jjeskeli@cs.uku.fi From jjeskeli@cs.uku.fi Tue, 20 Nov 2001 19:51:09 +0200 Date: Tue, 20 Nov 2001 19:51:09 +0200 From: Jari Eskelinen jjeskeli@cs.uku.fi Subject: [cpia] TerraCam progress Once again here. With my zero-c skills, I tried to find out why my TerraCam won't work. When I loaded usb-module, it reported camera with vendor/product id 0x5a9/0xa511. In cpia-driver version 1.2.0, there wasn't such id's defined in sources. I added those. Now hen I load cpia -module, led in terracam lights up and I can access /proc/cpia/video0 and see all settings camera have. Sounds good, but. No video. When I try to use /dev/video0, it says that no such device. There are (crw-r--r-- 1 root root 81, 0 Nov 20 09:19 /dev/video0). This is where my skills surely will be not enough :) So if somebody can help with this problem, again, I'd be grateful. It seems though that cpia-drivers are not developed actively, because they won't even compile with 2.4.x kernels without modifications :( -- Jari Eskelinen * http://jarpatus.cjb.net/ * jjeskeli@cs.uku.fi From steve.miller@st.com Tue, 20 Nov 2001 10:18:23 -0500 Date: Tue, 20 Nov 2001 10:18:23 -0500 From: Steve Miller steve.miller@st.com Subject: [cpia] TerraCam progress jjeskeli@cs.uku.fi wrote: > > Once again here. > > With my zero-c skills, I tried to find out why my TerraCam won't work. > When I loaded usb-module, it reported camera with vendor/product id > 0x5a9/0xa511. In cpia-driver version 1.2.0, there wasn't such id's > defined in sources. I added those. Now hen I load cpia -module, led in > terracam lights up and I can access /proc/cpia/video0 and see all > settings camera have. Sounds good, but. No video. When I try to use > /dev/video0, it says that no such device. There are (crw-r--r-- 1 > root root 81, 0 Nov 20 09:19 /dev/video0). This is where my > skills surely will be not enough :) > > So if somebody can help with this problem, again, I'd be grateful. It > seems though that cpia-drivers are not developed actively, because they > won't even compile with 2.4.x kernels without modifications :( > This is not a cpia camera. 0x5a9 is OmniVision, it uses the ov511 driver. Steve -- Steve Miller Software Engineer STMicroelectronics phone (602) 485-2014 From steve.miller@st.com Tue, 20 Nov 2001 08:16:34 -0500 Date: Tue, 20 Nov 2001 08:16:34 -0500 From: Steve Miller steve.miller@st.com Subject: [cpia] TerraCam USB not working, something changed in hardware? jjeskeli@cs.uku.fi wrote: > > Hi again! > > Yesterday I wondered why my TerraCam USB won't work with Linux. I > explored ome web-sites and it seems my TerraCam is not exactly like > original - I noticed now that in box there are sticker which says "New! > Now with snapshot button and FaceMail test versio!". Indeed there are > button on top of camera, which takes snapshot in Windows. Don't know > any other hardware changes though. > > Does anybody know if this camera could be made to work with > cpia-drivers or have the chip changed (to what)? Some minor tweaking? > I' no coder, but if I can help somehow with that camera, tell. > > Thanks for your time! > > -- > Jari Eskelinen * http://jarpatus.cjb.net/ * jjeskeli@cs.uku.fi > Can you provide the vendor and device ids? Just do a tail -f on /var/log/messages and plug the camera in. You should see this enumerated. It sounds like they did change the sensor/asic, this will tell you the new one. There is a new version of cpia (cpia2) which has a provision for a button like that, but I don't know if this camera is one. Steve -- Steve Miller Software Engineer STMicroelectronics phone (602) 485-2014 From adavis@saipan.com Thu, 29 Nov 2001 05:56:27 +1000 Date: Thu, 29 Nov 2001 05:56:27 +1000 From: Alan Davis adavis@saipan.com Subject: [cpia] Technical information about VLSI Vision chip (Utobia camera) I have traded a case of beer for a utobia USB camera, which is working fine on my Debian GNU/Linux (sid) box, now. Many sites on the internet describe modifications to the Quickcams, but I have not found much technical information on the VLSI Vision based cameras, including mine. I wish to modify the camera to be an IR sensitive camera. A site describes the modifications for the Quickcam: http://sunflower.bio.indiana.edu/~rhangart/quickcaminfo/quickcammod.html This procedure involves removing an IR filter from the internals of the camera. I have disassembled the utobia USB camera, and it is nicely made, but I don't immediately see any IR filter. There IS a glass plate overlying the CCD. How can I find out what the function of this plate is? If it is an IR filter, then I would remove it. I rather like the camera, and I don't wish to take a chance if it this going to certainly end in grief. The camera is at least modestly sensitive to IR without any modification at all. Interestingly, many astronomy sites describe the use of IR filters with Web cams to do telescope work. Any pointers would be appreciated... Alan Davis Marianas High School Saipan, Northern Mariana Islands adavis@saipan.com From steve.miller@st.com Thu, 29 Nov 2001 08:10:07 -0500 Date: Thu, 29 Nov 2001 08:10:07 -0500 From: Steve Miller steve.miller@st.com Subject: [cpia] Technical information about VLSI Vision chip (Utobia camera) adavis@saipan.com wrote: > > I have traded a case of beer for a utobia USB camera, which is working > fine on my Debian GNU/Linux (sid) box, now. > Many sites on the internet describe modifications to the Quickcams, but I > have not found much technical information on the VLSI Vision based > cameras, including mine. > > I wish to modify the camera to be an IR sensitive camera. A site > describes the modifications for the Quickcam: > > http://sunflower.bio.indiana.edu/~rhangart/quickcaminfo/quickcammod.html > > This procedure involves removing an IR filter from the internals of the > camera. I have disassembled the utobia USB camera, and it is nicely made, > but I don't immediately see any IR filter. There IS a glass plate > overlying the CCD. How can I find out what the function of this plate is? > If it is an IR filter, then I would remove it. I rather like the camera, > and I don't wish to take a chance if it this going to certainly end in > grief. > > The camera is at least modestly sensitive to IR without any modification > at all. Interestingly, many astronomy sites describe the use of IR > filters with Web cams to do telescope work. > > Any pointers would be appreciated... > > Alan Davis > Marianas High School > Saipan, Northern Mariana Islands > adavis@saipan.com > This is not a ccd camera, it uses a cmos sensor array. The clear plate is just to protect the array, it is not intended as an IR filter. Do not remove it. The diodes in the array itself are infused with dye to filter out all but the appropriate color (assuming you have a color camera). I don't know offhand what the spectral characteristics are for these arrays, but if you know which sensor you have (6410, 6407, 6500, etc for color, greyscale is 5xxx) you can get the specs from the vvl website (www.vvl.co.uk). If the chip is in current production you can find a pdf of the datasheet. If you can't find it there (somewhere under the "products" tree), let me know and I'll see if I can track something down (VVL is now part of ST), but no promises that I can find anything. Steve -- Steve Miller Software Engineer STMicroelectronics phone (602) 485-2014