Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work using the Realtek 8822BE driver

[Bob]

What you expected to happen
For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

What happened instead
Bluetooth does not work

lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04

My custom computer uses an Asus Maximus X Hero Wifi AC motherboard, which uses the Realtek 8822BE driver to cotrol wifi and bluetooth. Support for this driver was added on kernel 4.14, however only wifi works. Bluetooth appears as disabled on the Bluetooth adapters program, but on rfkill it is not blocked, and it is not disabled on the motherboards' settings.

This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: azul 1431 F.... pulseaudio
 /dev/snd/controlC0: azul 1431 F.... pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-08 (18 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-20-generic N/A
 linux-backports-modules-4.15.0-20-generic N/A
 linux-firmware 1.173
StagingDrivers: r8822be
Tags: bionic staging
Uname: Linux 4.15.0-20-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/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: Default string
dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1767180

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.

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Bob (basura1-p)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 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'.

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/v4.17-rc3

[Bob (basura1-p)]

So I tried the latest upstream kernel of 4.16 which at the moment was 4.16.6.Bluetooth still not working at the moment.

[penalvch (penalvch)]

Bob, to confirm this is an upstream issue, could you please test the latest mainline kernel available (4.17-rc5) and advise to the results?

Also, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

[Bob (basura1-p)]

Ok, so I tried to use the most recent kernel (4.17-rc6) and it finally got my bluetooth adapter recognized.

Tried it by pairing my phone, headphones and a ps3 controller on Ubuntu 16.04 & Ubuntu-Mate 18.04. Got my phone working on both, ps3 had trouble pairing, and my headphones worked on Ubuntu 16.04.

[penalvch (penalvch)]

Bob, the next step is to fully reverse commit bisect from kernel 4.16.6 to 4.17-rc6, in order to identify the earliest good kernel commit, preceded immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully reverse commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed.

Thank you for your help.

[Bob (basura1-p)]

Sorry, was super busy and internet here isnt very good. So not really getting the reverse kernel bisection, is it just going from 4.17rc6 to 4.16.6 and seeing when bluetooth started working? Sorry I'm not that good with this sort of stuff.

[penalvch (penalvch)]

Bob:

>"...is it just going from 4.17rc6 to 4.16.6 and seeing when bluetooth started working?"

Yes. To advise, the article https://wiki.ubuntu.com/Kernel/KernelBisection covers this answer precisely, and was written for folks who don't know anything about linux, so it's easy to follow.

[Bob (basura1-p)]

Ok so I tried looking back until I found the last working update. It was kernel version 4.16.12. When I installed 4.16.11 bluetooth appears as disabled and doesn't work.

[Kai-Heng Feng (kaihengfeng)]

So this should be the commit that fixes your issue:

commit 5f534bd8e8de22b75ddce4826af6f861a4b08e43
Author: Larry Finger <email address hidden>
Date: Sun Feb 11 12:24:32 2018 -0600

    Bluetooth: btusb: Add device ID for RTL8822BE

    [ Upstream commit fed03fe7e55b7dc16077f672bd9d7bbe92b3a691 ]

    The Asus Z370-I contains a Realtek RTL8822BE device with an associated
    BT chip using a USB ID of 0b05:185c. This device is added to the driver.

The same patch is already in Bionic's kernel tree and should be released soon.

[Andy Whitcroft (apw)]

This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.