i have successfully emerged gphoto2 0.6.2. when entering the kde control center, a digital camera is now listed under the "peripherals" category. Upon opening the Digital Camera application, the application mis-identifies the camera as an Olympus C-2040Z, even though the camera is a C-4040Z. When clicking on the Olympus C-2040Z camera icon, a dialog box is displayed that says, "Unable to initialize camera. Check your port settings and camera connectivity and try again." The details button provides the following additional text: "unsupported operation." Occasionaly, Gphoto2 will correctly identify the camera as an Olympus C-404Z, but I receive the same error messages about being unable to initialize the camera. dmesg output confirms recognition of USB devices by computer. recognition of the camera by the software appears intermittent. sometimes it is reported as a C-4040Z, but it is often reported as a C-2040Z. output of "gphoto2 -L" and "gphoto2 --debug -L" is lengthy, and is posted in the referenced thread at the Gentoo Discussion Forums. Reproducible: Always Steps to Reproduce: 1. Emerge digikam v 0.6.2 2. hook-up Olympus C-4040Z via OEM USB cable 3. Run the digital camera application Actual Results: Failure to initialize camera. Expected Results: camera recognition. gentoo linux # emerge info Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r8 i686) ================================================================= System uname: 2.6.9-gentoo-r8 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Jan 19 2005, 06:19:15)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r3 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS=" -O2 -march=pentium3 -pipe -mtune=pentium3" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS=" -O2 -march=pentium3 -pipe -mtune=pentium3" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig candy ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.netnitco.net http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 X aalib acpi alsa apm arts avi berkdb bitmap-fonts cdr crypt cups encode esd f77 fam flac font-server foomaticdb fortran gdbm gif gphoto2 gpm gtk2hal ide imagemagick imlib ipv6 ithreads java jpeg kde ldap libg++ libwww mad mikmod motif mpeg mysql ncurses nls nptl oggvorbis opengl oss pam pdf pdflib perl png posix pthreads python qt quicktime readline samba sdl slang snmp spell ssl svga tcpd tiff truetype truetype-fonts type1-fonts userlocales xine xinerama xml xml2 xmms xscreensaver xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS, PORTDIR_OVERLAY
Almost all Olympus Mass Storage camers share the same ID for it's mass storage mode.
"Almost all Olympus Mass Storage camers share the same ID for it's mass storage mode." OK, I can accept that. That explains why gphoto recognizes my camera as the wrong model. Presumably, gphoto2 will recognize every Olympus mass storage camera the same way. But I still don't understand why Gphoto2 does not work in any fashion with the camera, or why 50 Olympus cameras (including mine) that all share the same ID in mass storage mode are listed as supported by Gphoto2. Does the fact that almost all Olympus Mass Storage cameras share the same ID in mass storage mode mean that all 50 cameras suffer equally from the same level of non-functionality with gphoto2? A second question -- does gphoto2 support any of these 50 cameras in a mode other than mass storage mode?
Yes. You can do PC based remote capture with almost all the Olympus Mass Storage Devices using a special sequence: (from the Gphoto ML) "open the flash card door, then hold down the OK and quick view (or LCD) button at the same time for a few seconds until a menu appears. Then change the menu from storage -> control."
Thanks for the tip! I can change the status of the camera from Storage <--> Control using the suggested technique. But Gphoto2 still doesn't seem to offer appropriate control for the camera. To be fair, I can successfully query the camera using the command, "gphoto2 -a", which yields the following output: <snip> gentoo ~ # gphoto2 -a Abilities for camera : Olympus C-2040Z Serial port support : yes USB support : yes Transfer speeds supported : : 9600 : 19200 : 38400 : 57600 : 115200 Capture choices : : Image : Preview Configuration support : yes Delete files on camera support : yes File preview (thumbnail) support : yes File upload support : yes </snip> that's the good news. the bad news is that camera control features still do not appear to be working. for example: <snip> gentoo ~ # gphoto2 --capture-preview *** Error *** An error occurred in the io-library ('Unsupported operation'): Camera is supported by USB Storage driver. *** Error (-6: 'Unsupported operation') *** For debugging messages, please use the --debug option. Debugging messages may help finding a solution to your problem. If you intend to send any error or debug messages to the gphoto developer mailing list <gphoto-devel@lists.sourceforge.net>, please run gphoto2 as follows: env LANG=C gphoto2 --debug --capture-preview Please make sure there is sufficient quoting around the arguments. </snip> <snip> gentoo ~ # gphoto2 --summary *** Error *** An error occurred in the io-library ('Unsupported operation'): Camera is supported by USB Storage driver. *** Error (-6: 'Unsupported operation') *** For debugging messages, please use the --debug option. Debugging messages may help finding a solution to your problem. If you intend to send any error or debug messages to the gphoto developer mailing list <gphoto-devel@lists.sourceforge.net>, please run gphoto2 as follows: env LANG=C gphoto2 --debug --summary Please make sure there is sufficient quoting around the arguments. </snip> <snip> gentoo ~ # gphoto2 --capture-preview *** Error *** An error occurred in the io-library ('Unsupported operation'): Camera is supported by USB Storage driver. *** Error (-6: 'Unsupported operation') *** For debugging messages, please use the --debug option. Debugging messages may help finding a solution to your problem. If you intend to send any error or debug messages to the gphoto developer mailing list <gphoto-devel@lists.sourceforge.net>, please run gphoto2 as follows: env LANG=C gphoto2 --debug --capture-preview Please make sure there is sufficient quoting around the arguments. </snip> <snip> gentoo ~ # gphoto2 --interval=5 </snip> no photos were taken, even though no errors were issued. here's another test: <snip> gentoo ~ # gphoto2 --interval=5 --capture-preview *** Error *** An error occurred in the io-library ('Unsupported operation'): Camera is supported by USB Storage driver. *** Error (-6: 'Unsupported operation') *** For debugging messages, please use the --debug option. Debugging messages may help finding a solution to your problem. If you intend to send any error or debug messages to the gphoto developer mailing list <gphoto-devel@lists.sourceforge.net>, please run gphoto2 as follows: env LANG=C gphoto2 --debug --interval=5 --capture-preview Please make sure there is sufficient quoting around the arguments. </snip> so as you can see, its difficult for me to understand how gphoto2 is supposed to work with the camera. the camera mode has been appropriately changed to "Control", and gphoto2 recognizes the camera when issuing the "--abilities" command, but gphoto2 still fails when trying to perform any other command with the camera.
From the Gphoto ML "Try removing the usb-storage module first. It still shows up as usb-storage, but can't be accessed that way. There is currently (AFAIK) no way to unbind a single device from the usb-storage driver."
is this fixed in 2.1.6?
no response. assuming fixed
