Click to See Complete Forum and Search --> : USB camera devfs trouble


je_fro
07-09-2003, 08:12 PM
Howdy,
On Gentoo, I'm having trouble mounting a Sony digital camera. I have the following kernel stuff that may be related to my problem:
CONFIG_HOTPLUG=y
CONFIG_PNP=y
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_SR_EXTRA_DEVS=4
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_UMSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_SUPERMOUNT=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
CONFIG_USB_DEVICEFS=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_UHCI_ALT=y
CONFIG_USB_OHCI=y
CONFIG_USB_STORAGE=y
CONFIG_USB_STORAGE_DEBUG=y

Now, when I first plugged in the camera, usbview showed a Sony device attached. After stopping and starting the camera (to try to find the device) it only shows "Unknown Device", and it keeps on showing even after the camera is off. (I'll reboot later to see if it's still there. It may always be there.)
For the record, I am using the nforce2 chipset on an Abit-NF-7S MoBo, so that may also have something to do with it.
Dmesg gives this:
hub.c: new USB device 00:02.1-3, assigned address 3
usb-storage: act_altsettting is 0
usb-storage: id_index calculated to be: 21
usb-storage: Array length appears to be: 68
usb-storage: Vendor: Sony
usb-storage: Product: DSC-S30/S70/S75/505V/F505/F707
usb-storage: USB Mass Storage device detected
usb-storage: Endpoints: In: 0xf1ec9294 Out: 0xf1ec9280 Int: 0xf1ec92a8 (Period 255)
usb-storage: New GUID 054c00100000000000000000
usb-storage: Transport: Control/Bulk
usb-storage: Protocol: Transparent SCSI
usb-storage: *** thread sleeping.
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 ff 00 71 f5 43 b0 2b c0
usb-storage: Invoking Mode Translation
usb-storage: Call to usb_stor_control_msg() returned 6
usb-storage: usb_stor_transfer_partial(): xfer 255 bytes
usb-storage: usb_stor_bulk_msg() returned 0 xferred 56/255
usb-storage: CB data stage result is 0x1
usb-storage: -- CB transport device requiring auto-sense
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Call to usb_stor_control_msg() returned 6
usb-storage: usb_stor_transfer_partial(): xfer 18 bytes
usb-storage: usb_stor_bulk_msg() returned 0 xferred 18/18
usb-storage: usb_stor_transfer_partial(): transfer complete
usb-storage: CB data stage result is 0x0
usb-storage: -- Result from auto-sense is 0
usb-storage: -- code: 0x70, key: 0x0, ASC: 0x0, ASCQ: 0x0
usb-storage: No Sense: no additional sense information
usb-storage: Fixing INQUIRY data to show SCSI rev 2
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
Vendor: Sony Model: Sony DSC Rev: 4.01
Type: Direct-Access ANSI SCSI revision: 02
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad LUN (0/1)
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad target number (1/0)
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad target number (2/0)
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad target number (3/0)
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad target number (4/0)
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad target number (5/0)
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad target number (6/0)
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad target number (7/0)
usb-storage: *** thread sleeping.
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00 00 00 00 00 cb c1
usb-storage: Invoking Mode Translation
usb-storage: Call to usb_stor_control_msg() returned 6
usb-storage: -- CB transport device requiring auto-sense
usb-storage: Issuing auto-REQUEST_SENSE
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb-storage: command_abort() called
usb-storage: Call to usb_stor_control_msg() returned -104
usb-storage: -- auto-sense failure
usb-storage: CB_reset() called
usb-storage: CB[I] soft reset failed -32
usb-storage: scsi cmd done, result=0x70000
usb-storage: *** thread sleeping.
ldt allocation failed
ldt allocation failed
ldt allocation failed


Thanks for any help,
je_fro

je_fro
07-09-2003, 08:18 PM
gentoo je_fro # tail -f /var/log/everything/current

Jul 9 18:26:56 [kernel] Vendor: Sony Model: Sony DSC Rev: 4.01
Jul 9 18:26:56 [kernel] Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
Jul 9 18:27:01 [kernel] usb_control/bulk_msg: timeout

Hayl
07-09-2003, 08:25 PM
i'd report it to bugs.gentoo.org

especially if it works after a reboot but fails again after a disconnect / reconnect.

je_fro
07-10-2003, 02:04 AM
By trying gtkam, I found out that "PTP mode" is supported. I can almost mount the camera. It has become mostly a permissions issue. Root can view a few photos with gtkam, but I can't find the device to mount it. I get this in log:

Jul 10 01:01:54 [su(pam_unix)] session opened for user root by je_fro(uid=1000)
Jul 10 01:02:19 [kernel] usb.c: USB disconnect on device 00:02.1-3 address 5
Jul 10 01:02:29 [kernel] hub.c: new USB device 00:02.1-3, assigned address 6
Jul 10 01:02:29 [kernel] usb.c: USB device 6 (vend/prod 0x54c/0x4e) is not claimed by any active driver.
Jul 10 01:02:42 [gconfd (jeff-7180)] starting (version 1.0.8), pid 7180 user 'je_fro'

Any ideas how I can find the device other than trial and error?

I have no new sr or sg devices...can't find it anywhere.

bwkaz
07-10-2003, 10:21 PM
Originally posted by je_fro
Jul 10 01:02:29 [kernel] usb.c: USB device 6 (vend/prod 0x54c/0x4e) is not claimed by any active driver. Hmm... this message means that none of the USB drivers that your kernel has loaded are claiming that specific device type (or that specific device, I'm not 100% sure how it works). If that helps you at all...

It could be completely normal, actually. My LFS init scripts actually cause this error when they load USB support up -- when the USB bridge module is loaded (uhci.o), my USB mouse is connected, and my kernel logs a "usb.c: connect" message for the mouse, then a "device X is not claimed by any active driver" message a bit later, because I don't have any modules loaded that are saying "yeah, I'll take that mouse". When the init scripts later load the hid.o and mousedev.o modules, the kernel says "OK, now there's a USB driver loaded that will take that mouse, so I'll set up what's needed". It never logs any success message then, though.

This doesn't sound like exactly what's happening for you, since it doesn't end up working, but maybe it provides some insight? Maybe you just need to load an extra module? usb-storage is a good candidate, usually...