since I recently upgraded to the latest opensuse, my digital camera (canon Powershot A620) is not mountable any more as a separate file system.
It is, however, still recognized by gtkam and gphoto2, with complete functionality there.
lsusb is saying: Bus 001 Device 015: ID 04a9:30fc Canon, Inc. PowerShot A620 (PTP mode)
/var/log/messages is saying: Jan 26 23:34:16 stille-pc kernel: [42545.922521] usb 1-1.2: USB disconnect, device number 14
Jan 26 23:36:12 stille-pc kernel: [42661.258709] usb 1-1.2: new high-speed USB device number 15 using ehci_hcd
Jan 26 23:36:12 stille-pc kernel: [42661.356334] usb 1-1.2: New USB device found, idVendor=04a9, idProduct=30fc
Jan 26 23:36:12 stille-pc kernel: [42661.356338] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 26 23:36:12 stille-pc kernel: [42661.356342] usb 1-1.2: Product: Canon Digital Camera
Jan 26 23:36:12 stille-pc kernel: [42661.356344] usb 1-1.2: Manufacturer: Canon Inc.
so the usual way of mounting mount /dev/sdb1 /media/[size=1]camera[/size]
is not available?
On 01/26/2013 04:46 PM, velsd wrote:
>
> hi all,
>
> since I recently upgraded to the latest opensuse, my digital camera
> (canon Powershot A620) is not mountable any more as a separate file
> system.
>
> It is, however, still recognized by gtkam and gphoto2, with complete
> functionality there.
>
> lsusb is saying:
> -Bus 001 Device 015: ID 04a9:30fc Canon, Inc. PowerShot A620
> (PTP mode)-
>
> /var/log/messages is saying:
> -Jan 26 23:34:16 stille-pc kernel: [42545.922521] usb 1-1.2:
> USB disconnect, device number 14
> Jan 26 23:36:12 stille-pc kernel: [42661.258709] usb 1-1.2: new
> high-speed USB device number 15 using ehci_hcd
> Jan 26 23:36:12 stille-pc kernel: [42661.356334] usb 1-1.2: New USB
> device found, idVendor=04a9, idProduct=30fc
> Jan 26 23:36:12 stille-pc kernel: [42661.356338] usb 1-1.2: New USB
> device strings: Mfr=1, Product=2, SerialNumber=0
> Jan 26 23:36:12 stille-pc kernel: [42661.356342] usb 1-1.2: Product:
> Canon Digital Camera
> Jan 26 23:36:12 stille-pc kernel: [42661.356344] usb 1-1.2:
> Manufacturer: Canon Inc.-
>
> so the usual way of mounting
> -mount /dev/sdb1 /media/camera-
> is not available?
You should check the dmesg output to see if a /dev/sdX1 was created. Some things
in dmesg do not appear in /var/log/messages.
First, this is the last time that I will try to decipher the tiny font you use.
You post the mount command you use, but what is failing is any output of it. You should post the prompt, the command, the output including the next prompt. Then everybody can see what happened. Even when there is no output at all, that can be detected.
There are basicaly two ways to mount a storage device. One is for the end-users of a desktop environment. And as you say that several GUI applications can handle the files on it, my interpretation is that there is nothing wrong with the device, or the way that mounting using the desktop environment works.
The second way is doing it through command(s) as root. For that you need to know several things.
the device special file that is created by udev on connection of the device (or at boot). You assume that it is /dev/sdb and that it has a parrtition /dev/sdb1. But this assumption is only based on earlier experience and not on any computer facts. Remark that the giving of filemames like sda, sdb depends on what is connected to the system and in what sequence they are detected. Thus what is today sda can be tomorrow sdb, even when it is not a easily (dis)connectable device. Looking inside the several /dev/disk/by-* directories might be needed to see which device is what:
ls -l /dev/sd*
and
ls -l /dev/disk/by-*
the mount point must me specified and it must exist. You did not prove with computer facts that /media/camera does exist. A
ls -l /media/camerap/code]
would have done that.
BTW I strongly advise you not to create and use mountpoints inside /media yourself. /media is for the mounting as mentioned above in 1) and you may hinder the desktop to do this. Also, because /media is a temporary file system (in RAM) nothing you do there will survive a shutdown.
So please when you want more help in mounting this storage device in the CLI, post the commands above.
> in effect, the /dev/sd[x]1 is not being created, so the question would
> be: why?
That is the only important thing. If the device does not appear, nothing
in kde or gnome will help. No mount command, manual or automatic will
succeed. All the rest is moot.
> so I guess PTP storage mode is in effect available? what would that
> need from the kernel? is there an additional kernel module I should
> load?
It is possible that the camera is only available now in PTP mode. Maybe
the camera can switch from PTP mode to disk mode.
gtkam and gphoto2 probably do understand this protocol, and therefore allow direct access to the content of the camera. (gtkam, however, only deals with pictures, and gphoto2 is command line driven, so I’m not really satisfied with them.)
it still puzzles me, though, that before my current 12.2 opensuse, I was able to mount the memory card as a disk (directly from the camera, so without inserting it into a card reader).
so would there perhaps be a kernel option that offers some simulation of mounting the memory card, and is this option perhaps not selected in the default opensuse kernel?
Which desktop environment are you using. For KDE, Dolphin can access the photo files using the ‘camera:/’ KIO slave. This essentially allows you to manage the photos in the camera like you would with a normal filesystem. USB cameras should be detected automatically, and be reported by the notifier.
> it still puzzles me, though, that before my current 12.2 opensuse, I
> was able to mount the memory card as a disk, (without inserting it into
> a card reader, that is).
That’s probably a desktop feature. Or file browser feature, rather. I
don’t think the kernel is involved there.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Essentially, openSUSE was finding the device but then unmounting it because of a missing dependency, arising from the move to systemd, and an incorrect setting.
(I put in a bug report and it will be addressed in 12.3.)
udev does not seem to be involved, as switching on the camera merely gives:
tail /var/log/messages
Jan 29 21:47:59 stille-pc kernel: 4377.516943] usb 1-1.1: new high-speed USB device number 17 using ehci_hcd
Jan 29 21:47:59 stille-pc kernel: 4377.613912] usb 1-1.1: New USB device found, idVendor=04a9, idProduct=30fc
Jan 29 21:47:59 stille-pc kernel: 4377.613916] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 29 21:47:59 stille-pc kernel: 4377.613919] usb 1-1.1: Product: Canon Digital Camera
Jan 29 21:47:59 stille-pc kernel: 4377.613922] usb 1-1.1: Manufacturer: Canon Inc.
lsusb:
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 005 Device 002: ID 046d:0a0c Logitech, Inc. Clear Chat Comfort USB Headset
Bus 008 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 018: ID 04a9:30fc Canon, Inc. PowerShot A620 (PTP mode)
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
I played around a bit with the udev rules anyway, commenting out everything remotely referring to camera’s, but to no avail
really hard to understand why previously a /dev/sdxx was being created that I was able to mount with
mount /dev/sdb1 (or whatever it was being created as) /some/dir