Bonjour Je voulais savoir si quelqu'un a déjà réussi l'installation d'une webcam Logitech QuickCam Pro 4000 sous Linux. Il existe des drivers disponible ci-dessous http://www.smcc.demon.nl/webcam/ Par contre leur developpement a été arrêté. Je n'ai jamais réussi à comprendre comment les installer... Si quelqu'un pourrait expliquer en détail son installation se serait Super...

qu'est-ce que dit le fichier "install" quand tu désarchives pwc-xxxxx.tar.gz ?????

je viens de découvrir qu'il y a plein de fichiers html dans un des dossier dont un pour l'install Installation notes 8.* Since the PWC driver 8.0 and higher are in the main Linux kernel tree, you probably don't have to install anything on your system; just load the kernel module pwc.o and optionally pwcx.o and you should be up and running. Here's an extremely small HOWTO for upgrading your PWC in your current kernel; it's not very specific for the very simple reason that there are way too many different Linux distributions and I cannot describe them all. So I assume you know at least how to copy files, build a kernel, etc. Locate your kernel sources; they are usually installed in /usr/src/linux or something like /usr/src/linux-2.4.20. Check if the full source is available; if there are only include files present, install the full source from CD or DVD. Better yet, download a vanilla kernel from kernel.org and built from that. Start up the kernel configurator, with 'make menuconfig', 'make xconfig' or any (graphical) tool that's available on your system. Make sure the "Philips Webcam driver" is enabled under the USB section; you may have to turn on "Video 4 Linux" first. Compile as module. Exit the configurator. Go to drivers/usb/ (drivers/usb/media/ for kernel 2.5/2.6). There you will find the existing PWC driver. Check the version number in pwc.h Copy the *.c and *.h files from the pwc-X.Y.tar.gz packaged over the existing ones. Go back to the root of the kernel sources, and do a 'make modules', followed by 'make modules_install' as root. If this all went well, you should now have a new PWC module available for your system! I will write a small HOWTO soon if you want/need to upgrade the PWC in your kernel. For module parameters, etc., see >Documentation/usb/philips.txt in the kernel source for the latest information. RedHat 7.3/7.2 For those who are less familiair with building kernels and loading modules or are afraid to login as 'root', Curt Noll put up elaborate instrunctions on his site on how configure your RedHat system, including fully Automated hotplug support. Please direct all questions regarding these instructions to Curt Noll, and no, it's no use asking me or Curt for instructions on other Linux distributions. RedHat 7.3 RedHat 7.2 Installation notes for older versions of PWC Common installation problems First, if you get these errors while loading the module: /lib/modules/2.4.3/kernel/drivers/usb/pwc.o: unresolved symbol kmalloc /lib/modules/2.4.3/kernel/drivers/usb/pwc.o: unresolved symbol kfree /lib/modules/2.4.3/kernel/drivers/usb/pwc.o: unresolved symbol printk you forgot to turn module versioning off in your current kernel (or your Linux distribution has such a kernel installed for you). Recompile and install your kernel without this. Second, I've received a number of error reports that unfortunately have nothing to do with my driver. The error messages look like this: usb.c: USB device not accepting new address=10 (error=-110) hub.c: USB new device connect on bus1/1, assigned device number 12 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=12 (error=-110) The key phrase in here is "device not accepting new address". When a USB device is plugged in, it gets assigned a unique bus number (the address) by the USB core; only after this succeeds the device is probed for its Vendor and Device ID and a driver is sought. But appearantly this fails, and the USB device does not accept the new address. There can be a number of causes: obnoxious USB controllers (the most common problem) power overcurrent condition (= too many devices attached) poor cabling faulty HUBs etc. etc. The long and short of it is: it has nothing to do with my driver, so please don't send me bug reports when this happens. However, there are a few things you can try out: Make sure all USB connectors are inserted properly; it should be seated firmly, and not wiggly. Plug the cam directly into the PC. Use powered USB hub. In case of a laptop, use the power supply with it. When using the battery, the voltage may drop. Try the latest kernel that is available, even the 2.4.0-test* and 2.5, when available. If this doesn't help, try the linux-usb-user mailinglist at SourceForge. Try to search the archives first. When you must mail, make sure to include a description of your hardware (motherboard, USB controller, kernel, etc). Module load order This isn't strictly related to the Philips Webcam modules, but it's useful information anyway. The best order in which to load your USB modules is to load all 'device' drivers first (audio, pwc, acm, scanners, etc), and finally your USB controller (usb-uhci, usb-ohci). If you do it the other way around, you'll get spammed crazy by the USB-core with descriptor dumps because it couldn't find a driver for a particular device. The order in which you load the device drivers doesn't matter. Si je comprend bien le PWC devrait déjà être installé...j'ai trouvé des lignes contenant pwc dans le fichier suivant /lib/modules/2.6.3-19mdk/modules.usbmap tout cela c'est très floue pour moi je viens de brancher à chaud la webcam....hardrake détecte qu'il y a une webcam sur un port usb et que le module PWC est utilisé....mais dans "classe de materiel" et "description" il n'y a rien... PWC est donc bien installé...

Modifié par libertylaurent le 31/10/2004 17:12

en ce qui concerne le PWCX....voici le readme README for PWCX 9.0 This package contains code and patches to get PWCX running on a variety of kernels and processors. Hopefully this will eliminate a lot of the versioning problems. This is the official release, after 2 betas which have wrinkled out quite a lot of details. This release contains patches for 2.4.25 and 2.6.4 (may work on other kernels with a little tweaking). In addition, it contains the PWCX core code for the following CPUs: - ARM (hard- & software floating point) - MIPS (mips1 & mips4) - PowerPC - SH4 - x86 - ia64 (Itanium) In addition a small test utility is provided to test some new features from PWC 9 (more below). The idea behind this PWCX is simple: provide a small library (libpwcx.a) that gets linked against a small piece of 'glue' C code that is compiled in the kernel and contains all the kernel specific module stuff. The added bonus is that with a little support from the kernel driver it is possible to do decompression outside of the kernel, in your application. This allows you to stream the raw data from the camera over a limited bandwidth channel (old 10 MBit/s UTP, wireless LAN), and decompress at the remote end. Note: PWC/PWCX 9 is incompatible with PWC/PWCX 8 (that's why I bumped the major version number in the first place). I do not intend to try a similar approach for PWC 8. * Open issues - Currently the Bayer format does not work, while it did work okay in beta-2. Not sure what the problem is, IŽll look into it. * Changes ** 9.0 Official - Removed PWC 9.0 from the package, only PWCX is left. * Installation notes Below generic installation instructions are provided for 2.4 and 2.6 kernels. I assume you have at least some knowledge of kernel building; no real kernel compile is required: just modules. NB: the directorynames below may of course be different on your system; adjust as necessary. ** Installation 2.4.25 (probably works on 2.4.26 as well) - Download the tarball, extract (you probably already did this). I assume it is extracted in your homedirectory. - Go to your kernel sources (usually located in /usr/src/linux) # cd /usr/src/linux - Apply the proper patch for your kernel; this will modify the USB build structure # patch -p1 -s < ~/pwcx-9.0/patch-2.4.25 - Copy the proper libpwcx.a to the directory; see the various subdirectories for builds of the library. You may also have to rename the library while copying, e.g. # cp ~/pwcx-9.0/mipsel/libpwcx-mips4.a drivers/usb/libpwcx.a - Copy the glue code to the directory # cp ~/pwcx-9.0/pwcx/*.[ch] drivers/usb - Start up your kernel configurator # make menuconfig or # make xconfig - Go the USB section; you will find a "PWCX decompressor entry"; enable it as module - Build your modules: # make modules modules_install - If all went well, you now have a working PWCX on your system! !! Do not execute a 'make dep' or 'make clean' in your kernel source tree! !! That will remove all .a files :-( ** Installation 2.6.4 - Download the tarball, extract (you probably already did this). I assume it is extracted in your homedirectory. - Go to your kernel sources (usually located in /usr/src/linux) # cd /usr/src/linux - Apply the proper patch for your kernel; this will modify the USB build structure # patch -p1 -s < ~/pwcx-9.0/patch-2.6.4 - Copy the proper libpwcx.a to the directory; see the various subdirectories for builds of the library. You may also have to rename the library while copying, e.g. # cp ~/pwcx-9.0/mipsel/libpwcx-mips4.a drivers/usb/media/libpwcx.a - Copy the glue code to the directory # cp ~/pwcx-9.0/pwcx/*.[ch] drivers/usb/media - Start up your kernel configurator # make menuconfig or # make xconfig - Go the USB section; you will find a "PWCX decompressor entry"; enable it as module - Build your modules: # make modules modules_install - If all went well, you now have a working PWCX on your system! !! Do not execute a 'make dep' or 'make clean' in your kernel source tree! !! That will remove all .a files :-( ** TestPWCX I've also included a small test utility; it demonstrates two new features of PWC 9: raw data streaming + external decompression and Bayer image data (the latter will probably enlighten amateur astronomers (pun intentional :-))). testpwcx is a small Qt application and it requires also the libpwcx.a library, since it does decompression outside of the kernel. - Go to the testpwcx directory # cd ~/pwcx-9.0/testpwcx - Copy the proper pwcx.a to this directory (see kernel instructions above). # cp ../<CPU>/libpwcx.a . - Configure and build the application # qmake testpwcx.pro # make If that goes well you end up with a 'testpwcx' executable. Its use is simple: # testpwcx [options] /dev/videoX It will show the YUV data from the device (thus grayscale, not color). The supported options are: -r Use raw data from the device, perform decompression inside the program -B Show Bayer data For those interested: "Bayer data" refers to the layout on the CMOS/CCD sensor of the light-sensitive pixels; usually 1 red, 2 green and 1 blue in a 2x2 grid. The advantage of this mode is that you get the real, _unprocessed_ data straight from the CCD/CMOS (well, okay, it is compressed, but only by a factor of less than 2; I doubt you will ever notice that). I refrain from calling it "raw data" to avoid any confusion with the uncompressed datastream. C'est le grand floue à nouveau J'espere qu'il n'y aura pas de probleme avec le kernel car le mien (2.6.3-19) est inferieur au 2.6.4

A priori il te faut les sources du kernel. Ensuite tu lances Gnomeeting voir si il accroche une image en provenance de la webcam

Bonsoir Torrent...le kernel source est installé...je vais voir ce que cela donne avec gnomeeting

Elle marche !!! Avec la mandrake 9.2 le pc ne bootait même pas si la webcam était branchée... Avec la mandrake 10 kernel 2.6.3-7 j'avais essayé mais ça marchais pas...mais avec ce kernel 2.6.3-19 ça fonctionne....et sur tout les ports USB 1.1 et 2....j'utilise la carte son audigy2 pour la sortie audio et la carte son intégrée pour l'entré micro (car alsa ne marche pas en entrée audio avec la audigy) et le tout semble fonctionner sans problème...Pas de diffirence de qualité avec windows en ce qui concerne l'image...

La webcam marche mais il faut que je la branche à chaud après le boot... si elle est branchée quand je boot la mandrake je n'ai plus de son et une erreur apparait... plus de carte son dans kmix...

C'est une webcam avec microphone ? Essaies de changer ton serveur de son, si t'es sous OSS passes à ALSA & vice-versa

bonjour Torrent oui c'est une webcam avec microphone En ce qui concerne ALSA j'aimerais le conserver car la qualité audio est bien meilleur que sous OSS...tant pis je vais faire avec ce petit désagrément

à ma grande honte, je ne me suis jamais interessé au "son" sous Linux !!! pourriez-vous me donner quelques renseignements avant que je n'aille lire un ou 2 "howtos" ? quand je lance sur ma machine: ntsysv je vois: alsactl [*] --> est-ce le serveur son "alsa" dont vous parlez ? ceci m'est confirmé par la formidable commande: chkconfig --list | grep alsa alsactl 0:Arrêt 1:Arrêt 2:Marche 3:Marche 4:Marche 5:Marche 6:Arrêt qui permet de voir que "alsactl" est mis en "marche" dans les niveaux 2,3,4,5 et arreté dans les autres --> est-ce que vous utiliseriez "chkconfig --add" et "chkconfig --del" pour passer de alsa à oss ??? ou une autre manière ??? merci .................. ;-)

Non, dans le panneau de configuration de kde.

En interphase graphique (désolé je connais pas trop le moteur linux !!!) K --> Systeme --> KDE --> Son --> Systeme de sons (j'espere que c'est cela que tu recherche) pour ma part je vais peut-être desinstaller ALSA puis reinstaller la derniere version stable de ALSA...je l'avais déjà fait une fois sur la MDK 9.2 mais sans rien y comprendre) peut-être que l'entrée audio de la audigy2 sera active...