I've been trying to catch you on IRC, but haven't had any such luck (I
idle sometimes on freenode in #slackware). This log confirms what you
said about the BlackBerry resetting itself.
Tue Sep 8 14:51:00 2009
Bus 001 Device 064: ID 0fca:8007 Research In Motion, Ltd.
Bus 001 Device 004: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187
Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 045e:0025 Microsoft Corp. IntelliEye Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
0
Tue Sep 8 14:51:00 2009
Bus 001 Device 004: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187
Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 045e:0025 Microsoft Corp. IntelliEye Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
0
Tue Sep 8 14:51:00 2009
Bus 001 Device 065: ID 0fca:8004 Research In Motion, Ltd.
Bus 001 Device 004: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187
Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 045e:0025 Microsoft Corp. IntelliEye Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
This was produced from this snippet of code:
r...@tessai:~# perl -e 'do { print system("lsusb"); print
$/,scalar(localtime(time())),$/;} while(1);' >bb01.txt
This is with the Auto-MSC mode enabled.
Without the Auto-MSC mode enabled, this is the result:
Tue Sep 8 15:02:02 2009
Bus 001 Device 070: ID 0fca:8004 Research In Motion, Ltd.
Bus 001 Device 004: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187
Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 045e:0025 Microsoft Corp. IntelliEye Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
0
Tue Sep 8 15:02:02 2009
Bus 001 Device 004: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187
Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 045e:0025 Microsoft Corp. IntelliEye Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
0
Tue Sep 8 15:02:02 2009
Bus 001 Device 071: ID 0fca:8007 Research In Motion, Ltd.
Bus 001 Device 004: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187
Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 045e:0025 Microsoft Corp. IntelliEye Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
This was produced using the following code:
r...@tessai:~# perl -e 'do { print system("lsusb"); print
$/,scalar(localtime(time())),$/;} while(1);' >bb02.txt
My guess is that the usb_storage driver is doing some magic, and not
allowing the barry routines to detect the phone properly. In both cases,
the phone resets before being detected properly (what BB device
corresponds to 8004?). It's very odd that the detection works in reverse
when the Auto-MSC mode is enabled. I could just add ID 8004 to my udev
rules, but that seems incomplete. I'm curious to know why it's behaving
in that way. I'll have to peer into the code.
Chris Frey wrote:
> On Mon, Aug 24, 2009 at 02:38:24PM -0700, Theodore Charles III wrote:
>
>> I initially downloaded Barry, OpenSync, KitchenSync, and Kontact, and
>> had everything running smoothly. In connecting my 9630 to use the mass
>> storage mode (in order to get to the SD card), I noticed this:
>>
>> r...@tessai:~# lsusb
>> Bus 001 Device 024: ID 0fca:8004 Research In Motion, Ltd.
>>
>> r...@tessai:~# lsusb
>> Bus 001 Device 024: ID 0fca:8004 Research In Motion, Ltd.
>>
>> r...@tessai:~# lsusb
>> Bus 001 Device 025: ID 0fca:8007 Research In Motion, Ltd.
>>
>> r...@tessai:~# lsusb
>> Bus 001 Device 025: ID 0fca:8007 Research In Motion, Ltd.
>>
>> Notice how the device ID changes? When I enable auto-MSC mode, the
>> device id will remain 8004, which kills my udev rules. I'm guessing that
>> there is something in barry that looks for the MSC mode and tells the
>> kernel that the vendor id is 8004. Am I wrong? I haven't tried setting
>> my 9630 to ask on connect for MSC mode. I'll let you know more after I do.
>>
>
> The change in Device number from 024 to 025 means that it reset itself
> somehow. Only bcharge does this normally, but since it looks like your udev
> rules don't match for 8004, then bcharge shouldn't be running.
>
> Perhaps the Blackberry itself resets when the usb_storage module tries to
> make use of the mass storage mode? Does this product ID change happen
> if you comment out all udev rules that call bcharge?
>
> There is nothing in Barry that checks for mass storage endpoints. It
> doesn't really care if they are there are not. Bcharge merely tries
> to reset the device into a mode that charges properly at 500mA, and
> exposes the database USB endpoints, preferrably with both database and
> Mass Storage endpoints available. Mass storage is completely up to
> the kernel.
>
>
>
>
>> BUS=="usb", SUBSYSTEM=="usb_device", ACTION=="add",
>> ATTR{idVendor}=="0fca", ATTR{idProduct}=="8007", SYMLINK+="bb-%k",
>> RUN="/usr/sbin/bcharge -p %p"
>>
>
> It should be safe to duplicate the rules with different product IDs.
> This is what the existing Barry rules do, and if possible, I'd like
> to update them for the 9630, if you can help me test, since I don't have
> such a device.
>
> Once you have something that works, a patch against the existing rules
> would be excellent.
>
> Thanks,
> - Chris
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
--
Theodore Charles III
Network Administrator
Los Angeles Senior High
323-900-2724 / 323-900-2792
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
