Vimicro usb PC camera

Koristim Ubuntu Desktop 8.10 i na njemu mi radi skoro sve od hardwera na mom laptopu,osim ove webcam.Pošto sam tek od skora u linux vodama,a tu namjeravam i ostati,akobogda,molim sve iskusnije članove da mi objasne kako pokrenuti ovu webcam.Drivere sam našao,ali kako da ih instaliram?
Hvala unaprijed!

Pošalji nam izlaz naredbe “sudo lsusb” (da identifikujemo uređaj).

Što se tiče drajvera, ako su isti u formi kernel modula, vjerovatno ćeš morati instalirati pakete build-essentials i kernel-headers (valjda se tako zove), onda raspakovati drajver u neki direktorij, otvoriti terminal i kucati komande tipa “./configure; make; sudo make install” ali možda postoji i lakše rješenje.

Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 005: ID 0ac8:303b Z-Star Microelectronics Corp. ZC0303 WebCam
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 08ff:1600 AuthenTec, Inc. AES1600
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Evo što pokaže ta komanda.Šta dalje?

A evo readme file od drivera.

          ZC0301 and ZC0301P Image Processor and Control Chip
                            Driver for Linux

                           - Documentation -


  1. Copyright

  2. Disclaimer

  3. License

  4. Overview and features

  5. Driver installation

  6. Module loading

  7. Module parameters

  8. Supported devices

  9. Notes for V4L2 application developers

  10. Contact information

  11. Credits

  12. Copyright
    Copyright © 2006-2007 by Luca Risolia

  13. Disclaimer
    This software is not developed or sponsored by Z-Star Microelectronics Corp.
    Trademarks are property of their respective owner.

  14. License
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

  1. Overview and features
    This driver supports the video interface of the devices mounting the ZC0301 or
    ZC0301P Image Processors and Control Chips.

The driver relies on the Video4Linux2 and USB core modules of the official and
stable Linux kernels, version 2.6.19 or greater. It has been designed to run
properly on SMP systems as well.

The latest version of the ZC0301[P] driver can be found at the following URL:

Some of the features of the driver are:

  • full compliance with the Video4Linux2 API (see also “Notes for V4L2
    application developers” paragraph);
  • available mmap or read/poll methods for video streaming through isochronous
    data transfers;
  • automatic detection of image sensor;
  • video format is standard JPEG;
  • dynamic driver control thanks to various module parameters (see “Module
    parameters” paragraph);
  • up to 64 cameras can be handled at the same time; they can be connected and
    disconnected from the host many times without turning off the computer, if
    the system supports hotplugging;
  1. Driver installation
    As noted above, kernel 2.6.19 is the minimum for this driver; for it to work
    properly, the driver needs kernel support for Video4Linux and USB.

The following options of the kernel configuration file must be enabled and
corresponding modules must be compiled:

# Multimedia devices

# USB support

In addition, depending on the hardware being used, the modules below are

# USB Host Controller Drivers

The ZC0301 controller also provides a built-in microphone interface. It is
supported by the USB Audio driver thanks to the ALSA API:

# Sound

# Advanced Linux Sound Architecture

# USB devices

Moving along to the ZC0301 driver: after having downloaded the package,
decompress and compile:

[user@localhost home]$ tar xvzf zc0301-x.x.tar.gz
[user@localhost home]$ cd zc0301-x.x

(where “x.x” has to be substituted with the right version of the module just

It is necessary to properly configure your particular kernel source tree before
compiling the driver. The modular building process is used; therefore you must
have read and write access to your kernel source tree. If not, log in as root
before running the following commands:

[user@localhost zc0301-x.x]$ make clean
[user@localhost zc0301-x.x]$ make modules

If the commands fail, control the Makefile and change the path to the kernel
source tree or to any other files, according to your system configuration;
then run the previous commands again.

If everything went well, the ZC0301 driver can be used either immediatly
(skip to the next paragraph) or be installed.

The driver will not be installed in the default directory reserved for modules
being built outside the kernel. This means that the possible version of the
driver present in the official Linux kernel tree might be overwritten during
the installation process.

To install the driver, run as root:

[root@localhost zc0301-x.x]# make modules_install
  1. Module loading
    To use the driver, it is necessary to load the “zc0301” module into memory
    after every other module required: “videodev”, “v4l2_common”, “compat_ioctl32”,
    “usbcore” and, depending on the USB host controller you have, “ehci-hcd”,
    “uhci-hcd” or “ohci-hcd”.

Loading can be done as shown below.

If the ZC0301 driver has been installed as shown in the previous

[root@localhost home]# modprobe zc0301

otherwise, if you have not installed the driver, but have just compiled it,
run “insmod” indicating the path to the module; for example:

[root@localhost zc0301-x.x]# insmod ./zc0301.ko

At this point the devices should be recognized. You can invoke “dmesg” to
analyze kernel messages and verify that the loading process has gone well:

[user@localhost home]$ dmesg
  1. Module parameters
    Module parameters are listed below:

Name: video_nr
Type: short array (min = 0, max = 64)
Syntax: <-1|n[,…]>
Description: Specify V4L2 minor mode number:
-1 = use next available
n = use minor number n
You can specify up to 64 cameras this way.
For example:
video_nr=-1,2,-1 would assign minor number 2 to the second
registered camera and use auto for the first one and for every
other camera.
Default: -1

Name: force_munmap
Type: bool array (min = 0, max = 64)
Syntax: <0|1[,…]>
Description: Force the application to unmap previously mapped buffer memory
before calling any VIDIOC_S_CROP or VIDIOC_S_FMT ioctl’s. Not
all the applications support this feature. This parameter is
specific for each detected camera.
0 = do not force memory unmapping
1 = force memory unmapping (save memory)
Default: 0

Name: frame_timeout
Type: uint array (min = 0, max = 64)
Syntax: <n[,…]>
Description: Timeout for a video frame in seconds. This parameter is
specific for each detected camera. This parameter can be
changed at runtime thanks to the /sys filesystem interface.
Default: 2

Name: debug
Type: ushort
Description: Debugging information level, from 0 to 3:
0 = none (use carefully)
1 = critical errors
2 = significant informations
3 = more verbose messages
Level 3 is useful for testing only, when only one device
is used at the same time. It also shows some more informations
about the hardware being detected. This module parameter can be
changed at runtime thanks to the /sys filesystem interface.
Default: 2

  1. Supported devices
    None of the names of the companies as well as their products will be mentioned
    here. They have never collaborated with the author, so no advertising.

From the point of view of a driver, what unambiguously identify a device are
its vendor and product USB identifiers. Below is a list of known identifiers of
devices mounting the ZC0301 Image Processor and Control Chips:

Vendor ID Product ID

0x041e 0x4017
0x041e 0x401c
0x041e 0x401e
0x041e 0x401f
0x041e 0x4022
0x041e 0x4034
0x041e 0x4035
0x041e 0x4036
0x041e 0x403a
0x0458 0x7007
0x0458 0x700c
0x0458 0x700f
0x046d 0x08ae
0x055f 0xd003
0x055f 0xd004
0x0ac8 0x0301
0x0ac8 0x301b
0x0ac8 0x303b
0x10fd 0x0128
0x10fd 0x8050
0x10fd 0x804e

The list above does not imply that all those devices work with this driver: up
until now only the ones that mount the following image sensors are supported;
kernel messages will always tell you whether this is the case:

Model Manufacturer

PAS202BCB PixArt Imaging, Inc.
PB-0330 Photobit Corporation

  1. Notes for V4L2 application developers
    This driver follows the V4L2 API specifications. In particular, it enforces two
  • exactly one I/O method, either “mmap” or “read”, is associated with each
    file descriptor. Once it is selected, the application must close and reopen the
    device to switch to the other I/O method;

  • although it is not mandatory, previously mapped buffer memory should always
    be unmapped before calling any “VIDIOC_S_CROP” or “VIDIOC_S_FMT” ioctl’s.
    The same number of buffers as before will be allocated again to match the size
    of the new video frames, so you have to map the buffers again before any I/O
    attempts on them.

  1. Contact information
    The author may be contacted by e-mail at

GPG/PGP encrypted e-mail’s are accepted. The GPG key ID of the author is
’FCE635A4’; the public 1024-bit key should be available at any keyserver;
the fingerprint is: ‘88E8 F32F 7244 68BA 3958 5D40 99DA 5D2A FCE6 35A4’.

  1. Credits
  • Informations about the chip internals needed to enable the I2C protocol have
    been taken from the documentation of the ZC030x Video4Linux1 driver written
    by Andrew Birkett;
  • The initialization values of the ZC0301 controller connected to the PAS202BCB
    and PB-0330 image sensors have been taken from the SPCA5XX driver maintained
    by Michel Xhaard;
  • Stanislav Lechev donated one camera.

Mozda ce pomoci,ali moja malenkost nije mogla da skonta ovo.

Trebalo bi da radi sama od sebe. Instaliraj program Cheese i probaj. Šta ispiše?

Ako ne radi, pogledaj ovo:

Da obavjestim članove foruma,webcam je proradila na aMSN,ali užasno sporo i nekako mi se čini da je fokus kamere pomjeren u lijevo,u odnosu na ono što snima.I dalje očekujem pomoć,hvala.