14e4:4365 [Lenovo ThinkPad Edge E135] Bluetooth: can't load firmware, may not work correctly

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

apport-collect 1242079

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.

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

Did this issue occur in a previous version of Ubuntu, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc6-saucy/

I think I'm affected by this too. My machine is a Thinkpad X1 Carbon.
It was working on 12.04 without problems.
I tried the mainline Kernel v3.12-rc6-saucy, it didn't fix it.

Yes - I had the Problem also in Raring (13.04) over all Kernel Updates in this Version.
It is still be present in Saucy after the Update last Weekend

No - I have ot the skill to change the Kernel manually - and this is my production machine...

There are also many entrys in the internet that report's this Bug (see google:
"Ubuntu can't load firmware, may not work correctly" regarding with Broadcom) - but there is no solution!

Please see also Bug #1065400 in Launchpad

After my comment yesterday I remembered I disabled bluetooth on boot via TLP. On 12.04 this worked nice, it was disabled on boot and I could enable it if needed.
Removing the line and rebooting helped, I had a bluetooth icon and I could see my paired devices.
But after turning bluetooth of in the settings I'm not able to reactivate it. (dmesg show "Bluetooth: can't load firmware, may not work correctly" after each try.)

I have exactly the same problem with my Lenovo x230 (ubuntu 13.10) and this bluetooth broadcom device BCM20702A0

0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad].

I have the kernel 3.11.0-13-generic

And after resume/wake the Broadcom device (20702A0) needs to have firmware uploaded every startup/wake/resume. But it doesn't.

Typical log after resume:

[ 1944.459568] usbcore: registered new interface driver btusb
[ 1954.759815] usb 1-1.4: new full-speed USB device number 7 using ehci-pci
[ 1954.857085] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
[ 1954.857093] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1954.857098] usb 1-1.4: Product: BCM20702A0
[ 1954.857101] usb 1-1.4: Manufacturer: Broadcom Corp
[ 1954.857105] usb 1-1.4: SerialNumber: 689423EB8FC0
[ 1954.860964] Bluetooth: can't load firmware, may not work correctly

And given that the driver is loaded, but not the firmware, I see bt working but i never ever respond...

How I can ensure that the firmware is reloaded each time ?

Hi,
I have Ubuntu 13.10 in dell vostro laptop, unable to search for Bluetooth device. Below mentioned some logs....

command:- lsusb
logs:-
deepak@deepak-Vostro-1450:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 064e:8122 Suyin Corp.
Bus 001 Device 004: ID 0a5c:21d7 Broadcom Corp. BCM43142 Bluetooth 4.0
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

command:- dmesg|grep -i bluetooth
logs:-
deepak@deepak-Vostro-1450:~$ dmesg|grep -i bluetooth
[ 16.728440] Bluetooth: Core ver 2.16
[ 16.728469] Bluetooth: HCI device and connection manager initialized
[ 16.728479] Bluetooth: HCI socket layer initialized
[ 16.728484] Bluetooth: L2CAP socket layer initialized
[ 16.728491] Bluetooth: SCO socket layer initialized
[ 16.732109] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 16.732112] Bluetooth: BNEP filters: protocol multicast
[ 16.732121] Bluetooth: BNEP socket layer initialized
[ 16.733233] Bluetooth: RFCOMM TTY layer initialized
[ 16.733242] Bluetooth: RFCOMM socket layer initialized
[ 16.733244] Bluetooth: RFCOMM ver 1.11
[ 61.795518] Bluetooth: can't load firmware, may not work correctly
[ 8384.128955] Bluetooth: can't load firmware, may not work correctly
[ 8470.762579] Bluetooth: Failed to start inquiry: status 18
[ 8499.274918] Bluetooth: Failed to start inquiry: status 18
[ 8504.509804] Bluetooth: Failed to start inquiry: status 18

command:- sudo tail -f /var/log/syslog
logs:-
deepak@deepak-Vostro-1450:~$ sudo tail -f /var/log/syslog
[sudo] password for deepak:
Dec 28 17:27:12 deepak-Vostro-1450 mtp-probe: bus: 1, device: 4 was not an MTP device
Dec 28 17:27:13 deepak-Vostro-1450 kernel: [ 2829.194201] usbcore: registered new interface driver btusb
Dec 28 17:27:13 deepak-Vostro-1450 kernel: [ 2829.200659] Bluetooth: can't load firmware, may not work correctly
Dec 28 17:27:15 deepak-Vostro-1450 kernel: [ 2831.204790] Bluetooth: hci0 command 0x1003 tx timeout
Dec 28 17:27:15 deepak-Vostro-1450 bluetoothd[691]: Unknown command complete for opcode 19
Dec 28 17:27:15 deepak-Vostro-1450 bluetoothd[691]: Adapter /org/bluez/691/hci0 has been enabled
Dec 28 17:27:30 deepak-Vostro-1450 bluetoothd[691]: Discovery session 0x7f3ff6170bd0 with :1.95 activated
Dec 28 17:27:41 deepak-Vostro-1450 bluetoothd[691]: Stopping discovery
Dec 28 17:28:41 deepak-Vostro-1450 dbus[651]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper)
Dec 28 17:28:41 deepak-Vostro-1450 dbus[651]: [system] Successfully activated service 'org.freedesktop.hostname1'
Dec 28 17:39:02 deepak-Vostro-1450 bluetoothd[691]: Discovery session 0x7f3ff6170bd0 with :1.95 activated
Dec 28 17:39:13 deepak-Vostro-1450 bluetoothd[691]: Stopping discovery

I investigated this bug today and discovered two things.
If i boot with Kernel 3.8.0-35 (latest raring Kernel) I do not encounter this bug.

For Saucy I found a workaround and some kind of a fix.
Workaround:
I can enable bluetooth from a shell using "sudo rfkill unblock bluetooth"
http://askubuntu.com/a/369844/173286

Fix:
Follow these instruktions: http://askubuntu.com/a/370386/173286
This works for me as long as I use the On/Off switch from the indicator. If I switch it On using Bluetooth in Systemsettings it still switches back to Off.

"sudo rfkill unblock bluetooth" works for me - thanks!

This is also happening for me:

frapell@padme:~$ dmesg |grep -i bluet
[ 12.692409] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 12.760442] Bluetooth: Core ver 2.16
[ 12.760469] Bluetooth: HCI device and connection manager initialized
[ 12.760477] Bluetooth: HCI socket layer initialized
[ 12.760479] Bluetooth: L2CAP socket layer initialized
[ 12.760489] Bluetooth: SCO socket layer initialized
[ 12.778260] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 12.778265] Bluetooth: BNEP filters: protocol multicast
[ 12.778274] Bluetooth: BNEP socket layer initialized
[ 12.801231] Bluetooth: RFCOMM TTY layer initialized
[ 12.801245] Bluetooth: RFCOMM socket layer initialized
[ 12.801247] Bluetooth: RFCOMM ver 1.11
[ 13.119271] Bluetooth: can't load firmware, may not work correctly

frapell@padme:~$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
        Soft blocked: no
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

syslog output when I try to initiate discovery:

Apr 2 13:09:46 padme bluetoothd[807]: Discovery session 0x7f63e6177e90 with :1.57 activated
Apr 2 13:09:46 padme bluetoothd[807]: hci0: Start Discovery (0x0023) failed: Not Powered (0x0f)

lsusb:

Bus 001 Device 004: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]

Computer is a Thinkpad X1 Carbon

frapell@padme:~$ uname -a
Linux padme 3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 13.10, was working fine in previous versions of Ubuntu

"sudo rfkill unblock bluetooth" does nothing for me

I'm affected too. This is my "dmesg" log:

[ 6511.928736] usb 3-2: new full-speed USB device number 13 using xhci_hcd
[ 6511.948071] usb 3-2: New USB device found, idVendor=0a5c, idProduct=21e8
[ 6511.948083] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6511.948089] usb 3-2: Product: BCM20702A0
[ 6511.948094] usb 3-2: Manufacturer: Broadcom Corp
[ 6511.948098] usb 3-2: SerialNumber: 00190E124F47
[ 6511.952833] Bluetooth: can't load firmware, may not work correctly

"sudo rfkill unblock bluetooth" did nothing for me. I also reinstalled "gnome-bluetooth" and nothing happened.

Bug is still marked as "Incomplete" but no more info is requested and still remains "Unassigned".

I own a Targus USB dongle and I found this bug marked as "Expired":

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1155845

I marked it as a Duplicate of this current bug (not branded).

As you can see in the other bug comments, bluetooth worked in previous kernel versions (3.9.0-030900rc3-generic). Something went wrong with ubuntu 13.11.

Thank you in advance and, please, request more info in order to help to solve the problem.

Sorry, there is more info:

juanca@mobility:~$ uname -r
3.11.0-18-generic

juanca@mobility:~$ lsusb | grep -i bluetooth
Bus 003 Device 013: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0

Juan Carlos Fernández, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

The Problem still exists in 14.04 Trusty Thar after upgrade yesterday.

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

I confirm this bug no longer affects me after upgrading to 14.04

Bluetooth works perfect again

ref: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242079/comments/25

I have updated my BIOS to 2.53 now

This does not change anything to the Bluetooth-Problem

Output from Command-Line above:

georg@ThinkPad-Edge-E135:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for georg:
HMET93WW (2.53 )
07/11/2013

is there a link to launchpad #1065400 ??

Georg Graf, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.15-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

I tried linux-image-3.15.0-031500rc2-generic_3.15.0-031500rc2.201404201435_amd64 from the link/description above

I'm not sure if I did it right

System is booting up, but with this Kernel there is NO WiFi/WLAN and NO Bluetooth-Indicator in Status bar.
So I can't really test the Bluetooth-Issue...

but:
dmesg|grep -i bluetooth shows NOT the "can't load Firmware..." Message - does it help?

I have not set any tags

Tip: My Problem looks exactly like this:
http://askubuntu.com/questions/395937/ubuntu-13-10-broadcom-43142-not-finding-bluetooth-devices

Linked to Launchpad #1264311

BCM43142 is also inside my Edge 135

Georg Graf, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc5-utopic/ and advise to the results?

I tried linux-image-3.15.0-031500rc5-generic_3.15.0-031500rc5.201405091635_amd64

but sorry: This kernel does not boot on my system. - Screen is dimming slowly to whole white screen in a early boot phase - system screwed up (OMG!)

no testing is possible. Kernel immediately removed....

Georg Graf, did this problem not occur in a release prior to 13.04?

can't say - 13.04 was the initial OS on this PC after buy

I don't think this is a kernel issue - It looks like Launchpad #1264311

OK, much closer to Target now!

according to last post in Launchpad #1264311 I installed:

http://wielki.tk/vostro/debs/bt-bcm43142-onereic_0.0+20111116somerville2_amd64.deb
http://wielki.tk/vostro/debs/bt-reload-module-after-resume-oneiric_0.1_all.deb

then copy /lib/firmware/BCM43142A0_001.001.011.0028.0036.hcd to /lib/firmware/fw-105b_e065.hcd and reboot

result:
dmesg|grep -i bluetooth shows
...
[ 21.591578] Bluetooth: firmware loaded (!!!)
...
Search for new BT divices shows my Telephone - sec-code is shown on Computer and telephone, but paring fails finaly :(

who can help?

Georg Graf, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

OK, I get it work now. The 14.04 kernel is missing the firmware for the bluetooth hardware.

I have downloaded the firmware, renamed and copied it appropriately and now bluetooth is working:

wget http://wielki.tk/vostro/debs/bt-bcm43142-onereic_0.0+20111116somerville2_amd64.deb

dpkg-deb -x bt-bcm43142-onereic_0.0+20111116somerville2_amd64.deb bt-bcm43142

sudo cp bt-bcm43142/lib/firmware/BCM43142A0_001.001.011.0028.0036.hcd /lib/firmware/fw-105b_e065.hcd

sudo rmmod btusb

sudo modprobe btusb

Claus' fix worked for me too on my Lenovo Z50

xrayA4T, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

I got the same problem, the workarounds described here didn't work for me. I've filed a new bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1406014 with ubuntu-bug linux because I don't know another way to include all this nifty system information.

I have a Dell Inspiron 11 3148, had the same problem, and the workaround fixed it.