Author Topic: "berry_charge" missing from 2.6.37 kernel?  (Read 623 times)

Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
"berry_charge" missing from 2.6.37 kernel?
« on: March 15, 2011, 06:27:08 AM »
Does anyone know what happened to the berry_charge module in the 2.6.37 kernel?
Quote
[jpaglia@gx620 ~]$ uname -a
Linux gx620.xxx.xxx 2.6.37.2-pclos1.bfs #1 SMP PREEMPT Mon Feb 28 21:20:49 CST 2011 i686 i686 i386 GNU/Linux
[jpaglia@gx620 ~]$ find /lib/modules/ -iname *berry*
/lib/modules/2.6.33.5-pclos1.bfs/kernel/drivers/usb/misc/berry_charge.ko.gz
[jpaglia@gx620 ~]$


Without it, the USB port does not "ramp up" its voltage when charging a Blackberry, resulting in very long charge times.  :(

TIA.

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12662
Re: "berry_charge" missing from 2.6.37 kernel?
« Reply #1 on: March 15, 2011, 11:35:21 AM »
It's gone now... :'( :'( :'(

The Linux kernel configuration item CONFIG_USB_BERRY_CHARGE:

    prompt: USB BlackBerry recharge support
    type: tristate
    depends on: CONFIG_USB
    defined in drivers/usb/misc/Kconfig
    found in Linux Kernels: from 2.6.21 release to 2.6.33 release, thus this is an obsolete configuration
    module created: berry_charge


Thanks to everyone who donates. You keep the servers running.
Follow me on Twitter for the latest development info.

Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
Re: "berry_charge" missing from 2.6.37 kernel?
« Reply #2 on: March 15, 2011, 11:45:07 AM »
 :'( :'( :'(

Any idea what (module or user-space) can be used in its stead?  I've had my Blackberry plugged in for over 5 hours, now, and I'd guess it's gone up less than 25%.  :-\
(...and here, at the office, I'm out of outlet that the stupid, over-sized AC adapter will fit into  >:().

 ???
Thanks.

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12662
Re: "berry_charge" missing from 2.6.37 kernel?
« Reply #3 on: March 15, 2011, 11:54:40 AM »
:'( :'( :'(

Any idea what (module or user-space) can be used in its stead?  I've had my Blackberry plugged in for over 5 hours, now, and I'd guess it's gone up less than 25%.  :-\
(...and here, at the office, I'm out of outlet that the stupid, over-sized AC adapter will fit into  >:().

 ???
Thanks.



I dunno. Nothing is popping up in google.  :'(


Edit: Seems to have something to do with usb auto suspend and needing to turn it off...

[root@localhost ~]# echo -1 >/sys/module/usbcore/parameters/autosuspend


« Last Edit: March 15, 2011, 12:07:10 PM by Texstar »

Thanks to everyone who donates. You keep the servers running.
Follow me on Twitter for the latest development info.

Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
Re: "berry_charge" missing from 2.6.37 kernel?
« Reply #4 on: March 15, 2011, 01:01:31 PM »
:'( :'( :'(

Any idea what (module or user-space) can be used in its stead?  I've had my Blackberry plugged in for over 5 hours, now, and I'd guess it's gone up less than 25%.  :-\
(...and here, at the office, I'm out of outlet that the stupid, over-sized AC adapter will fit into  >:().

 ???
Thanks.



I dunno. Nothing is popping up in google.  :'(


Edit: Seems to have something to do with usb auto suspend and needing to turn it off...

[root@localhost ~]# echo -1 >/sys/module/usbcore/parameters/autosuspend




I'll look into trying that...

...I ran bcharge,
Code: [Select]
[jpaglia@core2pclinux ~]$ bcharge
Scanning for Blackberry devices...
Found device #007...adjusting charge setting...adjusting Pearl mode to dualDetecting possible kernel driver conflict, trying to resolve...

usb_reset failed: No such file or directory
...done
[jpaglia@core2pclinux ~]$
and that seems to up the current, also...looks like it's almost charged, now.  It does some kind of reset, as it makes the BlackBerry re-prompt whether it should enable it's mass-storage option (to allow the internal SD card to be mounted).

The thing is, I have the barry apps from before...not sure if they're still in Synaptic.
... never-mind, just checked another (updated) install, and they're there (but not yet installed).

Just used to be nice and automatic, with the kernel module (even if no user was logged in).

Oh, well...

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12662
Re: "berry_charge" missing from 2.6.37 kernel?
« Reply #5 on: March 15, 2011, 01:16:53 PM »
Saw this.

Equivalently, you could add to /etc/modprobe.conf a line saying:

options usbcore autosuspend=-1


Thanks to everyone who donates. You keep the servers running.
Follow me on Twitter for the latest development info.

Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
Re: "berry_charge" missing from 2.6.37 kernel?
« Reply #6 on: March 15, 2011, 01:44:17 PM »
Saw this.

Equivalently, you could add to /etc/modprobe.conf a line saying:

options usbcore autosuspend=-1




Thanks.  I'll try these...

you made me curious, and I found
Code: [Select]
143 power/autosuspend
144
145 This file contains an integer value, which is the
146 number of seconds the device should remain idle before
147 the kernel will autosuspend it (the idle-delay time).
148 The default is 2.  0 means to autosuspend as soon as
149 the device becomes idle, and negative values mean
150 never to autosuspend.  You can write a number to the
151 file to change the autosuspend idle-delay time.
152
153 Writing "-1" to power/autosuspend and writing "on" to power/control do
154 essentially the same thing -- they both prevent the device from being
155 autosuspended.  Yes, this is a redundancy in the API.

at
http://www.mjmwired.net/kernel/Documentation/usb/power-management.txt

So, at least I know what I'm changing... :)

Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
Re: "berry_charge" missing from 2.6.37 kernel?
« Reply #7 on: March 15, 2011, 01:49:03 PM »
Tried setting it (/sys/module/usbcore/parameters/autosuspend) to "-1", but the "USB charging current is not sufficient" message remains on the BlackBerry's screen (as opposed to disappearing once the current ramps up, as it used to).

Running bcharge clears the message (and resets the port/device, so the "Mass Storage Mode" prompt comes up).

???