I get the same result if I run btool as a regular user or sudo (assume that
would achieve what you mean by running as root?):
[...@zev ~] btool
>
> Blackberry devices found:
>
> No device selected
>
>
Is there something I can do to check how permissions are being assigned via
udev and correct them?
On Wed, Mar 24, 2010 at 7:59 AM, Theodore Charles III <txc5...@lausd.net>wrote:
> Well, your machine is detecting the blackberry. The issue seems to be
> whether or not it's being assigned the proper permissions via udev. Are you
> running btool as root? If your udev rules are not catching it and assigning
> the permissions, btool will only work as root (because root has access to
> all devices).
>
> Sent from my Verizon Wireless BlackBerry
> ------------------------------
> *From: * CzechWonderNine <czechwondern...@gmail.com>
> *Date: *Wed, 24 Mar 2010 07:20:04 +1300
> *To: *<txc5...@lausd.net>; Barry project development discussion<
> barry-devel@lists.sourceforge.net>
> *Subject: *Re: [Barry-devel] Barry 0.16 not finding 8110
>
> Thanks for your response.
>
> I don't use anything like virtualbox or vmware. The box is a basic
> workstation used for surfing (chrome), office apps (open office), graphics
> (inkscape and gimp), and watching tv (as a mythtv client).
>
> My 8110 shows up in lsusb. Here's the relevant output using the -v switch:
>
> Bus 004 Device 003: ID 0fca:0004 Research In Motion, Ltd.
>
> Device Descriptor:
>
> bLength 18
>
> bDescriptorType 1
>
> bcdUSB 1.10
>
> bDeviceClass 0 (Defined at Interface level)
>
> bDeviceSubClass 0
>
> bDeviceProtocol 0
>
> bMaxPacketSize0 16
>
> idVendor 0x0fca Research In Motion, Ltd.
>
> idProduct 0x0004
>
> bcdDevice 1.06
>
> iManufacturer 1 Research In Motion
>
> iProduct 5 RIM Composite Device
>
> iSerial 3 E2BAF2E830535D0C1A97884BBB26D19647A7EC62
>
> bNumConfigurations 1
>
> Configuration Descriptor:
>
> bLength 9
>
> bDescriptorType 2
>
> wTotalLength 69
>
> bNumInterfaces 2
>
> bConfigurationValue 1
>
> iConfiguration 0
>
> bmAttributes 0x80
>
> (Bus Powered)
>
> MaxPower 500mA
>
> Interface Descriptor:
>
> bLength 9
>
> bDescriptorType 4
>
> bInterfaceNumber 0
>
> bAlternateSetting 0
>
> bNumEndpoints 4
>
> bInterfaceClass 255 Vendor Specific Class
>
> bInterfaceSubClass 1
>
> bInterfaceProtocol 255
>
> iInterface 2 BlackBerry Device
>
> Endpoint Descriptor:
>
> bLength 7
>
> bDescriptorType 5
>
> bEndpointAddress 0x81 EP 1 IN
>
> bmAttributes 2
>
> Transfer Type Bulk
>
> Synch Type None
>
> Usage Type Data
>
> wMaxPacketSize 0x0040 1x 64 bytes
>
> bInterval 0
>
> Endpoint Descriptor:
>
> bLength 7
>
> bDescriptorType 5
>
> bEndpointAddress 0x02 EP 2 OUT
>
> bmAttributes 2
>
> Transfer Type Bulk
>
> Synch Type None
>
> Usage Type Data
>
> wMaxPacketSize 0x0040 1x 64 bytes
>
> bInterval 0
>
> Endpoint Descriptor:
>
> bLength 0
>
> bDescriptorType 0
>
> bEndpointAddress 0x00 EP 0 OUT
>
> bmAttributes 0
>
> Transfer Type Control
>
> Synch Type None
>
> Usage Type Data
>
> wMaxPacketSize 0x0000 1x 0 bytes
>
> bInterval 0
>
> Endpoint Descriptor:
>
> bLength 0
>
> bDescriptorType 0
>
> bEndpointAddress 0x00 EP 0 OUT
>
> bmAttributes 0
>
> Transfer Type Control
>
> Synch Type None
>
> Usage Type Data
>
> wMaxPacketSize 0x0000 1x 0 bytes
>
> bInterval 0
>
> Device Status: 0x0000
>
> (Bus Powered)
>
>
> Let me know if any other output would be useful.
>
> On Tue, Mar 23, 2010 at 9:52 PM, Theodore Charles III
> <txc5...@lausd.net>wrote:
>
>> No, do not remove yourself from the plugdev group. Do you use any
>> virtualization programs like virtualbox or vmware? Also, do you have any
>> output from lsusb showing your device connected? Make sure to run lsusb as
>> root. You can add -v for more output, but for now, just seeing your device
>> in the output is ok.
>> Sent from my Verizon Wireless BlackBerry
>>
>> -----Original Message-----
>> From: CzechWonderNine <czechwondern...@gmail.com>
>> Date: Tue, 23 Mar 2010 21:08:58
>> To: Barry project development discussion<
>> barry-devel@lists.sourceforge.net>
>> Subject: Re: [Barry-devel] Barry 0.16 not finding 8110
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Barry-devel mailing list
>> Barry-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/barry-devel
>>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
