On Fri, Jun 20, 2008 at 03:59:09AM -0700, Peter Gamboa wrote: > Hello, Hi Peter,
> 1) bcharge doesn't run upon plugging in the BB. This is likely due to your Blackberry having one of the new Product ID's. If it is 8004, then the latest CVS should work for you. If it is a different product ID, please let me know. You can check this using "lsusb -v" *before* bcharge runs. > The SD card is mounted automatically. This can cause problems on some of the newer devices. I've tested an 8120 here and if I'm copying files off the card at the same time I use btool to access the database, the device resets itself when the Barry side of the conversation closes its USB handles. I believe this to be a bug in the Blackberry firmware, but I'm still pondering a workaround. So far, the best you can do is remove usb_storage when you want to sync or backup. > the following output when running bcharge for the first time per mount: > Scanning for Blackberry devices... > Found device #048...adjusting charge setting...adjusting Pearl mode to > dualDetecting possible kernel driver conflict, trying to resolve... > > usb_reset failed: could not reset: No such device > ...done Some of these errors are normal, since Pearl devices don't all behave alike. So bcharge adds a slight delay, and the Pearls that reset themselves are gone by the time bcharge tries to reset. This is ok, and you shouldn't see these errors once the udev rules are fixed. > 2) Per the suggestions, I unloaded usb_storage right before running the > sync, and at no time was berry_charge loaded. msynctool hangs during the > sync. Based on the output it seems process all my contacts and resolve > any conflicts, send them to the pearl, and then hang. I've tried wiping > all the data from the BB and the sync seems to add all the contacts, no > calendar events, and no tasks. In addition it duplicates contact entries > that exist in both Evolution and the BB, so it seems to hang after > adding all the contacts but before cleaning up any extras. I've also > tried deleting the sync group and starting a new one from scratch after > failed syncs, but it still seems to hang in the same place. If you wait for 30 to 60 seconds, does the Barry module quit? Or can you wait "forever" and it just sits there? If Barry times out in 30 seconds, I'd like to see the USB traffic. In the Barry plugin configuration, enable the DebugMode setting (just comment it out). This should dump lots of protocol info to the screen as you sync. I need the last couple of screens of hex output when it hangs. If you can wait "forever", then I'm assuming that OpenSync is hanging in its engine somewhere. Can you check the output of 'top' and see if osengine or osplugin is taking CPU? If so, set the environment variable OSYNC_TRACE to an empty directory, and look at the logs to see where they stop. If you want, you can email them to me directly, since they can contain private data. Thanks, - Chris ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
