Some time ago I purchased an Aiptek "Pocket DVII 1.3 Mega digital camera. I would like to get this working under Linux. On connecting the camera to the USB port the following is logged: kernel: hub.c: new USB device 00:11.2-1, assigned address 6 /sbin/hotplug: arguments (usb) env (DEVFS=/proc/bus/usb OLDPWD=/ \ PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug \ SHLVL=1 HOME=/ DEVICE=/proc/bus/usb/001/006 INTERFACE=8/6/80 \ PRODUCT=8ca/105/100 TYPE=0/0/0 DEBUG=yes _=/bin/env) /sbin/hotplug: invoke /etc/hotplug/usb.agent () /etc/hotplug/usb.agent: Setup usb-storage for USB product 8ca/105/100 When I attempt to access the camera under gphoto: kernel: usb-uhci.c: interrupt, status 3, frame# 1901 kernel: SCSI device (ioctl) reports ILLEGAL REQUEST. kernel: SCSI device sda: 12288 512-byte hdwr sectors (6 MB) kernel: sda: test WP failed, assume Write Enabled kernel: sda: I/O error: dev 08:00, sector 0 kernel: I/O error: dev 08:00, sector 0 kernel: unable to read partition table is logged. I have also attempted to "mount" the camera using every file system I can think of without being able to read it. Any suggestions anyone? I must be doing something wrong! Leon Stedman
On Friday 07 May 2004 17:20, Leon Stedman wrote:
When I attempt to access the camera under gphoto: kernel: usb-uhci.c: interrupt, status 3, frame# 1901 kernel: SCSI device (ioctl) reports ILLEGAL REQUEST. kernel: SCSI device sda: 12288 512-byte hdwr sectors (6 MB) kernel: sda: test WP failed, assume Write Enabled kernel: sda: I/O error: dev 08:00, sector 0 kernel: I/O error: dev 08:00, sector 0 kernel: unable to read partition table is logged.
I've seen these branded as Nisis. I would guess that perhaps the camera uses some kind of wierd file system, that fact that sda gets assigned to it would lead us to believe that it does support the USB mass storage controller, but based on what you said about trying different mounts and the errors above it looks like the filesystem is unrecognised. Notice how the kernel thinks the disk is 6MB when if fact the built in ram on your camera is 16MB, looks like the sector count is screwed up. There are a few things you could try here. Look at how the camera behaves when plugged into a win2000/XP box, does it mount up as a removeable drive without any third party drivers ? If not then it either has a strange filesystem or it is not a standard usb mass storage device. What happens if you plug in a standard CF card, can you mount that through the camera ? 3rd (potentially dangerous) option....what does fsck make of sda ?....personally I would think very carefully before trying that though, if it is an odd filesystem there is a chance that fsck could break it.
On Friday 07 May 2004 23:33, Wayne Stallwood wrote:
On Friday 07 May 2004 17:20, Leon Stedman wrote:
When I attempt to access the camera under gphoto: kernel: usb-uhci.c: interrupt, status 3, frame# 1901 kernel: SCSI device (ioctl) reports ILLEGAL REQUEST. kernel: SCSI device sda: 12288 512-byte hdwr sectors (6 MB) kernel: sda: test WP failed, assume Write Enabled kernel: sda: I/O error: dev 08:00, sector 0 kernel: I/O error: dev 08:00, sector 0 kernel: unable to read partition table is logged.
A bit of googling brings up this http://www.mail-archive.com/linux-usb-users@lists.sourceforge.net/ msg06729.html You can find the file you need to modify in /drivers/usb/storage of the kernel source, means a recompile I know but at least it can be made to work. It's been submitted so maybe it appears in later kernels now (can't see it in 2.4.21)
On Sat, 8 May 2004, Wayne Stallwood wrote:
On Friday 07 May 2004 23:33, Wayne Stallwood wrote:
On Friday 07 May 2004 17:20, Leon Stedman wrote:
When I attempt to access the camera under gphoto: kernel: usb-uhci.c: interrupt, status 3, frame# 1901 kernel: SCSI device (ioctl) reports ILLEGAL REQUEST. kernel: SCSI device sda: 12288 512-byte hdwr sectors (6 MB) kernel: sda: test WP failed, assume Write Enabled kernel: sda: I/O error: dev 08:00, sector 0 kernel: I/O error: dev 08:00, sector 0 kernel: unable to read partition table is logged.
http://www.mail-archive.com/linux-usb-users@lists.sourceforge.net/ msg06729.html
You can find the file you need to modify in /drivers/usb/storage of the kernel source, means a recompile I know but at least it can be made to work.
It's been submitted so maybe it appears in later kernels now (can't see it in 2.4.21)
I can report some progress: I added the following to Linux/drivers/usb/unusual_dev.h UNUSUAL_DEV( 0x8ca, 0x105, 0x0000, 0x9999, "Aiptek", "Mega DV", US_SC_SCSI, US_PR_BULK, NULL, US_FL_START_STOP | US_FL_MODE_XLATE), recompiled the module and used the new usb-storage.o module. I am using 2.4.20-8 RedHat. Added to /etc/fstab the line: /dev/sda1 /mnt/cam auto noauto,owner,user,rw 0 0 I can now read the camera, but the files are corrupt, blocks of the picture appear in the wrong places. The JPEG files, which I expect to be of the same size, are of different sizes. Running fdisk gives: Disk /dev/sda: 6 MB, 6291456 bytes 2 heads, 32 sectors/track, 192 cylinders Units = cylinders of 64 * 512 = 32768 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 192 6137+ 1 FAT12 Partition 1 has different physical/logical beginnings (non-Linux?): phys=(0, 1, 1) logical=(0, 0, 14) The internal memory should be 16 MB. Anyone suggest the next move please? Leon Stedman
I can report some progress:
I added the following to Linux/drivers/usb/unusual_dev.h UNUSUAL_DEV( 0x8ca, 0x105, 0x0000, 0x9999, "Aiptek", "Mega DV", US_SC_SCSI, US_PR_BULK, NULL, US_FL_START_STOP | US_FL_MODE_XLATE),
recompiled the module and used the new usb-storage.o module. I am using 2.4.20-8 RedHat.
Added to /etc/fstab the line: /dev/sda1 /mnt/cam auto noauto,owner,user,rw 0 0
I can now read the camera, but the files are corrupt, blocks of the picture appear in the wrong places. The JPEG files, which I expect to be of the same size, are of different sizes.
Running fdisk gives: Disk /dev/sda: 6 MB, 6291456 bytes 2 heads, 32 sectors/track, 192 cylinders Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System /dev/sda1 * 1 192 6137+ 1 FAT12 Partition 1 has different physical/logical beginnings (non-Linux?): phys=(0, 1, 1) logical=(0, 0, 14)
The internal memory should be 16 MB.
hmmmm Fat12 looks pretty suspicious, The CF card inserted will almost always be FAT32 so why would they bother with a different format for the built in storage........ JPEG files can be of different sizes even when they are the same pixel size and colour depth. It all depends on the level of compression used and how well the content compresses (varies somewhat) Can you send me one of these JPEG's by email, I would like to take a look at it.
On Mon, 2004-05-10 at 23:24, Wayne Stallwood wrote:
hmmmm Fat12 looks pretty suspicious, The CF card inserted will almost always be FAT32 so why would they bother with a different format for the built in storage........
My Canon certainly doesn't recognise FAT32... -- Regards, Adam Allen. adam@dynamicinteraction.co.uk pgp http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x553349DB
On Tuesday 11 May 2004 00:16, Mr. Adam ALLEN wrote:
On Mon, 2004-05-10 at 23:24, Wayne Stallwood wrote:
hmmmm Fat12 looks pretty suspicious, The CF card inserted will almost always be FAT32 so why would they bother with a different format for the built in storage........
My Canon certainly doesn't recognise FAT32...
My mistake, I meant FAT16, most CF cards are preformatted to FAT16....was tired last night
Dunno if it helps but this is in /etc/fstab when I plug in my Olympus D-380: none /mnt/camera supermount dev=/dev/sda1,fs=ext2:vfat,--,iocharset=iso88 59-15,kudzu,codepage=850 0 0 (all one line - auto line wrapped by Kmail, sorry) Syd
participants (4)
-
Leon Stedman -
Mr. Adam ALLEN -
Syd Hancock -
Wayne Stallwood