lib: removed virtual inheritance from some ALX parser classes
[barry.git] / doc / www / troubleshooting.php
blob70626d00d470f6091c031d0363a07f4fab58a9f4
1 <? include ("barry.inc"); ?>
3 <? createHeader("Troubleshooting"); ?>
5 <? createSubHeader("Common Issues When Working With Barry"); ?>
8 <p><b>Q:</b> I have one of the newer Pearl devices, such as the 8120.
9 When I try to run a backup using the GUI, the device resets itself.</p>
11 <p><b>A:</b> This is a known problem, and is likely a bug in the
12 Blackberry firmware which gets triggered when both the usb_storage kernel
13 module and Barry access the device at the same time. When Barry closes
14 its USB connection, the device gets confused and resets itself.</p>
16 <p>The only known workaround is to unload the usb_storage module when
17 accessing the database (such as when syncing or doing backups).</p>
20 <hr/>
23 <p><b>Q:</b> When I run btool, it hangs for 30 seconds and then times out on
24 the USB read call.</p>
26 <p><b>A:</b> From reports on the mailing list, this appears most likely to be
27 a bug in the BlackBerry firmware. Sometimes upgrading your
28 Blackberry will fix this issue.</p>
30 <p>This is not conclusive, and may be a kernel issue as well.</p>
32 <p>To verify that you are experiencing the right issue, run
33 "btool -vl" to get a verbose USB log. At the beginning
34 the USB configuration and endpoint information is printed.
35 If the last set of endpoints have 0's in the values, you are
36 experiencing the problem. The proper set of endpoints will not
37 be displayed with "lsusb -v" in this case either.</p>
39 <p>One workaround is to run bcharge twice like this:</p>
41 <pre>
42 bcharge
43 bcharge -o
44 </pre>
46 <p>After the second bcharge, btool should work normally.</p>
49 <hr/>
52 <p><b>Q:</b> I've installed Barry, and bcharge is set to run automatically,
53 but as soon as I plug my device into the USB port, the device reboots.</p>
55 <p><b>A:</b>This is a bug in the udev script, which causes the bcharge program
56 to be run 7 to 10 times back to back. This confuses the BlackBerry
57 enough to reset it. As of 2007/07/28, there is a corrected
58 udev script example in Barry CVS. This corrected script
59 was included in the Barry 0.8 release, and newer versions.</p>
61 <p>Alternative issue: You may have the berry_charge kernel module
62 running, in which case you need to choose which method you wish
63 to use. Do not run both berry_charge and bcharge.</p>
66 <hr/>
69 <p><b>Q:</b> btool is giving me errors, saying it can't find my device, or
70 can't access it!</p>
72 <p><b>A:</b> If you have one of the newer BlackBerry devices, such as the Pearl
73 or the Curve, these devices default to USB Mass Storage mode
74 when you first plug them in. The Linux kernel detects this,
75 and on most systems loads the usb_storage module automatically,
76 sometimes mounting the device as a drive.</p>
78 <p>If you are running an older version of Barry, please upgrade, as
79 this issue has been fixed so usb_storage and database access can
80 coexist in peace.</p>
83 <hr/>
86 <p><b>Q:</b> One of the Barry applications crashed, and now I keep getting
87 a Desktop error message in hex.</p>
89 <p><b>A:</b> If a Barry application crashes, that means the Desktop mode was
90 not shutdown properly. Your device will likely appear to still
91 be "busy" as well. Currently the only way to fix this is to
92 reset the device, either by unplugging/replugging it, or by
93 running the program "breset".</p>
96 <hr/>
99 <p><b>Q:</b> Everytime I restore a backup with the backup GUI, the database
100 I need does not get restored. What gives?</p>
102 <p><b>A:</b> Both the backup and the restore are filtered based on your
103 configuration. Check your Edit | Config... settings and make
104 sure the needed database is turned on in <i>both</i> backup and restore.</p>
107 <hr/>
110 <p><b>Q:</b> I ran the backup, but can't find my backup files!
111 Where did they go?</p>
113 <p><b>A:</b> The backup program saves all backup files as gzip'd tarballs
114 under your home directory: ~/.barry/backup/pin_number/</p>
116 <p> Each backup session creates a new file, named with the
117 pin number, date, and time.</p>