Cams Cpia (Netcam e Videoblaster)

rogeriojlle · 02 de Novembro de 2005, 22:17

Estou com problemas ao instalar os driver para mina webcam, ela é uma Netcam310 porta paralela, a mesma da videoblaster da Creative, inclusive já usei ela no windows com os driver da creative quando perdi o cd original e no site webcam.sourceforge.net o driver é o mesmo pras duas também
O site da creative não oferece mais suporte pra esse equipamento e a Tce(netcam) os links estão todos quebrados
Bom agora pra instalar no Ubuntu estou tendo um problema que não sei como resolver, seguinte:
No gerenciador de pacotes do Ubuntu está lá o CPIA Control, mas não instala o pacote mensagem é a seguinte:
"cpia-control:

O pacote cpia-control não possúi nenhuma versão disponível, mas existe na base de dados.
Isso tipicamente significa que o pacote foi mencionado em uma dependência mas nunca foi enviado para o repositório, foi obsoletado, ou não está disponível com o conteúdo atual do arquivo sources.list."

Ok encontrei os tais pacotes no webcam.sourceforge.net

aí aconteceu algo que realmente não sei como lidar(sou iniciante em linux)
erro:
cpia control depende de python-gtk 1.2; porém:
versão de python no seu sistema é 2.4.2-Oubuntu2

consegui o pacote python-gtk 1.2 tentei intalá-lo mas deu a mesma mensagem anterior:
python-gtk-1.2 depende de python (<< 2.4);porém:
versão de python no seu sistema é 2.4.2-Oubuntu2
Qual é procedimento ?

Aproveitando, alguem tem os drivers da canon ip1000 pro Ubuntu? No site da canon tem só pra SUSE

rogeriojlle · 18 de Novembro de 2005, 02:28

dessa vez vou deixar o texto do tutorial que veio junto, deve ajudar.
O estranho é que os arquivos que o tutorial manda substituir não existem, na tal pasta tem os tais arquivos mas com extensoes diferentes.(cpia.c, cpia_pp.c cpia.h cpia_pp.h, no diretório ....../media/video está com a extensão .ko)
O pacote cpia-control está como pacote quebrado no sinaptic porque uma dependencia dele conflita com uma outra que já está instalada
bom aí vai o texto:

Notes for use with 2.4 kernels.

****************************************************
IMPORTANT:
For users of RedHat 7.x/8.x 2.4.18 kernels
(and other 2.4.18 kernels patched to provide the new
Video4Linux interface - e.g., 2.4.18-ac* kernels)

Changes (in the Linux-2.4.19 kernel) are patched into these 2.4.18
kernels. If you have such a kernel, and you disconnect your CPiA
camera while it is working, a deadlock that can eventually crash your
system will occur. To fix this, apply the patch

redhat-2.4.18-kernel-videodev.patch

to drivers/media/video/videodev.c

(No action is necessary for standard 2.4.18 kernels, or any other
kernel release, though if you also use non-cpia Video4Linux drivers in
2.4.19 or 2.4.20 kernels, it's a good idea to apply this patch...)
****************************************************

The cpia driver included in the 2.4.x series Linux kernels (x <=20) is an
older version that does not yet include all the features and improvements
found in this driver available at http://webcam.sourceforge.net.

Some earlier 2.4.x. kernels have a cpia driver with disabled camera
control so cpia-control cannot be used, or do not support features
of the Intel Play QX3 microscope, and do not support DMA access by fast
ECP parallel ports.
[The support for DMA access for parallel port cpia cameras
is now available here, thanks to Blaise Gassend.]

To use with 2.4.x kernels:

(a) compile the kernel with cpia support. Activate this in the
multimedia devices/video for linux section, select
   CPiA Video for Linux (CONFIG_VIDEO_CPIA)
and, as appropriate,
   CPiA Parallel Port lowlevel support (CONFIG_VIDEO_CPIA_PP)
   CPiA USB lowlevel support (CONFIG_VIDEO_CPIA_USB)

(b) replace the files cpia.c cpia_usb.c cpia_pp.c cpia.h in the
kernel source subdirectory drivers/media/video/
with the ones from here (in the subdirectory "module"), and recompile.

If the kernel source is in /usr/src/linux-2.4/....
go to .../drivers/media/video/
rename the kernel cpia files to cpia.c.orig, cpia.h.orig, etc. and copy
the new versions into this directory. Then cd to /usr/src/linux-2.4, and

make modules

You can now do

make modules_install

or (to avoid messing with your system too much)
cp drivers/media/video/cpia*o /lib/modules/`uname -r`/kernel/drivers/media/video
depmod -ae

This should replace the old drivers with the new ones.

---
Using the CPiA camera: (see also the appended file below ("cpia.txt"))

If you compiled the drivers as modules, load them:

modprobe cpia_usb

or

modprobe cpia_pp

as appropriate for your camera.

start a v4l viewer, like gqcam (see below)

If the camera is at /dev/video0,
cat /proc/cpia/video0 to see what you can control:
e.g.,
echo color_balance_mode: manual > /proc/cpia/video0
echo toplight: on > /proc/cpia/video0
(this is for the QX3 microscope only)

The program cpia-control by Peter Prengler, available at the
sourceforge site, is a graphical interface to (most) of these features,
using /proc/cpia/video[n]. It is now at a cpia-control-0.4 release.

I found gqcam-0.9 works well with the cpia drivers
(get it at http://cse.unl.edu/~cluening/gqcam/ ),
but it needs the following patch
===========begin patch===============================
diff -uNr gqcam-0.9/gqcam.c gqcam-0.9-patched/gqcam.c
--- gqcam-0.9/gqcam.c Tue Nov 7 11:52:06 2000
+++ gqcam-0.9-patched/gqcam.c Tue Dec 17 04:03:34 2002
@@ -55,7 +55,7 @@
camera->savetype = PNG;
camera->capture = 1;
camera->dev = 0;
- strcpy(camera->devname, "/dev/video");
+ strcpy(camera->devname, "/dev/video0");
camera->docked = 1;
camera->dump=0;
camera->speed_fastest = 0;
@@ -96,13 +96,16 @@
ioctl(camera->dev, VIDIOCGWIN, &camera->vid_win);
ioctl(camera->dev, VIDIOCGPICT, &camera->vid_pic);

- for (i = 0; i < 32; i++) {
- vid_clips.x = 0;
- vid_clips.y = 0;
- vid_clips.width = 0;
- vid_clips.height = 0;
- }
+ camera->vid_win.clips = NULL;
+ if (camera->vid_caps.type & VID_TYPE_CLIPPING) {
+ for (i = 0; i < 32; i++) {
+ vid_clips.x = 0;
+ vid_clips.y = 0;
+ vid_clips.width = 0;
+ vid_clips.height = 0;
+ }
camera->vid_win.clips = vid_clips;
+ }
camera->vid_win.clipcount = 0;

if (camera->vid_caps.type & VID_TYPE_MONOCHROME) {
@@ -188,13 +191,16 @@

void open_cam(struct Camera *camera)
{
+ char devname[80];
if((camera->dev<=0)){
camera->dev = open(camera->devname, O_RDWR);
- // printf("Opening: %d\n", camera->dev);
+ printf("Opening: %s %d\n", camera->devname,camera->dev);
+ snprintf(devname,80,"%s",camera->devname);
if (camera->dev < 0) {
- perror("/dev/video");
+ perror(devname);
exit(1);
}
+ print_cam_info(camera);
}
pthread_mutex_unlock( &camera->iscam_mutex );
}
=============end gqcam patch==============================
duncan_haldane@users.sourceforge.net
2002-05-11

--------------------cpia.txt--------------------------------------------

This is a video4linux (v4l1) driver for cameras that use the (now obsolete)
CPiA PPC2 chipset. Both parallel port and USB-connected cameras are supported.

The website for this driver is:
http://webcam.sourceforge.net
http://sourceforge.net/projects/webcam

Author: [1]Peter Pregler, Linz 2000, published under the [2]GNU GPL

This driver is no longer in active development but is is "low-maintenance"
mode[5]: contact the cpia mailing list for maintenance issues.
(see http://webcam.sourceforge.net for mailing list details)
Recent work on improving USB and parallel port transfer modes has been
done, though. (December 2002).
---------------------------------------------------
Devices know to be supported by this driver are:

(a) Parallel port webcams:

Creative Video Blaster WebCam II
CVideo-Mail Express
**-SeeMe Cam Kit
Digicom Galileo Plus
ZoomCam

The driver supports High-speed ECP parallel ports, and will use DMA
if available. It now will also support standard IEEE1284 parallel ports,
using software emulation of ECP on "BiDirectional" (TRISTATE) ports,
or a special enhanced "Nibble" mode on non-Bidirectional PCSPP ports;
but these mode have a low transfer rate of about 60KB/s (about one
compressed frame every one or two seconds). The CPiA firmware does not
support EPP parallel port modes.

The source code for the Windows(TM) 9x parallel port driver has been released
by the CPiA chip maker STM under the GPL as:
http://webcam.sourceforge.net/docs/ppc2.zip
and the CPiA Developer's Guide is also available there.

(b) USB devices:

Intel Play QX3 and QX3+ Microscopes

USB webcams:

Aiptek HyperVcam Fun USB (some use the OV511 chip instead of CPiA!)
Creative Video Blaster WebCam II
Digicom Galileo USB
Dynalink Digital Camera
Ezonics EZCam (Not Pro or Plus)
Microtek EyeStar
Pace Colour Video Camera
SuperCam WonderEye
TCE Netcam 310 USB
Terracam USB(Not Pro)
Trust SpaceC@m Lite
Utobia USB Camera
ZoomCam

---------------------------------------------------------------------------

USAGE:

General:
========

1) Make sure you have created the video devices (/dev/video*):

- if you have a recent MAKEDEV do a 'cd /dev;./MAKEDEV video'
- otherwise do a:

cd /dev
mknod video0 c 81 0

Repeat for /dev/video1, /dev/video2 etc as needed.

2) Compile the kernel (see below for the list of options to use).
If applicable, configure your parport. Reboot.

3) If all worked well you should get messages similar
to the following (your versions may be different) on the console:

V4L-Driver for Vision CPiA based cameras v1.2.2
parport0: read2 timeout.
parport0: Multimedia device, VLSI Vision Ltd PPC2
Parallel port driver for Vision CPiA based camera
CPIA Version: 1.20 (2.0)
CPIA PnP-ID: 0553:0002:0100
VP-Version: 1.0 0100
1 camera(s) found

Building the Driver as modules:
============================

Make sure you have selected the following kernel options (you can
select all stuff as modules):

parallel port:

CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_PC_FIFO=y (needed for high-speed ECP modes, if available)

usb:
CONFIG_USB=m
CONFIG_USB_[OHCI/UHCI/UHCI_ALT/EHCI_HCD]=m (as appropiate for your usb)

The cpia-stuff is in the section 'Character devices -> Video For Linux'.
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_CPIA=m

also, depending on whether you have parport or USB cameras (or both):

CONFIG_VIDEO_CPIA_PP=m
CONFIG_VIDEO_CPIA_USB=m

Finally for controlling the camera using the /proc/cpia/video<n>
interface you need
CONFIG_PROC_FS=y

The cpia module supports the module parameter option:

options cpia usb_alt=[1,2,3] (initial "usb alt interface" setting <usb_alt>)

The usb_alt parameter only affects usb cameras, and selects the
"alternate usb interface setting " that is assigned when the camera is
first registered (i.e., when it is initially plugged in to the USB
hub, and registered as /dev/video<n>).
(see below)

The cpia_pp module supports module options for selecting parallel ports:
options cpia_pp parport=[none,auto,0,1,2,...] (just like lp)

If your parallel port has ECP hardware, it will not get used unless you:
(a) Build the kernel with CONFIG_PARPORT_PC_FIFO=y
(b) You may have to select ECP mode for the parallel port in the computer's
BIOS setup.
(c) load the parport_pc module with options specifying the interrupt
(and dma channel, if available)

For (c), add the following lines to your modutils config-file
(e.g. /etc/modules.conf or wherever your distribution does store that
stuff):

options parport_pc io=0x378 irq=7 dma=3
alias char-major-81 cpia_pp

The first line tells the dma/irq channels to use. Those _must_ match
the settings of your BIOS. Do NOT simply use the values above. See
Documentation/parport.txt for more information about this. The second
line associates the video-device file with the driver. Of cause you
can also load the modules once upon boot (usually done in /etc/modules).

Building the Driver linked into the kernel:
============================================

Make sure you have selected the following kernel options. Note that
you cannot compile the parport-stuff/usb-stuff as modules and the cpia-driver
statically (the other way round is okay though).

CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_1284=y

and/or

CONFIG_USB=y
CONFIG_USB_[OHCI/UHCI/UHCI_ALT/EHCI_HCD]=y

The cpia-stuff is in the section 'Character devices -> Video For Linux'.

CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_CPIA=y
and (as needed):
CONFIG_VIDEO_CPIA_PP=y
CONFIG_VIDEO_CPIA_USB=y

For camera control using /proc/cpia/video<n>,
CONFIG_PROC_FS=y

The kernel-linked cpia_pp driver supports boot-parameter options for
selecting parallel ports: You can give these at the LILO-prompt,
or specify them in lilo.conf, with an append-line:

append="cpia_pp=<...>",

where <...> is one of: [ none, auto, parport <n>], where
<n> is the desired parport number.

To use fast DMA/irq ECP parallel port modes, you will need to tell the kernel
upon boot time the hardware configuration of the parport. You can give the
boot-parameter at the LILO-prompt or specify it in lilo.conf.
I use the following
append-line in lilo.conf:

append="parport=0x378,7,3"

See Documentation/parport.txt for more information about the
configuration of the parport and the values given above. Do not simply
use the values given above.

Sharing the port with lp.
================================.
By default, the driver lp will register itself for all available
parallel ports. Presumably, no printer is sharing a port with the
CPiA camera. (The CPiA does have provision for a "pass-through" mode,
but none of the parallel-port CPiA webcams appear to have a pass-through
port, so the driver does not implement this feature; if it is in
fact needed, the CPiA datasheet and the GPL'd Windows driver available
at the website have the information on how to do it.) In principle
it doesn't matter that lp also is registered on the port, but if it
is causing difficulties, or stopping the cpia_pp driver from
claiming the port, use lp's boot-time or module-load-time
options to prevent it from using the same port as the CPiA.
(For example, "options lp parport=auto" in the modules.conf file)

Using/controlling CPiA cameras.
=================================
The camera is mainly controlled by a V4L application
using the Video4Linux interface, but extra driver settings
not accessible this way can be set by writing to /proc/cpia/video*.

A camera attached as /dev/video0 is controlled by /proc/cpia/video0,
which also gives information about the camera state:

Only the user owning the V4L process that "owns" the camera
can write to the corresponding /proc/cpia/video* file.
The variables listed as "read-only" are informational and cannot be
changed by the user. The "read-write" variables can be changed:

For example "compression_mode" has an entry

read-write
----------------------- current min max default comment

compression_mode: auto none,auto,manual auto

This means the current setting is the default (startup) value of
"auto", but the ranges of possible values is "none,auto,manual".

In "auto" mode, the camera adjusts the compression automatically,
in "none" mode it is disabled. In "manual" mode the user can set
the compression parameters using the /proc/cpia/video* interface.

To change the compression mode of a camera attached to /dev/video0,
mode, type at a command line:

"echo compression_mode: manual > /proc/cpia/video0"

A convenient gtk-python-based graphical application for controlling
the camera in this way is "cpia-control", by Peter Pregler, available
at http://sourveforge.net/projects/webcam.

The camera parameters controllable via the /proc interface,
and their ranges, are given below. Only a limited subset of these are
controllable by the latest cpia-control (v0.41) at this time; these are
marked by "X" in the last column. Other parameters are unlikely to be
changed by regular users. See the cpia Developer's Guide [4] for more
details.

----------------------- min max default comment cpia-control?
usb_alt_setting: 1 3 3 (usb only) X
ecp_timing slow normal normal (parport only*) X
brightness: 0 100 50 X
contrast: 0 96 48 steps of 8 X
saturation: 0 100 50 X
sensor_fps: 3 30 15 X
stream_start_line: 0 288 240
sub_sample: 420 422 422 X
yuv_order: YUYV UYVY YUYV X
color_balance_mode: manual auto auto X
red_gain: 0 212 32 X
green_gain: 0 212 6 X
blue_gain: 0 212 92 X
max_gain: 1 8 2 1,2,4 or 8 ** X
exposure_mode: manual auto auto X
centre_weight: off on on X
gain: 1 max_gain 1 1,2,4,8 possible X
fine_exp: 0 510 0 X
coarse_exp: 0 302 185 X
red_comp: 220 255 220
green1_comp: 214 255 214
green2_comp: 214 255 214
blue_comp: 230 255 230
apcor_gain1: 0x0 0xff 0x1c
apcor_gain2: 0x0 0xff 0x1a
apcor_gain4: 0x0 0xff 0x2d
apcor_gain8: 0x0 0xff 0x2a
vl_offset_gain1: 0 255 24
vl_offset_gain2: 0 255 28
vl_offset_gain4: 0 255 30
vl_offset_gain8: 0 255 30
flicker_control: off on off X
mains_frequency: 50 60 50 only 50/60 X
allowable_overexposure: auto 255 auto
compression_mode: none,auto,manual auto X
decimation_enable: off off on off X
compression_target: framerate quality quality X
target_framerate: 1 30 15 X
target_quality: 1 64 5 X
y_threshold: 0 31 6 X
uv_threshold: 0 31 6 X
hysteresis: 0 255 3
threshold_max: 0 255 11
small_step: 0 255 1
large_step: 0 255 3
decimation_hysteresis: 0 255 2
fr_diff_step_thresh: 0 255 5
q_diff_step_thresh: 0 255 3
decimation_thresh_mod: 0 255 2
toplight: off on off (QX3 microscope only) X
bottomlight: off on off (QX3 microscope only) X

* The "ecp timing" setting switches between a "normal" and a "slow" mode for
ECP image streams from the camera. Use the slow mode if too many frames
are being lost. This setting will not appear unless either hardware
ECP or software ECP (TRISTATE) parallel port modes are available.

** An early version of the CPiA chip (v1.02) has a bug in its firmware; the
driver works around this by imposing lower limits on max_gain and other
settings when this version of the CPiA chip is detected.

Multiple USB cameras on the same hub, and the "usb_alt_setting".
===============================================================

The "usb_alt setting" controls USB bandwidth use by USB cameras by setting
the maximum USB Packet Size for transmission of streamed images. The
three "alternate interface settings" and the corresponding Max PacketSize are
alt 1: 448
alt 2: 704
alt 3: 960 (default)

If two or more cameras are attached to the _same_ USB hub, they can only
work if both are running with reduced USB PacketSize. There is no problem
if they are on different hubs, but if a camera is started at alt setting 3,
the hub interference will cause another cpia device attached to the same hub
to get unregistered, as if its cable had been brutally yanked out!

Until this problem is fixed, here are three possible workarounds:

(1) If you are using the module form of the driver, load the cpia
module with module option "usb_alt=2" or "usb_alt=1". (see above).

(2) If you compile the module into the kernel, edit cpia.h, and
change the line "#define DEFAULT_USB_ALT_SETTING 3" to a lower value,
and rebuild the kernel.

(3) If you can't use either of these strategies, don't despair!

Just open the first camera (say, on /dev/video0) with a
Video4Linux application, so you become the temporary owner of
/proc/cpia/video0. Now change the alt setting with cpia-control v0.4.1 or
later, or by typing "echo usb_alt_setting: 2 > /proc/cpia/video0".
Now close the V4L application; you will no longer be able to write to
/proc/cpia/video0 until you restart the application, but the new alt=2
setting will be remembered as long as the camera remains attached.

Now start the second camera (which will correspond to a different video
device, say /dev/video1). Next reduce its alt setting to alt=2. Now
you can safely reopen the first camera (/dev/video0) which will now start
with the remembered alt=2 setting. Two USB cameras coexist happily
when both are using alt=2. More than two on the same hub may require
alt=1 settings. Non-cpia webcams may have similar ways to reduce the
USB Packet size: e.g., the ov511 driver has a "cams=n" module parameter
which selects among the possible "alt" settings of those USB devices.

The usb alt setting has no effect on parallel-port cameras.

---------------------------------------------------------------------

DRIVER FEATURES:

- mmap/read v4l-interface (but no overlay)
- image formats: CIF/QCIF, SIF/QSIF, various others used by isabel;
note: all sizes except CIF/QCIF are implemented by clipping, i.e.
pixels are not uploaded from the camera
- palettes: VIDEO_PALETTE_GRAY, VIDEO_PALETTE_RGB565, VIDEO_PALETTE_RGB555,
VIDEO_PALETTE_RGB24, VIDEO_PALETTE_RGB32, VIDEO_PALETTE_YUYV,
VIDEO_PALETTE_UYVY, VIDEO_PALETTE_YUV422
- state information (color balance, exposure, ...) is preserved between
device opens
- complete control over camera via proc-interface (_all_ camera settings are
supported), there is also a python-gtk application available for this [3]
- works under SMP (but the driver is completely serialized and synchronous)
so you get no benefit from SMP, but at least it does not crash your box
- might work for non-Intel architecture, let us know about this

---------------------------------------------------------------------------
TESTED APPLICATIONS: (TODO: versions referred to here need updating)

- a simple test application based on Xt is available at [3]
- another test-application based on gqcam-0.4 (uses GTK)
- gqcam-0.6 should work (also gqcam-0.9, with a patch available from
http://sourceforge.net/projects/webcam.)
- xawtv-3.x (also the webcam software)
- xawtv-2.46
- w3cam (cgi-interface and vidcat, e.g. you may try out 'vidcat |xv
-maxpect -root -quit +noresetroot -rmode 5 -')
- vic, the MBONE video conferencing tool (version 2.8ucl4-1)
- isabel 3R4beta (barely working, but AFAICT all the problems are on
their side)
- camserv-0.40

See [3] for pointers to v4l-applications.

---------------------------------------------------------------------------
KNOWN PROBLEMS:

- some applications do not handle the image format correctly, you will
see strange horizontal stripes instead of a nice picture -> make sure
your application does use a supported image size or queries the driver
for the actually used size (reason behind this: the camera cannot
provide any image format, so if size NxM is requested the driver will
use a format to the closest fitting N1xM1, the application should now
query for this granted size, most applications do not).
- all the todo
- if there is not enough light and the picture is too dark try to
adjust the SetSensorFPS setting, automatic frame rate adjustment
has its price
- do not try out isabel 3R4beta (built 135), you will be disappointed

---------------------------------------------------------------------------
TODO: (but driver development is not currently active...).

- multiple camera support (struct camera or something) - This should work,
but hasn't been tested yet (OK, it works, but if a USB camera is streaming
video, and another USB camera is attached to the same hub and run at
alt=3, it causes the first camera to get deregistered.....) (Now done).
- architecture independence?
- SMP-safe asynchronous mmap interface (Done ?)
- nibble mode for old parport interfaces (Done)
- streaming capture, this should give a performance gain
- DMA parport access in 2.4 and later kernels (Done)
- conversion to video4linux-2
---------------------------------------------------------------------------
IMPLEMENTATION NOTES:

The camera can act in two modes, streaming or grabbing. Right now a
polling grab-scheme is used. Maybe interrupt driven streaming will be
used for a asynchronous mmap interface in the next major release of the
driver. This might give a better frame rate.

---------------------------------------------------------------------------
THANKS (in no particular order):

- Scott J. Bertin <sbertin@mindspring.com> for cleanups, the proc-filesystem
and much more
- Henry Bruce <whb@vvl.co.uk> for providing developers information about
the CPiA chip, I wish all companies would treat Linux as seriously
- Karoly Erdei <Karoly.Erdei@risc.uni-linz.ac.at> and RISC-Linz for being
my boss resp. my employer and for providing me the hardware and
allow me to devote some working time to this project
- Manuel J. Petit de Gabriel <mpetit@dit.upm.es> for providing help
with Isabel (http://isabel.dit.upm.es/)
- Bas Huisman <bhuism@cs.utwente.nl> for writing the initial parport code
- Jarl Totland <Jarl.Totland@bdc.no> for setting up the mailing list
and maintaining the web-server[3]
- Chris Whiteford <Chris@informinteractive.com> for fixes related to the
1.02 firmware
- special kudos to all the tester whose machines crashed and/or
will crash.

---------------------------------------------------------------------------
REFERENCES

1. http://www.risc.uni-linz.ac.at/people/ppregler
mailto:Peter_Pregler@email.com
2. see the file COPYING in the top directory of the kernel tree
3. http://webcam.sourceforge.net/
4. CPiA documentation is avaliable at [3].
5. In December 2002 duncan_haldane@users.sourceforge.net was
maintaining the driver. The original authors do not appear to
be active.

rogeriojlle · 18 de Novembro de 2005, 02:58

eu não consigo instalr por causa desse negócio de nome de pacote

rogerio@ubuntu:~$ sudo dpkg -i /home/rogerio/cpia/python-gtk-1.2_0.6.12-2_i386.deb
Selecionando pacote previamente não selecionado python-gtk-1.2.
(Lendo banco de dados ... 58299 arquivos e diretórios atualmente instalados.)
Descompactando python-gtk-1.2 (de .../python-gtk-1.2_0.6.12-2_i386.deb) ...
dpkg: problemas de dependência impedem configuração de python-gtk-1.2:
python-gtk-1.2 depende de python (<< 2.4); porém:
Versão de python no sistema é 2.4.2-0ubuntu2.
dpkg: erro processando python-gtk-1.2 (--install):
problemas de dependência - deixando desconfigurado
Erros foram encontrados durante processamento de:
python-gtk-1.2
rogerio@ubuntu:~$

Cams Cpia (Netcam e Videoblaster)

rogeriojlle

rogeriojlle

rogeriojlle