On Tue, 21 Oct 2003, Jon Wilson wrote: > [1] Kernel oops generated when I try to access my USB camera > > [2] If I try to access my digital camera, using gphoto2, an "oops" is > generated. Here's what I did: > > [EMAIL PROTECTED] usb-debug]# lspci | grep -i usb > 00:14.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) > > [EMAIL PROTECTED] usb-debug]# lsusb > Bus 001 Device 001: ID 0000:0000 > > # now I turn the cam on > > [EMAIL PROTECTED] usb-debug]# lsusb > Bus 001 Device 002: ID 0919:0100 Tiger Electronics Fast Flicks Digital > Camera > Bus 001 Device 001: ID 0000:0000 > > # dmesg give me this: > hub 1-0:1.0: port 2, status 101, change 1, 12 Mb/s > drivers/usb/host/uhci-hcd.c: 6420: wakeup_hc > hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101 > hub 1-0:1.0: new USB device on port 2, assigned address 2 > usb 1-2: new device strings: Mfr=0, Product=0, SerialNumber=0 > drivers/usb/core/usb.c: usb_hotplug > usb 1-2: config 0 descriptor??
That last message is very odd. It indicates something might be wrong with your camera. Can you post the output from "lsusb -v" with your camera plugged in and turned on? Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
