Bug 213369
Summary: | Bluetooth Will Not Enable Intel AX200 | ||
---|---|---|---|
Product: | Drivers | Reporter: | hankins.bruce |
Component: | Bluetooth | Assignee: | linux-bluetooth (linux-bluetooth) |
Status: | NEW --- | ||
Severity: | normal | CC: | CoelacanthusHex, hankins.bruce, luiz.dentz, steven, tomek |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 5.11.22-180 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
hankins.bruce
2021-06-08 17:42:38 UTC
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]# Does dmesg show any errors? Looks like the controller could not be configured for some reason. 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 Tomasz, your issue is likely https://bugzilla.kernel.org/show_bug.cgi?id=213829. Thank you Steven, that indeed looks more like issue I'm having. |