No bluetooth on kernel 5.9

[nanoone]

On the kernel 5.7:

[bluetooth]# show
Controller 70:66:55:BB:04:B6 (public)
        Name: MTN-Lap
        Alias: MTN-Lap
        Class: 0x00000000
        Powered: no
        Discoverable: yes
        DiscoverableTimeout: 0x00000000
        Pairable: yes
        UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0537
        Discovering: no
        Roles: central
        Roles: peripheral
Advertising Features:
        ActiveInstances: 0x00 (0)
        SupportedInstances: 0x05 (5)
        SupportedIncludes: tx-power
        SupportedIncludes: appearance
        SupportedIncludes: local-name
        SupportedSecondaryChannels: 1M
        SupportedSecondaryChannels: 2M
        SupportedSecondaryChannels: Coded

[cjalba]

Hi,
I have the same issue. Upgraded today: No Bluetooth.

[aerian]

Same issue. So I downgrade to linux 5.8. I think it is kernel problem.

[SLaItEr]

@nanoone

bluetoothctl :

Running 5.9.8-2-MANJARO and tested bluetooth.

> uname -a                                                   
Linux manjarh 5.9.8-2-MANJARO #1 SMP PREEMPT Wed Nov 18 06:38:03 UTC 2020 x86_64 GNU/Linux

> bluetoothctl
Agent registered
[CHG] Controller 00:1A:7D:DA:71:11 Pairable: yes
[bluetooth]# show
Controller 00:1A:7D:DA:71:11 (public)
	Name: my
	Alias: my
	Class: 0x00000000
	Powered: no
	Discoverable: no
	DiscoverableTimeout: 0x000000b4
	Pairable: yes

please check if it is not blocked by the kernel with

rfkill list

when you get an output similar to this

rfkill list           
0: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: yes

try

rfkill unblock bluetooth

It should unblock it

rfkill list             
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

[nanoone]

I guess so
But I didn’t find any bugs about Bluetooth in Bugzilla

[nanoone]

@SLaItEr

rfkill list

The output:

1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

So I guess it’s not blocked

[SLaItEr]

To bad it is not something so simple.

Could you do following.

Open 2 terminals

in the first enter this command.

 sudo btmon --write ~/hcitrace.snoop | tee ~/hcitrace.txt

In the second first do

sudo btmgmt power off

Next

sudo btmgmt power on

You should see an output in the first terminal like so

Bluetooth monitor ver 5.55
= Note: Linux version 5.9.8-2-MANJARO (x86_64)                         0.815898
= Note: Bluetooth subsystem version 2.22                               0.815899
= New Index: 00:1A:7D:DA:71:11 (Primary,USB,hci0)               [hci0] 0.815900
= Open Index: 00:1A:7D:DA:71:11                                 [hci0] 0.815900
= Index Info: 00:1A:7D:DA:71:11 (Cambridge Silicon Radio)       [hci0] 0.815901
@ MGMT Open: bluetoothd (privileged) version 1.18             {0x0001} 0.815902
@ MGMT Open: btmgmt (privileged) version 1.18                {0x0002} 15.454724
@ MGMT Command: Set Powered (0x0005) plen 1           {0x0002} [hci0] 15.454769
        Powered: Disabled (0x00)
< HCI Command: Write Scan Enable (0x03|0x001a) plen 1       #1 [hci0] 15.454807
        Scan enable: No Scans (0x00)
> HCI Event: Command Complete (0x0e) plen 4                 #2 [hci0] 15.566007
      Write Scan Enable (0x03|0x001a) ncmd 1
        Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 7        {0x0002} [hci0] 15.566101
      Set Powered (0x0005) plen 4
        Status: Success (0x00)
        Current settings: 0x00000ac0
          Secure Simple Pairing
          BR/EDR
          Low Energy
          Secure Connections

Check if you find something odd or put the output here.

even better is when you also do the same thing with the kernel that works.
Only make sure the first command is a bit different to get 2 separated txt files. So do a

sudo btmon --write ~/hcitrace.snoop | tee ~/hcitrace1.txt

next check if the files differ and in what way with

diff  hcitrace.txt hcitrace1.txt

and put the outcome here

[nanoone]

@SLaItEr

sudo btmgmt power off

I ran sudo btmgmt --index 1 power off
The output:

Set Powered for hci1 failed with status 0x11 (Invalid Index)

[SLaItEr]

that’s not the command I did ask to run. Why with --index 1?
Just do sudo btmgmt power off

[nanoone]

Yes you’re right but that causes the same issue
I added that index because I thought the index of my bluetooth was hci1
Sorry for that
Running sudo btmgmt power off :

Set Powered for hci0 failed with status 0x11 (Invalid Index)

[SLaItEr]

That’s really odd it should not show such an error.

[nanoone]

Exactly!
I created a bugzilla link waiting for an answer
The weird thing is that everything works very well with previous kernels

[SLaItEr]

Oke, but because of the error you got there is one other thing I would like you to try.

open bluetoothctl and give the following command.

[bluetooth]# agent on

does that give you any output.

[nanoone]

@SLaItEr

does that give you any output.

Yes

Agent registered
[bluetooth]# agent on
Agent is already registered

[PhotoJim]

I have the same problem, with all the same symptoms and the same investigative results. I’m on an 8-core Ryzen 7 laptop (Asus Tufbook A17). All was fine in the most recent 5.8 kernel, and the kernels prior to that.

[dial25lx]

I’m experiencing the same problem on kernel 5.9 (also with today’s update). bluetooth works perfectly fine with kernel 5.8, I’m on a HP machine with Ryzen processor and NVIDIA graphics too.

[dial25lx]

Today’s update to the kernel just fixed this issue for me! Thanks!

[nanoone]

Today’s update fixed the issue!!

[Nils]

And mine stopped working

Since 5.8 there are some kernel upgrades that messes with Bluetooth.

Can't find bluetooth devices after reboot/update

Here in the forum there is a bunch of people were having problems with bluetooth when the kernel is changed. In special with the linux58 But when I try to boot on any other kernel from the bootloader Manjaro cannot mount the /home and other locations. So I tried to force it. I fixed it by running sudo mhwd-kernel -i linux57 rmc *rmc will not work if you have dependencies on linux58 *I also recommend you to try a kernel that was working for you before. I found it here. https://wiki.man…