Broadcom bluetooth device BCM20702A0 [0489:e031] not supported

[Christophe H]

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

[Brad Figg (brad-figg)]

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.

[Jesse Sung (wenchien)]

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

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

apport information

[Christophe H (chrissc-humbert)]

Hello Jesse,

I have done the command you wanted

Kind Regards

[Christophe H (chrissc-humbert)]

And I have still no adapters found

[Christophe H (chrissc-humbert)]

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)]

@Christophe,

What's the output when running these commands?

[Jesse Sung (wenchien)]

@Christophe,

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

[Christophe H (chrissc-humbert)]

@Jesse

No ouput of the commands

[Jesse Sung (wenchien)]

@Christophe,

Do you have windows installed on the machine?

[Christophe H (chrissc-humbert)]

@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)]

@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)]

@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)]

@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)]

@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)]

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

[Christophe H (chrissc-humbert)]

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)]

Hello Jesse,

Is there something that can be done to move forward.

Regards

[Jesse Sung (wenchien)]

Hi Christophe,

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

[Jeremy Kerr (jk-ozlabs)]

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.

[Mike R (mike-fusebuilder)]

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)]

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?

[Mike R (mike-fusebuilder)]

Hi Jesse, thanks for the link, I'll look at it as soon as I can to see if it's something my meager intelligence can handle. Regarding the ID of my Bluetooth device, here is the output from usb-devices:

Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a5c ProdID=21e3 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=9439E5C8450A
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)

Thanks again for all your help on this issue,
Mike

[Christophe H (chrissc-humbert)]

Hello Guys,

it seems that good news are on their way...see https://bbs.archlinux.org/viewtopic.php?pid=1041396

Hope it will make it in the repo soon

Chris

[Christophe H (chrissc-humbert)]

Hello Jesse,

It seems that the meber laloch has somne questions on its firmware laoding in luez..maybe you can contact him and hive him some advice..it would speed up the process
https://bbs.archlinux.org/viewtopic.php?pid=1041396

Thanks a lot
Chris

[James M. Leddy (jm-leddy)]

Hi Christophe,

Jesse's on vacation at the moment, but you'll be pleased to know we are aware of the problem and are working on a fix.

[Christophe H (chrissc-humbert)]

Hello James

It is good to hear...nevertheless the guy on the archlinux forum has a working solution so it may save time to contact him and work with him.

BTW do you think the fix will make it in the 12.04 version?

Thanks

Chris

[James M. Leddy (jm-leddy)]

The solution from archlinux isn't complete enough to work upstream, we're still engineering a complete solution. I think it will make 12.04 but I can't promise that it will.

[Christophe H (chrissc-humbert)]

Hello James,

Ah ok...If you need some help....I am quite newbie but I think I can handle some tests :)

Thanks
Chris

[Mike R (mike-fusebuilder)]

Hi Guys,

This morning I tried to get my Bluetooth to turn on, using the same scripts I was using before and i got an error "/sys/bus/usb/drivers/btusb/new_id: No such file or directory" I did some digging and sure enough, there is no btusb folder in drivers. I then did some more digging, and typing 'btusb' in Synaptic Package Manager shows zero listings, like it was uninstalled and the package has been removed. If Ubuntu has a new method for managing Bluetooth devices, is there a way to apply the manual script I've been using to it? I'm now back to having no notifier icon in the tray :(

Mike

[Anthony Wong (anthonywong)]

Hi Mike, try 'sudo modprobe btusb', perhaps your btusb kernel module was not loaded for some reason, and so there's no /sys/bus/usb/drivers/btusb.

[Christophe H (chrissc-humbert)]

Hello James/Jesse,

How are the progress? Anything to be tested that I can help with?

Thanks
Chris

[Jesse Sung (wenchien)]

Hi Chris,

Still working on it... Will post some test kernels here once I get something working.

Thank you. :)

[Pep (teleki-farkas-peter)]

Hi,

I'm a new subscriber to this bug.

The following bug seems to be a duplication of this one:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863051

My notebook type:
Sony VPCEH

# lsusb
tells this about my bluetooth device:
0489:e027 Foxconn / Hon Hai

In Jesse we trust... :)

Regards!

[Jesse Sung (wenchien)]

Hi Pep,

Please attach the output of usb-devices of 0489:e027, thank you.

[Pep (teleki-farkas-peter)]

Hi Jesse!

Here you are:

T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0489 ProdID=e027 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

If any further info needed please let me know!

Thanks!

[Christophe H (chrissc-humbert)]

Hello,

Just a question... is this ok in 12.04 beta 1?

Thanks

[Anthony Wong (anthonywong)]

Christophe, it's still a work in progress, so it's still not working yet in 12.04 beta1.

[Jesse Sung (wenchien)]

Hi Pep,

It seems that this one (0489:e027) is not a BCM20702A0 device as 0489:e031?

[Pep (teleki-farkas-peter)]

Oh damned, you're right!

I was inattentive... I think I've just lost hope... I'm trying to find another discussion that is about my problem.

Good luck for you! ;-)

[Christophe H (chrissc-humbert)]

@Anthony,

Ok thanks

Keep up the good work

[bakytn (bakytn)]

It is great to know that it's in progress!!! Thank YOU!!!! Hopefully we'll have drivers soon!

[alextoind (alextoind)]

Same problem here...

T: Bus=02 Lev=02 Prnt=02 Port=03 Cnt=04 Dev#= 6 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=9439E5D05C01
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)

[Christophe H (chrissc-humbert)]

Hello Anthony,Jesse,

As next version is due to be out this Thursday, any chance it will be on board?

Thansk a lot for the effort put in already

[Christophe H (chrissc-humbert)]

Hello,

Just for people following. Not yet in 12.04

[bakytn (bakytn)]

Do you need any help from us? it's the first time I am lacking of drivers for Linux for any device...

[James M. Leddy (jm-leddy)]

Sorry for the delay. Needless to say, this is taking much longer than expected. But I'd like to let everyone know that we are still working on getting a solution here.

[Christophe H (chrissc-humbert)]

Hello James,

Anyway we can help/give a hand

Thanks

[Mike R (mike-fusebuilder)]

Hi James/Christophe,

Just a quick note to tell you that I've got some progress on my computer at least. I have a HP Pavilion G6, just upgraded to Ubuntu 12.04. Now the Bluetooth icon shows for me immediately during bootup, w00t!

Now I only need to run the bcmfwup.py routine to get the telephony to work through it. Maybe one day in the future that will be unnecessary too!

Keep up the great work,
Mike

[Christophe H (chrissc-humbert)]

Hello Mike,

Good for you, but I am in 12.04 since the General Release and Bluetooth card is still not recognized...so maybe it is just on Kubuntu
that does not work

Bye

[Cryptoanarchist (cryptoanarchist)]

Hi,

I've got Dell Inspiron N5520 with 14e4:4365 wireless device. It's Broadcom BCM43142 hybrid chip if I understood correctly. It was recognized by preinstalled Ubuntu 11.10, but did't manage to connect to my wireless router. I did clean install of 12.04, and now it isn't even recognized. I tried every method from Ubuntu wiki (including ndiswrapper), and neither worked for me.

Came here from Bug #921911, is this the right place to follow for updates?

Thanks.

[Marcus Weber (ich-marcusweber)]

On my Fujitsu SH 531 i have got it working: Copied the Firmware files from the Windows Driver to /lib/firmware and put the following to a local startup script:
modprobe btusb
echo "0489 e027" >> /sys/bus/usb/drivers/btusb/new_id

[Christophe H (chrissc-humbert)]

Hello Marcus,

Yes I know the different workarounds but what I would like is a definitive solution

Kind Regards
Chris

[Marcus Weber (ich-marcusweber)]

I wanted to point out that, in my case, this problem is a mix of two problems:

1. the device is not recognized correctly - therefore btusb does not get loaded.
2. btusb once loaded, i was not able to connect to any bt-device, unless i either rebooted from windows, or fired up my Windows Virtualbox.

[Thomas Hotz (thotz-deactivatedaccount)]

Hello, I have just bought a Dell Vostro 3560 (with Ivy Bridge Chipset) and having the same problem.

[Ahmad Jawad (ahmad-jawad)]

Hello Marcus and Christophe,

I am a newbie and stuck in the same issue as pointed in #69. Can you kindly point to the solution/workaround. I can see the following files in windows 7 (64 bit) installation.

bcmihvsrv64.dll
bcmihvui64.dll
BCMWL664.SYS
bcmwlcoi.dll
vwifibus.sys

Which files should I copy to /lib/firmware?

[Marcus Weber (ich-marcusweber)]

@Ahmad
None of those !
In my Driver Package were the following files, cause i don't know which firmware exactly fits my Card i copied them all.

BCM20702A0_001.001.024.0023.0040.hex
BCM20702A0_001.001.024.0023.0055.hex
BCM20702A0_001.001.024.0023.0051.hex
BCM20702A0_001.001.024.0023.0063.hex
BCM20702A0_001.001.024.0023.0052.hex
BCM20702A0_001.001.024.0023.0065.hex

[Anthony Wong (anthonywong)]

@Marcus
Copying the *.hex firmware files over to /lib/firmware should not be able to help, as there is not yet a mechanism exists to load them. But adding your device ID to /sys/bus/usb/drivers/btusb/new_id is the pre-requisite to make it work, and the fact that you have boot to windows as you said in #72 has the side-effect of loading the bluetooth firmware.

[Rafał Miłecki (zajec5)]

We can see what 14e4:4365 actually is if someone help me.

Please try the following:
 modprobe bcma
 echo "14e4 4365" > /sys/bus/pci/drivers/bcma-pci-bridge/new_id
 dmesg | grep bcma
 rmmod bcma
 modprobe ssb
 echo "14e4 4365" > /sys/bus/pci/drivers/b43-pci-bridge/new_id
 dmesg | grep ssb

and provide output you get in console.

[b3niup (b3niup)]

bcma:
  [ 114.076431] bcma: Found chip with id 0xA886, rev 0x01 and package
  0x08
  [ 114.076474] bcma: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev
  0x28, class 0x0)
  [ 114.076505] bcma: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812,
  rev 0x21, class 0x0)
  [ 114.076577] bcma: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x16,
  class 0x0)
  [ 114.076660] bcma: Core 3 found: UNKNOWN (manuf 0x43B, id 0x368, rev
  0x00, class 0x0)
  [ 114.076778] bcma: PLL init unknown for device 0xA886
  [ 114.077710] bcma: PMU resource config unknown for device 0xA886
  [ 114.078832] bcma: PMU switch/regulators init unknown for device
  0xA886
  [ 114.080054] bcma: Workarounds unknown for device 0xA886
  [ 114.105257] bcma: Using fallback SPROM failed (err -2)
  [ 114.105262] bcma: No SPROM available
  [ 114.106026] bcma: Bus registered

ssb:
  [ 205.523615] ssb: PCI-ID not in fallback list
  [ 205.524423] ssb: Found chip with id 0x0000, rev 0x01 and package 0x00
  [ 205.524426] ssb: CHIPID not in nrcores fallback list
  [ 205.525388] ssb: Core 0 found: UNKNOWN (cc 0x8FF, rev 0x7F, vendor
  0xFFFF)
  [ 205.541168] ssb: WARNING: Using fallback SPROM failed (err -2)
  [ 205.541173] ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
  [ 205.541176] ssb: Unsupported SPROM revision 0 detected. Will extract
  v1
  [ 205.556856] ssb: Sonics Silicon Backplane found on PCI device
  0000:02:00.0

[Rafał Miłecki (zajec5)]

Thanks to b3niup we have full info about the hardware now. Broadcom cards differs by PHY and radio.

In case of 14e4:4365 BCM43142:
* PHY is LCN40 (revision 3)
* RADIO is 0xA065 (revision 0)

Unfortunately there are not specs for LCN40 available, b43 doesn't support (just like brcmsmac).

I'm not sure if we can have hopes in Broadcom (brcmsmac driver [0]). They are planning to add more N-PHY support for almost two years and they still didn't release (planned) HT-PHY support. Not sure if LCN40 is on their internal TODO at all.

I also don't think anyone is working on specs [1] right now and I won't be able to add support for LCN40 without them.

[0] http://wireless.kernel.org/en/users/Drivers/brcm80211
[1] http://bcm-v4.sipsolutions.net/

[Kazimierz Uromski (kazimierzuromski)]

Will 6.20.55.19 broadcom-sta dkms module package help in this process? This is the package added to Ubuntu 11.10 64bit on my Vostro 3460:
http://semprefidelis.pl/wireless-bcm43142-oneiric-dkms_6.20.55.19~bdcom0602.0400.1000.0400-0somerville1_amd64.deb

All packages are here: http://wielki.tk/vostro-3460-debs.7z , but as I found out wlan is a real problem.

[Kazimierz Uromski (kazimierzuromski)]

Forgot to write: this 6.20.55.19 wl module supports 14e4:4365 wlan.
This package does not work with 3.2+ kernels (only 3.0), but maybe some small changes will bring 4365 support to 12.04+ ubuntu?

In the "all packages" archive there are also some packages for bluetooth part.

[mauribera (maurizio-szn)]

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 1879 F.... pulseaudio
CRDA:
 country IT:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
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

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

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

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[mauribera (maurizio-szn)]

apport information

[bakytn (bakytn)]

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

[Christophe H (chrissc-humbert)]

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)]

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

[bakytn (bakytn)]

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)]

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)]

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.

[Christophe H (chrissc-humbert)]

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

[Thilo Cestonaro (tephraim)]

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

This prevents the adapter to work properly.