No bluetooth on kernel 5.9

Support
, ,
1

Hi everyone
The bluetooth doesn’t work on kernel 5.9 but works on previous kernels
Specs:

System:    Kernel: 5.9.8-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE Plasma 5.20.3 
           tk: Qt 5.15.1 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Laptop System: HP product: HP Pavilion Gaming Laptop 15-ec1xxx v: N/A 
           serial: <superuser/root required> Chassis: type: 10 serial: <superuser/root required> 
           Mobo: HP model: 87B1 v: 31.17 serial: <superuser/root required> UEFI: AMI v: F.02 date: 05/14/2020 
Battery:   ID-1: BAT0 charge: 11.5 Wh condition: 49.2/49.2 Wh (100%) volts: 11.1/11.6 
           model: Hewlett-Packard Primary serial: N/A status: Discharging 
CPU:       Info: 6-Core model: AMD Ryzen 5 4600H with Radeon Graphics bits: 64 type: MT MCP arch: Zen rev: 1 
           L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 71897 
           Speed: 1397 MHz min/max: 1400/3000 MHz boost: enabled Core speeds (MHz): 1: 1397 2: 1397 3: 1397 
           4: 1396 5: 1397 6: 1397 7: 1397 8: 1397 9: 1397 10: 1397 11: 1398 12: 1397 
Graphics:  Device-1: NVIDIA TU117M vendor: Hewlett-Packard driver: N/A bus ID: 01:00.0 chip ID: 10de:1f99 
           Device-2: Advanced Micro Devices [AMD/ATI] Renoir vendor: Hewlett-Packard driver: amdgpu v: kernel 
           bus ID: 05:00.0 chip ID: 1002:1636 
           Device-3: Luxvisions Innotech Limited HP TrueVision HD Camera type: USB driver: uvcvideo 
           bus ID: 3-3:3 chip ID: 30c9:0013 
           Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 driver: amdgpu resolution: 1920x1080~60Hz 
           s-dpi: 96 
           OpenGL: renderer: AMD RENOIR (DRM 3.39.0 5.9.8-2-MANJARO LLVM 11.0.0) v: 4.6 Mesa 20.2.2 
           direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor 
           vendor: Hewlett-Packard driver: N/A bus ID: 05:00.5 chip ID: 1022:15e2 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 05:00.6 chip ID: 1022:15e3 
           Sound Server: ALSA v: k5.9.8-2-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard 
           driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eno1 state: down mac: b0:5c:da:42:34:3f 
           Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard 
           driver: rtw_8822ce v: N/A port: d000 bus ID: 03:00.0 chip ID: 10ec:c822 
           IF: wlo1 state: up mac: 70:66:55:bb:04:b7 
Drives:    Local Storage: total: 476.94 GiB used: 133.59 GiB (28.0%) 
           ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNV512G KIOXIA size: 476.94 GiB speed: 31.6 Gb/s 
           lanes: 4 serial: 306PEEC9PBV1 
Partition: ID-1: / size: 459.50 GiB used: 133.59 GiB (29.1%) fs: ext4 dev: /dev/nvme0n1p2 
Swap:      ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 43.5 C mobo: N/A gpu: amdgpu temp: 43.0 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 304 Uptime: 4m Memory: 7.21 GiB used: 1.66 GiB (23.1%) Init: systemd v: 246 Compilers: 
           gcc: 10.2.0 Packages: pacman: 1610 Shell: Bash v: 5.0.18 running in: konsole inxi: 3.1.08

Also i typed show inside bluetoothctl:

[bluetooth]# show
No default controller available
1 Like
2

boot into a working kernel and post the bluetoothctl output again …

3

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
4

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

1 Like
5

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

6

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
7

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

8

The output:

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

So I guess it’s not blocked :confused:

9

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

1 Like
10

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

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

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

12

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

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

14

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

15

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.

16

Yes

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

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.

1 Like
18

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.

1 Like
19

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

1 Like
20

Today’s update fixed the issue!!