[Theodor]

Just got a 8320 and am running Fedora 8. I get the "current is not sufficient..." error.

looking a the output from lsusb -v I see differences in mine and the origanial poster.

mine :idProduct 0x0006
OP: idProduct 0x0004
then i see this in the third post

"For a Pearl and Curve that value is 0x0006 and for 8700 and older it's 0x0001; these are (to my knowledge) the only two idProducts the driver knows about. Is the 8830 a 0x0006 device?"

We might want to add 0x0004 =), so three now

mine: iProduct 4 RIM Mass Storage Device
OP: iProduct 5 RIM Composite Device

and

mine: MaxPower 100mA
OP: MaxPower 500mA

Power seems to be my issue, not sure how to fix it yet, but I am interested to know why the idProduct and iProduct are not the same for myself and the OP given we have the same device and carrier.

[rivviepop]

Originally Posted by Theodor

looking a the output from lsusb -v I see differences in mine and the origanial poster.

mine :idProduct 0x0006
OP: idProduct 0x0004
then i see this in the third post

OK 4 means it's been "triggered" (unlocked? opened?) from the default 6, so *something* is happening. Let me ask if you've verified these:

- you're running the 2.6.23.X kernel (2.6.23.8-63.fc8 e.g.)
- you do not have any barry or bcharge bits installed
- you are plugging directly into your PC and not an external USB hub

The first item has to do with having a new enough berry_charge.ko kernel module, earlier versions did *not* support the 81/83/88xx devices yet. The second is because the bcharge from barry conflicts with the kernel module berry_charge. The last is because there's some sort of bug (there's a ticket in Bugzilla) with using an external USB hub that hasn't been fixed yet.

[Theodor]

Linux black10 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 i686 i386 GNU/Linux

If barry or bcharge are packages, neither are installed.

I have 6 USB ports on the machine, two on the front panel and 4 in the back.

I've tired all of them with the same results. the full output of lsusb -v shows all USB connected devices are MaxPower 100mA. I have a keyboard and mouse connected USB.

[rivviepop]

Hmm. Here's what happens on my Thinkpad (T43, 2 USB ports only) after a fresh reboot and then plugging in the device (I just updated to the same kernel as you):

/var/log/messages

Dec 22 11:48:09 ender kernel: usb 3-2: new full speed USB device using uhci_hcd and address 2
Dec 22 11:48:09 ender kernel: usb 3-2: configuration #1 chosen from 1 choice
Dec 22 11:48:09 ender kernel: usbcore: registered new interface driver berry_charge
Dec 22 11:48:10 ender kernel: Initializing USB Mass Storage driver...
Dec 22 11:48:10 ender kernel: usb 3-2: USB disconnect, address 2
Dec 22 11:48:10 ender kernel: usbcore: registered new interface driver usb-storage
Dec 22 11:48:10 ender kernel: USB Mass Storage support registered.
Dec 22 11:48:10 ender kernel: usb 3-2: new full speed USB device using uhci_hcd and address 3
Dec 22 11:48:11 ender kernel: usb 3-2: configuration #1 chosen from 1 choice
Dec 22 11:48:11 ender kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Dec 22 11:48:11 ender kernel: usb 3-2: USB disconnect, address 3
Dec 22 11:48:11 ender kernel: usb 3-2: new full speed USB device using uhci_hcd and address 4
Dec 22 11:48:11 ender kernel: usb 3-2: configuration #1 chosen from 1 choice
Dec 22 11:48:12 ender kernel: scsi3 : SCSI emulation for USB Mass Storage devices
Dec 22 11:48:17 ender kernel: scsi 3:0:0:0: Direct-Access     RIM      BlackBerry SD    0001 PQ: 0 ANSI: 4 CCS
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] 3970048 512-byte hardware sectors (2033 MB)
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Write Protect is off
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] 3970048 512-byte hardware sectors (2033 MB)
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Write Protect is off
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
Dec 22 11:48:17 ender kernel:  sdb:
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Attached SCSI removable disk
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0
Dec 22 11:48:17 ender gnome-keyring-daemon[2197]: adding removable location: volume_uuid_A0A7_9311 at /media/disk
Dec 22 11:48:17 ender gnome-keyring-daemon[2874]: adding removable location: volume_uuid_A0A7_9311 at /media/disk
Dec 22 11:48:17 ender hald: mounted /dev/sdb on behalf of uid 500

I get nothing in my dmesg, this is the only debugging output I see (without loading modules with debug switches and all that jazz). You see the third line there where it registers the berry_charge module, then the USB Mass Storage line, then the 5th line is the "disconnect" message? That's berry_charge resetting the port to expose the 0x0004 endpoint and increase the charging to 500mA.

Do you see the same pattern on your machine? What differences are there? You can also try using the debug mode of berry_charge; make sure the module is unloaded (rmmod berry_charge) then add to /etc/modprobe.conf the line:

options berry_charge debug=1

You may or may not need to reboot to activate this, I've had mixed results with various modules, some work fine without a reboot but some don't - I'd say reboot just to be safe that you know it's active/working.

There is also another parameter that I see (I ran 'strings' on the module) for "pearl_dual_mode" - setting this may or may not provide some more debugging output, it's a boolean as well. (options berry_charge debug=1 pearl_dual_mode=1)

The strings output:

# strings /lib/modules/2.6.23.9-85.fc8/kernel/drivers/usb/misc/berry_charge.ko 
UWVS
[^_]
<7>%s %s: Power is set to %dmA
<7>%s %s: device is already charging, power is set to %dmA
<7>%s %s: Sending first magic command
<3>%s %s: First magic command failed: %d.
<7>%s %s: Sending second magic command
<3>%s %s: Second magic command failed: %d.
<7>%s %s: Calling set_configuration
<3>%s %s: Set Configuration failed :%d.
<7>%s %s: Sending magic pearl command
<7>%s %s: Magic pearl command returned %d
berry_charge
parm=pearl_dual_mode:Change Blackberry Pearl to run in dual mode
parmtype=pearl_dual_mode:bool
parm=debug:Debug enabled or not
parmtype=debug:bool
author=Greg Kroah-Hartman <gregkh@suse.de>
license=GPL
alias=usb:v0FCAp0004d*dc*dsc*dp*ic*isc*ip*
alias=usb:v0FCAp0006d*dc*dsc*dp*ic*isc*ip*
alias=usb:v0FCAp0001d*dc*dsc*dp*ic*isc*ip*
depends=
vermagic=2.6.23.9-85.fc8 SMP mod_unload 686 4KSTACKS 
pearl_dual_mode
debug
berry_charge

[Theodor]

Thanks for you help on this =)

I get this in messages

Dec 23 20:16:40 black10 kernel: usb 2-2: new full speed USB device using ohci_hcd and address 6
Dec 23 20:16:40 black10 kernel: usb 2-2: configuration #1 chosen from 1 choice
Dec 23 20:16:40 black10 kernel: scsi10 : SCSI emulation for USB Mass Storage devices
Dec 23 20:16:45 black10 kernel: scsi 10:0:0:0: Direct-Access     RIM      BlackBerry SD    0001 PQ: 0 ANSI: 4 CCS
Dec 23 20:16:45 black10 kernel: sd 10:0:0:0: [sdb] Attached SCSI removable disk
Dec 23 20:16:45 black10 kernel: sd 10:0:0:0: Attached scsi generic sg2 type 0
Dec 23 20:21:52 black10 kernel: usb 2-2: USB disconnect, address 6
Dec 23 20:22:06 black10 kernel: usb 2-2: new full speed USB device using ohci_hcd and address 7
Dec 23 20:22:06 black10 kernel: usb 2-2: configuration #1 chosen from 1 choice
Dec 23 20:22:06 black10 kernel: scsi11 : SCSI emulation for USB Mass Storage devices
Dec 23 20:22:11 black10 kernel: scsi 11:0:0:0: Direct-Access     RIM      BlackBerry SD    0001 PQ: 0 ANSI: 4 CCS
Dec 23 20:22:11 black10 kernel: sd 11:0:0:0: [sdb] Attached SCSI removable disk
Dec 23 20:22:11 black10 kernel: sd 11:0:0:0: Attached scsi generic sg2 type 0

Setting the debug gave no further information.

The first thing i see right away is
mine: usb 2-2
yours: usb 3-2

Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] 3970048 512-byte hardware sectors (2033 MB)
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Write Protect is off
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] 3970048 512-byte hardware sectors (2033 MB)
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Write Protect is off
Dec 22 11:48:17 ender kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
Dec 22 11:48:17 ender kernel:  sdb:

I am guessing this is your miniSD

[rivviepop]

Yeah, that 3-2, 2-2 stuff is simply the ID of the specific USB port in question, which bus and all that stuff. Unless we're using the exact same laptop/desktop it'll probably be different.

So in your dmesg output I notice that the messages for the initialization of usbcore, usb_storage and berry_charge are conspicuously missing, it's as if the modules are already loaded or not loading at all. Mainly the most important one is berry_charge, it's as if it's not even loading; if you to a 'lsmod | grep berry" to you see/have/get the module loaded?

If the above answer is no, what happens if you run this command:

modprobe berry_charge debug=1

Does the module load if you manually run that command?

[Theodor]

This feels like "Doh!" moment. The module is there but wasn't loading by default.

Thanks for your help riv

[rivviepop]

Originally Posted by Theodor

This feels like "Doh!" moment. The module is there but wasn't loading by default.

Thanks for your help riv

doh! if it's not automagically loading then I suspect a bug somewhere (like maybe udev isn't seeing the device? a guess only), if you feel like debugging it. At least it works when you manually load it which is half the battle - your not loading problem might be related to the bug where it crashes udev on the PC and reboots the BB when you plug it into an external hub.

It might be time to start searching the Bugzilla for Fedora...

[Theodor]

Had to correct this.

After more trial and error I found my issue to be a user error. The smart card reader daemon wasn't enabled.