Bluetooth not working on (latest) VirtualBox kernel

[Phlox]

My bluetooth device (Intel Corp.|Wireless-AC 9260) is not working when booting with the latest VirtualBox kernel.

In XFCE and Gnome the device can't be started and stopped.

Booting with the normal Desktop kernel my bluetooth device is working.

Not working:
5.14.10-desktop-1.mga8

Working:
5.10.75-desktop-1.mga8

Code: Select all

lspcidrake -v | grep -i bluetooth
btusb           : Intel Corp.|Wireless-AC 9260 Bluetooth Adapter [Wireless|Radio Frequency|Bluetooth] (vendor:8087 device:0025)

Do I need to do some extra action to make it work on the VirtualBox kernel?

[doktor5000]

Hi there, what do you mean by virtualbox kernel ?

Please provide the output as root of

Code: Select all

journalctl -ab|grep -i bluetooth

and as regular user from

Code: Select all

rfkill list all
bluetoothctl list
bluetoothctl show

[Phlox]

Hi there, what do you mean by virtualbox kernel ?

Just looked into it and I named it wrong, sorry.

When installing Virtualbox it installs a newer Desktop kernel (kernel-desktop-5.14.10-1) and:

Code: Select all

virtualbox-kernel-5.14.10-desktop-1.mga8 - virtualbox driver for kernel-desktop-5.14.10-1.mga8​                                                                                                                        
Prebuilt dkms binary kernel modules for the virtualbox driver version 6.1.26 built for kernel-desktop-5.14.10-1.mga8.


When using this newer kernel I can't get bluetooth working any more on Gnome and on XFCE.
Nothing happens when enabling or disabling bluetooth. Also the bluetooth settings wont show also.

Booting with the previous kernel (5.10.75-desktop-1.mga8) I can enable/disable/edit bluetooth settings in Gnome and XFCE.

Code: Select all

rpm -qa |grep kernel
virtualbox-kernel-5.14.10-desktop-1.mga8-6.1.26-2.8.mga8
virtualbox-kernel-5.10.75-desktop-1.mga8-6.1.28-1.2.mga8
kernel-desktop-5.10.16-1.mga8-1-1.mga8
virtualbox-kernel-desktop-latest-6.1.28-1.2.mga8
kernel-firmware-20201218-1.mga8
kernel-firmware-nonfree-20210716-1.mga8.nonfree
virtualbox-kernel-5.10.70-desktop-1.mga8-6.1.28-1.mga8
kernel-desktop-5.10.75-1.mga8-1-1.mga8
kernel-desktop-5.10.70-1.mga8-1-1.mga8
kernel-desktop-5.14.10-1.mga8-1-1.mga8
kernel-desktop-latest-5.10.75-1.mga8
kernel-userspace-headers-5.10.75-1.mga8


The following output is with the booted kernel-desktop-5.14.10-1.mga8-1-1.mga8 kernel:

Code: Select all

journalctl -ab|grep -i bluetooth
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: Core ver 2.22
Oct 26 19:21:01 localhost.localdomain kernel: NET: Registered PF_BLUETOOTH protocol family
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: HCI device and connection manager initialized
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: HCI socket layer initialized
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: L2CAP socket layer initialized
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: SCO socket layer initialized
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: hci0: Device revision is 2
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: hci0: Secure boot is enabled
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: hci0: OTP lock is enabled
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: hci0: API lock is enabled
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: hci0: Debug lock is disabled
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Oct 26 19:21:01 localhost.localdomain kernel: Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Oct 26 19:21:02 localhost.localdomain kernel: Bluetooth: hci0: Waiting for firmware download to complete
Oct 26 19:21:02 localhost.localdomain kernel: Bluetooth: hci0: Firmware loaded in 1305573 usecs
Oct 26 19:21:02 localhost.localdomain kernel: Bluetooth: hci0: Waiting for device to boot
Oct 26 19:21:02 localhost.localdomain kernel: Bluetooth: hci0: Device booted in 16918 usecs
Oct 26 19:21:02 localhost.localdomain kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc
Oct 26 19:21:02 localhost.localdomain kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Oct 26 19:21:02 localhost.localdomain kernel: Bluetooth: hci0: Firmware revision 0.1 build 6 week 12 2021
Oct 26 19:21:02 localhost.localdomain kernel: Bluetooth: hci0: MSFT filter_enable is already on
Oct 26 19:21:11 localhost.localdomain service_harddrake[917]: BLUETOOTH took:  0:00:00
Oct 26 19:21:11 localhost.localdomain systemd[1]: Starting Bluetooth service...
Oct 26 19:21:11 localhost.localdomain bluetoothd[950]: Bluetooth daemon 5.55
Oct 26 19:21:11 localhost.localdomain bluetoothd[950]: Starting SDP server
Oct 26 19:21:11 localhost.localdomain kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 26 19:21:11 localhost.localdomain kernel: Bluetooth: BNEP filters: protocol multicast
Oct 26 19:21:11 localhost.localdomain kernel: Bluetooth: BNEP socket layer initialized
Oct 26 19:21:11 localhost.localdomain bluetoothd[950]: Bluetooth management interface 1.21 initialized
Oct 26 19:21:11 localhost.localdomain systemd[1]: Started Bluetooth service.
Oct 26 19:21:11 localhost.localdomain systemd[1]: Reached target Bluetooth.
Oct 26 19:21:11 localhost.localdomain bluetoothd[950]: Failed to set mode: Blocked through rfkill (0x12)
Oct 26 19:21:11 localhost.localdomain NetworkManager[1025]: <info>  [1635268871.9705] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.26.6/libnm-device-plugin-bluetooth.so)
Oct 26 19:21:13 localhost.localdomain bluetoothd[950]: Failed to set mode: Blocked through rfkill (0x12)
Oct 26 19:21:14 localhost.localdomain bluetoothd[950]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc
Oct 26 19:21:14 localhost.localdomain bluetoothd[950]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc
Oct 26 19:21:14 localhost.localdomain kernel: Bluetooth: RFCOMM TTY layer initialized
Oct 26 19:21:14 localhost.localdomain kernel: Bluetooth: RFCOMM socket layer initialized
Oct 26 19:21:14 localhost.localdomain kernel: Bluetooth: RFCOMM ver 1.11
Oct 26 19:21:23 localhost.localdomain bluetoothd[950]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSink/sbc
Oct 26 19:21:23 localhost.localdomain bluetoothd[950]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSource/sbc
Oct 26 19:21:23 localhost.localdomain bluetoothd[950]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Oct 26 19:21:24 localhost.localdomain bluetoothd[950]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc
Oct 26 19:21:24 localhost.localdomain bluetoothd[950]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc
Oct 26 19:21:57 localhost.localdomain systemd[1815]: Starting Bluetooth OBEX service...
Oct 26 19:21:57 localhost.localdomain systemd[1815]: Started Bluetooth OBEX service.


Code: Select all

rfkill list all
0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no


Code: Select all

bluetoothctl list
Controller 3C:58:C2:A2:D8:5B localhost.localdomain [default]


Code: Select all

bluetoothctl show
Controller 3C:58:C2:A2:D8:5B (public)
   Name: localhost.localdomain
   Alias: localhost.localdomain
   Class: 0x00000000
   Powered: no
   Discoverable: yes
   DiscoverableTimeout: 0x00000000
   Pairable: yes
   UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
   UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
   UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
   UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
   UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
   UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
   UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
   UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
   UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
   UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
   UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
   UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
   UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
   Modalias: usb:v1D6Bp0246d0537
   Discovering: no
   Roles: central
   Roles: peripheral
   Roles: central-peripheral
Advertising Features:
   ActiveInstances: 0x00 (0)
   SupportedInstances: 0x06 (6)
   SupportedIncludes: tx-power
   SupportedIncludes: appearance
   SupportedIncludes: local-name
   SupportedSecondaryChannels: 1M
   SupportedSecondaryChannels: 2M
   SupportedSecondaryChannels: Coded


This is booting with the 5.14.10-desktop-1.mga8 VirtualBox kernel

[doktor5000]

Code: Select all

virtualbox-kernel-5.14.10-desktop-1.mga8 - virtualbox driver for kernel-desktop-5.14.10-1.mga8​                                                                                                                        
Prebuilt dkms binary kernel modules for the virtualbox driver version 6.1.26 built for kernel-desktop-5.14.10-1.mga8.


When using this newer kernel I can't get bluetooth working any more on Gnome and on XFCE.

The package you mentioned is only for the virtualbox kernel module, it's prebuilt for the new kernel, it's not a kernel by itself.

This might be an issue, although the rfkill output says otherwise:

Code: Select all

Oct 26 19:21:11 localhost.localdomain bluetoothd[950]: Failed to set mode: Blocked through rfkill (0x12)


Code: Select all

bluetoothctl show
Controller 3C:58:C2:A2:D8:5B (public)
   Powered: no


The controller is not powered up, try as regular user with

Code: Select all

bluetoothctl power on

[Phlox]

Code: Select all

bluetoothctl power on
Changing power on succeeded

The gnome session doesn't see it when I activate it, even when I activate it on the console and then log in via gdm.

I got an error yesterday in gnome settings telling me that I need to install a bluetooth device to be able to edit bluetooth settings or something close to that.

After running bluetoothctl power on:

Code: Select all

bluetoothctl show
Controller 3C:58:C2:A2:D8:5B (public)
   Name: localhost.localdomain
   Alias: localhost.localdomain
   Class: 0x00000000
   Powered: no


When booting the previous kernel 5.10.75-desktop-1.mga8 bluetooth just works like it should and I have zero problems but I need virtualbox from time to time.

Its not working with the newer kernel-desktop-5.14.10-1.mga8-1-1.mga8.