BlackBerry Forums Support Community

vostok4 · 04-01-2008, 12:21 PM

I used to have my BB setup perfectly in linux, I would connect it, and I would be able to see my MicroSD card mounted in linux no problem and then grab my photos from there etc, but as of late that has just stopped working.

I have it charging, btool -l lists it:

Code:

Device ID: 0x9f84ee8. PIN: 204faa76, Description: RIM 8100 Series Colour GPRS Handheld

But it won't mount... anyone have any ideas what kernel module is used to mount it in the FS?

rivviepop · 04-04-2008, 10:35 AM

The kernel module is usb_storage (which has a bunch of other dependencies) - I just applied the latest updates to everything last night (there was a new kernel), and this morning plugged in my 8320 and it's charging fine and the SD card mounted (I wanted to get a pic off it). This is using the stock 'berry_charge' kernel module though, not any part of the Barry project.

Try stopping all Barry components from running, then plug in your BB and look at /var/log/messages - do you see a bunch of chatter about the SD/USB Mass Storage being found? Start with a basic "is it plugged in" test with nothing more than the stock kernel and go from there, worry about Barry later (just to take it one step at a time).

vostok4 · 04-16-2008, 02:44 PM

Hey, thanks for the reply, here is what happens when I'm connecting:

Code:

Apr 16 15:39:22 mafiu kernel: usb 4-1: new full speed USB device using uhci_hcd and address 8
Apr 16 15:39:22 mafiu kernel: usb 4-1: configuration #1 chosen from 1 choice

So what should I test next?

EDIT: Here is some output from btool, lsusb and bidentify:

Code:

[root@mafiu ~]# lsusb
Bus 001 Device 001: ID 0000:0000  
Bus 005 Device 006: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 005 Device 001: ID 0000:0000  
Bus 004 Device 010: ID 0fca:0001 Research In Motion, Ltd. Blackberry Handheld
Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 005: ID 046d:c518 Logitech, Inc. MX610 Laser Cordless Mouse
Bus 002 Device 001: ID 0000:0000

Code:

[root@mafiu ~]# btool -l
Blackberry devices found:
Device ID: 0xa033e58. PIN: 204faa76, Description: RIM 8100 Series Colour GPRS Handheld

Code:

[root@mafiu ~]# bidentify -v
usb_set_debug: Setting debugging level to 9 (on)
usb_os_init: Found USB VFS at /dev/bus/usb
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 001
usb_os_find_devices: Found 006 on 005
usb_os_find_devices: Found 001 on 005
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 010 on 004
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 005 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
device_desc loaded
bLength: 18
bDescriptorType: 1
bcdUSB: 272
bDeviceClass: 255
bDeviceSubClass: 255
bDeviceProtocol: 255
bMaxPacketSize0: 16
idVendor: 4042
idProduct: 1
bcdDevice: 262
iManufacturer: 1
iProduct: 2
iSerialNumber: 0
bNumConfigurations: 1

  config_desc #0 loaded
bLength: 9
bDescriptorType: 2
wTotalLength: 74
bNumInterfaces: 1
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 128
MaxPower: 250

    interface_desc #0 loaded
bLength: 9
bDescriptorType: 4
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 8
bInterfaceClass: 255
bInterfaceSubClass: 1
bInterfaceProtocol: 255
iInterface: 2

      endpoint_desc #0 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 129
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 129
        pair.read = 129
        pair.type = 2
      endpoint_desc #1 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 2
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 2
        pair.write = 2
        pair.type = 2
        pair added! (read: 129,write: 2,type: 2)
      endpoint_desc #2 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 131
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 131
        pair.read = 131
        pair.type = 2
      endpoint_desc #3 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 4
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 4
        pair.write = 4
        pair.type = 2
        pair added! (read: 131,write: 4,type: 2)
      endpoint_desc #4 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 133
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 133
        pair.read = 133
        pair.type = 2
      endpoint_desc #5 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 6
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 6
        pair.write = 6
        pair.type = 2
        pair added! (read: 133,write: 6,type: 2)
      endpoint_desc #6 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 135
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 135
        pair.read = 135
        pair.type = 2
      endpoint_desc #7 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 8
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 8
        pair.write = 8
        pair.type = 2
        pair added! (read: 135,write: 8,type: 2)
    interface added to map with bInterfaceNumber: 0
  config added to map with bConfigurationValue: 1
usb_open(0x9a93760)
usb_claim_interface(0x9a89738,0)
usb_clear_halt(0x9a89738,131)
usb_clear_halt(0x9a89738,4)
BulkWrite to endpoint 4:
    00000000: 00 00 10 00 01 ff 00 00 a8 18 da 8d 6c 02 00 00  ............l...

BulkRead (131):
    00000000: 00 00 10 00 02 ff 00 00 a8 18 da 8d 6c 02 00 00  ............l...

BulkWrite to endpoint 4:
    00000000: 00 00 0c 00 05 ff 00 00 14 00 01 00              ............

Socket::Send: Endpoint 131
Received:
    00000000: 00 00 20 00 06 ff 00 00 14 00 01 00 27 89 e0 0a  .. .........'...
    00000010: 0b ab ce 04 10 39 b9 d0 c3 c3 11 cf f7 a6 55 85  .....9........U.

BulkWrite to endpoint 4:
    00000000: 00 00 0c 00 05 ff 00 01 08 00 04 00              ............

Socket::Send: Endpoint 131
Received:
    00000000: 00 00 14 00 06 ff 00 01 08 00 04 00 03 00 00 00  ................
    00000010: 76 aa 4f 20                                      v.O 

BulkWrite to endpoint 4:
    00000000: 00 00 0c 00 05 ff 00 02 08 00 02 00              ............

Socket::Send: Endpoint 131
Received:
    00000000: 00 00 c4 01 06 ff 00 02 b8 01 02 00 0a 00 04 00  ................
    00000010: b8 01 00 00 01 17 02 05 03 0d 00 84 52 49 4d 20  ............RIM 
    00000020: 38 31 30 30 20 53 65 72 69 65 73 20 43 6f 6c 6f  8100 Series Colo
    00000030: 75 72 20 47 50 52 53 20 48 61 6e 64 68 65 6c 64  ur GPRS Handheld
    00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00000050: 00 00 00 00 00 00 00 00 00 00 00 00 6e 70 61 72  ............npar
    00000060: 74 68 69 62 61 6e 00 00 00 00 00 00 4a 75 6c 20  thiban......Jul 
    00000070: 31 33 20 32 30 30 36 00 00 00 00 00 31 30 3a 32  13 2006.....10:2
    00000080: 37 3a 35 36 00 00 00 00 00 00 00 00 00 01 0f 00  7:56............
    00000090: 00 00 00 00 00 00 00 00 a4 00 00 00 0a 00 00 00  ................
    000000a0: b8 00 00 00 40 00 00 00 02 00 00 00 90 65 00 80  ....@........e..
    000000b0: 01 05 02 c5 03 01 04 03 07 12 ff ff ff ff ff ff  ................
    000000c0: ff ff ff ff 4a 56 be 92 0c 00 01 00 03 0c 00 00  ....JV..........
    000000d0: 00 00 00 80 ff ff 3f 80 03 0c 00 01 00 00 00 d0  ......?.........
    000000e0: ff ff 07 d0 03 0c 01 00 00 00 40 80 ff ff 3f 82  ..........@...?.
    000000f0: 03 0c 01 01 00 00 40 82 ff ff 3f 84 0e 10 00 00  ......@...?.....
    00000100: 00 00 02 80 ff ff 05 80 00 00 01 00 02 08 00 00  ................
    00000110: 00 00 06 80 15 14 00 00 00 00 02 00 ff ff 3d 82  ..............=.
    00000120: 00 00 02 00 00 00 42 80 07 14 00 00 00 00 02 00  ......B.........
    00000130: 00 00 42 82 ff ff 33 84 00 00 02 00 0c 0c 00 00  ..B...3.........
    00000140: 00 00 34 84 ff ff 35 84 05 14 00 00 00 00 02 00  ..4...5.........
    00000150: 00 00 36 84 ff ff 3f 84 00 00 02 00 12 0c 00 00  ..6...?.........
    00000160: 00 00 00 d0 ff ff 07 d0 09 08 00 00 e9 2c ad d8  .............,..
    00000170: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
    00000180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
    00000190: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
    000001a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
    000001b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
    000001c0: ff ff ff ff                                      ....

BulkWrite to endpoint 4:
    00000000: 00 00 0c 00 05 ff 00 03 04 00 05 00              ............

Socket::Send: Endpoint 131
Received:
    00000000: 00 00 0c 00 06 ff 00 03 00 00 00 00              ............

BulkWrite to endpoint 4:
    00000000: 00 00 0c 00 05 ff 00 04 04 00 06 00              ............

Socket::Send: Endpoint 131
Received:
    00000000: 00 00 10 00 06 ff 00 04 04 00 06 00 00 01 00 00  ................

BulkWrite to endpoint 4:
    00000000: 00 00 0c 00 05 ff 00 05 04 00 07 00              ............

Socket::Send: Endpoint 131
Received:
    00000000: 00 00 10 00 06 ff 00 05 04 00 07 00 00 02 00 00  ................

BulkWrite to endpoint 4:
    00000000: 00 00 0c 00 05 ff 00 06 04 00 08 00              ............

Socket::Send: Endpoint 131
Received:
    00000000: 00 00 0c 00 06 ff 00 06 00 00 00 00              ............

Using ReadEndpoint: 131
      WriteEndpoint: 4
usb_release_interface(0x9a89738,0)
usb_close(0x9a89738)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 001
usb_os_find_devices: Found 006 on 005
usb_os_find_devices: Found 001 on 005
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 010 on 004
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 005 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
204faa76, RIM 8100 Series Colour GPRS Handheld

rivviepop · 04-16-2008, 05:34 PM

Have you checked your BlackBerry to make sure that the SD card is being shown? Options -> Media Card -> Mass Storage Mode Support: On

Your first entry (again, stop with the btool junk - that is confusing you and getting in the way) shows that the device is being plugged in but not "showing" the SD card to the PC. Here's how it's supposed to look - notice my first two lines are the same as yours but then are followed by the SD card:

Code:

Apr 16 15:04:44 boomstick kernel: usb 3-1: new full speed USB device using uhci_
hcd and address 3
Apr 16 15:04:44 boomstick kernel: usb 3-1: configuration #1 chosen from 1 choice
Apr 16 15:04:44 boomstick kernel: scsi3 : SCSI emulation for USB Mass Storage de
vices
Apr 16 15:04:49 boomstick kernel: scsi 3:0:0:0: Direct-Access     RIM      Black
Berry SD    0001 PQ: 0 ANSI: 4 CCS
Apr 16 15:04:49 boomstick kernel: sd 3:0:0:0: [sdb] 3970048 512-byte hardware se
ctors (2033 MB)

... etc. more junk ...

The fact that you're not seeing that info like mine points to the device not "showing" the SD card to the PC, or your PC not loading the proper usb_storage module.

If you plug it in, then as root run 'modprobe usb_storage' - does it work?

vostok4 · 04-16-2008, 05:43 PM

Sorry about the btool stuff, forgot that we aren't interested in that. My blackberry does have the Mass Storage Mode Support On, it is set to Auto Enable when connected, and there is no encryption set on the card.

I have tried to run modprobe usb_storage, but that didn't do anything after unplugging-replugging the device.

Let me try in Windows to ensure that its either the OS or the Pearl.

rivviepop · 04-16-2008, 05:50 PM

Quote:

Originally Posted by vostok4

Let me try in Windows to ensure that its either the OS or the Pearl.

yup! my next suggestion so we can narrow down exactly where the problem is a little further. I've read here and there on the forum up people's devices just stop working in this regard, but I've never experienced it myself.

vostok4 · 04-17-2008, 12:30 AM

So I didn't manage to test it on Windows yet, however my friend brought over his 8100 and it worked perfectly right when plugged in. I have no idea what it is, but I now know its Pearl specific.

Hm, this wouldn't be the first time a Pearl has just stopped functioning in some respect, my previous one stopped allowing me to use the Pearl as an actual button. I've tried toggling every setting and reconnecting in the Media Card page, to no avail.

Thanks for the help though!

rivviepop · 04-17-2008, 11:37 AM

Have you tried physically removing the card, gently cleaning the contacts (use a clean pencil eraser, works great) then reseating it all inside the device?

vostok4 · 04-17-2008, 06:19 PM

Yep, tried that out when I realized it was my pearl. What's weird is in the pearl, I can use the card fine (for photos etc), and bluetooth them to my laptop. At least that still works.

BlackBerry Forums Support Community

Barry Doesn't Automount on F8 Anymore