Philips webcam

[Gerald Dachs]

Am Sat, 5 Jan 2008 13:08:53 +0200
schrieb "Dotan Cohen" <dotancohen at gmail.com>:
> feisty at feisty-laptop:~$ sudo modprobe -r gspca
> feisty at feisty-laptop:~$ sudo modprobe gspca
> feisty at feisty-laptop:~$
> 
> There were no errors, however, there is _still_ no /dev/video.
> Unplugging and then plugging in the camera gives me this:
> 
> feisty at feisty-laptop:~$ tail /var/log/kern.log
> Jan  5 11:06:53 feisty-laptop kernel: [42838.700000] b44: eth0: Link
> is up at 100 Mbps, full duplex.
> Jan  5 11:06:53 feisty-laptop kernel: [42838.700000] b44: eth0: Flow
> control is off for TX and off for RX.
> Jan  5 11:06:53 feisty-laptop kernel: [42838.760000]
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> Jan  5 11:07:09 feisty-laptop kernel: [42853.752000] eth0: no IPv6
> routers present
> Jan  5 12:58:50 feisty-laptop kernel: [49555.468000] Linux video
> capture interface: v2.00
> Jan  5 12:58:50 feisty-laptop kernel: [49555.484000] usbcore:
> registered new interface driver gspca
> Jan  5 12:58:50 feisty-laptop kernel: [49555.484000]
> ubuntu/media/gspcav1/gspca_core.c: gspca driver 01.00.12 registered
> Jan  5 13:01:56 feisty-laptop kernel: [49741.084000] usb 2-1: USB
> disconnect, address 3
> Jan  5 13:01:59 feisty-laptop kernel: [49744.104000] usb 2-1: new full
> speed USB device using uhci_hcd and address 4
> Jan  5 13:01:59 feisty-laptop kernel: [49744.332000] usb 2-1:
> configuration #1 chosen from 1 choice
> feisty at feisty-laptop:~$

Most likely this version of the driver doesn't recognize your
camera. I would look now into the source code, whether the
vendor and product id of your camera can be found.
In similar situations with wlan usb sticks I could add the
missing ids and the stick simply worked. This works very
often, because the driver is made for a chip inside the device,
but these chips are used then by many vendors with their unique
vendor ids. The driver checks whether a device with his chip is
installed by probing for all vendor and product ids it knows.
If a new vendor decides to use this chip, or a vendor makes a
change of the product id, it is invisible for the driver. 

Gerald