https://elinux.org/api.php?action=feedcontributions&user=Rmast&feedformat=atomeLinux.org - User contributions [en]2024-03-28T22:55:56ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=RPi_Linaro_GCC_Compilation&diff=416626RPi Linaro GCC Compilation2016-08-11T18:16:02Z<p>Rmast: /* Configure system to use new compiler */</p>
<hr />
<div>[[Category: RaspberryPi]]<br />
{{Template:RPi_Software}}<br />
<br />
==Overview==<br />
<br />
This page explains how to build yourself a version of Linaro GCC specifically for building software for the RPi.<br />
<br />
From the Linaro website: "Linaro GCC is performance focused branch of the current GCC stable release and includes backports of the improvements and bug fixes that Linaro and others have done upstream" <ref>https://launchpad.net/gcc-linaro</ref><br />
<br />
==Requirements==<br />
<br />
This process should be carried out on the Linux system you wish to compile RPi software on. Therefore, you will require a reasonably powerful computer (preferably 64bit). If you are running on Windows, it is possible to use a linux virtual machine running on [https://www.virtualbox.org/ Virtualbox]. The only software required is [http://crosstool-ng.org/ crosstool-NG] (plus its dependencies).<br />
<br />
==Procedure==<br />
The whole process takes about an hour on a dual-core 2.8GHz 64-bit AMD system using an 8Mbit ADSL connection.<br />
NOTE: This procedure was tested on 24th November 2012 using crosstool-ng 1.17.0. It may not be accurate for newer versions of the software.<br />
<br />
===Install crosstool-NG===<br />
* Download the crosstool-NG source (from http://crosstool-ng.org/).<br />
* Extract the source tarball into your home directory: <br />
<pre><br />
tar -xjvf crosstool-ng-1.17.0.tar.bz2<br />
</pre><br />
* Or clone a more recent version from git, I saw this newest version work as well:<br />
<br />
<pre><br />
git clone https://github.com/crosstool-ng/crosstool-ng.git<br />
cd crosstool-ng<br />
git checkout 1.22<br />
</pre><br />
<br />
* Change to the extracted directory, then configure it. You should specify an installation prefix to keep it separate from the OS in case you want to run multiple versions - we are using <tt>/opt/crosstool-ng-1.17.0</tt> in this example:<br />
<pre><br />
./configure --prefix=/opt/crosstool-ng-1.17.0<br />
</pre><br />
<br />
* If configure fails due to missing dependencies, install them for your platform using the package manager (i.e. yum install, apt-get install, etc.)<br />
* during the build you might need packages for expat, libexpat1-dev, python-dev<br />
* When configure completes successfully, make and install it:<br />
<pre><br />
make<br />
make install<br />
</pre><br />
* Add the crosstool-NG bin folder to your path. The easiest way to do this is add it to PATH in your <tt>.profile</tt>, for example: <br />
<pre><br />
PATH=$PATH:/opt/crosstool-ng-1.17.0/bin<br />
</pre><br />
<br />
===Build GCC Linaro===<br />
* Make a new directory in your home directory where you want to run crosstool-NG, then change to it.<br />
* Configure crosstool-NG:<br />
<pre><br />
ct-ng menuconfig<br />
</pre><br />
* Set the following options (derived from the arm-bcm2708hardfp-linux-gnueabi build on GitHub):<br />
** Paths & Misc: <br />
*** Check "Try features marked as EXPERIMENTAL"<br />
*** Set "Prefix directory" to whereever you want the finished toolchain to be placed (e.g. /home/<yourname>/crosscompile)<br />
*** Set "Number of parallel jobs" to be the number of processor cores in your system x1.5<br />
** Target options:<br />
*** Set "Target architecture" to "ARM"<br />
*** Set "Endianness" to "Little endian"<br />
*** Set "Bitness" to "32-bit"<br />
*** Set "Architecture level" to "armv6zk"<br />
*** Set "Emit assembly for CPU" to "arm1176jzf-s"<br />
*** Set "Tune for CPU" to "arm1176jzf-s"<br />
*** Set "Use specific FPU" to "vfp"<br />
*** Set "Floating point" to "hardware (FPU)"<br />
*** Set "Default instruction set mode" to "arm"<br />
*** Check "Use EABI"<br />
** General toolchain:<br />
*** Set "Tuple's vendor string" to "rpi" - you can choose whatever you like here and it will appear in the compiler filenames.<br />
** Operating system:<br />
*** Set "Target OS" to "linux"<br />
*** Set "Linux kernel version" to match that running on the RPI (it was tested with the 3.6 branch patched to version 3.6.3)<br />
** Binary utilities:<br />
*** Set "Binary format" to "ELF"<br />
*** Set "binutils version" to "2.22"<br />
** C compiler:<br />
*** Check "Show linaro versions"<br />
*** Set "gcc version" to "linaro-4.7-2012.10"<br />
*** Check "C++"<br />
*** Set "gcc extra config" to "--with-float=hard" (Note: see "Discussion" page)<br />
*** Check "Link libstdc++ statically into gcc binary"<br />
** C-library:<br />
*** Set "C library" to "eglibc", or, as eglibc gets deprecated<ref>http://www.eglibc.org/home</ref>, glibc from version 2.19 up.<br />
*** Set "eglibc version" to "2_13", however, to reduce the size of your executables you could also try to match it with the libc already present on the Pi and select a custom libc-version here, for example the exact commit your libc was build from if you can reveal that. The major version of libc can be made visible with <br />
<pre><br />
ldd <br />
</pre><br />
<br />
* Build it:<br />
<pre><br />
ct-ng build<br />
</pre><br />
* All the required source will now be downloaded and built - exact times vary according to processing power and internet connection speed.<br />
<br />
===Configure system to use new compiler===<br />
Your compiler will be located in <tt>/home/<yourname>/crosscompile</tt> (or whereever you specified in the configuration). You can choose to move it to another location (e.g. /opt/arm) if you want to. Then, add that location to your PATH:<br />
<pre><br />
PATH=$PATH:/opt/arm/bin:/opt/crosstool-ng-1.17.0/bin<br />
</pre><br />
<br />
Now if you run:<br />
<pre><br />
arm-rpi-linux-gnueabi-gcc -v<br />
</pre><br />
you should get the version information from your new build. It should end something like:<br />
<pre><br />
gcc version 4.7.3 20121001 (prerelease) (crosstool-NG 1.17.0)<br />
</pre><br />
<br />
By the way, this manual also works for the newest stable gcc-linaro-5.3-2016.05 at http://releases.linaro.org/components/toolchain/gcc-linaro/5.3-2016.05/<br />
<br />
==References==<br />
<references/><br />
<br />
{{Template:Raspberry Pi}}</div>Rmasthttps://elinux.org/index.php?title=RPi_Linaro_GCC_Compilation&diff=416621RPi Linaro GCC Compilation2016-08-11T18:08:33Z<p>Rmast: /* Build GCC Linaro */</p>
<hr />
<div>[[Category: RaspberryPi]]<br />
{{Template:RPi_Software}}<br />
<br />
==Overview==<br />
<br />
This page explains how to build yourself a version of Linaro GCC specifically for building software for the RPi.<br />
<br />
From the Linaro website: "Linaro GCC is performance focused branch of the current GCC stable release and includes backports of the improvements and bug fixes that Linaro and others have done upstream" <ref>https://launchpad.net/gcc-linaro</ref><br />
<br />
==Requirements==<br />
<br />
This process should be carried out on the Linux system you wish to compile RPi software on. Therefore, you will require a reasonably powerful computer (preferably 64bit). If you are running on Windows, it is possible to use a linux virtual machine running on [https://www.virtualbox.org/ Virtualbox]. The only software required is [http://crosstool-ng.org/ crosstool-NG] (plus its dependencies).<br />
<br />
==Procedure==<br />
The whole process takes about an hour on a dual-core 2.8GHz 64-bit AMD system using an 8Mbit ADSL connection.<br />
NOTE: This procedure was tested on 24th November 2012 using crosstool-ng 1.17.0. It may not be accurate for newer versions of the software.<br />
<br />
===Install crosstool-NG===<br />
* Download the crosstool-NG source (from http://crosstool-ng.org/).<br />
* Extract the source tarball into your home directory: <br />
<pre><br />
tar -xjvf crosstool-ng-1.17.0.tar.bz2<br />
</pre><br />
* Or clone a more recent version from git, I saw this newest version work as well:<br />
<br />
<pre><br />
git clone https://github.com/crosstool-ng/crosstool-ng.git<br />
cd crosstool-ng<br />
git checkout 1.22<br />
</pre><br />
<br />
* Change to the extracted directory, then configure it. You should specify an installation prefix to keep it separate from the OS in case you want to run multiple versions - we are using <tt>/opt/crosstool-ng-1.17.0</tt> in this example:<br />
<pre><br />
./configure --prefix=/opt/crosstool-ng-1.17.0<br />
</pre><br />
<br />
* If configure fails due to missing dependencies, install them for your platform using the package manager (i.e. yum install, apt-get install, etc.)<br />
* during the build you might need packages for expat, libexpat1-dev, python-dev<br />
* When configure completes successfully, make and install it:<br />
<pre><br />
make<br />
make install<br />
</pre><br />
* Add the crosstool-NG bin folder to your path. The easiest way to do this is add it to PATH in your <tt>.profile</tt>, for example: <br />
<pre><br />
PATH=$PATH:/opt/crosstool-ng-1.17.0/bin<br />
</pre><br />
<br />
===Build GCC Linaro===<br />
* Make a new directory in your home directory where you want to run crosstool-NG, then change to it.<br />
* Configure crosstool-NG:<br />
<pre><br />
ct-ng menuconfig<br />
</pre><br />
* Set the following options (derived from the arm-bcm2708hardfp-linux-gnueabi build on GitHub):<br />
** Paths & Misc: <br />
*** Check "Try features marked as EXPERIMENTAL"<br />
*** Set "Prefix directory" to whereever you want the finished toolchain to be placed (e.g. /home/<yourname>/crosscompile)<br />
*** Set "Number of parallel jobs" to be the number of processor cores in your system x1.5<br />
** Target options:<br />
*** Set "Target architecture" to "ARM"<br />
*** Set "Endianness" to "Little endian"<br />
*** Set "Bitness" to "32-bit"<br />
*** Set "Architecture level" to "armv6zk"<br />
*** Set "Emit assembly for CPU" to "arm1176jzf-s"<br />
*** Set "Tune for CPU" to "arm1176jzf-s"<br />
*** Set "Use specific FPU" to "vfp"<br />
*** Set "Floating point" to "hardware (FPU)"<br />
*** Set "Default instruction set mode" to "arm"<br />
*** Check "Use EABI"<br />
** General toolchain:<br />
*** Set "Tuple's vendor string" to "rpi" - you can choose whatever you like here and it will appear in the compiler filenames.<br />
** Operating system:<br />
*** Set "Target OS" to "linux"<br />
*** Set "Linux kernel version" to match that running on the RPI (it was tested with the 3.6 branch patched to version 3.6.3)<br />
** Binary utilities:<br />
*** Set "Binary format" to "ELF"<br />
*** Set "binutils version" to "2.22"<br />
** C compiler:<br />
*** Check "Show linaro versions"<br />
*** Set "gcc version" to "linaro-4.7-2012.10"<br />
*** Check "C++"<br />
*** Set "gcc extra config" to "--with-float=hard" (Note: see "Discussion" page)<br />
*** Check "Link libstdc++ statically into gcc binary"<br />
** C-library:<br />
*** Set "C library" to "eglibc", or, as eglibc gets deprecated<ref>http://www.eglibc.org/home</ref>, glibc from version 2.19 up.<br />
*** Set "eglibc version" to "2_13", however, to reduce the size of your executables you could also try to match it with the libc already present on the Pi and select a custom libc-version here, for example the exact commit your libc was build from if you can reveal that. The major version of libc can be made visible with <br />
<pre><br />
ldd <br />
</pre><br />
<br />
* Build it:<br />
<pre><br />
ct-ng build<br />
</pre><br />
* All the required source will now be downloaded and built - exact times vary according to processing power and internet connection speed.<br />
<br />
===Configure system to use new compiler===<br />
Your compiler will be located in <tt>/home/<yourname>/crosscompile</tt> (or whereever you specified in the configuration). You can choose to move it to another location (e.g. /opt/arm) if you want to. Then, add that location to your PATH:<br />
<pre><br />
PATH=$PATH:/opt/arm/bin:/opt/crosstool-ng-1.17.0/bin<br />
</pre><br />
<br />
Now if you run:<br />
<pre><br />
arm-rpi-linux-gnueabi-gcc -v<br />
</pre><br />
you should get the version information from your new build. It should end something like:<br />
<pre><br />
gcc version 4.7.3 20121001 (prerelease) (crosstool-NG 1.17.0)<br />
</pre><br />
<br />
==References==<br />
<references/><br />
<br />
{{Template:Raspberry Pi}}</div>Rmasthttps://elinux.org/index.php?title=RPi_Linaro_GCC_Compilation&diff=416616RPi Linaro GCC Compilation2016-08-11T18:07:42Z<p>Rmast: Changed the preferred eglibc for glibc and a hint to link to the libc-version on the Pi</p>
<hr />
<div>[[Category: RaspberryPi]]<br />
{{Template:RPi_Software}}<br />
<br />
==Overview==<br />
<br />
This page explains how to build yourself a version of Linaro GCC specifically for building software for the RPi.<br />
<br />
From the Linaro website: "Linaro GCC is performance focused branch of the current GCC stable release and includes backports of the improvements and bug fixes that Linaro and others have done upstream" <ref>https://launchpad.net/gcc-linaro</ref><br />
<br />
==Requirements==<br />
<br />
This process should be carried out on the Linux system you wish to compile RPi software on. Therefore, you will require a reasonably powerful computer (preferably 64bit). If you are running on Windows, it is possible to use a linux virtual machine running on [https://www.virtualbox.org/ Virtualbox]. The only software required is [http://crosstool-ng.org/ crosstool-NG] (plus its dependencies).<br />
<br />
==Procedure==<br />
The whole process takes about an hour on a dual-core 2.8GHz 64-bit AMD system using an 8Mbit ADSL connection.<br />
NOTE: This procedure was tested on 24th November 2012 using crosstool-ng 1.17.0. It may not be accurate for newer versions of the software.<br />
<br />
===Install crosstool-NG===<br />
* Download the crosstool-NG source (from http://crosstool-ng.org/).<br />
* Extract the source tarball into your home directory: <br />
<pre><br />
tar -xjvf crosstool-ng-1.17.0.tar.bz2<br />
</pre><br />
* Or clone a more recent version from git, I saw this newest version work as well:<br />
<br />
<pre><br />
git clone https://github.com/crosstool-ng/crosstool-ng.git<br />
cd crosstool-ng<br />
git checkout 1.22<br />
</pre><br />
<br />
* Change to the extracted directory, then configure it. You should specify an installation prefix to keep it separate from the OS in case you want to run multiple versions - we are using <tt>/opt/crosstool-ng-1.17.0</tt> in this example:<br />
<pre><br />
./configure --prefix=/opt/crosstool-ng-1.17.0<br />
</pre><br />
<br />
* If configure fails due to missing dependencies, install them for your platform using the package manager (i.e. yum install, apt-get install, etc.)<br />
* during the build you might need packages for expat, libexpat1-dev, python-dev<br />
* When configure completes successfully, make and install it:<br />
<pre><br />
make<br />
make install<br />
</pre><br />
* Add the crosstool-NG bin folder to your path. The easiest way to do this is add it to PATH in your <tt>.profile</tt>, for example: <br />
<pre><br />
PATH=$PATH:/opt/crosstool-ng-1.17.0/bin<br />
</pre><br />
<br />
===Build GCC Linaro===<br />
* Make a new directory in your home directory where you want to run crosstool-NG, then change to it.<br />
* Configure crosstool-NG:<br />
<pre><br />
ct-ng menuconfig<br />
</pre><br />
* Set the following options (derived from the arm-bcm2708hardfp-linux-gnueabi build on GitHub):<br />
** Paths & Misc: <br />
*** Check "Try features marked as EXPERIMENTAL"<br />
*** Set "Prefix directory" to whereever you want the finished toolchain to be placed (e.g. /home/<yourname>/crosscompile)<br />
*** Set "Number of parallel jobs" to be the number of processor cores in your system x1.5<br />
** Target options:<br />
*** Set "Target architecture" to "ARM"<br />
*** Set "Endianness" to "Little endian"<br />
*** Set "Bitness" to "32-bit"<br />
*** Set "Architecture level" to "armv6zk"<br />
*** Set "Emit assembly for CPU" to "arm1176jzf-s"<br />
*** Set "Tune for CPU" to "arm1176jzf-s"<br />
*** Set "Use specific FPU" to "vfp"<br />
*** Set "Floating point" to "hardware (FPU)"<br />
*** Set "Default instruction set mode" to "arm"<br />
*** Check "Use EABI"<br />
** General toolchain:<br />
*** Set "Tuple's vendor string" to "rpi" - you can choose whatever you like here and it will appear in the compiler filenames.<br />
** Operating system:<br />
*** Set "Target OS" to "linux"<br />
*** Set "Linux kernel version" to match that running on the RPI (it was tested with the 3.6 branch patched to version 3.6.3)<br />
** Binary utilities:<br />
*** Set "Binary format" to "ELF"<br />
*** Set "binutils version" to "2.22"<br />
** C compiler:<br />
*** Check "Show linaro versions"<br />
*** Set "gcc version" to "linaro-4.7-2012.10"<br />
*** Check "C++"<br />
*** Set "gcc extra config" to "--with-float=hard" (Note: see "Discussion" page)<br />
*** Check "Link libstdc++ statically into gcc binary"<br />
** C-library:<br />
*** Set "C library" to "eglibc", or, as eglibc gets deprecated<ref>http://www.eglibc.org/home</ref>, glibc from version 2.19 up.<br />
*** Set "eglibc version" to "2_13", however, to reduce the size of your executables you could also try to match it with the libc already present on the Pi and select a custom libc-version here, for example the exact commit your libc was build from if you can reveal that.<br />
The major version of libc can be made visible with <br />
<pre><br />
ldd <br />
</pre><br />
<br />
* Build it:<br />
<pre><br />
ct-ng build<br />
</pre><br />
* All the required source will now be downloaded and built - exact times vary according to processing power and internet connection speed.<br />
<br />
===Configure system to use new compiler===<br />
Your compiler will be located in <tt>/home/<yourname>/crosscompile</tt> (or whereever you specified in the configuration). You can choose to move it to another location (e.g. /opt/arm) if you want to. Then, add that location to your PATH:<br />
<pre><br />
PATH=$PATH:/opt/arm/bin:/opt/crosstool-ng-1.17.0/bin<br />
</pre><br />
<br />
Now if you run:<br />
<pre><br />
arm-rpi-linux-gnueabi-gcc -v<br />
</pre><br />
you should get the version information from your new build. It should end something like:<br />
<pre><br />
gcc version 4.7.3 20121001 (prerelease) (crosstool-NG 1.17.0)<br />
</pre><br />
<br />
==References==<br />
<references/><br />
<br />
{{Template:Raspberry Pi}}</div>Rmasthttps://elinux.org/index.php?title=RPi_Linaro_GCC_Compilation&diff=416611RPi Linaro GCC Compilation2016-08-11T17:41:07Z<p>Rmast: Added more actual versions and needed packages based on a recent experience</p>
<hr />
<div>[[Category: RaspberryPi]]<br />
{{Template:RPi_Software}}<br />
<br />
==Overview==<br />
<br />
This page explains how to build yourself a version of Linaro GCC specifically for building software for the RPi.<br />
<br />
From the Linaro website: "Linaro GCC is performance focused branch of the current GCC stable release and includes backports of the improvements and bug fixes that Linaro and others have done upstream" <ref>https://launchpad.net/gcc-linaro</ref><br />
<br />
==Requirements==<br />
<br />
This process should be carried out on the Linux system you wish to compile RPi software on. Therefore, you will require a reasonably powerful computer (preferably 64bit). If you are running on Windows, it is possible to use a linux virtual machine running on [https://www.virtualbox.org/ Virtualbox]. The only software required is [http://crosstool-ng.org/ crosstool-NG] (plus its dependencies).<br />
<br />
==Procedure==<br />
The whole process takes about an hour on a dual-core 2.8GHz 64-bit AMD system using an 8Mbit ADSL connection.<br />
NOTE: This procedure was tested on 24th November 2012 using crosstool-ng 1.17.0. It may not be accurate for newer versions of the software.<br />
<br />
===Install crosstool-NG===<br />
* Download the crosstool-NG source (from http://crosstool-ng.org/).<br />
* Extract the source tarball into your home directory: <br />
<pre><br />
tar -xjvf crosstool-ng-1.17.0.tar.bz2<br />
</pre><br />
* Or clone a more recent version from git, I saw this newest version work as well:<br />
<br />
<pre><br />
git clone https://github.com/crosstool-ng/crosstool-ng.git<br />
cd crosstool-ng<br />
git checkout 1.22<br />
</pre><br />
<br />
* Change to the extracted directory, then configure it. You should specify an installation prefix to keep it separate from the OS in case you want to run multiple versions - we are using <tt>/opt/crosstool-ng-1.17.0</tt> in this example:<br />
<pre><br />
./configure --prefix=/opt/crosstool-ng-1.17.0<br />
</pre><br />
<br />
* If configure fails due to missing dependencies, install them for your platform using the package manager (i.e. yum install, apt-get install, etc.)<br />
* during the build you might need packages for expat, libexpat1-dev, python-dev<br />
* When configure completes successfully, make and install it:<br />
<pre><br />
make<br />
make install<br />
</pre><br />
* Add the crosstool-NG bin folder to your path. The easiest way to do this is add it to PATH in your <tt>.profile</tt>, for example: <br />
<pre><br />
PATH=$PATH:/opt/crosstool-ng-1.17.0/bin<br />
</pre><br />
<br />
===Build GCC Linaro===<br />
* Make a new directory in your home directory where you want to run crosstool-NG, then change to it.<br />
* Configure crosstool-NG:<br />
<pre><br />
ct-ng menuconfig<br />
</pre><br />
* Set the following options (derived from the arm-bcm2708hardfp-linux-gnueabi build on GitHub):<br />
** Paths & Misc: <br />
*** Check "Try features marked as EXPERIMENTAL"<br />
*** Set "Prefix directory" to whereever you want the finished toolchain to be placed (e.g. /home/<yourname>/crosscompile)<br />
*** Set "Number of parallel jobs" to be the number of processor cores in your system x1.5<br />
** Target options:<br />
*** Set "Target architecture" to "ARM"<br />
*** Set "Endianness" to "Little endian"<br />
*** Set "Bitness" to "32-bit"<br />
*** Set "Architecture level" to "armv6zk"<br />
*** Set "Emit assembly for CPU" to "arm1176jzf-s"<br />
*** Set "Tune for CPU" to "arm1176jzf-s"<br />
*** Set "Use specific FPU" to "vfp"<br />
*** Set "Floating point" to "hardware (FPU)"<br />
*** Set "Default instruction set mode" to "arm"<br />
*** Check "Use EABI"<br />
** General toolchain:<br />
*** Set "Tuple's vendor string" to "rpi" - you can choose whatever you like here and it will appear in the compiler filenames.<br />
** Operating system:<br />
*** Set "Target OS" to "linux"<br />
*** Set "Linux kernel version" to match that running on the RPI (it was tested with the 3.6 branch patched to version 3.6.3)<br />
** Binary utilities:<br />
*** Set "Binary format" to "ELF"<br />
*** Set "binutils version" to "2.22"<br />
** C compiler:<br />
*** Check "Show linaro versions"<br />
*** Set "gcc version" to "linaro-4.7-2012.10"<br />
*** Check "C++"<br />
*** Set "gcc extra config" to "--with-float=hard" (Note: see "Discussion" page)<br />
*** Check "Link libstdc++ statically into gcc binary"<br />
** C-library:<br />
*** Set "C library" to "eglibc"<br />
*** Set "eglibc version" to "2_13"<br />
* Build it:<br />
<pre><br />
ct-ng build<br />
</pre><br />
* All the required source will now be downloaded and built - exact times vary according to processing power and internet connection speed.<br />
<br />
===Configure system to use new compiler===<br />
Your compiler will be located in <tt>/home/<yourname>/crosscompile</tt> (or whereever you specified in the configuration). You can choose to move it to another location (e.g. /opt/arm) if you want to. Then, add that location to your PATH:<br />
<pre><br />
PATH=$PATH:/opt/arm/bin:/opt/crosstool-ng-1.17.0/bin<br />
</pre><br />
<br />
Now if you run:<br />
<pre><br />
arm-rpi-linux-gnueabi-gcc -v<br />
</pre><br />
you should get the version information from your new build. It should end something like:<br />
<pre><br />
gcc version 4.7.3 20121001 (prerelease) (crosstool-NG 1.17.0)<br />
</pre><br />
<br />
==References==<br />
<references/><br />
<br />
{{Template:Raspberry Pi}}</div>Rmasthttps://elinux.org/index.php?title=RPi_USB_Webcams&diff=395031RPi USB Webcams2015-11-18T20:41:12Z<p>Rmast: </p>
<hr />
<div><br />
This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!<br />
<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''Verified OS'''<br />
| '''Verified OS version'''<br />
| '''Verified Resolution'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Canyon<br />
|<br />
| CNR-FWC113<br />
| 0c45:6340<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 640x480<br />
| works fine out of the box. Lacks autofocus (manual focus ring works fine). Has auto exposure, but seems to be optimized for indoor use. When using outdoors, image is completely overexposed.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Canyon<br />
|<br />
| CNR-FWC120H<br />
| <br />
| raspbian/wheezy <br />
| 2013-07-26<br />
| 640x480<br />
| Works well out of the box. Tested with guvcview and also with mjpg-streamer. Also works outside after some manual adjustment of exposure.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Canyon<br />
|<br />
|CNR-WCAM820<br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1280x1024<br />
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|CBR<br />
|<br />
| CW 835M Black<br />
|<br />
| raspbian/wheezy <br />
| 2013-02-12<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! <br />
| VF0470<br />
|<br />
| ArchLinux<br />
| <br />
|<br />
| works out of the box on ArchLinux<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize HD<br />
| VF0610<br />
|041e:4080<br />
| raspbian/wheezy <br />
| 2012-11-26<br />
| 960x544<br />
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! Cam Sync HD<br />
| <br />
|041e:4095<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 1280x720<br />
| Works out of the box. Autoexposure works well both indoors and outdoors. By default the image is bit too software enhanced (they call it "sharpness"), but this "sharpness" level can be set to a lower level via fswebcam tool.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Go<br />
|PD00040 <br />
|<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| <br />
| Not working at all. Tried various apps (fswebcam/motion) - none work. Corrupt JPEG data: premature end of data segment.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Vista IM<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Webcam Notebook<br />
| PD1170<br />
|<br />
| <br />
|<br />
| <br />
| Detects, untested.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Webcam Pro<br />
|PD1030<br />
|<br />
|<br />
|<br />
|<br />
|ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Eminent<br />
|<br />
| EM1089<br />
| <br />
| raspbian/wheezy <br />
| 2014-05-06<br />
| 640x480<br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|GE<br />
|MiniCam Pro<br />
|98756<br />
|0ac8:3420<br />
|raspbian/wheezy<br />
|2014-01-07<br />
|640x480, 352x288, 320x240, 176x144, 160x120<br />
|Tested and works with motion. Runs on the model B without a powered hub (rated 100 mA).<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Hercules<br />
|Webcam Deluxe<br />
|<br />
|05a9:4519<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|ov519 driver "Corrupt JPEG data: premature end of data segment" gives corrupt image in motion and fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam-2100<br />
|2100<br />
|<br />
|Raspbian<br />
|3.18.7<br />
|640x480<br />
|Needs to skip frames when using fswebcam until exposure settings calculated.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2200<br />
| HD-2200<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2300<br />
| HD-2300<br />
|<br />
| raspbian/wheezy <br />
| 2013-08-28<br />
| 1280x720<br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HP-3100<br />
|HP-3100<br />
|<br />
| <br />
|<br />
| <br />
| UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and Wheezy out of the box<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Kodak<br />
|Webcam S101<br />
|Kodak S101<br />
|0979:0206<br />
|raspbian/wheezy <br />
|2014-02-09<br />
|640x480, 320x240<br />
| /dev/video0 Works out of the box with guvcview. Tested and works with motion. Runs on the model B without a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C100<br />
| V-U0013<br />
|<br />
| raspbian/wheezy <br />
| 2012-08-16<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C110<br />
|<br />
| 046d:0829<br />
| raspbian/wheezy <br />
| 2014-04-04<br />
| <br />
| works fine without powered hub. can be unpredictable, however for sanity try fswebcam -p YUYV test.jpeg <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Logitech<br />
| Webcam C160<br />
| V-U0011<br />
| <br />
| Raspbian<br />
| 2015-03-04<br />
| 640x480, 320x240<br />
| works fine without powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C170<br />
|<br />
|<br />
| raspbian/wheezy <br />
| <br />
| 1024x760<br />
| works fine without powered hub, image/video quality is poor<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C200<br />
| <br />
| 046d:0802<br />
| <br />
|<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C210<br />
| <br />
| 046d:0819<br />
| Raspbian/wheezy<br />
| 2012-12-16<br />
| 320x240, 640x480<br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Logitech<br />
| Webcam C270<br />
| <br />
| 046d:0825<br />
| Raspbian/wheezy<br />
| <br />
| 1280x720<br />
| works fine with external power, image/video quality is crisp. Caution: Pi may hang (at least not accessible remotely) when using the UVC video kernel module. Fix: load the module using the following magic incantation: `modprobe uvcvideo nodrop=1 timeout=5000 quirks=0x80` . (2014-06-01, Raspbian Linux 3.12.20+)<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C300<br />
|V-U0004<br />
|046d:0805<br />
|Raspbian/Wheezy<br />
|2013-02-09<br />
|320x240, 640x480, 1280x1024<br />
|Works out of the box. Does not appear to require a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C310<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Does not require a powered hub to capture snapshots<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C510<br />
| <br />
|046d:081d<br />
|Raspbian/Wheezy<br />
|2013-08-30<br />
|320x240, 640x480 <br />
|Image capture works without powered hub. Other resolutions/video are untested. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C525<br />
| <br />
|046d:0826<br />
|<br />
| <br />
| 1920x1080<br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C615<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C905<br />
| <br />
|046d:080a<br />
|Raspbian/Wheezy + occidentalis<br />
|v0.2<br />
|1600x1200<br />
| Works fine without powered hub, detected out of then box as Video0 V4L device (uvcvideo module). 1600x1200 at slow rate but ok (tested with motion, uv4l_uvc)<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C910<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C920<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1920x1080<br />
| With powered hub, detected out of box as Video0 V4L device. <br />
Works out of the box on model B+ without a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam E2500<br />
| <br />
|046d:089d<br />
|Raspbian/Wheezy<br />
|3.12<br />
|320x240 <br />
|Image capture and motion works without powered hub. Other resolutions/video are untested. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Orbit/Sphere<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works with external power<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Express<br />
|861037-0000 V-UB2<br />
|046d:0840<br />
|raspbian/wheezy<br />
|2014-02-09<br />
|320x240<br />
|/dev/video0 Works out of the box. Runs on the model B+ without a powered hub. Verified with fswebcam.<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|QuickCam Messenger<br />
|V-UM14<br />
|046d:08f0<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|Not working, STV06xx driver "ioctl (VIDIOCGCAP): Inappropriate ioctl for device", Supported palettes: GRBG, gives corrupt image in fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|QuickCam Communicate STX<br />
|<br />
|<br />
|raspbian/wheezy<br />
|2013-09-25<br />
|<br />
|Not working, There is a video image but its corrupted. Tried with and without a usb powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Communicate STX<br />
|<br />
|<br />
|Raspbian<br />
|2015-11-17 <br />
|<br />
|corruption gets solved for a poor 320x240 4fps after putting <b>options usbcore autosuspend=-1</b> in /etc/modprobe.d/disable-usb-autosuspend.conf and then reboot. Higher resolutions and framerates still get corrupt. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 5000<br />
| <br />
|<br />
|<br />
|<br />
|<br />
| Works fine (not tried without powered hub)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| V-UBM46<br />
| 046d:0990<br />
| 3.10.25-1-ARCH<br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro for Notebooks<br />
|960-000047<br />
|046d:0991<br />
|Raspbian Wheezy<br />
|2012-12-16<br />
|160x120 320x240 640x480<br />
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Ultra Vision<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 4000<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 9000<br />
| <br />
| 046d:0809<br />
| Arch Linux<br />
|<br />
| <br />
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medion<br />
|<br />
| MD86511<br />
|<br />
| raspbian/wheezy <br />
| 2012-07-15<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Mexxcom<br />
|<br />
| M-104<br />
|<br />
| raspbian/wheezy <br />
| 2012-12-16<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Cinemap 720p USB HD Webcam<br />
| H5D-00001<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| Archlinux<br />
| 2013-02-06<br />
| 160x120<br />
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other USB port.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 1280x720<br />
| Discard the first couple frames after activating, otherwise picture breaks up & exposure is bad. Sample command: fswebcam -S 5 -r 1280x720 tmp.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam HD-5000<br />
| HD-5000<br />
|<br />
| raspbian/wheezy<br />
|21-02-2014<br />
| <br />
| Picture breaks up at the bottom. EDIT: I recently acquired a Pi and I have the LifeCam HD-5000 Picture is NOT breaking up on the bottom for me. But YMMV. 21-2-14 edit<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam HD-6000<br />
|HD-6000 <br />
|<br />
| raspbian/wheezy <br />
|<br />
| 1280x720<br />
| Powered by USB hub and direct from Pi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-3000<br />
| 045e:0721<br />
| raspbian/wheezy <br />
| 2014-01-07<br />
| 640*480<br />
| Powered by Raspberry<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 1280x720<br />
| Powered by USB hub <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-7000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-3000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-500<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| 640x480. Tested with power direct from the Raspberry Pi. <br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-1000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Does not seem to work. Tried with a powered USB hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-1000<br />
|<br />
| Octopi (Raspbian tweaked) <br />
|<br />
| <br />
| It works after a couple of tests, I installed fswebcam on my raspberry pi 2 and now it takes 320x240 pixel photos .<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LifeCam<br />
| VX-2000<br />
| 045e:0761<br />
| raspbian/wheezy <br />
| 2013-12-20<br />
| 320x240, 640x480<br />
| Works without powered hub. Tried motion and fswebcam, both running smoothly.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-800<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 352x288<br />
| Doesn't work at full resolution<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam Studio/Cinema<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Studio<br />
|1080p HD <br />
|045e:0772<br />
| Raspbian Wheezy<br />
| 2013-04-12<br />
| 1280x720<br />
| Works for me without any issues with a powered usb-hub (Belkin).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| Xbox Live Vision<br />
| X806235<br />
| 045e:0294<br />
| Arch Linux/Raspbian Wheezy<br />
|<br />
| 960x720<br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|MSI<br />
|MSI StarCam 370i<br />
|370i (snake)<br />
| <br />
| Raspbian Wheezy<br />
|<br />
| 352 x 288<br />
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Novatek<br />
| Webcam<br />
| <br />
| 0603:8124<br />
| Arch Linux<br />
| 2014-09-19<br />
| 640x480<br />
| Picture breaks up on at the down in Arch Linux, powered by either USB hub (0424:9512) or Raspberry (not preferred: max current draw 500mA). <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| Webcam<br />
| SPC 900NC<br />
| 0471:0329<br />
| Raspbian Wheezy<br />
| 2012-12-16<br />
| 160x120<br />
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| toucam<br />
| Philips 720K/40 webcam<br />
| 0471:0313<br />
| Raspbian Wheezy<br />
| 2013-04-03<br />
| 320x240<br />
| Recognised as lsusb ID 0471:0329 Philips (or NXP). Works with $> guvcview -s 320x240 -f yv12 -t 5 -n rec5sec.mkv --exit_on_close --no_display, but not with command $> fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Realtek<br />
|Generic Camera<br />
|2SF022<br />
|0bda:5801<br />
|Raspbian Wheezy<br />
|<br />
|<br />
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second <br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Silicon Motion<br />
| SM731 Camera<br />
| <br />
| 090c:71b3<br />
| Raspbian Wheezy<br />
|<br />
| <br />
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS3<br />
| SLEH-00448<br />
|<br />
| wheezy-raspbian<br />
| 2014-06-20<br />
| 640x480 320x240<br />
| Works out of the box directly plugged in to the raspberry pi. Had no problems. Tested using motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| EyeToy for PS2<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| EyeToy for PS2<br />
| SLEH 00030<br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|T'nB<br />
| Minipix 100K pixels<br />
| IMWB032992<br />
| 1e4e:0100<br />
| raspbian/wheezy<br />
| 2012-12-16<br />
| <br />
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| 2 MP Auto Focus Webcam<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| 1600x1200<br />
| Works fine without powered hub. 160x120 - 1600x1200. 5 days stress test without any problems.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| SPACEC@M 200<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| SPYC@M 100<br />
| <br />
| 0553:0202<br />
| Raspbian/Wheezy<br />
| 2013-08-22<br />
| 352x288 <br />
| Works out of the box. Tested with a powered hub, not tested direct from the Raspberry Pi. May had LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/libv4l/v4l2convert.so for motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| Spotlight<br />
| <br />
| 0c45:62c0<br />
| Raspbian/Wheezy<br />
| <br />
| 640x480 <br />
| Works out of the box. Tested with power direct from the Raspberry Pi, not tested on a hub. <br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| WB-1400T<br />
| <br />
|<br />
| Raspbian/Wheezy<br />
|<br />
| <br />
| Cheap camera, recognised in 'lsusb' but not supported<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| WB-1200p Mini Webcam<br />
| <br />
| 093a:2468<br />
| Raspbian/Wheezy<br />
| 2013-12-12<br />
| <br />
| Recognised in 'lsusb' as Pixart Imaging, Inc. SoC PC-Camera. Doesn't work. gspca_main reports constant "ISOC data error".<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Vega<br />
| USB 2.0 Camera<br />
| <br />
| 0ac8:c302<br />
| Raspbian Wheezy<br />
| 2014-01-01<br />
| 640x480<br />
| Should be connected to powered USB hub. Cheap no name webcam from China. Uses UVC driver.<br />
<br />
<br />
|-<br />
|}<br />
<br />
== References ==<br />
<references><br />
</references><br />
<br />
{{Template:Raspberry Pi}}</div>Rmasthttps://elinux.org/index.php?title=RPi_USB_Webcams&diff=395026RPi USB Webcams2015-11-18T20:26:32Z<p>Rmast: </p>
<hr />
<div><br />
This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!<br />
<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''Verified OS'''<br />
| '''Verified OS version'''<br />
| '''Verified Resolution'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Canyon<br />
|<br />
| CNR-FWC113<br />
| 0c45:6340<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 640x480<br />
| works fine out of the box. Lacks autofocus (manual focus ring works fine). Has auto exposure, but seems to be optimized for indoor use. When using outdoors, image is completely overexposed.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Canyon<br />
|<br />
| CNR-FWC120H<br />
| <br />
| raspbian/wheezy <br />
| 2013-07-26<br />
| 640x480<br />
| Works well out of the box. Tested with guvcview and also with mjpg-streamer. Also works outside after some manual adjustment of exposure.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Canyon<br />
|<br />
|CNR-WCAM820<br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1280x1024<br />
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|CBR<br />
|<br />
| CW 835M Black<br />
|<br />
| raspbian/wheezy <br />
| 2013-02-12<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! <br />
| VF0470<br />
|<br />
| ArchLinux<br />
| <br />
|<br />
| works out of the box on ArchLinux<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize HD<br />
| VF0610<br />
|041e:4080<br />
| raspbian/wheezy <br />
| 2012-11-26<br />
| 960x544<br />
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! Cam Sync HD<br />
| <br />
|041e:4095<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 1280x720<br />
| Works out of the box. Autoexposure works well both indoors and outdoors. By default the image is bit too software enhanced (they call it "sharpness"), but this "sharpness" level can be set to a lower level via fswebcam tool.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Go<br />
|PD00040 <br />
|<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| <br />
| Not working at all. Tried various apps (fswebcam/motion) - none work. Corrupt JPEG data: premature end of data segment.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Vista IM<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Webcam Notebook<br />
| PD1170<br />
|<br />
| <br />
|<br />
| <br />
| Detects, untested.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Webcam Pro<br />
|PD1030<br />
|<br />
|<br />
|<br />
|<br />
|ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Eminent<br />
|<br />
| EM1089<br />
| <br />
| raspbian/wheezy <br />
| 2014-05-06<br />
| 640x480<br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|GE<br />
|MiniCam Pro<br />
|98756<br />
|0ac8:3420<br />
|raspbian/wheezy<br />
|2014-01-07<br />
|640x480, 352x288, 320x240, 176x144, 160x120<br />
|Tested and works with motion. Runs on the model B without a powered hub (rated 100 mA).<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Hercules<br />
|Webcam Deluxe<br />
|<br />
|05a9:4519<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|ov519 driver "Corrupt JPEG data: premature end of data segment" gives corrupt image in motion and fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam-2100<br />
|2100<br />
|<br />
|Raspbian<br />
|3.18.7<br />
|640x480<br />
|Needs to skip frames when using fswebcam until exposure settings calculated.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2200<br />
| HD-2200<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2300<br />
| HD-2300<br />
|<br />
| raspbian/wheezy <br />
| 2013-08-28<br />
| 1280x720<br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HP-3100<br />
|HP-3100<br />
|<br />
| <br />
|<br />
| <br />
| UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and Wheezy out of the box<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Kodak<br />
|Webcam S101<br />
|Kodak S101<br />
|0979:0206<br />
|raspbian/wheezy <br />
|2014-02-09<br />
|640x480, 320x240<br />
| /dev/video0 Works out of the box with guvcview. Tested and works with motion. Runs on the model B without a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C100<br />
| V-U0013<br />
|<br />
| raspbian/wheezy <br />
| 2012-08-16<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C110<br />
|<br />
| 046d:0829<br />
| raspbian/wheezy <br />
| 2014-04-04<br />
| <br />
| works fine without powered hub. can be unpredictable, however for sanity try fswebcam -p YUYV test.jpeg <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Logitech<br />
| Webcam C160<br />
| V-U0011<br />
| <br />
| Raspbian<br />
| 2015-03-04<br />
| 640x480, 320x240<br />
| works fine without powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C170<br />
|<br />
|<br />
| raspbian/wheezy <br />
| <br />
| 1024x760<br />
| works fine without powered hub, image/video quality is poor<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C200<br />
| <br />
| 046d:0802<br />
| <br />
|<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C210<br />
| <br />
| 046d:0819<br />
| Raspbian/wheezy<br />
| 2012-12-16<br />
| 320x240, 640x480<br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Logitech<br />
| Webcam C270<br />
| <br />
| 046d:0825<br />
| Raspbian/wheezy<br />
| <br />
| 1280x720<br />
| works fine with external power, image/video quality is crisp. Caution: Pi may hang (at least not accessible remotely) when using the UVC video kernel module. Fix: load the module using the following magic incantation: `modprobe uvcvideo nodrop=1 timeout=5000 quirks=0x80` . (2014-06-01, Raspbian Linux 3.12.20+)<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C300<br />
|V-U0004<br />
|046d:0805<br />
|Raspbian/Wheezy<br />
|2013-02-09<br />
|320x240, 640x480, 1280x1024<br />
|Works out of the box. Does not appear to require a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C310<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Does not require a powered hub to capture snapshots<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C510<br />
| <br />
|046d:081d<br />
|Raspbian/Wheezy<br />
|2013-08-30<br />
|320x240, 640x480 <br />
|Image capture works without powered hub. Other resolutions/video are untested. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C525<br />
| <br />
|046d:0826<br />
|<br />
| <br />
| 1920x1080<br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C615<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C905<br />
| <br />
|046d:080a<br />
|Raspbian/Wheezy + occidentalis<br />
|v0.2<br />
|1600x1200<br />
| Works fine without powered hub, detected out of then box as Video0 V4L device (uvcvideo module). 1600x1200 at slow rate but ok (tested with motion, uv4l_uvc)<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C910<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C920<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1920x1080<br />
| With powered hub, detected out of box as Video0 V4L device. <br />
Works out of the box on model B+ without a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam E2500<br />
| <br />
|046d:089d<br />
|Raspbian/Wheezy<br />
|3.12<br />
|320x240 <br />
|Image capture and motion works without powered hub. Other resolutions/video are untested. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Orbit/Sphere<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works with external power<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Express<br />
|861037-0000 V-UB2<br />
|046d:0840<br />
|raspbian/wheezy<br />
|2014-02-09<br />
|320x240<br />
|/dev/video0 Works out of the box. Runs on the model B+ without a powered hub. Verified with fswebcam.<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|QuickCam Messenger<br />
|V-UM14<br />
|046d:08f0<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|Not working, STV06xx driver "ioctl (VIDIOCGCAP): Inappropriate ioctl for device", Supported palettes: GRBG, gives corrupt image in fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|QuickCam Communicate STX<br />
|<br />
|<br />
|raspbian/wheezy<br />
|2013-09-25<br />
|<br />
|Not working, There is a video image but its corrupted. Tried with and without a usb powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Communicate STX<br />
|<br />
|<br />
|Raspbian<br />
|2015-11-17 <br />
|<br />
|corruption gets solved for a poor 320x240 4fps after putting <b>options usbcore autosuspend=-1</b> in /etc/modprobe.d/disable-usb-autosuspend.conf and then reboot. Higher resolutions and framerates still get corrupt. For the rest follow this guide http://868mhz.blogspot.nl/2012/09/raspberry-pi-logitech-quickcam.html. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 5000<br />
| <br />
|<br />
|<br />
|<br />
|<br />
| Works fine (not tried without powered hub)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| V-UBM46<br />
| 046d:0990<br />
| 3.10.25-1-ARCH<br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro for Notebooks<br />
|960-000047<br />
|046d:0991<br />
|Raspbian Wheezy<br />
|2012-12-16<br />
|160x120 320x240 640x480<br />
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Ultra Vision<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 4000<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 9000<br />
| <br />
| 046d:0809<br />
| Arch Linux<br />
|<br />
| <br />
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medion<br />
|<br />
| MD86511<br />
|<br />
| raspbian/wheezy <br />
| 2012-07-15<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Mexxcom<br />
|<br />
| M-104<br />
|<br />
| raspbian/wheezy <br />
| 2012-12-16<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Cinemap 720p USB HD Webcam<br />
| H5D-00001<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| Archlinux<br />
| 2013-02-06<br />
| 160x120<br />
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other USB port.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 1280x720<br />
| Discard the first couple frames after activating, otherwise picture breaks up & exposure is bad. Sample command: fswebcam -S 5 -r 1280x720 tmp.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam HD-5000<br />
| HD-5000<br />
|<br />
| raspbian/wheezy<br />
|21-02-2014<br />
| <br />
| Picture breaks up at the bottom. EDIT: I recently acquired a Pi and I have the LifeCam HD-5000 Picture is NOT breaking up on the bottom for me. But YMMV. 21-2-14 edit<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam HD-6000<br />
|HD-6000 <br />
|<br />
| raspbian/wheezy <br />
|<br />
| 1280x720<br />
| Powered by USB hub and direct from Pi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-3000<br />
| 045e:0721<br />
| raspbian/wheezy <br />
| 2014-01-07<br />
| 640*480<br />
| Powered by Raspberry<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 1280x720<br />
| Powered by USB hub <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-7000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-3000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-500<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| 640x480. Tested with power direct from the Raspberry Pi. <br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-1000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Does not seem to work. Tried with a powered USB hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-1000<br />
|<br />
| Octopi (Raspbian tweaked) <br />
|<br />
| <br />
| It works after a couple of tests, I installed fswebcam on my raspberry pi 2 and now it takes 320x240 pixel photos .<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LifeCam<br />
| VX-2000<br />
| 045e:0761<br />
| raspbian/wheezy <br />
| 2013-12-20<br />
| 320x240, 640x480<br />
| Works without powered hub. Tried motion and fswebcam, both running smoothly.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-800<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 352x288<br />
| Doesn't work at full resolution<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam Studio/Cinema<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Studio<br />
|1080p HD <br />
|045e:0772<br />
| Raspbian Wheezy<br />
| 2013-04-12<br />
| 1280x720<br />
| Works for me without any issues with a powered usb-hub (Belkin).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| Xbox Live Vision<br />
| X806235<br />
| 045e:0294<br />
| Arch Linux/Raspbian Wheezy<br />
|<br />
| 960x720<br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|MSI<br />
|MSI StarCam 370i<br />
|370i (snake)<br />
| <br />
| Raspbian Wheezy<br />
|<br />
| 352 x 288<br />
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Novatek<br />
| Webcam<br />
| <br />
| 0603:8124<br />
| Arch Linux<br />
| 2014-09-19<br />
| 640x480<br />
| Picture breaks up on at the down in Arch Linux, powered by either USB hub (0424:9512) or Raspberry (not preferred: max current draw 500mA). <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| Webcam<br />
| SPC 900NC<br />
| 0471:0329<br />
| Raspbian Wheezy<br />
| 2012-12-16<br />
| 160x120<br />
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| toucam<br />
| Philips 720K/40 webcam<br />
| 0471:0313<br />
| Raspbian Wheezy<br />
| 2013-04-03<br />
| 320x240<br />
| Recognised as lsusb ID 0471:0329 Philips (or NXP). Works with $> guvcview -s 320x240 -f yv12 -t 5 -n rec5sec.mkv --exit_on_close --no_display, but not with command $> fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Realtek<br />
|Generic Camera<br />
|2SF022<br />
|0bda:5801<br />
|Raspbian Wheezy<br />
|<br />
|<br />
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second <br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Silicon Motion<br />
| SM731 Camera<br />
| <br />
| 090c:71b3<br />
| Raspbian Wheezy<br />
|<br />
| <br />
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS3<br />
| SLEH-00448<br />
|<br />
| wheezy-raspbian<br />
| 2014-06-20<br />
| 640x480 320x240<br />
| Works out of the box directly plugged in to the raspberry pi. Had no problems. Tested using motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| EyeToy for PS2<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| EyeToy for PS2<br />
| SLEH 00030<br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|T'nB<br />
| Minipix 100K pixels<br />
| IMWB032992<br />
| 1e4e:0100<br />
| raspbian/wheezy<br />
| 2012-12-16<br />
| <br />
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| 2 MP Auto Focus Webcam<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| 1600x1200<br />
| Works fine without powered hub. 160x120 - 1600x1200. 5 days stress test without any problems.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| SPACEC@M 200<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| SPYC@M 100<br />
| <br />
| 0553:0202<br />
| Raspbian/Wheezy<br />
| 2013-08-22<br />
| 352x288 <br />
| Works out of the box. Tested with a powered hub, not tested direct from the Raspberry Pi. May had LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/libv4l/v4l2convert.so for motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| Spotlight<br />
| <br />
| 0c45:62c0<br />
| Raspbian/Wheezy<br />
| <br />
| 640x480 <br />
| Works out of the box. Tested with power direct from the Raspberry Pi, not tested on a hub. <br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| WB-1400T<br />
| <br />
|<br />
| Raspbian/Wheezy<br />
|<br />
| <br />
| Cheap camera, recognised in 'lsusb' but not supported<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| WB-1200p Mini Webcam<br />
| <br />
| 093a:2468<br />
| Raspbian/Wheezy<br />
| 2013-12-12<br />
| <br />
| Recognised in 'lsusb' as Pixart Imaging, Inc. SoC PC-Camera. Doesn't work. gspca_main reports constant "ISOC data error".<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Vega<br />
| USB 2.0 Camera<br />
| <br />
| 0ac8:c302<br />
| Raspbian Wheezy<br />
| 2014-01-01<br />
| 640x480<br />
| Should be connected to powered USB hub. Cheap no name webcam from China. Uses UVC driver.<br />
<br />
<br />
|-<br />
|}<br />
<br />
== References ==<br />
<references><br />
</references><br />
<br />
{{Template:Raspberry Pi}}</div>Rmasthttps://elinux.org/index.php?title=RPi_USB_Webcams&diff=394981RPi USB Webcams2015-11-17T15:52:47Z<p>Rmast: correction for logitech communicate stx and added logitech quickcam 5000 pro</p>
<hr />
<div><br />
This list is not entirely reliable, working does not necessarily mean working without errors. Please contribute with your own experiences!<br />
<br />
<div style="margin: -.3em -1em -1em -1em;"><br />
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"<br />
|- align="center" bgcolor="#e7eef6"<br />
| '''Brand'''<br />
| '''Name'''<br />
| '''Model Number'''<br />
| '''Hardware ID'''<br />
| '''Verified OS'''<br />
| '''Verified OS version'''<br />
| '''Verified Resolution'''<br />
| '''Additional Information'''<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Canyon<br />
|<br />
| CNR-FWC113<br />
| 0c45:6340<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 640x480<br />
| works fine out of the box. Lacks autofocus (manual focus ring works fine). Has auto exposure, but seems to be optimized for indoor use. When using outdoors, image is completely overexposed.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Canyon<br />
|<br />
| CNR-FWC120H<br />
| <br />
| raspbian/wheezy <br />
| 2013-07-26<br />
| 640x480<br />
| Works well out of the box. Tested with guvcview and also with mjpg-streamer. Also works outside after some manual adjustment of exposure.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Canyon<br />
|<br />
|CNR-WCAM820<br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1280x1024<br />
| 2 Mpixel camera with manual focus; works with fswebcam and v4l4j on Raspbian Wheezy armhf; problems with 1600x1200 resolution in some apps (timeouts - probably too slow USB); 1280x1024 and lower resolutions works OK<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|CBR<br />
|<br />
| CW 835M Black<br />
|<br />
| raspbian/wheezy <br />
| 2013-02-12<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! <br />
| VF0470<br />
|<br />
| ArchLinux<br />
| <br />
|<br />
| works out of the box on ArchLinux<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize HD<br />
| VF0610<br />
|041e:4080<br />
| raspbian/wheezy <br />
| 2012-11-26<br />
| 960x544<br />
| Works at 1280x720 taking stills in fswebcam with some errors using MJPEG, unusable with YUYV. 960x544 works in both MJPEG and YUYV. Has some stabilitiy issues if powered from RasPi (Drops USB +eth0 every 8 or so hours). Helps to append nodrop=1 and timeout=5000 to uvcvideo module.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Live! Cam Sync HD<br />
| <br />
|041e:4095<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 1280x720<br />
| Works out of the box. Autoexposure works well both indoors and outdoors. By default the image is bit too software enhanced (they call it "sharpness"), but this "sharpness" level can be set to a lower level via fswebcam tool.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Go<br />
|PD00040 <br />
|<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| <br />
| Not working at all. Tried various apps (fswebcam/motion) - none work. Corrupt JPEG data: premature end of data segment.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Vista IM<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Live! Cam Socialize<br />
| VF0640<br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| works on Raspbian at 320x240 resolution, 15fps<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Creative<br />
|Webcam Notebook<br />
| PD1170<br />
|<br />
| <br />
|<br />
| <br />
| Detects, untested.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Creative<br />
|Webcam Pro<br />
|PD1030<br />
|<br />
|<br />
|<br />
|<br />
|ov519 driver crashes almost immediately. ("gspca: ISOC data error: [0] len=0, status=-4004")<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Eminent<br />
|<br />
| EM1089<br />
| <br />
| raspbian/wheezy <br />
| 2014-05-06<br />
| 640x480<br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|GE<br />
|MiniCam Pro<br />
|98756<br />
|0ac8:3420<br />
|raspbian/wheezy<br />
|2014-01-07<br />
|640x480, 352x288, 320x240, 176x144, 160x120<br />
|Tested and works with motion. Runs on the model B without a powered hub (rated 100 mA).<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Hercules<br />
|Webcam Deluxe<br />
|<br />
|05a9:4519<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|ov519 driver "Corrupt JPEG data: premature end of data segment" gives corrupt image in motion and fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam-2100<br />
|2100<br />
|<br />
|Raspbian<br />
|3.18.7<br />
|640x480<br />
|Needs to skip frames when using fswebcam until exposure settings calculated.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2200<br />
| HD-2200<br />
|<br />
| <br />
| <br />
| <br />
|<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HD-2300<br />
| HD-2300<br />
|<br />
| raspbian/wheezy <br />
| 2013-08-28<br />
| 1280x720<br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|HP<br />
|Webcam HP-3100<br />
|HP-3100<br />
|<br />
| <br />
|<br />
| <br />
| UVCVideo /dev/video0 Needs chmod to 666 to operate. Will work without hub if only device in USB ports. Works with both Arch and Wheezy out of the box<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Kodak<br />
|Webcam S101<br />
|Kodak S101<br />
|0979:0206<br />
|raspbian/wheezy <br />
|2014-02-09<br />
|640x480, 320x240<br />
| /dev/video0 Works out of the box with guvcview. Tested and works with motion. Runs on the model B without a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C100<br />
| V-U0013<br />
|<br />
| raspbian/wheezy <br />
| 2012-08-16<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C110<br />
|<br />
| 046d:0829<br />
| raspbian/wheezy <br />
| 2014-04-04<br />
| <br />
| works fine without powered hub. can be unpredictable, however for sanity try fswebcam -p YUYV test.jpeg <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Logitech<br />
| Webcam C160<br />
| V-U0011<br />
| <br />
| Raspbian<br />
| 2015-03-04<br />
| 640x480, 320x240<br />
| works fine without powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C170<br />
|<br />
|<br />
| raspbian/wheezy <br />
| <br />
| 1024x760<br />
| works fine without powered hub, image/video quality is poor<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C200<br />
| <br />
| 046d:0802<br />
| <br />
|<br />
| <br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C210<br />
| <br />
| 046d:0819<br />
| Raspbian/wheezy<br />
| 2012-12-16<br />
| 320x240, 640x480<br />
| works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Logitech<br />
| Webcam C270<br />
| <br />
| 046d:0825<br />
| Raspbian/wheezy<br />
| <br />
| 1280x720<br />
| works fine with external power, image/video quality is crisp. Caution: Pi may hang (at least not accessible remotely) when using the UVC video kernel module. Fix: load the module using the following magic incantation: `modprobe uvcvideo nodrop=1 timeout=5000 quirks=0x80` . (2014-06-01, Raspbian Linux 3.12.20+)<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C300<br />
|V-U0004<br />
|046d:0805<br />
|Raspbian/Wheezy<br />
|2013-02-09<br />
|320x240, 640x480, 1280x1024<br />
|Works out of the box. Does not appear to require a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C310<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Does not require a powered hub to capture snapshots<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C510<br />
| <br />
|046d:081d<br />
|Raspbian/Wheezy<br />
|2013-08-30<br />
|320x240, 640x480 <br />
|Image capture works without powered hub. Other resolutions/video are untested. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C525<br />
| <br />
|046d:0826<br />
|<br />
| <br />
| 1920x1080<br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C615<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C905<br />
| <br />
|046d:080a<br />
|Raspbian/Wheezy + occidentalis<br />
|v0.2<br />
|1600x1200<br />
| Works fine without powered hub, detected out of then box as Video0 V4L device (uvcvideo module). 1600x1200 at slow rate but ok (tested with motion, uv4l_uvc)<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C910<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| With external power, is uncvideo. 320x240 works powered directly by the Raspberry Pi.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|Webcam C920<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| 1920x1080<br />
| With powered hub, detected out of box as Video0 V4L device. <br />
Works out of the box on model B+ without a powered hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam E2500<br />
| <br />
|046d:089d<br />
|Raspbian/Wheezy<br />
|3.12<br />
|320x240 <br />
|Image capture and motion works without powered hub. Other resolutions/video are untested. <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Orbit/Sphere<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Works with external power<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Express<br />
|861037-0000 V-UB2<br />
|046d:0840<br />
|raspbian/wheezy<br />
|2014-02-09<br />
|320x240<br />
|/dev/video0 Works out of the box. Runs on the model B+ without a powered hub. Verified with fswebcam.<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|QuickCam Messenger<br />
|V-UM14<br />
|046d:08f0<br />
|raspbian/wheezy + Arch<br />
|2013-02-09<br />
|<br />
|Not working, STV06xx driver "ioctl (VIDIOCGCAP): Inappropriate ioctl for device", Supported palettes: GRBG, gives corrupt image in fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|QuickCam Communicate STX<br />
|<br />
|<br />
|raspbian/wheezy<br />
|2013-09-25<br />
|<br />
|Not working, There is a video image but its corrupted. Tried with and without a usb powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Communicate STX<br />
|<br />
|<br />
|Raspbian<br />
|2015-11-17 <br />
|<br />
|corruption gets solved after putting <b>options usbcore autosuspend=-1</b> in /etc/modprobe.d/disable-usb-autosuspend.conf and then reboot. For the rest follow this guide http://868mhz.blogspot.nl/2012/09/raspberry-pi-logitech-quickcam.html<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 5000<br />
| <br />
|<br />
|<br />
|<br />
|<br />
| Works fine (not tried without powered hub)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| V-UBM46<br />
| 046d:0990<br />
| 3.10.25-1-ARCH<br />
|<br />
| <br />
| Works fine without powered hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro 9000<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Pro for Notebooks<br />
|960-000047<br />
|046d:0991<br />
|Raspbian Wheezy<br />
|2012-12-16<br />
|160x120 320x240 640x480<br />
|With guvcview it shows at about 4fps at 160x120, and at about 1fps at 640x480. GUVCViewer Controls are available for focus and exposure.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Logitech<br />
|QuickCam Ultra Vision<br />
| <br />
|<br />
| raspbian/wheezy<br />
|<br />
| <br />
| Powered by RasPi<br />
<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 4000<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| It uses pwc driver which does not work. Maybe it's because of general Raspberry Pi USB bug.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Logitech<br />
|Webcam Pro 9000<br />
| <br />
| 046d:0809<br />
| Arch Linux<br />
|<br />
| <br />
| Powered by RasPi, measured ~120 mA current capturing at ~5fps. Has issues capturing images at higher than default resolutions (using motion - Arch and Debian).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Medion<br />
|<br />
| MD86511<br />
|<br />
| raspbian/wheezy <br />
| 2012-07-15<br />
| <br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Mexxcom<br />
|<br />
| M-104<br />
|<br />
| raspbian/wheezy <br />
| 2012-12-16<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Cinemap 720p USB HD Webcam<br />
| H5D-00001<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| Archlinux<br />
| 2013-02-06<br />
| 160x120<br />
| Works out of the box at the tested resolution. Can be powered directly by the Raspberry Pi and works fine also with a wifi dongle attached to the other USB port.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LiveCam HD-3000<br />
| HD-3000<br />
| 045e:0779<br />
| raspbian/wheezy <br />
| 2013-04-11<br />
| 1280x720<br />
| Discard the first couple frames after activating, otherwise picture breaks up & exposure is bad. Sample command: fswebcam -S 5 -r 1280x720 tmp.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam HD-5000<br />
| HD-5000<br />
|<br />
| raspbian/wheezy<br />
|21-02-2014<br />
| <br />
| Picture breaks up at the bottom. EDIT: I recently acquired a Pi and I have the LifeCam HD-5000 Picture is NOT breaking up on the bottom for me. But YMMV. 21-2-14 edit<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam HD-6000<br />
|HD-6000 <br />
|<br />
| raspbian/wheezy <br />
|<br />
| 1280x720<br />
| Powered by USB hub and direct from Pi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-3000<br />
| 045e:0721<br />
| raspbian/wheezy <br />
| 2014-01-07<br />
| 640*480<br />
| Powered by Raspberry<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 1280x720<br />
| Powered by USB hub <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-7000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-3000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| There do appear to be some issues with image quality and getting partial frames and such, with fswebcam<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-500<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| 640x480. Tested with power direct from the Raspberry Pi. <br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-1000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Does not seem to work. Tried with a powered USB hub.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-1000<br />
|<br />
| Octopi (Raspbian tweaked) <br />
|<br />
| <br />
| It works after a couple of tests, I installed fswebcam on my raspberry pi 2 and now it takes 320x240 pixel photos .<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| LifeCam<br />
| VX-2000<br />
| 045e:0761<br />
| raspbian/wheezy <br />
| 2013-12-20<br />
| 320x240, 640x480<br />
| Works without powered hub. Tried motion and fswebcam, both running smoothly.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam<br />
| NX-6000<br />
|<br />
| raspbian/wheezy <br />
|<br />
| <br />
| Powered by USB hub<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam<br />
| VX-800<br />
|<br />
| raspbian/wheezy <br />
|<br />
| 352x288<br />
| Doesn't work at full resolution<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Microsoft<br />
|LifeCam Studio/Cinema<br />
| <br />
|<br />
| <br />
|<br />
| <br />
| Has UVC issues detailed here [http://www.ideasonboard.org/uvc/#devices]. Horizontal lines problem [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12304]. Stability issues [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=12247].<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Microsoft<br />
|LifeCam Studio<br />
|1080p HD <br />
|045e:0772<br />
| Raspbian Wheezy<br />
| 2013-04-12<br />
| 1280x720<br />
| Works for me without any issues with a powered usb-hub (Belkin).<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
| Microsoft<br />
| Xbox Live Vision<br />
| X806235<br />
| 045e:0294<br />
| Arch Linux/Raspbian Wheezy<br />
|<br />
| 960x720<br />
| Powered by RasPi<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|MSI<br />
|MSI StarCam 370i<br />
|370i (snake)<br />
| <br />
| Raspbian Wheezy<br />
|<br />
| 352 x 288<br />
| Works powered by RasPi or USB Hub - set up with Motion at 352 x 288 - works great. Has manual infra-red leds, but turned on through software in Windows, so doesn't work on Pi, but normal capture no problems.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Novatek<br />
| Webcam<br />
| <br />
| 0603:8124<br />
| Arch Linux<br />
| 2014-09-19<br />
| 640x480<br />
| Picture breaks up on at the down in Arch Linux, powered by either USB hub (0424:9512) or Raspberry (not preferred: max current draw 500mA). <br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| Webcam<br />
| SPC 900NC<br />
| 0471:0329<br />
| Raspbian Wheezy<br />
| 2012-12-16<br />
| 160x120<br />
| Recognised as USB device ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R). Works with guvcview , but not with luvcview. Also working using command ~$ fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Philips<br />
| toucam<br />
| Philips 720K/40 webcam<br />
| 0471:0313<br />
| Raspbian Wheezy<br />
| 2013-04-03<br />
| 320x240<br />
| Recognised as lsusb ID 0471:0329 Philips (or NXP). Works with $> guvcview -s 320x240 -f yv12 -t 5 -n rec5sec.mkv --exit_on_close --no_display, but not with command $> fswebcam -r 160x120 -d v4l2:/dev/video0 test.jpg<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Realtek<br />
|Generic Camera<br />
|2SF022<br />
|0bda:5801<br />
|Raspbian Wheezy<br />
|<br />
|<br />
|When started with luvcview at 15fps and 320x240 it seemed to give a frame rate of barely 1 per second <br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Silicon Motion<br />
| SM731 Camera<br />
| <br />
| 090c:71b3<br />
| Raspbian Wheezy<br />
|<br />
| <br />
| Required UVCVideo driver - worked out of the box. Tested for 320x240 using motion & camorama for pictures,streaming.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| Playstation Eye for PS3<br />
| SLEH-00448<br />
|<br />
| wheezy-raspbian<br />
| 2014-06-20<br />
| 640x480 320x240<br />
| Works out of the box directly plugged in to the raspberry pi. Had no problems. Tested using motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| EyeToy for PS2<br />
| <br />
|<br />
|<br />
| <br />
| <br />
| Occasional 'mangled frame' directly connected to Rev 2 Raspberry P<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Sony<br />
| EyeToy for PS2<br />
| SLEH 00030<br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV519 camera). Picture constantly breaks up on xawtv and wxcam under Arch Linux. Noted there were ISOC data error len=0 status=-4004 errors in dmesg. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|T'nB<br />
| Minipix 100K pixels<br />
| IMWB032992<br />
| 1e4e:0100<br />
| raspbian/wheezy<br />
| 2012-12-16<br />
| <br />
| RasPi freezes (reboot needed) after a few minutes of using Motion to stream (tested with external power)<br />
<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| 2 MP Auto Focus Webcam<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| 1600x1200<br />
| Works fine without powered hub. 160x120 - 1600x1200. 5 days stress test without any problems.<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| SPACEC@M 200<br />
| <br />
|<br />
| Arch Linux<br />
|<br />
| <br />
| (OV511 camera). Picture stops after a few seconds in xawtv under Arch Linux and xawtv reports libv4l2 errors. This happens when powered from the Raspberry Pi and when powered from a Pluscom USB Hub. Arch was updated on 17th July 2012<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| SPYC@M 100<br />
| <br />
| 0553:0202<br />
| Raspbian/Wheezy<br />
| 2013-08-22<br />
| 352x288 <br />
| Works out of the box. Tested with a powered hub, not tested direct from the Raspberry Pi. May had LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/libv4l/v4l2convert.so for motion.<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Trust<br />
| Spotlight<br />
| <br />
| 0c45:62c0<br />
| Raspbian/Wheezy<br />
| <br />
| 640x480 <br />
| Works out of the box. Tested with power direct from the Raspberry Pi, not tested on a hub. <br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| WB-1400T<br />
| <br />
|<br />
| Raspbian/Wheezy<br />
|<br />
| <br />
| Cheap camera, recognised in 'lsusb' but not supported<br />
<br />
|- valign="top" align="left" style="background: #F6D2CF;"<br />
|Trust<br />
| WB-1200p Mini Webcam<br />
| <br />
| 093a:2468<br />
| Raspbian/Wheezy<br />
| 2013-12-12<br />
| <br />
| Recognised in 'lsusb' as Pixart Imaging, Inc. SoC PC-Camera. Doesn't work. gspca_main reports constant "ISOC data error".<br />
<br />
|- valign="top" align="left" style="background: #F5FAFF;"<br />
|Vega<br />
| USB 2.0 Camera<br />
| <br />
| 0ac8:c302<br />
| Raspbian Wheezy<br />
| 2014-01-01<br />
| 640x480<br />
| Should be connected to powered USB hub. Cheap no name webcam from China. Uses UVC driver.<br />
<br />
<br />
|-<br />
|}<br />
<br />
== References ==<br />
<references><br />
</references><br />
<br />
{{Template:Raspberry Pi}}</div>Rmast