Easy Snap Snake Eye WebCam does not work with gspca

Bug #148289 reported by Markus
10
Affects Status Importance Assigned to Milestone
linux-ubuntu-modules-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have a Webcam from Trust called WB-1200p, which identifies itself on USB as Pixart Imaging, Inc. Easy Snap Snake Eye WebCam. It works with dapper out of the box using the spca5xx driver. This driver is replaced in gutsy with the gspca driver.

After plugging this camera into the usb port gspca is loaded and a device file is created under /dev/video0, but neither camorama nor ekiga are able to access the camera. Camorama reports "Could not connect to video device (/dev/video0). Please check connection". Ekiga simply doesn't recognize any video input.

Revision history for this message
Albert Damen (albrt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux-ubuntu-modules-2.6.22.

Secondly, can you please run the command lsusb and paste the line describing your camera in this bug report?

Revision history for this message
giap (giap-fastwebnet) wrote :

My WB-1200p webcam works with ekiga and camera monitor BUT
it doesn't work with camorama, cheese and stopmotion.

lsusb

Bus 005 Device 006: ID 093a:2468 Pixart Imaging, Inc. Easy Snap Snake Eye WebCam
Bus 005 Device 005: ID 0ea0:2168 Ours Technology, Inc. Transcend JetFlash 2.0 / Astone USB Drive
Bus 005 Device 003: ID 03f0:110c Hewlett-Packard
Bus 005 Device 004: ID 05e3:0608 Genesys Logic, Inc.
Bus 005 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Bus 001 Device 004: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 001 Device 001: ID 0000:0000

Revision history for this message
markusd112 (markusd112) wrote :

I have the same problem: each time I start camorama it displays the following error message:

"Could not connect to video device /dev/video0. Please check connection.

lsusb gives the following informations:

Bus 005 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 004: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub
Bus 004 Device 006: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Bus 004 Device 005: ID 0e55:110a Speed Dragon Multimedia, Ltd
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 046d:0a01 Logitech, Inc.
Bus 001 Device 005: ID 093a:2468 Pixart Imaging, Inc. Easy Snap Snake Eye WebCam
Bus 001 Device 001: ID 0000:0000

Revision history for this message
markusd112 (markusd112) wrote :

I have solved the problem:

- download the drivers (http://mxhaard.free.fr/spca50x/Download … 214.tar.gz)
- unzip it: tar -xzf gspcav1-20071214.tar.gz /tmp/.
- build and install it: sudo /tmp/gpscav1-20071214/gspca_build

Yours,

Markus

Revision history for this message
Albert Damen (albrt) wrote :

The Hardy Heron Alpha series has been released. Alpha5 contains an updated version of the kernel and modules. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test this bug with the new kernel on the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks!
Please note Hardy has not been finalized yet, so please only use it for testing.

Revision history for this message
jp (janpaulhoelzel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-ubuntu-modules-2.6.22:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.