https://bugzilla.kernel.org/show_bug.cgi?id=213369
Bug ID: 213369
Summary: Bluetooth Will Not Enable Intel AX200
Product: Drivers
Version: 2.5
Kernel Version: 5.11.22-180
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: No
So a new issue that started recently, I enable my Bluetooth, but when I go into
settings it shows it's not enabled and when I click add device from the tray it
says "Your Bluetooth adapter is not pairable". Not sure what's going on. I've
tried manually installing the driver, but no luck. Running on Solus 4.2 KDE
Plasma DE, stable repos, fully updated. Bluetooth/WiFi adapter is an Intel
AX200. Here is the output of commands I've tried so far. Manually installing
BlueZ 5.55-30 fixes the issue. Have tried installing BlueZ 5.56 with bluez-qt
and bluedevil rebuilt against the new BlueZ version and still have the same
issue.
`bruce@s145-15api ~ $ modprobe btusb
bruce@s145-15api ~ $ sudo systemctl enable bluetooth.service
Password:
bruce@s145-15api ~ $ sudo systemctl start bluetooth.service
bruce@s145-15api ~ $ systemctl is-enabled bluetooth
enabled
bruce@s145-15api ~ $ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running) since Sun 2021-06-06 11:18:38 EDT; 6min ago
Docs: man:bluetoothd(8)
Main PID: 698 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 11730)
Memory: 1.9M
CPU: 30ms
CGroup: /system.slice/bluetooth.service
└─698 /usr/lib64/bluez/bluetooth/bluetoothd
Warning: some journal files were not opened due to insufficient permissions.
bruce@s145-15api ~ $ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running) since Sun 2021-06-06 11:18:38 EDT; 6min ago
Docs: man:bluetoothd(8)
Main PID: 698 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 11730)
Memory: 1.9M
CPU: 30ms
CGroup: /system.slice/bluetooth.service
└─698 /usr/lib64/bluez/bluetooth/bluetoothd
Jun 06 11:18:38 s145-15api systemd[1]: Starting Bluetooth service...
Jun 06 11:18:38 s145-15api bluetoothd[698]: Bluetooth daemon 5.58
Jun 06 11:18:38 s145-15api systemd[1]: Started Bluetooth service.
Jun 06 11:18:38 s145-15api bluetoothd[698]: Starting SDP server
Jun 06 11:18:38 s145-15api bluetoothd[698]: Bluetooth management interface 1.19
initialized
Jun 06 11:18:38 s145-15api bluetoothd[698]: Failed to set mode: Blocked through
rfkill (0x12)
Jun 06 11:18:46 s145-15api bluetoothd[698]: Endpoint registered: sender=:1.39
path=/MediaEndpoint/A2DPSink/>
Jun 06 11:18:46 s145-15api bluetoothd[698]: Endpoint registered: sender=:1.39
path=/MediaEndpoint/A2DPSourc>
bruce@s145-15api ~ $ rfkill
ID TYPE DEVICE SOFT HARD
0 wlan ideapad_wlan unblocked unblocked
1 bluetooth ideapad_bluetooth unblocked unblocked
2 bluetooth hci0 unblocked unblocked
3 wlan phy0 unblocked unblocked
bruce@s145-15api ~ $ blutoothctl
bash: blutoothctl: command not found
bruce@s145-15api ~ $ bluetoothctl
Agent registered
[bluetooth]# show
Controller A4:B1:C1:36:53:11 (public)
Name: s145-15api
Alias: s145-15api
Class: 0x00000000
Powered: no
Discoverable: no
DiscoverableTimeout: 0x000000b4
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 (00001108-0000-1000-8000-00805f9b34fb)
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: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d053A
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x06 (6)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
[bluetooth]# agent KeyboardOnly
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Busy
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady`
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=213369
Tomasz Kołosowski ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from Tomasz Kołosowski ([email protected]) ---
I have a very similar issue with Intel AX210 since kernel 5.13, last working
version for me is 5.12.15. In my case downgrading bluez doesn't solve the
issue, only downgrading the kernel helps.
$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor
preset: disabled)
Active: active (running) since Mon 2021-08-02 16:14:22 CEST; 14min ago
Docs: man:bluetoothd(8)
Main PID: 78618 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 76960)
Memory: 748.0K
CPU: 11ms
CGroup: /system.slice/bluetooth.service
└─78618 /usr/lib/bluetooth/bluetoothd
sie 02 16:14:22 nest systemd[1]: Starting Bluetooth service...
sie 02 16:14:22 nest bluetoothd[78618]: Bluetooth daemon 5.60
sie 02 16:14:22 nest systemd[1]: Started Bluetooth service.
sie 02 16:14:22 nest bluetoothd[78618]: Starting SDP server
sie 02 16:14:22 nest bluetoothd[78618]: Bluetooth management interface 1.20
initialized
Intrestingly, on kernel 5.12 it reports management interface version 1.19
$ rfkill
ID TYPE DEVICE SOFT HARD
0 wlan phy0 blocked unblocked
1 bluetooth hci0 unblocked unblocked
$ bluetoothctl
Agent registered
[bluetooth]# show
No default controller available
[bluetooth]#
$ btmgmt
[mgmt]# info
Index list with 0 items
[mgmt]# config
Unconfigured index list with 1 item
hci0: Unconfigured controller
manufacturer 2
supported options: public-address
missing options: public-address
[mgmt]#
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=213369
Luiz Von Dentz ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #2 from Luiz Von Dentz ([email protected]) ---
Does dmesg show any errors? Looks like the controller could not be configured
for some reason.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=213369
--- Comment #3 from Tomasz Kołosowski ([email protected]) ---
No, dmesg looks clean
$ sudo dmesg | egrep -i 'bluetooth|firmware'
[ 1.276885] i915 0000:00:02.0: Direct firmware load for
i915/gvt/vid_0x8086_did_0x9b41_rid_0x02.golden_hw_state failed with error -2
[ 1.353260] i915 0000:00:02.0: [drm] Finished loading DMC firmware
i915/kbl_dmc_ver1_04.bin (v1.4)
[ 1.398367] i915 0000:00:02.0: [drm] GuC firmware i915/kbl_guc_49.0.1.bin
version 49.0 submission:disabled
[ 1.398376] i915 0000:00:02.0: [drm] HuC firmware i915/kbl_huc_4.0.0.bin
version 4.0 authenticated:yes
[ 11.400827] platform regulatory.0: Direct firmware load for regulatory.db
failed with error -2
[ 11.786671] snd_hda_intel 0000:00:1f.3: Applying patch firmware
'system76-audio-patch'
[ 11.945138] iwlwifi 0000:27:00.0: loaded firmware version 63.c04f3485.0
ty-a0-gf-a0-63.ucode op_mode iwlmvm
[ 12.856911] Bluetooth: Core ver 2.22
[ 12.872636] Bluetooth: HCI device and connection manager initialized
[ 12.872640] Bluetooth: HCI socket layer initialized
[ 12.872643] Bluetooth: L2CAP socket layer initialized
[ 12.872649] Bluetooth: SCO socket layer initialized
[ 13.386729] Bluetooth: hci0: Firmware timestamp 2021.19 buildtype 1 build
25171
[ 13.388842] Bluetooth: hci0: No device address configured
[ 13.393579] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 13.393627] Bluetooth: hci0: Boot Address: 0x100800
[ 13.393629] Bluetooth: hci0: Firmware Version: 83-19.21
[ 13.393631] Bluetooth: hci0: Firmware already loaded
[ 14.130910] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.130915] Bluetooth: BNEP filters: protocol multicast
[ 14.130920] Bluetooth: BNEP socket layer initialized
[ 16.065398] usb 1-3.4: Direct firmware load for ti_usb-v0451-p3410.fw failed
with error -2
[ 16.912255] usb 1-3.4: device firmware changed
The last two lines are about different device, not bluetooth related
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.