Hello everybody,
After adding the following lines to Linux 2.4.18-14 (Redhat 8)
kernel version of drivers/usb/storage/unusual_devs.h:
UNUSUAL_DEV( 0x0a17, 0x0004, 0x0000, 0xffff,
"PENTAX",
"DIGITAL_CAMERA",
US_SC_8070, US_PR_CB, NULL,
US_FL_MODE_XLATE|US_FL_FIX_INQUIRY ),
usb-storage started working as one would expect (the usual
disclaimers of not trying this at home apply):
Oct 18 11:57:03 trap kernel: hub.c: USB new device connect on bus1/1, assigned device
number 2
Oct 18 11:57:03 trap kernel: usb.c: USB device 2 (vend/prod 0xa17/0x4) is not claimed
by any active driver.
Oct 18 11:57:06 trap /etc/hotplug/usb.agent: Setup usb-storage for USB product
a17/4/1000
Oct 18 11:57:06 trap kernel: SCSI subsystem driver Revision: 1.00
Oct 18 11:57:06 trap kernel: Initializing USB Mass Storage driver...
Oct 18 11:57:06 trap kernel: usb.c: registered new driver usb-storage
Oct 18 11:57:06 trap kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Oct 18 11:57:06 trap kernel: Vendor: PENTAX Model: DIGITAL_CAMERA Rev: 1000
Oct 18 11:57:06 trap kernel: Type: Direct-Access ANSI SCSI
revision: 02
Oct 18 11:57:06 trap kernel: USB Mass Storage support registered.
Oct 18 11:58:23 trap modprobe: modprobe: Can't locate module block-major-188
Oct 18 11:58:24 trap last message repeated 16 times
Oct 18 11:58:44 trap kernel: Attached scsi removable disk sda at scsi0, channel 0, id
0, lun 0
Oct 18 11:58:44 trap kernel: usb-uhci.c: interrupt, status 3, frame# 106
Oct 18 11:58:44 trap kernel: SCSI device sda: 250880 512-byte hdwr sectors (128 MB)
Oct 18 11:58:44 trap kernel: sda: Write Protect is off
Oct 18 11:58:44 trap kernel: sda:<7>usb-storage: queuecommand() called
Oct 18 11:58:44 trap kernel: sda1
Oct 18 11:58:49 trap apmd[696]: Charge: -1.954397 (0:05) 0:20 (60% unknown)
Oct 18 12:00:24 trap kernel: usb.c: USB disconnect on device 2
I was able to mount the camera and copy the images. However,
I still got some debug error messages whose fatality is not
exactly clear to me:
[...]
usb-storage: Bad target number (1/0)
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.
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
trap /proc/scsi # cat scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: PENTAX Model: DIGITAL_CAMERA Rev: 1000
Type: Direct-Access ANSI SCSI revision: 02
trap /proc/scsi # cat usb-storage-0/0
Host scsi0: usb-storage
Vendor: ASAHI PENTAX
Product: PENTAX OPTIO 330
Serial Number: None
Protocol: 8070i
Transport: Control/Bulk
GUID: 0a1700040000000000000000
Attached: Yes
trap /mnt # mount /dev/sda1 /mnt/camera
trap /mnt # cd /mnt/camera/dcim/100pentx/
imgp0858.jpg imgp0859.jpg imgp0860.jpg imgp0861.jpg
Defining the US_FL_SCM_MULT_TARG does not sound right, what do you
people recommend?
(PS. I would appreciate it if you could cc me directly if replying to
this message, I am not an active participant on the mailing list)
Best regards,
Mikko Ahonen
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
