[Blackberry Curve 8310] Sometimes does not detect partition

[Jonathan]

Binary package hint: devicekit-disks

When plugged in, my system detects my Blackberry 8310 smartphone in lsusb as "Bus 007 Device 005: ID 0fca:0004 Research In Motion, Ltd." but does not always mount the file system. The device is set to present itself as a mass storage device, but usually doesn't show up in Device Notifier when plugged in, even though it can be seen in lsusb.
I am running Kubuntu Karmic Koala, and trying to fill the device with music using the Banshee media player. The device only shows up in Banshee once the system has mounted it, for obvious reasons.

ProblemType: Bug
Architecture: amd64
CustomUdevRuleFiles: 10-vboxdrv.rules
DKDisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
Date: Thu Jan 14 09:44:10 2010
DistroRelease: Ubuntu 9.10
HotplugNewDevices: /dev/sde1 /dev/sde
HotplugNewMounts:

InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: devicekit-disks 007-2ubuntu4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=/dev/sdc1 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: devicekit-disks
Symptom: storage
Uname: Linux 2.6.31-17-generic x86_64
dmi.bios.date: 03/09/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/09/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Martin Pitt (pitti)]

Looks alright from udev/dk-disks point of view. Please

  * remove the Blackberry
  * open a Terminal, do "gvfs-mount -oi"
  * plug in the Blackberry, and wait until output has settled
  * copy&paste the entire output of gvfs-mount

[Jonathan (jonfritz)]

jon@THEGIBSON:~$ gvfs-mount -oi
Monitoring events. Press Ctrl+C to quit.
Drive connected: 'RIM Blackberry SD'
  Drive(0): RIM Blackberry SD
    Type: GProxyDrive (GProxyVolumeMonitorGdu)
    ids:
     unix-device: '/dev/sde'
    themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
    is_media_removable=1
    has_media=1
    is_media_check_automatic=1
    can_poll_for_media=1
    can_eject=1
    can_start=0
    can_stop=1
    start_stop_type=shutdown
    Volume(0): BLACKBERRY
      Type: GProxyVolume (GProxyVolumeMonitorGdu)
      ids:
       uuid: '0124-E9DB'
       unix-device: '/dev/sde1'
       label: 'BLACKBERRY'
      themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
      can_mount=1
      can_eject=1
      should_automount=1

Volume added: 'BLACKBERRY'
  Volume(0): BLACKBERRY
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '0124-E9DB'
     unix-device: '/dev/sde1'
     label: 'BLACKBERRY'
    themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
    can_mount=1
    can_eject=1
    should_automount=1
^C

In that particular instance, the Blackberry was properly detected by the system, and appeared in my Device Notifier as soon as I plugged it in.

[Martin Pitt (pitti)]

That looks fine. Can you please get another output when it's not running? (Just keep plugging it in, umount, pull out, restart the monitor so that you know where the relevant output started). Thanks!

[Jonathan (jonfritz)]

jon@THEGIBSON:~$ gvfs-mount -oi
Monitoring events. Press Ctrl+C to quit.
Drive connected: 'RIM Blackberry SD'
  Drive(0): RIM Blackberry SD
    Type: GProxyDrive (GProxyVolumeMonitorGdu)
    ids:
     unix-device: '/dev/sdd'
    themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
    is_media_removable=1
    has_media=0
    is_media_check_automatic=1
    can_poll_for_media=1
    can_eject=0
    can_start=0
    can_stop=1
    start_stop_type=shutdown
^C

That's an example of the blackberry being plugged in, but this time, Device Notifier did not pick it up.

[Martin Pitt (pitti)]

OK, in order to figure out what's wrong I think I need simultaneous logs from all three. Please remove the blackberry, open a Terminal, and copy&paste the following commands into it:

  gvfs-mount -oi > /tmp/gvfs.log 2>&1 &
  devkit-disks --monitor-detail > /tmp/dkd.log 2>&1 &
  udevadm monitor -e --udev >/tmp/udev.log 2>&1 &

Then plug it in, wait 10 s, and check if the bug happened.

  - If so: please close the terminal, and attach /tmp/gvfs.log, /tmp/dkd.log, and /tmp/udev.log here.
  - If not: close the terminal, reopen one, and start over.

Thanks!

[Martin Pitt (pitti)]

Oh, and after it reproduced the bug, please attach /var/log/kern.log. Thanks!

[Jonathan (jonfritz)]

Hope that helps. Thanks again for your attention on this.

[Martin Pitt (pitti)]

Thanks. So the dmesg shows that the kernel does not detect partitions on that device in the case when it fails:

Feb 23 19:07:22 THEGIBSON kernel: [83339.675258] usb-storage: device found at 3
Feb 23 19:07:22 THEGIBSON kernel: [83339.675261] usb-storage: waiting for device to settle before scanning
Feb 23 19:07:27 THEGIBSON kernel: [83344.671222] usb-storage: device scan complete
Feb 23 19:07:27 THEGIBSON kernel: [83344.674204] scsi 11:0:0:0: Direct-Access RIM Blackberry SD 0001 PQ: 0 ANSI: 4 CCS
Feb 23 19:07:27 THEGIBSON kernel: [83344.674655] sd 11:0:0:0: Attached scsi generic sg4 type 0
Feb 23 19:07:27 THEGIBSON kernel: [83344.689501] sd 11:0:0:0: [sdd] Attached SCSI removable disk

Reassigning to kernel.

[scnaifeh (scnaifeh)]

I've got the same issue with a Blackberry Bold 9700, also on Karmic. I see an icon for the blackberry in Nautilus, but it doesn't seem to have mounted, and it won't open. Kern.log attached. Other logs coming.

[scnaifeh (scnaifeh)]

gvfs.log

[scnaifeh (scnaifeh)]

dkd.log

[scnaifeh (scnaifeh)]

udev.log

[Jeremy Foshee (jeremyfoshee)]

Hi Jonathan,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 507510

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Carl Moss (carl-moss-me)]

Just to say that I have the same problem with a BlackBerry 9700 in both karmic and lucid. I've never been able to recognise the SD partitions, even though everything works fine with my older BB 9000.

[Carl Fink (carl-finknetwork)]

Possible data point: with my BlackBerry Bold 9700, it was detected exactly ONCE, after I ran an XP VM win VirtualBox (PUEL), passed USB through, and mounted the device in Windows XP. When I shut down the XP VM, Ubuntu detected the device and mounted it normally. After unplugging, though, it doesn't get detected on replugging, and I can't reproduce this now. I can continue to mount it in the XP VM, but I hate starting Windows up just to copy some files to a device.

Suggestion--it might be this problem: http://ubuntuforums.org/showthread.php?t=1366021

I can't try the fix suggested there since 10.0.4 doesn't have the files and directories mentioned in the article.

[Carl Fink (carl-finknetwork)]

And now that I say I can't reproduce it, it just happened again. I started the Win XP VM, mounted the BB, copied 200+ megs of MP3 files to the MicroSD card, and when I unmounted the device in Windows, Ubuntu immediately mounted it as /dev/sdb1 (using udev).

[Carl Fink (carl-finknetwork)]

Additional data--as an experiment I set up a Debian VM in VirtualBox. Debian instantly sees the device as /dev/sdb. And once I disconnect it from Debian, Ubuntu can then see it and mount it. The problem seems to be Ubuntu-specific, and some action other operating systems take would appear to put it in a mode which can then be detected by udev. (I'm not developer, I'm just speculating.)

No developer has commented on this since April. Any chance of a fix?

[zx5000 (jpowell-ipipes)]

I have the same problem with my Curve 8900. The first time it mounts like a charm then afterwards nothing until a reboot.

This phone works every time in Fedora 11 and WinXP.

2.6.32-24-generic

Here's a relevant portion of dmesg output.

[ 127.720016] usb 1-4: new high speed USB device using ehci_hcd and address 4
[ 127.852959] usb 1-4: configuration #1 chosen from 1 choice
[ 129.064019] usb 1-4: reset high speed USB device using ehci_hcd and address 4
[ 129.325972] Initializing USB Mass Storage driver...
[ 129.326281] scsi6 : SCSI emulation for USB Mass Storage devices
[ 129.326464] usbcore: registered new interface driver usb-storage
[ 129.326468] USB Mass Storage support registered.
[ 129.328103] usb-storage: device found at 4
[ 129.328107] usb-storage: waiting for device to settle before scanning
[ 134.328160] usb-storage: device scan complete
[ 134.329515] scsi 6:0:0:0: Direct-Access RIM BlackBerry SD 0002 PQ: 0 ANSI: 0 CCS
[ 134.330011] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 134.331625] sd 6:0:0:0: [sdb] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB)
[ 134.332120] sd 6:0:0:0: [sdb] Write Protect is off
[ 134.332124] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 134.332127] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 134.334111] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 134.334116] sdb: sdb1
[ 134.343112] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 134.343117] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 246.419773] usb 1-4: USB disconnect, address 4
[ 295.340017] usb 1-4: new high speed USB device using ehci_hcd and address 5
[ 295.472989] usb 1-4: configuration #1 chosen from 1 choice
[ 295.479943] scsi7 : SCSI emulation for USB Mass Storage devices
[ 295.480138] usb-storage: device found at 5
[ 295.480141] usb-storage: waiting for device to settle before scanning
[ 295.556704] usb 1-4: usbfs: interface 1 claimed by usb-storage while 'bcharge' sets config #1
[ 296.676018] usb 1-4: reset high speed USB device using ehci_hcd and address 5

[zx5000 (jpowell-ipipes)]

I also can allow VBox XP claim the device the after releasing it Lucid puts it in the taskbar.

[Carl Fink (carl-finknetwork)]

Since I actually need to use the BlackBerry, I just removed Ubuntu from my netbook and installed Debian Squeeze, which instantly detects the phone.

I gather no developers are interested. Oh, well.

[Diego (diego-for-launchpad)]

I have just checked with a new BB 9700 and it mounts OK under Ubuntu 9.10. I am connecting it through a D-Link USB hub with external power supply.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Mark Rose (markrose)]

I also have this bug.

My Blackberry 8330 is detected after rebooting, but not subsequently.

LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid

2.6.32-24-generic

gvfs-mount -oi > /tmp/gvfs.log 2>&1
produces an empty log

udisks --monitor-detail > /tmp/dkd.log 2>&1
produces an empty log

udevadm monitor -e --udev > /tmp/udev.log 2>&1
produced the attached log

[Carl Fink (carl-finknetwork)]

OK, found a fix, at least for my box.

I uninstalled barry-utils. Apparently berrycharge was changing some setting on the phone, perhaps incorrectly detecting it as a Pearl (which requires a mode change to be charged by a computer). Removing berrycharge means the phone is instantly detected by the system. It remains *unstable* and can't be mounted, but that's also true with this particular phone on other operating systems--I think the phone is borked.

Perhaps other people experiencing the problem could test this?

[zx5000 (jpowell-ipipes)]

I switched to iPhone. My bb curve started flip-flopping between handset
and headset during calls. The iPhone works flawlessly. RIM better wake
up before they're buried by the competition.

On 11/07/2010 08:39 AM, Carl Fink wrote:
> OK, found a fix, at least for my box.
>
> I uninstalled barry-utils. Apparently berrycharge was changing some
> setting on the phone, perhaps incorrectly detecting it as a Pearl (which
> requires a mode change to be charged by a computer). Removing
> berrycharge means the phone is instantly detected by the system. It
> remains *unstable* and can't be mounted, but that's also true with this
> particular phone on other operating systems--I think the phone is
> borked.
>
> Perhaps other people experiencing the problem could test this?
>

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]