Jump to content

Pentax Optio 33l problems


Guest whenelvisdied
 Share

Recommended Posts

Guest whenelvisdied

Hey all,

 

I've had this problem since I first installed Mandrake 10.1 (Kernel 2.6.8.1-12mdk) nearly 8 months ago. I have a Pentax Optio 33l camera, and I love it, but I haven't been able to get Linux to mount it. It recognizes it, and I get an icon my desktop which will not mount, and when i try and mount from console I get the following message:

 

mount: /dev/sde1 is not a valid block device

 

Some things I've been able to figure out:

 

lsusb lists it with the following entry:

 

Bus 003 Device 007: ID 0a17:0006 Pentax Corp. Pentax Optio S

 

I've got hotplug installed--use it with two flash drives and a Creativelabs mp3 player.

 

here's what I get with cat /var/log/messages ( a little long)

 

Dec  1 21:09:42 192 kernel: usb 3-2: new full speed USB device using address 9

Dec  1 21:09:42 192 kernel: scsi10 : SCSI emulation for USB Mass Storage devices

Dec  1 21:09:42 192 kernel:  Vendor: Pentax    Model: Optio S/S4        Rev: 0100

Dec  1 21:09:42 192 kernel:  Type:  Direct-Access                      ANSI SCSI revision: 02

Dec  1 21:09:43 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:43 192 kernel: sde: Write Protect is off

Dec  1 21:09:43 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:43 192 kernel:  /dev/scsi/host10/bus0/target0/lun0:scsi10: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 00 7a 00 00 00 01 00

Dec  1 21:09:43 192 kernel: Current sde: sense key Medium Error

Dec  1 21:09:43 192 kernel: Additional sense: Unrecovered read error

Dec  1 21:09:43 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:43 192 kernel: Buffer I/O error on device sde, logical block 31232

Dec  1 21:09:43 192 kernel: scsi10: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 00 7a 00 00 00 01 00

Dec  1 21:09:43 192 kernel: Current sde: sense key Medium Error

Dec  1 21:09:43 192 kernel: Additional sense: Unrecovered read error

Dec  1 21:09:43 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:43 192 kernel: Buffer I/O error on device sde, logical block 31232

Dec  1 21:09:43 192 kernel:  p1

Dec  1 21:09:43 192 kernel: Attached scsi removable disk sde at scsi10, channel0, id 0, lun 0

Dec  1 21:09:43 192 kernel: Attached scsi generic sg4 at scsi10, channel 0, id 0, lun 0,  type 0

Dec  1 21:09:43 192 scsi.agent[16602]: disk at /devices/pci0000:00/0000:00:10.2/usb3/3-2/3-2:1.0/host10/10:0:0:0

Dec  1 21:09:43 192 perl: drakupdate_fstab called with --auto --add /dev/sde1

Dec  1 21:09:44 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:44 192 kernel: sde: Write Protect is off

Dec  1 21:09:44 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:44 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:44 192 kernel: sde: Write Protect is off

Dec  1 21:09:44 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:44 192 kernel:  /dev/scsi/host10/bus0/target0/lun0:scsi10: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 00 7a 00 00 00 01 00

Dec  1 21:09:44 192 kernel: Current sde: sense key Medium Error

Dec  1 21:09:44 192 kernel: Additional sense: Unrecovered read error

Dec  1 21:09:44 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:44 192 kernel: Buffer I/O error on device sde, logical block 31232

Dec  1 21:09:44 192 kernel: scsi10: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 00 7a 00 00 00 01 00

Dec  1 21:09:44 192 kernel: Current sde: sense key Medium Error

Dec  1 21:09:44 192 kernel: Additional sense: Unrecovered read error

Dec  1 21:09:44 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:44 192 kernel: Buffer I/O error on device sde, logical block 31232

Dec  1 21:09:44 192 kernel:  p1

Dec  1 21:09:44 192 perl: drakupdate_fstab called with --auto --del /dev/sde1

Dec  1 21:09:45 192 perl: drakupdate_fstab called with --auto --add /dev/sde1

Dec  1 21:09:45 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:45 192 kernel: sde: Write Protect is off

Dec  1 21:09:45 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:45 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:45 192 kernel: sde: Write Protect is off

Dec  1 21:09:45 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:45 192 kernel:  /dev/scsi/host10/bus0/target0/lun0:scsi10: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 00 7a 00 00 00 01 00

Dec  1 21:09:45 192 kernel: Current sde: sense key Medium Error

Dec  1 21:09:45 192 kernel: Additional sense: Unrecovered read error

Dec  1 21:09:45 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:45 192 kernel: Buffer I/O error on device sde, logical block 31232

Dec  1 21:09:45 192 kernel: scsi10: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 00 7a 00 00 00 01 00

Dec  1 21:09:45 192 kernel: Current sde: sense key Medium Error

Dec  1 21:09:45 192 kernel: Additional sense: Unrecovered read error

Dec  1 21:09:45 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:45 192 kernel: Buffer I/O error on device sde, logical block 31232

Dec  1 21:09:45 192 kernel:  p1

Dec  1 21:09:45 192 perl: drakupdate_fstab called with --auto --del /dev/sde1

Dec  1 21:09:46 192 perl: drakupdate_fstab called with --auto --add /dev/sde1

Dec  1 21:09:46 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:46 192 kernel: sde: Write Protect is off

Dec  1 21:09:46 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:46 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:46 192 kernel: sde: Write Protect is off

Dec  1 21:09:46 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:46 192 kernel:  /dev/scsi/host10/bus0/target0/lun0:scsi10: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 00 7a 00 00 00 01 00

Dec  1 21:09:46 192 kernel: Current sde: sense key Medium Error

Dec  1 21:09:46 192 kernel: Additional sense: Unrecovered read error

Dec  1 21:09:46 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:46 192 kernel: Buffer I/O error on device sde, logical block 31232

Dec  1 21:09:46 192 kernel: scsi10: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 00 7a 00 00 00 01 00

Dec  1 21:09:46 192 kernel: Current sde: sense key Medium Error

Dec  1 21:09:46 192 kernel: Additional sense: Unrecovered read error

Dec  1 21:09:46 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:46 192 kernel: Buffer I/O error on device sde, logical block 31232

Dec  1 21:09:46 192 kernel:  p1

Dec  1 21:09:47 192 perl: drakupdate_fstab called with --auto --del /dev/sde1

Dec  1 21:09:47 192 perl: drakupdate_fstab called with --auto --add /dev/sde1

Dec  1 21:09:47 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:47 192 kernel: sde: Write Protect is off

Dec  1 21:09:47 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:47 192 kernel: SCSI device sde: 31233 512-byte hdwr sectors (16 MB)

Dec  1 21:09:47 192 kernel: sde: Write Protect is off

Dec  1 21:09:47 192 kernel: sde: assuming drive cache: write through

Dec  1 21:09:47 192 kernel:  /dev/scsi/host10/bus0/target0/lun0:SCSI error : <10 0 0 0> return code = 0x10070000

Dec  1 21:09:47 192 kernel: end_request: I/O error, dev sde, sector 31232

Dec  1 21:09:47 192 kernel: Buffer I/O error on device sde, logical block 31232

 

Crazy, huh? I have no clue what's going on, and after scouring the net looking for answers, I thought I'd try my luck here.

 

Any help would be much appreciated

Edited by whenelvisdied
Link to comment
Share on other sites

Here the camera is reported as usb-storage compliant, so mounting it as a typical USB drive shouldn't be a problem.

Please checkout the camera menus if there's any choice between Normal USB, PictBridge and PTP- set it as normal.

Also, doing an lsmod you must have "usb-storage" listed. If not, do a "modprobe usb-storage" manually.

Link to comment
Share on other sites

Guest whenelvisdied

I have usb-storage listed. Which camera menus do you mean? In the camera itself? In Digikam?

 

I'm actually concerned that there's a problem with my scsi drivers, but I'm dreading having to recompile them in. Is there any way to avoid doing this?

Link to comment
Share on other sites

  • 1 month later...
Guest whenelvisdied

I've got two memory cards, both of which I've formatted and tried in the camera. Still nothing.

 

I should probably mention that when I lsmod, usb-storage is listed with a 0 next to it, while other things have some four, five, or six digit number. Does this mean I haven't configured it correctly?

 

Any other ideas? I'd really like to use this camera.

Link to comment
Share on other sites

There should be little to need configuring...

My camera A Nikon D70 has two modes a USB mass storage and a PTP .. and these need selecting in the camera memory... when its USB mass storage it should mount but if not you will need digikam etc. to 'mount' it and then its not like a regular USB-SCSI mount.

 

I honestly haven't tried the PtP mode but if I were you I'd try a standalone reader if you are 100% sure the camera is set to USB MS mode if you know anyone with one... its better to make sure what is wrong before messing about...

 

you can

dmesg | tail -f

ïn a terminal when you turn on the camera power and it shoudl show the connections :D

 

hope this helps

Link to comment
Share on other sites

USB mass storage triggers the usb_storage kernel module, which in general needs nothing at all! You should be able to mount your camera as an ordinary flash drive in that mode.

Gphoto/ Digikam (and their virtual gphotofs) are useful for devices that can only operaate in PTP mode. For the ones uder the usb_storage protocol, they are quite odd/not needed.

Link to comment
Share on other sites

This may be way-off, but do you need to mount the camera? Maybe you can communicate with it using gphoto2 or digikam without it being mounted. What happens when you run from the command line:

gphoto2 --auto-detect
gphoto2 --list-files

?

And when you're in digikam, can you select from the menu Camera - add camera - auto-detect and then view the pictures on the camera?

Link to comment
Share on other sites

Guest whenelvisdied
There should be little to need configuring...

My camera A Nikon D70 has two modes a USB mass storage and a PTP .. and these need selecting in the camera memory... when its USB mass storage it should mount but if not you will need digikam etc. to 'mount' it and then its not like a regular USB-SCSI mount. 

 

I honestly haven't tried the PtP mode but if I were you I'd try a standalone reader if you are 100% sure the camera is set to USB MS mode if you know anyone with one... its better to make sure what is wrong before messing about... 

 

you can

dmesg | tail -f   

ïn a terminal when you turn on the camera power and it shoudl show the connections :D 

 

hope this helps

 

Here's what I get from dmesg:

sde: assuming drive cache: write through

SCSI device sde: 125953 512-byte hdwr sectors (64 MB)

sde: Write Protect is off

sde: Mode Sense: 00 46 02 00

sde: assuming drive cache: write through

/dev/scsi/host8/bus0/target0/lun0:scsi8: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 00 01 ec 00 00 00 01 00

Current sde: sense key Medium Error

Additional sense: Unrecovered read error

end_request: I/O error, dev sde, sector 125952

Buffer I/O error on device sde, logical block 125952

tail: standard input: file truncated

tail: standard input: cannot seek to offset 0: Illegal seek

 

When I turn the camera on, I get an icon on the desktop, but when I click on it, or try to mount it, it sits for about 30 seconds and then tells me the disk is not a valid block device.

 

Curiouser and Curiouser

Link to comment
Share on other sites

When I turn the camera on, I get an icon on the desktop, but when I click on it, or try to mount it, it sits for about 30 seconds and then tells me the disk is not a valid block device. 

Curiouser and Curiouser

 

Try re-formatting the stick within your OS as vfat, and get sure that you do have FAT(32) filesystem support in your box ( something named "dosfstools" or a similar program which brings FAT support to Linux should be installed).

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...