summaryrefslogtreecommitdiff
path: root/doc/faq.xml
blob: 3a24f8e589abe4d580c0f52039506141ce8cdf67 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
<?xml version='1.0' ?>

<!-- =================================================================
About this file:

 - It is written in Docbook XML

 - You're best off using an XML editor for this file

 - If you have installed the Docbook XML DTDs properly, 
   you can do syntax checks

 - You can view this file directly using any XML+CSS capable browser. 
   Examples are Mozilla, Galeon, Opera.

 - If you need more information about Docbook and XML, have a look at
   http://docbook.org/ and http://nwalsh.com/

 - We use Tim Waugh's xmlto to process this file within the build
   system, but you're free to use any other adequate processing tool,
   of course :-)

================================================================= -->

<?xml-stylesheet type="text/css" href="docbook-xml.css"?>

<!--
  leave DOCTYPE commented out for easy inclusion as external entity 
-->
<!-- DOCTYPE qandaset PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
  "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" -->

<qandaset>

  <qandaentry>
    <question>
      <simpara>What can I do about the error message "Could not find USB device"?</simpara>
    </question>
    <answer>
      <para>
	The exact error message looks like
      </para>
      <screen>
Could not find USB device (vendor 0x0000, product 0x0000). Make
sure this device is connected to the computer
      </screen>
      <para>
	You have to set up the permissions on your USB device correctly.
	This is described in The gPhoto2 Manual, which is available at

	<ulink url="http://n-dimensional.de/projects/digicam/The_gPhoto2_Manual/">http://n-dimensional.de/projects/digicam/The_gPhoto2_Manual/</ulink>.

	See especially the section "Setting up permissions for USB ports".
      </para>
    </answer>
  </qandaentry>

  <qandaentry>
    <question>
      <simpara>gphoto2 does not find my camera. What shall I do?</simpara>
    </question>
    <answer>
      <para>      
	First try to run "gphoto2 --list-ports" and look whether the ports 
	you want to use are listed there:
      </para>
      <itemizedlist>
	<listitem>
	  <simpara>	
	    For serial devices, the port with the appropriate device must be
	    listed
	  </simpara>
	</listitem>
	<listitem>
	  <simpara>
	    For USB devices, you need the "usb:" port in the list. If you
	    don't see it, check whether you compiled gphoto2 with libusb
	    support.
	  </simpara>
	</listitem>
      </itemizedlist>
      <para>
	Then try to run "gphoto2 --auto-detect" and look whether the camera
	is detected.
      </para>
      <para>
	If your gphoto2 cannot access the USB device as non-root users, you
	have to set up hotplugging correctly. See FIXME for details.
      </para>
      <para>
	AND DO NOT RUN gphoto2 AS ROOT. And no other libgphoto2 frontend either.
      </para>
    </answer>
  </qandaentry>

  <qandaentry>
    <question>
      <simpara>Why do I get the error message "Could not claim the USB device"?</simpara>
    </question>
    <answer>
      <para>
	The exact message looks like
      </para>
      <screen>
*** Error ('Could not claim the USB device') ***

Could not claim interface 0 (Operation not permitted). Make sure no
other program or kernel module (e.g. dc2xx or stv680) is using the 
device and you have read/write access to the device. 
      </screen>
      <para>
	You have to make sure that no such kernel module is loaded and that
	you have set up the permissions on your USB device correctly,
	such that you have (non-root) write access to the camera device.
	How to set this up, is described at FIXME.
      </para>
    </answer>
  </qandaentry>

  <qandaentry>
    <question>
      <simpara>
	Why does my Canon PowerShot G1/Pro 90 IS not work with gphoto2
	when using the AC adapter?
      </simpara>
    </question>
    <answer>
      <para>
	This is a longstanding bug which we cannot fix since none of
	the active gphoto2 developers own one of these cameras. Your
	options are as follows, in descending order of preference:
      </para>  
      <itemizedlist>
	<listitem>
	  <simpara>
	    Fix it and send us a patch.
	  </simpara>
	</listitem>
	<listitem>
	  <simpara>Donate a G1 to one of the active Canon driver
	    developers.</simpara>
	</listitem>
	<listitem>
	  <simpara>Run the camera on battery instead of the AC adapter.</simpara>
	</listitem>
      </itemizedlist>
      <para>
	There is some more info regarding this at
	<ulink url="http://krixor.xy.org/fredrik/gp/canon-g1-ac-problem/">http://krixor.xy.org/fredrik/gp/canon-g1-ac-problem/</ulink>.
	Good luck.
      </para>
    </answer>
  </qandaentry>

  <qandaentry>
    <question>
      <simpara>I've got a serial camera, but gphoto2 doesn't work on SuSE 7.0
   (or greater). You told me that my camera is supported! Fix
	it!</simpara>
    </question>
    <answer>
      <para>
	Cool down, Joe, and listen to the wise words of Linda
	MacPhee-Cobb:
      </para>
      <para>
	<citation>
	  If you are not getting a response from a camera plugged into
	  the serial port, check your /var/log/boot.msg file for the
	  following entry near the end:
	</citation>
	<screen>
	    *This package use the ttyS0 device by default.
	    The installation of this package only makes sense
	    if you use a braille display.
	</screen>
	<citation>
	  This is from blinx, and you will need to turn it off,
	  or better, uninstall it.
	</citation>
      </para>
    </answer>
  </qandaentry>

  <qandaentry>
    <question>
      <simpara>Dudes, Windows is the way to go. How do I compile
	gphoto2 for that environment?</simpara>
    </question>
    <answer>
      <para>
	We don't have the money to buy Windows and something like Visual C.
	Therefore, we can't provide you a gphoto2 for Windows. You have two 
	choices (at least):
      </para>
      <itemizedlist>
	<listitem>
	  <simpara>
	    Buy a fast computer, buy Windows and Visual C and some manuals on
	    how to access USB or serial ports on Windows. Send all that
	    including a blank cheque to us (ask for the address on
	    gphoto-devel@gphoto.org).
	  </simpara>
	</listitem>
	<listitem>
	  <simpara>
	    Try to figure out how to get gphoto2 working on Windows
	    and send us the patches.
	  </simpara>
	</listitem>
      </itemizedlist>
    </answer>
  </qandaentry>

  <qandaentry>
    <question>
      <simpara>I wanna have CVS write access. How do I get one?</simpara>
    </question>
    <answer>
      <simpara>
	We provide CVS write access to persons that show 
	<emphasis>continued</emphasis> interest in a 
	<emphasis>specific part</emphasis>
	of gphoto2. 
	If there is already a person maintaining this 
	specific part of gphoto2 (i.e. a camera driver), we prefer you
	submit patches to the maintainer who will then check them in
	or request modifications.
      </simpara>
    </answer>
  </qandaentry>

  <qandaentry>
    <question>
      <simpara>You took away my CVS write access! What did I do
	wrong?</simpara>
    </question>

    <answer>
      <para>     
	If your name is not listed in gphoto2/MAINTAINERS, and if we
	haven't heard from you lately, we assume that you finished
	your work on gphoto2 and that you don't need write access any
	longer. If this is not the case, please contact one of the
	project admins.
      </para>
    </answer> 
  </qandaentry>

</qandaset>