Since this is a new camera, and I don't have any personal information on it, can you give me the 8-series level part number from the tag, and the actual name that Logitech has on the packaging?
I can tell you that the E2500 is a PEPI2 camera (VC302 chip), so it *should* use the spca driver (with whatever modifications are necessary to make it work).
Thanks.
KachiWachi - Webcam Forum Guru since 2002, Logi Legend since 2007, QuickCam® Team (2007)
(I am not affiliated with Logitech®, Inc., Lithium™ Technologies, Inc., or RightNow® Technologies, Inc.)
You should try the gspca driver. In order to get it to recognize your camera you'll need to add the VID/PID into the driver's list of supported devices and then recompile it.
Please let us know if it works. You can also contact Michel Xhaard, the driver's author once you have any results.
I don't remember by heart which file it is but if you search for the VID in the sources ("046d") you'll find the appropriate file.
Yes, lsusb gives you the VID and PID. You may have to play around with the other data in that table. The data for the camera with VID 046d and PID 08dd should be a good starting point to try.
so I found a file called gspca_core.c and put the informations for my camera into it. However, there is still no effect after compiling the driver. DMESG tells me that gspca is loaded but still there is only a new unknown usb device listed. There is also afile called gspca_core.o and this one is according to the output of make install processed but I cannot open it with a text editor. Is this probably the real file? Does anyone here ever tried to put in a camera by hand and probably can think of something I forgot to do??
As for the 8-series level part number (P/N), this information can be found on the USB cable tag.
Thanks.
KachiWachi - Webcam Forum Guru since 2002, Logi Legend since 2007, QuickCam® Team (2007)
(I am not affiliated with Logitech®, Inc., Lithium™ Technologies, Inc., or RightNow® Technologies, Inc.)
Hello, are there any news about this Camera? I already tried to modify the driver and i even get a /dev/video an can select the Camera in Skype, but it simply doesnt work. (I already posted what dmesg gives me: http://forums.quickcamteam.net/showthread.php?tid=349). I think there is still something wrong with my switch case direction in gspca_core.c in line 3339. I think the sensor and/or the bridge are not correct. What do i have to put there?
Hi,
i have also a problem with the E2500. I have patched my gspcav1-20071224 source with an " patch -p1 < ../quickcamE2500.diff " and it was sucessfull.
But if i put the webcam in the usb port, i only see the follow in /var/log/messages and i have no /dev/video or /dev/video0.
/var/log/messages:
------------------------------
Aug 9 17:00:14 sam kernel: [ 935.125100] Linux video capture interface: v2.00
Aug 9 17:00:14 sam kernel: [ 935.130820] usbcore: registered new interface driver gspca
Aug 9 17:00:14 sam kernel: [ 935.130827] /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/media/gspcav1/gspca_core.c: gspca driver 01.00.20 registered
Aug 9 17:00:56 sam kernel: [ 1730.897638] usb 2-1: new full speed USB device using uhci_hcd and address 2
Aug 9 17:00:56 sam kernel: [ 1731.088613] usb 2-1: configuration #1 chosen from 1 choice
Aug 9 17:00:56 sam kernel: [ 1731.486502] usbcore: registered new interface driver snd-usb-audio
Aug 9 17:00:58 sam pulseaudio[5975]: alsa-util.c: Device hw:1 doesn't support 44100 Hz, changed to 16000 Hz.
Aug 9 17:00:58 sam pulseaudio[5975]: alsa-util.c: Device hw:1 doesn't support 2 channels, changed to 1.
------------------------------
Hi guys, I managed to get this camera working as well, after a bit of fiddling. It seems the autoexpo option in the gspca driver is a bit unhelpful if you're trying to use skype, otherwise it's fine (worked on xawtv without). I posted a step by step guide for newbies like myself on my blog, hope it helps someone out. Cheers to redeye for that patch.
only problem on skype is it freezes after a while!
edit: hopefully sorted the freezing on skype now too - used gstfakevideo and it bought the CPU usage down from 100% for some reason. Haven't tested extensively though.
This post was last modified: 2008-08-13 15:49 by actionshrimp.
The patch provided above does work for the Logitech Quickcam E2500 but no other logitech webcam (with product id 0×046d) will work with the gspca driver then.
This is due to a bad placement of the case for the model id 089d.
The following patch will let all other logitech webcams work as usual with the gspca driver, providing support for the E2500 also.
This post was last modified: 2008-09-16 04:40 by brice.
at line 7527 of drivers/media/video/gspca/zc3xx.c
Then a /dev/video0 device is created and :
- it does work with amsn correctly, but an error appears in the console at every displayed frame "Corrupt JPEG data, premature end of data segment" ;
- it displays random pixels in Skype, unusable ;
- I get the following error with gstreamer based programs, with no picture at all, as in the following example :
gst-launch-0.10 v4l2src ! xvimagesink
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /pipeline0/v4l2src0: Could not negotiate format
Additional debug info:
gstbasesrc.c(2359): gst_base_src_start (): /pipeline0/v4l2src0:
Check your filtered caps, if any
Setting pipeline to NULL ...
FREEING pipeline ...
It doesn't change anything. So we need additional help...
Is anybody out there who understands the source code, so that he can tell us how broken JPEG frames can be generated?
How did you know that gspca_zc3xx was the correct one out of all the choices?
I don't know if its the correct choice. But in the old patch zc3xx was used. And because this is only a new version i think it must be the same sensor / bridge combination...
The source wouldnt compile before, but patched it does, and then rmmod gspca_main, modprobe gspca (the newly compiled one) seems to do the trick, if you watch out for a few permission problems which can occur... a lot of apps get permission denied /dev/video0 unless you run the app sudo. Maybe not ideal, but at least I can get video on skype again now...