How do I copy pictures from my kodak digital camera? [SOLVED]
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How do I copy pictures from my kodak digital camera? [SOLVED]
I've been a Linux user for about a year now, and I am very happy to have done so. However, I fear I have overlooked some very important tools that would give me the information I'm looking for.
What I'm trying to do is -
Plug in a USB camera
find /dev/camera-pseudonym
mount /dev/camera-pseudonym /camera
cp * ~/pictures
umount /dev/camera-pseudonym
and then work on adding this camera to /etc/fstab so that it will automatically mount to the usual place.
I don't know how to find the pseudonym.
I can, lsusb and see
Bus 004 Device 009: ID 040a:05c1 Kodak Co. Digital Camera
I can fdisk -l and not see any new partitions (which, with most USB devices with storage, I can usually see the partition listed in fdisk -l)
After these two commands related to search FOR the pseudonym, I draw a blank and resort to manually searching /dev for things that may be useful.
This is difficult, though, because there are dozens of files named usb-something, and they're all very similar to one another, and not related to typical pseudonyms I'm used to (like /dev/usb[0-9], /dev/sd[a-z], etc)
I would like to be able to find the /dev entry based on the ID 040a:05c1 because every USB devices I've tried has been listed by lsusb, and is accompanied by an ID number. I really don't even know what that ID number is for (or when it is assigned, or what assigns it), so I will add that to the list of questions.
How do I find the pseudonym in /dev for any usb device?
What is the ID number in the output from lsusb for?
Huh.. I guess if I ever do find the answer, then I'll know something that at least 41 other people don't know.
UPDATE --
Device ID numbers as listed by lsusb refer to
manufacturer:model
kodak:digital camera == 040a:05c1
I don't believe this will be useful in finding the pseudonym for the camera.
Also, dmesg gave plenty of info about the device, so I think once I figure out how/where/what the device file is, then I should be able to mount it.
*dmesg snip*
usb 4-1: new full speed USB device using ohci_hcd and address 4
usb 4-1: New USB device found, idVendor=040a, idProduct=05c1
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-1: Product: KODAK EasyShare M863 Digital Camera
usb 4-1: Manufacturer: Eastman Kodak Company
usb 4-1: SerialNumber: M863 0A3354156
usb 4-1: configuration #1 chosen from 1 choice
*dmesg snip*
Assuming no relationship between /dev/usbdev4.1 and usb 4-1:
UPDATE--
Modifying previous assumption based on results from udevadm
It would appear no "block" situations occur in the previous example. When using a tried and true USB device, the output from udevadm monitor contains block assignments and other pertinent info.
Likely solution is: find driver, use it, be happy.
UPDATE --
Likely solution turned out to be a bit off, but lead to the right answer.
The right answer, ladies and gentlemen, was gphoto2.
bash-3.1# gphoto2 -p 194-203
Downloading '100_0340.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0340.JPG
Downloading '100_0341.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0341.JPG
Downloading '100_0342.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0342.JPG
Downloading '100_0343.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0343.JPG
Downloading '100_0344.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0344.JPG
Downloading '100_0345.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0345.JPG
Downloading '100_0346.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0346.JPG
Downloading '100_0347.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0347.JPG
Downloading '100_0348.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0348.JPG
Downloading '100_0349.JPG' from folder '/store_00010001/DCIM/100KM863'...
Saving file as 100_0349.JPG
What you ran into there boy is a camera that uses PTP (Picture transfer protocol) which is why you didn't see a block device. Cameras using the PTP protocol doesn't use the standard mass storage system hence they doesn't mount as a volume.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.