[rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[George Hunter]

It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes.

The previous answers listed below suggest the following diagnostics

Bluetooth not working after update
How can I make my bluetooth works on Ubuntu 16.04?
Ubuntu 16.04 bluetooth not working (Dell XPS13)
Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
Bluetooth not working on Ubuntu 16.04 LTS
Bluetooth cannot find any devices
Stuck on a bluetooth problem

The service seems to be running

/home >sudo service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
   Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
     Docs: man:bluetoothd(8)
 Main PID: 790 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─790 /usr/lib/bluetooth/bluetoothd

Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87
Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87
Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset
Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12
Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12
Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset
Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1.
Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1.
Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1.
Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1.

and not blocked

/home >rfkill list
0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

I have edited /etc/bluetooth/main.conf to include

AutoEnable=true

but I noted that the entire file was commented out.

The kernel seems reasonably up to date

 >uname -a
Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out.

 >hcitool dev
Devices:
 hci0 24:0A:64:F5:EE:86

and the output of dmsg is

>dmesg | grep Blue
[ 2.030855] usb 1-1.4: Product: Bluetooth Radio
[ 13.806355] Bluetooth: Core ver 2.22
[ 13.806369] Bluetooth: HCI device and connection manager initialized
[ 13.806372] Bluetooth: HCI socket layer initialized
[ 13.806373] Bluetooth: L2CAP socket layer initialized
[ 13.806377] Bluetooth: SCO socket layer initialized
[ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821
[ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
[ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
[ 13.877382] Bluetooth: hci0: rom_version status=0 version=1
[ 13.877387] Bluetooth: cfg_sz 0, total size 17428
[ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 16.550281] Bluetooth: BNEP filters: protocol multicast
[ 16.550284] Bluetooth: BNEP socket layer initialized
[ 27.868345] Bluetooth: RFCOMM TTY layer initialized
[ 27.868350] Bluetooth: RFCOMM socket layer initialized
[ 27.868354] Bluetooth: RFCOMM ver 1.11

and of lsusb is

>lsusb
Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 13d3:3414 IMC Networks
Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
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

Thanking you in anticipation
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2017-09-06 (145 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830_M11AA-8
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic root=UUID=8520e78a-1bf6-402d-8e84-8fd01b98ffb3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Tags: xenial
Uname: Linux 4.13.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/17/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0704
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CM6330_CM6630_CM6730_CM6830_M11AA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd04/17/2013:svnASUSTeKComputerINC.:pnCM6330_CM6630_CM6730_CM6830_M11AA-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6330_CM6630_CM6730_CM6830_M11AA:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: CM6330_CM6630_CM6730_CM6830_M11AA-8
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 24:0A:64:F5:EE:86 ACL MTU: 820:8 SCO MTU: 255:16
  UP RUNNING PSCAN ISCAN
  RX bytes:1259 acl:0 sco:0 events:131 errors:0
  TX bytes:22606 acl:0 sco:0 commands:131 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2018-01-22T14:27:55.611724

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1745828/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Daniel van Vugt (vanvugt)]

This sounds like it could be a firmware (missing) issue. Please attach full output from 'dmesg', and also run this command to attach more information automatically:

  apport-collect 1745828

[Daniel van Vugt (vanvugt)]

Oh, actually this sounds like bug 1542743. Please also try the workaround mentioned there.

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

apport information

[George Hunter (c-admin-g)]

bug 1542743 takes me into uncharted territory - patching the kernel is well outside my comfort zone. But the fix suggested at #14 does not work (see #35) for the kernel version 4.13 which I believe is the one I have.

[Daniel van Vugt (vanvugt)]

Thanks.

Yes you can ignore bug 1542743 now. I was confused by your mentioning "AR3012" but it turns out you don't have one of them. It was only a diagnostic question you pasted.

I can see that you have a:

  Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

which seems to be loading wifi firmware OK and then not so OK for Bluetooth...

[ 13.648049] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
[ 13.668472] rtl8821ae: Using firmware rtlwifi/rtl8821aefw_29.bin
[ 13.668476] rtl8821ae: Using firmware rtlwifi/rtl8821aefw_wowlan.bin
...
[ 13.702717] bluetooth hci0: Direct firmware load for rtl_bt/rtl8821a_config.bin failed with error -2
[ 13.702719] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin

All the firmware files come from package 'linux-firmware'. The missing file "rtl8821a_config.bin" may be the problem, or may not be...

It's also possible you need a fix in the kernel itself (package 'linux'), which is where the driver is that depends on having firmware preloaded.

Just in case the latest kernel fixes this issue, please try installing one of the newest ones like 4.15 which was released this week:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

[George Hunter (c-admin-g)]

I am not sure how I go about installing the 4.15 kernel
I have used Synaptic package manager to upgrade linux-firmware to 1.157.15 and the kernel to 4.13.0.32.52. Neither fixed the problem, but the kernal produced a second Bluetooth icon on the task bar, with a different drop down menu.

[Daniel van Vugt (vanvugt)]

You can install the kernel by just downloading and installing these three:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201801282230_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500-generic_4.15.0-041500.201801282230_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-image-4.15.0-041500-generic_4.15.0-041500.201801282230_amd64.deb

[George Hunter (c-admin-g)]

I tried downloading these, bur got an errorr 404 - File not Found.

Supposing I had succeeded, how do I install them? Is it just

install <filename>

[Daniel van Vugt (vanvugt)]

You just double-click on them and follow the instructions. If for some reason that doesn't work then you can run 'dpkg -i <filenames>'

Here are some new links that work:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-headers-4.15.1-041501_4.15.1-041501.201802031831_all.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-headers-4.15.1-041501-generic_4.15.1-041501.201802031831_amd64.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-image-4.15.1-041501-generic_4.15.1-041501.201802031831_amd64.deb

[George Hunter (c-admin-g)]

I've now updated to kernel 4.15.1

~ >uname -a
Linux george-CM6330 4.15.1-041501-generic #201802031831 SMP Sat Feb 3 18:32:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

It makes no difference to the symptoms.

[Daniel van Vugt (vanvugt)]

Thanks.

We'll need to try something different to see if this is now a bluez bug rather than a kernel bug.

Please try downloading and just live booting (don't install) Ubuntu 18.04 from here:
  http://cdimages.ubuntu.com/daily-live/current/

If that works then please also try live booking (don't install) 17.10.1 from here:
  https://www.ubuntu.com/download/desktop

Does Bluetooth work properly in either of those live sessions?

[Kai-Heng Feng (kaihengfeng)]

Please attach dmesg under v4.15.1, thanks!

[George Hunter (c-admin-g)]

~ >dmesg>dmesg.txt

[George Hunter (c-admin-g)]

for Daniel
I have now downloaded "Ubuntu 18.04 LTS amd64", which appears on my desktop as a bootable disc. but how do I boot it?

[Daniel van Vugt (vanvugt)]

https://help.ubuntu.com/community/BurningIsoHowto

[Kai-Heng Feng (kaihengfeng)]

If you have, AutoEnable=true, you need to remove the udev rule that turns on HCI devices.

Also, you may need the config file, but I can't find it in upstream linux-firmware:
[ 14.348128] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
....
[ 14.439245] bluetooth hci0: Direct firmware load for rtl_bt/rtl8821a_config.bin failed with error -2

[Daniel van Vugt (vanvugt)]

Yes, same as in comment #20 with kernel 4.13

[Kai-Heng Feng (kaihengfeng)]

Sorry for missing your comment.
Please remove /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules

[George Hunter (c-admin-g)]

#26. I have finally managed to boot Ubuntu 18.04. It makes no difference.

#31. Setting AutoEnable=true makes no difference to the symptoms. If including it in the config file requires subsequent modifications elsewhere, it seems simpler to remove it.

There are four config files in /etc/bluetooth, consisting almost entirely of comments.

/etc/bluetooth >ls
input.conf main.conf network.conf proximity.conf

#33. Done that, no difference. I am proposing to undo it.

[Daniel van Vugt (vanvugt)]

I guess the next step would be to try and find that 'rtl8821a_config.bin'. Although I don't know where to get it. It's certainly missing from the 'linux-firmware' package, which is where I would expect to see it.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

See also bug 1747336, where a closely-related rtl bluetooth chip just got a fix.

[George Hunter (c-admin-g)]

I upgraded linux-firmware/1.157.16 to linux-firmware/1.157.17, which is what I think is neede to fix bug 1747336, but it made no difference.

[Zero (zerofossilfuel)]

Not sure if this is the same problem. Everything was working perfectly until the massive update that came out last night. Now cannot find internal Atheros BT adapter in Blueman-applet. It appears to allow me to enable BT. Lights on but no one home. Linux firmware looks borked.

user@UX32VD:~$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
2: asus-wlan: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: asus-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no

user@UX32VD:~$ dmesg | grep Blue
[ 2.999406] Bluetooth: Core ver 2.21
[ 2.999422] Bluetooth: HCI device and connection manager initialized
[ 2.999425] Bluetooth: HCI socket layer initialized
[ 2.999428] Bluetooth: L2CAP socket layer initialized
[ 2.999434] Bluetooth: SCO socket layer initialized
[ 3.020951] Bluetooth: hci0: don't support firmware rome 0x11020000
[ 3.028458] Bluetooth: hci0: don't support firmware rome 0x11020000
[ 4.600699] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.600704] Bluetooth: BNEP filters: protocol multicast
[ 4.600709] Bluetooth: BNEP socket layer initialized

user@UX32VD:~$ lspci -knn | grep Net -A2; lsusb
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01)
 Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-size Mini PCIe Card [1a56:2003]
 Kernel driver in use: ath9k
 Kernel modules: ath9k
Bus 002 Device 004: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
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 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
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
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Daniel van Vugt (vanvugt)]

There hasn't been a bluez update to 16.04 since last year. And here hasn't been a kernel update to 16.04 since last month; the same goes for linux-firmware.

So I'm not sure what changed for you Zero. Are you using 16.04?

[Zero (zerofossilfuel)]

This is now working again as of Linux-Firmware 1.157.20 received today.

THANK YOU, THANK YOU, THANK YOU!!!

[Daniel van Vugt (vanvugt)]

Yes that was released a few hours ago:
https://launchpad.net/ubuntu/+source/linux-firmware/1.157.20

George: as the original reporter can you confirm that today's update to the 'linux-firmware' package has fixed it?

[George Hunter (c-admin-g)]

I hope that is good news!
How do I install the fix on my system - the link seems to be to source code?

I am very busy at the moment, and may not be able to do much testing
till next week.

On 10/07/18 02:42, Daniel van Vugt wrote:
> Yes that was released a few hours ago:
> https://launchpad.net/ubuntu/+source/linux-firmware/1.157.20
>
> George: as the original reporter can you confirm that today's update to
> the 'linux-firmware' package has fixed it?
>
> ** Changed in: linux-firmware (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: bluez (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: bluez (Ubuntu)
> Status: Incomplete => Invalid
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Invalid
>

--
George Hunter
10A Roome Bay Crescent
Crail Tel [phone]
Fife KY10 3TT Email <email address hidden>
UK

[Daniel van Vugt (vanvugt)]

Just do:

sudo apt update
sudo apt install linux-firmware
sudo apt full-upgrade
sudo reboot

[George Hunter (c-admin-g)]

It is wonderful news! It works - I can now find two devices!
Whether I can work out how to use them is another matter, but as far as I can see the bug is fixed.

Thanks for your efforts.

[Daniel van Vugt (vanvugt)]

Great! Thanks for testing.