I am trying to access the memory stick in a Soney DSC Cybershot P-73.
I've done it before with the P-50 - load the modules and viola! However, this time, something is detected (see dmesg output later) but no driver is assigned. I've included lsmod and dmesg so you can check what I'm saying.

I've googled the problem so I'm probably missed something obvious and simple.

The main difference is that this is a memory stick pro - is that supposed to be different? Alternatively the camera is handling USB differently...

Here's lsmod
-----------------------------------
Module Size Used by Not tainted
ppp_deflate 4536 0 (autoclean)
zlib_inflate 21540 0 (autoclean) [ppp_deflate]
zlib_deflate 21368 0 (autoclean) [ppp_deflate]
bsd_comp 5464 0 (autoclean)
ppp_async 9440 1 (autoclean)
ppp_generic 21180 3 (autoclean) [ppp_deflate bsd_comp ppp_async]
slhc 6740 1 (autoclean) [ppp_generic]
usbserial 20188 0 (unused)
nls_iso8859-1 3516 0 (autoclean)
isofs 20812 0 (autoclean)
udf 97312 0 (autoclean)
sd_mod 12556 0 (unused)
usb-ohci 21448 0 (unused)
usb-storage 28400 0 (unused)
scsi_mod 70836 1 [sd_mod usb-storage]
ide-cd 35680 0 (autoclean)
cdrom 33696 0 (autoclean) [ide-cd]
i810_audio 27592 0 (autoclean)
ac97_codec 17192 0 (autoclean) [i810_audio]
parport_pc 19044 1 (autoclean)
lp 8320 0 (autoclean)
parport 37056 1 (autoclean) [parport_pc lp]
apm 12680 2
8139too 17320 0
mii 3976 0 [8139too]
crc32 3712 0 [8139too]
ipt_state 1048 3 (autoclean)
ip_conntrack 27272 1 (autoclean) [ipt_state]
iptable_filter 2412 1 (autoclean)
ip_tables 15520 2 [ipt_state iptable_filter]
microcode 4668 0 (autoclean)
keybdev 2944 0 (unused)
mousedev 5556 1
input 5760 0 [keybdev mousedev]
hid 12408 0 (unused)
unix 18120 249 (autoclean)

here's dmesg
-----------------------------------
hub.c: new USB device 00:0b.0-1, assigned address 9
usb.c: kmalloc IF c03ca360, numif 1
usb.c: new device strings: Mfr=1, Product=2, SerialNumber=0
usb.c: USB device number 9 default language ID 0x409
Manufacturer: Sony
Product: Sony DSC
usb.c: unhandled interfaces on device
usb.c: USB device 9 (vend/prod 0x54c/0x10) is not claimed by any active driver.
Length = 18
DescriptorType = 01
USB version = 2.00
Vendor:Product = 054c:0010
MaxPacketSize0 = 64
NumConfigurations = 1
Device version = 5.00
Device Class:SubClass:Protocol = 00:00:00
Per-interface classes
Configuration:
bLength = 9
bDescriptorType = 02
wTotalLength = 0027
bNumInterfaces = 01
bConfigurationValue = 01
iConfiguration = 00
bmAttributes = c0
MaxPower = 2mA

Interface: 0
Alternate Setting: 0
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 00
bNumEndpoints = 03
bInterface Class:SubClass:Protocol = 08:ff:01
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 01 (out)
bmAttributes = 02 (Bulk)
wMaxPacketSize = 0040
bInterval = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 82 (in)
bmAttributes = 02 (Bulk)
wMaxPacketSize = 0040
bInterval = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 83 (in)
bmAttributes = 03 (Interrupt)
wMaxPacketSize = 0008
bInterval = ff
usb.c: kusbd: /sbin/hotplug add 9
hub.c: port 2, portstatus 100, change 0, 12 Mb/s

-----------------------------------
and that's it... hope someone knows what's happening.
Simon

Basic question: have you tried just manually mounting the memory stick? -- J.W.

J.W. Yes - I have tried looking through sda(x) to see if I could find the block special device corresponding to the camera -

fsatb adn mstab make no mention of a camera mount point and /dev/camera and /mnt/camera do not exist... yet I have had a camera mounted before. This is the trouble when the system mounts things for you, you don't learn how it does it

Anyway - I did:

%mount /dev/sda1 -t vfat /mnt/camera as follows...

[root@indigo-prime mnt]# mount /dev/sda1 -t vfat /mnt/camera
mount: /dev/sda1 is not a valid block device


Same for others

Curiously, fstab had two (2) lines referring to /dev/cdrom, where there was but one before. Some sort of silly-buggers seems to be going on. The only other odd thing to occur was the dissappearance of the video-card driver... which reappeared after a power reboot. This after a day of brownouts... though I also updated my a-virus software and cleaned the system (no viruses detected).

same problem here.
Soon I'll try gtkam (http://www.gphoto.org/)
and I think u should try to.
Please report me whatever occurs.

I'm not sure I'm interested in getting yet another camera reader.... if worst comes to worst, I'll just get a media reader and access the memory stick that way.

I note that the memory stick is the same one I used in the old camera... so I think it is the new camera that's at fault here. I'm getting a replacement for the old one soonish so I'll get to see then

Meanwhile - anyone who *can* access a memory stick via a memory stick pro camera - please let me know! Especially, show my your lsmod output and what dmesg says when the camera is plugged in.

(C'mon folks... there must be someone!)

Thanks.

Simon

gtkam didn' t worked for me,
and I cannot mount my camera yet.
Do you have a clue?

<sigh> Surely somebody has managed to mount this camera??? OK ericKFis ...

to use gtkam, you will need to make sure your camera is not in "normal" mode. There will be other modes for data transfer using third party camera software... it's just that Sony like you to use it as a mass storage device.

reset your system, connect the camera and do dmesg and lsmod and paste the output to your reply. Also state which camera you're using and the stick and the linux version/CPU etc.

The most common reason for being unable to mount a fs is due to a missing driver.

eg. I suspect the mem-stick pro system uses a compression or fs that my kernel dosn't know about.

the formatted stick is supposed to be FAT, but the "pro" version could use NTFS... which would cause writing difficulties but not reading difficulties. Anyway... it shouod still show up as a device and the error message would be "unknown file system" style. So I don't think it's the fs. Could this be a driver problem? Do we need a special driver to interface with mem-stick pro devices?

Simon

Ok, I'll try it.
But since I'm not at home now, I can try only on saturday.
Then I'll come back to tell you what happens.

OK - an alternative transfer method supported by Sony is PTP. I've discovered that gphoto does NOT support PTP. However, there is a very small utility that claims to, called jPhoto. (Suspect I need a Java Runtime Environment... but we'll see...) I'll give this a go sometime this week, since it's sooo small!

Meanwhile, my P-32 turns out to be unfixable... the shop has replaced it with a P-43... which is unfortunately also memory stick PRO! grrr.

Can anyone tell me if the later kernels explicitly support memory stick pro devices?

If the usb-storage driver won't recognise the camera with "pro" then I don't see why it should recognise a media reader for same!
Simon

The breif test with jPhoto was odd... I tried to load the rpm from the project page, but it insisted I needed an old version of the java libraries... the ones I had installed were too new !?!

So @$#%! I say, and I got a flash-card (7 in 1) reader from Dick Smith (NZ$33.00). This works fine! (Tho only in the 2.4.20-6 kernel not the 2.4.22... I'm trying to find the missing module...)

So - I say good bye to this thread - lots of luck all you others who are trying this out.

Simon

gtkam with PTP recognises the P73 as a differnt camera - P72. But it goes.

Thanks for helping Simon,
but a long time ago I've started to use the
kernel 2.6, wich actually is able to mount my camera
without problems.

Best regards!!!!

Oh nice one I only posted to finish the thread - I( didn't know anyone was still watching.