Blackberry 7730, possibly others don't work in at least Edgy Eft, Gutsy Gibbon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
When I plug in my Blackberry 7730 to either an Efty Eft or a Gutsy Gibbon PC, the following happens in dmesg:
Oct 14 13:20:27 momo kernel: [13131.488000] usb 2-1: new full speed USB device using uhci_hcd and address 2
Oct 14 13:20:28 momo kernel: [13131.672000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:28 momo kernel: [13131.748000] usb 2-1: USB disconnect, address 2
Oct 14 13:20:28 momo kernel: [13132.508000] usb 2-1: new full speed USB device using uhci_hcd and address 3
Oct 14 13:20:29 momo kernel: [13132.700000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:29 momo kernel: [13132.760000] usb 2-1: USB disconnect, address 3
Oct 14 13:20:29 momo kernel: [13133.516000] usb 2-1: new full speed USB device using uhci_hcd and address 4
Oct 14 13:20:30 momo kernel: [13133.696000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:30 momo kernel: [13133.768000] usb 2-1: USB disconnect, address 4
Oct 14 13:20:30 momo kernel: [13134.516000] usb 2-1: new full speed USB device using uhci_hcd and address 5
Oct 14 13:20:31 momo kernel: [13134.700000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:31 momo kernel: [13134.704000] usb 2-1: USB disconnect, address 5
Oct 14 13:20:31 momo kernel: [13135.320000] usb 2-1: new full speed USB device using uhci_hcd and address 6
Oct 14 13:20:31 momo kernel: [13135.504000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:31 momo kernel: [13135.544000] usb 2-1: USB disconnect, address 6
Oct 14 13:20:32 momo kernel: [13136.292000] usb 2-1: new full speed USB device using uhci_hcd and address 7
Oct 14 13:20:32 momo kernel: [13136.480000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:32 momo kernel: [13136.484000] usb 2-1: USB disconnect, address 7
Oct 14 13:20:33 momo kernel: [13137.300000] usb 2-1: new full speed USB device using uhci_hcd and address 8
Oct 14 13:20:33 momo kernel: [13137.480000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:33 momo kernel: [13137.484000] usb 2-1: USB disconnect, address 8
Oct 14 13:20:34 momo kernel: [13138.104000] usb 2-1: new full speed USB device using uhci_hcd and address 9
Oct 14 13:20:34 momo kernel: [13138.284000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:34 momo kernel: [13138.316000] usb 2-1: USB disconnect, address 9
Oct 14 13:20:35 momo kernel: [13139.068000] usb 2-1: new full speed USB device using uhci_hcd and address 10
Oct 14 13:20:35 momo kernel: [13139.260000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:35 momo kernel: [13139.264000] usb 2-1: USB disconnect, address 10
Oct 14 13:20:36 momo kernel: [13140.072000] usb 2-1: new full speed USB device using uhci_hcd and address 11
Oct 14 13:20:36 momo kernel: [13140.256000] usb 2-1: configuration #1 chosen from 1 choice
Oct 14 13:20:36 momo kernel: [13140.260000] usb 2-1: USB disconnect, address 11
Among Blackberry Linux users it is known that such behaviour might be caused by the berry_charge kernel module. Despite many tries to rmmod it, I could not get rid of the continuous connects and disconnects. I discovered then that disabling udevd and _then_ rmmod'ing berry_charge would solve the problem; my quickfix for now is to rename berry_charge.ko but this needs to be addressed in a proper manner. The other distributions I tried this with (Slax and openSUSE namely) got it right, whatever they're doing differently...
I also suggest shipping the Barry software with Ubuntu, or at least including it in some repository. It can be found at http://
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Okay, I take that quickfix back. After reboot it's all the same again. The connect-disconnect cycle can only be stopped by kill'ing udevd, and now btool doesn't report my BB at all anymore :-(