[Bug 267581] ubt: 13.1-RELEASE fails to attach Intel Wireless-AC 3168 (USB: 0x8087:0x0aa7, ASRock X399 Taichi and others)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267581

--- Comment #14 from Vladimir Kondratyev <wulf@freebsd.org> ---
(In reply to Andrey Korobkov from comment #13)

> No locking happen, but still no ubt device node appear.

ng_ubt is netgraph device, so no /dev/ubt0 should appear

Properly initialized bt device looks like:

# ngctl list
There are 9 total nodes:
  Name: ubt0            Type: ubt             ID: 00000001   Num hooks: 1
  Name: btsock_hci_raw  Type: btsock_hci_raw  ID: 00000002   Num hooks: 1
  Name: btsock_l2c_raw  Type: btsock_l2c_raw  ID: 00000003   Num hooks: 1
  Name: btsock_l2c      Type: btsock_l2c      ID: 00000004   Num hooks: 1
  Name: btsock_sco      Type: btsock_sco      ID: 00000005   Num hooks: 0
  Name: ubt0hci         Type: hci             ID: 00000007   Num hooks: 3
  Name: ubt0l2cap       Type: l2cap           ID: 0000000b   Num hooks: 3
  Name: wlan0           Type: ether           ID: 00000011   Num hooks: 0
  Name: ngctl11859      Type: socket          ID: 00000012   Num hooks: 0


> When trying to start bluetooth service manually adapter locks so any following download attempts fail until power cycle.

There was a report that fw_patch_num 0x41 may not work with our BT stack. Try
to downgrade it to fw_patch_num 0x36. It can be downloaded directly from VCS:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq?id=6be4747ea1d731f661c5320acf3f1273a459d6da

It worth to test other firmwares newer than fw_patch_num 0x36. especially
fw_patch_num 0x43 (latest). They can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq?showmsg=1

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.