I'm coming to this thread late, so please excuse me if you've covered this already. I've had to use gscpa from upstream to get some more recent logitech cameras to work. You can get the upstream tarball from http://mxhaard.free.fr/download.html I see now, though that sid has the package gspca-source updated to the latest version from upstream. You have to use module-assistant etc, but it works for me on a couple logitech cameras (not "chat"). hth A On Mon, Apr 16, 2007 at 09:40:57PM +0200, Florian Kulzer wrote: > On Sun, Apr 15, 2007 at 21:08:03 +0000, David Dawson wrote: > > Florian Kulzer wrote: > > > > > On Sun, Apr 15, 2007 at 18:28:03 +0000, David Dawson wrote: > > >> Magnus Pedersen wrote: > > >> > > >> > David Dawson wrote: > > >> >>>> > > >> >> Thanks! ... > > >> >>> What does dmesg give your right after: > > >> >>> > > >> >>> - you plug in the device? > > >> >> This: > > >> >> usb 4-2: new full speed USB device using uhci_hcd and address 3 > > >> >> usb 4-2: configuration #1 chosen from 1 choice > > >> >> > > >> >> > > >> >>> - you modprobe the module? > > >> >> This: > > >> >> Linux video capture interface: v2.00 > > >> >> usbcore: registered new driver spca5xx > > >> >> /usr/src/modules/spca5xx/drivers/usb/spca5xx.c: spca5xx driver > > >> >> 00.60.00 registered > > >> > > > >> > And even after this you dont get /dev/video ? > > >> > > >> That's correct. > > >> I tried using MAKDEV, but it only created stuff in /dev/.static/dev > > > > > > That happens because udev should normally handle the device nodes > > > automatically. What messages do you get if you start > > > > > > udevmonitor > > > > > > and then plug in the camera? > > I get the following: > > UEVENT[1176670280.086049] add@/devices/pci0000:00/0000:00:13.1/usb4/4-2 > > UEVENT[1176670280.086132] > > add@/devices/pci0000:00/0000:00:13.1/usb4/4-2/usbdev4.3_ep00 > > UEVENT[1176670280.089077] > > add@/devices/pci0000:00/0000:00:13.1/usb4/4-2/4-2:1.0 > > UDEV [1176670280.089077] add@/devices/pci0000:00/0000:00:13.1/usb4/4-2 > > UEVENT[1176670280.089137] > > add@/devices/pci0000:00/0000:00:13.1/usb4/4-2/4-2:1.0/usbdev4.3_ep81 > > UEVENT[1176670280.089149] add@/class/usb_device/usbdev4.3 > > UDEV [1176670280.124411] > > add@/devices/pci0000:00/0000:00:13.1/usb4/4-2/usbdev4.3_ep00 > > UDEV [1176670280.127800] > > add@/devices/pci0000:00/0000:00:13.1/usb4/4-2/4-2:1.0 > > UDEV [1176670280.219247] > > add@/devices/pci0000:00/0000:00:13.1/usb4/4-2/4-2:1.0/usbdev4.3_ep81 > > UDEV [1176670280.260397] add@/class/usb_device/usbdev4.3 > > So udev does create some device nodes but not /dev/video0. What happens > if you symlink the device as /dev/video? > > [ snip: purging hotplug has been taken care of ] > > > As a parenthetical note, I have an elcheapo webcam which is detected, the > > module is loaded and the /dev/video0 device created just perfectly, so I am > > sure udev is doing its job, in the case of that device > > Is there any difference in the output of udevmonitor when you plug in > that camera? > > -- > Regards, | http://users.icfo.es/Florian.Kulzer > Florian | > > > -- > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > >
Attachment:
signature.asc
Description: Digital signature