Ubuntu

Broadcom bluetooth device BCM20702A0 [0489:e031] not supported

Reported by Christophe H on 2011-09-30
166
This bug affects 28 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Canonical Kernel Team

Bug Description

The broadcom USB bluetooth device "BCM20702A0" (appearing as FoxConn Hon Hai) (vendor:device ids 0489:e031) does not match any drivers' probe functions, as there is no suitable USB device ID match in the kernel.

here the output of usb-devices

Bus=02 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0489 ProdID=e031 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=C0F8DAB42725
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

I am available for more information and you can refer to https://answers.launchpad.net/ubuntu/+question/164787
for more information

Thanks a lot
(opened on the Jesse Sung advice)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 16328 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xe2720000 irq 49'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,10cf1100,00100100 HDA:80862805,80860101,00100000'
   Controls : 18
   Simple ctrls : 10
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=e03c321b-1e66-4d5a-a33e-a31bd5e6b7b3
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
MachineType: FUJITSU LIFEBOOK S761
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB
 LANG=en_GB.UTF-8
 LC_MESSAGES=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-11-generic-pae root=UUID=044e2213-889f-4194-9e22-f23ef30be935 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic-pae 2.6.38.8
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-11-generic-pae N/A
 linux-backports-modules-2.6.38-11-generic-pae N/A
 linux-firmware 1.52
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: natty
Uname: Linux 2.6.38-11-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 04/27/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.14
dmi.board.name: FJNB225
dmi.board.vendor: FUJITSU
dmi.board.version: B1
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: LIFEBOOK S761
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.14:bd04/27/2011:svnFUJITSU:pnLIFEBOOKS761:pvr10601115935:rvnFUJITSU:rnFJNB225:rvrB1:cvnFUJITSU:ct10:cvrLIFEBOOKS761:
dmi.product.name: LIFEBOOK S761
dmi.product.version: 10601115935
dmi.sys.vendor: FUJITSU

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 863051

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
assignee: nobody → Jesse Sung (wenchien)
status: Incomplete → Confirmed
Jesse Sung (wenchien) wrote :

Hi @Christophe,

Could you try this and see if bluetooth works?

open a terminal and run following commands:
sudo -i
modprobe -r bluetooth
modprobe btusb
echo "413c 8197" >> /sys/bus/usb/drivers/btusb/new_id
modprobe bluetooth

apport information

tags: added: apport-collected natty
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
importance: Undecided → Medium
Christophe H (chrissc-humbert) wrote :

Hello Jesse,

I have done the command you wanted

Kind Regards

Christophe H (chrissc-humbert) wrote :

And I have still no adapters found

Christophe H (chrissc-humbert) wrote :

Hello Jesse,

I have changed a bit your command to echo "0489 e031" >> /sys/bus/usb/drivers/btusb/new_id matching my hardware information and no the bluetooth adapter is recognised :) but I am not able to discover any devices....

Kind Regards
Christophe

Jesse Sung (wenchien) wrote :

@Christophe,

What's the output when running these commands?

Jesse Sung (wenchien) wrote :

@Christophe,

Ah... right... should be "0489 e031" instead.

Christophe H (chrissc-humbert) wrote :

@Jesse

No ouput of the commands

Jesse Sung (wenchien) wrote :

@Christophe,

Do you have windows installed on the machine?

Christophe H (chrissc-humbert) wrote :

@Jesse,

Hello,

So I have restarted my laptop and I have again no adapters found....
Otherwise, I have a virtualbox installed with Windows 7....

Kind Regards

Jesse Sung (wenchien) wrote :

@Christophe,

It's a temporary way to verify if btusb works with this adaptor. Need to run the commands again every time the machine is reboot.

Could you try following methods and let me know if each one has a working adaptor and can connect to a device?

test 1:
* power off
* power on and boot into ubuntu
* run above commands
* Is there an adaptor found? If yes, can it connect to a device?

test 2:
* power off
* power on and boot into windows
* Is there an adaptor found? If yes, can it connect to a device?

test 3:
* power off
* power on and boot into windows
* reboot into ubuntu
* Is there an adaptor found? If yes, can it connect to a device?

Thank you!

Christophe H (chrissc-humbert) wrote :

@Jesse,

To complete all tests I need to install windows in dual boot.....It will take some time as my windows for the moment is only running in VirtualBox...
Test1:
Adaptor Found and not able to connect to a device

See you..

Jesse Sung (wenchien) wrote :

@Christophe,

Let's modify the tests:

test 2:
* power off, and then power up and boot into ubuntu
* run virtualbox and windows
* Set bt device directly connected to windows through virtualbox's USB settings
* In windows, is there an adaptor found? If yes, can it connect to a device?

test 3:
* after running test 2, turn virtualbox off
* run above commands
* Is there an adaptor found? If yes, can it connect to a device?

Christophe H (chrissc-humbert) wrote :

@Jesse
Test 2: In windows the adaptor is found but it can not connect to a device

Test3
Adaptor is found and yes U can connect to my smartphone and was able to send a file through...

Jesse Sung (wenchien) wrote :

humm... looks like a firmware issue...

Christophe H (chrissc-humbert) wrote :

Hello Jesse,

Yes it is. I have contacted someone @broadcom already some week ago to know if they would consider releasing an opensource firmware for linux but ....

Is there anything doable in the meantime?

Regards

Christophe H (chrissc-humbert) wrote :

Hello Jesse,

Is there something that can be done to move forward.

Regards

Jesse Sung (wenchien) wrote :

Hi Christophe,

If it is a firmware issue, I'm afraid that there's nothing we could do currently IMHO... :(

Jeremy Kerr (jk-ozlabs) wrote :

Reassigning to kernel-team - there doesn't seem to be much we can do ourselves on this issue, without hardware. We'll keep an eye out for firmware updates though.

Changed in linux (Ubuntu):
assignee: Jesse Sung (wenchien) → Canonical Kernel Team (canonical-kernel-team)
Mike R (mike-fusebuilder) wrote :

Hi Jesse,

Is there a way to make the temporary insert of the device ID permanent? After following these commands I get the bluetooth notifier and I can pair with my headset, but can't get sound through to it. Would like to try the headset again with bluetooth enabled out of the gate.

TIA

Jesse Sung (wenchien) wrote :

Hi Mike,

Need to patch kernel source and then build it into kernel packages. You may want to take a look at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/854399
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

By the way, what's the ID of your device?

tags: added: blocks-hwcert-enablement
Changed in linux (Ubuntu):
status: Confirmed → In Progress
51 comments hidden view all 131 comments

apport information

tags: added: precise running-unity staging

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: maurizio 2027 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xe2720000 irq 50'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,10cf1100,00100100 HDA:80862805,80860101,00100000'
   Controls : 30
   Simple ctrls : 12
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=905cbb82-436d-4759-a688-30c6379b2000
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: FUJITSU LIFEBOOK P771
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=b3863535-fc4e-4ada-9cc9-0a1f2c3f1407 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-29-generic N/A
 linux-backports-modules-3.2.0-29-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
StagingDrivers: rts_pstor mei
Tags: precise running-unity staging
Uname: Linux 3.2.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/08/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.13
dmi.board.name: FJNB22A
dmi.board.vendor: FUJITSU
dmi.board.version: K5
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: LIFEBOOK P771
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd03/08/2012:svnFUJITSU:pnLIFEBOOKP771:pvr10601409513:rvnFUJITSU:rnFJNB22A:rvrK5:cvnFUJITSU:ct10:cvrLIFEBOOKP771:
dmi.product.name: LIFEBOOK P771
dmi.product.version: 10601409513
dmi.sys.vendor: FUJITSU

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

bakytn (bakytn) wrote :

Just upgraded to Quantal Quetzal Beta which has Linux 3.5.0.15 kernel version. Still no support for this bluetooth adapter.

Hello Bakytn,

hope you are fine

It is coming soon it seens see discussion here http://marc.info/?l=linux-bluetooth&m=134704995714896&w=2

Kind Regards

bakytn (bakytn) wrote :

The patch seems applied about 2 weeks ago. I hope with the next kernel they will ship it ;) Thanks!

bakytn (bakytn) wrote :

I have just upgraded to the new kernel (with the new dist-upgrade)

Kernel version: 3.5.0-17-generic

Now this BT adapter is at least visible!

But it's useless i.e. system says I have bt adapter and I can turn on/off it. But I can't communicate with other devices in any way.

Jesse Sung (wenchien) wrote :

Although the rule of binding this device to btusb is in quantal and precise proposed, firmware loading is still not supported currently. The work for supporting firmware loading is tracked at https://launchpad.net/bugs/1065400 .

bakytn (bakytn) wrote :

I performed some actions above.

I have loaded to VirtualBox with Windows 7 guest. I was able to work with my BT adaptor.
Then I just shut it down and closed VirtualBox.
From linux I am able to send/receive files and pair devices.

So I guess the only issue is to load firmware from the start.

Thanks!

P.S: had problems with Apple Magic Mouse though, but that's another story.

Hello I confirmed that the bluetooth chipset is now recognized with official 12.10 release.....next step is https://launchpad.net/bugs/1065400

Keep up the good work guys...almost there

Ephraim (thilo) wrote :

In ubuntu 13.04 the firmware isn't uploaded during system startup anymore.

This prevents the adapter to work properly.

Displaying first 40 and last 40 comments. View all 131 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions