Access my digital camera via USB
Markus Hoenicka
markus.hoenicka at mhoenicka.de
Tue Apr 14 21:05:00 UTC 2015
At 2015-04-14 22:39, William A. Mahaffey III was heard to say:
> On 04/14/15 15:27, Chris Hill wrote:
>> On Tue, 14 Apr 2015, William A. Mahaffey III wrote:
>>
>>> I am trying to get some photos off of my digital camera via USB
>>> cable. WHen I plug it in, I get the following in my messages file:
>>>
>>>
>>> Apr 14 14:44:44 kabini1 kernel: ugen3.2: <SAMSUNG> at usbus3
>>> Apr 14 14:44:44 kabini1 kernel: umass0: <SAMSUNG Samsung Digital
>>> Camera, class 0/0, rev 2.00/0.00, addr 2> on usbus3
>>> Apr 14 14:44:44 kabini1 kernel: umass0: 8070i (ATAPI) over
>>> Bulk-Only; quirks = 0x4100
>>> Apr 14 14:44:44 kabini1 kernel: umass0:4:0:-1: Attached to scbus4
>>> Apr 14 14:44:44 kabini1 kernel: da0 at umass-sim0 bus 0 scbus4 target
>>> 0 lun 0
>>> Apr 14 14:44:44 kabini1 kernel: da0: <Samsung Digital Camera >
>>> Removable Direct Access SCSI-0 device
>>> Apr 14 14:44:44 kabini1 kernel: da0: Serial Number E00000000002
>>> Apr 14 14:44:44 kabini1 kernel: da0: 40.000MB/s transfers
>>> Apr 14 14:44:44 kabini1 kernel: da0: 2909MB (5959296 512 byte
>>> sectors: 255H 63S/T 370C)
>>> Apr 14 14:44:44 kabini1 kernel: da0: quirks=0x2<NO_6_BYTE>
>>> Apr 14 14:44:44 kabini1 kernel: GEOM_PART: integrity check failed
>>> (da0, MBR)
>>>
>>>
>>> How do I mount this to access the data, there are (apparently) no
>>> mountable partitions .... TIA.
>>
>> I would do this:
>>
>> ls /dev | grep ^da
>>
>> ...before and after plugging in the camera, and see what's changed.
>>
>> If you see that (for example) /dev/da0 has appeared, try mounting it.
>> Bear in mind that it may well be msdosfs. If that fails, you may need
>> to use gphoto or some such. Personally I use gtkam. Of course it could
>> also be that your camera's SD card is on the way out.
>>
>> Speaking of which, you could also try removing the SD (or whatever it
>> is) card from the camera and mounting via a USB card reader.
>>
>> HTH.
>>
>
> [root at kabini1, /etc, 3:00:38pm] 374 % lf /dev/
> acpi ad6@ ada0p1 ada2p2 bpf0@ dsp1.0
> kbd1@ mixer0 pci ttyu0 ttyv8 ugen2.1@ usb/
> ad10@ ad6p1@ ada0p2 ada2p3 console dsp2.0
> kbd2@ mixer1 ppi0 ttyu0.init ttyv9 ugen3.1@
> usbctl
> ad10p1@ ad6p2@ ada0p3 ada2p4 consolectl dsp3.0
> kbdmux0 mixer2 ptmx ttyu0.lock ttyva ugen3.2@
> vboxdrv
> ad10p2@ ad6p3@ ada0p4 ada3 ctty dumpdev@ klog
> mixer3 pts/ ttyv0 ttyvb ugen4.1@ vboxdrvu
> ad10p3@ ad6p4@ ada1 ada3p1 cuau0 fd/ kmem
> nfslock random ttyv1 ttyvc ugen4.2@
> vboxnetctl
> ad10p4@ ad8@ ada1p1 ada3p2 cuau0.init fido
> log@ null sndstat ttyv2 ttyvd ugen4.3@ xpt0
> ad4@ ad8p1@ ada1p2 ada3p3 cuau0.lock geom.ctl
> lpt0 pass0 stderr@ ttyv3 ttyve ugen5.1@ zero
> ad4p1@ ad8p2@ ada1p3 ada3p4 da0 gpt/
> lpt0.ctl pass1 stdin@ ttyv4 ttyvf ukbd0
> ad4p2@ ad8p3@ ada1p4 atkbd0 devctl gptid/
> mdctl pass2 stdout@ ttyv5 ufssuspend ums0
> ad4p3@ ad8p4@ ada2 audit devstat io
> mem pass3 stripe/ ttyv6 ugen0.1@ ums1
> ad4p4@ ada0 ada2p1 bpf dsp0.0 kbd0@
> midistat pass4 sysmouse ttyv7 ugen1.1@ urandom@
> [root at kabini1, /etc, 3:42:51pm] 375 % ls /dev | grep ^da
> [root at kabini1, /etc, 3:42:58pm] 376 % lf /dev/da*
> /dev/da0
> [root at kabini1, /etc, 3:43:10pm] 377 % ll !$
> ll /dev/da*
> crw-r----- 1 root operator 0xc9 Apr 14 14:50 /dev/da0
> [root at kabini1, /etc, 3:43:14pm] 378 %
>
> the only thing that appeared was /dev/da0
>
>
> [root at kabini1, /etc, 3:44:53pm] 379 % mount -t msdosfs /dev/da0
> /media/flash/
> mount_msdosfs: /dev/da0: Invalid argument
> [root at kabini1, /etc, 3:45:22pm] 380 %
>
>
> I'm stumped, need anything else, please ask & thanks :-) ....
If your camera speaks PTP, you may try this instead:
http://www.mhoenicka.de/system-cgi/blog/index.php?itemid=2234
regards,
Markus
--
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38
More information about the freebsd-questions
mailing list