ubt0 device fails to appear for Integrated Bluetooth module Intel Wireless-AC 3168 on ASRock X399 Taichi motherboard after upgrade FreeBSD from 13.0 to 13.1. Similar to bug #237083. On 13.0 (works): ugen0.2: <vendor 0x8087 product 0x0aa7> at usbus0 ubt0 on uhub0 ubt0: <vendor 0x8087 product 0x0aa7, class 224/1, rev 2.00/0.01, addr 1> on usbus0 --- On 13.1 (fails): ugen0.2: <vendor 0x8087 product 0x0aa7> at usbus0 --- # usbconfig ugen0.2 dump_device_desc ugen0.2: <vendor 0x8087 product 0x0aa7> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00e0 <Wireless controller> bDeviceSubClass = 0x0001 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x8087 idProduct = 0x0aa7 bcdDevice = 0x0001 iManufacturer = 0x0000 <no string> iProduct = 0x0000 <no string> iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 --- Some hint(?): on 13.1 iwmbtfw considers this device as Intel 7260 (by VID:PID) and tries to load it's firmware (ibt-hw-37.8.bseq)… May it be related to this? I hope, as we already had this device successfully working in 13.0, with all needed firmware, we could make it work again in 13.1 too… I'm ready to provide any needed information and assist with debugging this issue.
@Reporter Could you include a full /var/run/dmesg.boot as an attachment please
Created attachment 238040 [details] Dmesg with working BT on 13.0
Created attachment 238041 [details] Dmesg with non-working BT on 13.1
Thank you for your willingness to help me and take my regrets for so long delay with my response.
Not the same as this device, but my ubt is also not attached immediately after reboot. At that time, when the USB mouse is re-plugged, the ubt is also attached at the same time. In my case it is 12.4-STABLE, but it has been that way since about 12.3.
> on 13.1 iwmbtfw considers this device as Intel 7260 (by VID:PID) and tries > to load it's firmware (ibt-hw-37.8.bseq)… May it be related to this? Yes, it is related. ibt-hw-37.8.bseq is a dummy firmware. Probably your device does not require any external firmware to work. What is the output of the following command?: iwmbtfw -I -d ugen0.2 -f /usr/local/share/iwmbt-firmware
Created attachment 238249 [details] iwmbtfw output on 13.0
Created attachment 238250 [details] iwmbtfw output on 13.1 with iwmbt-firmware installed
Created attachment 238251 [details] iwmbtfw output on 13.1 without iwmbt-firmware installed
Your iwmbt-firmware looks outdated. It misses ibt-hw-37.8.10-fw-22.50.19.14.f.bseq file which match your bt adapter. Try to upgrade comms/iwmbt-firmware to latest ports version.
Created attachment 238272 [details] iwmbtfw output on 13.1 when adapter is locked (fail)
Created attachment 238273 [details] iwmbtfw output on 13.1 when adapter is unlocked (success)
Thank you for the advice. I've checked my iwmbt-firmware version, it's the latest 20210315 (so should have it). I've just had tried to examine the behavior both with and without this installed (should it be useful). Now have partial success, as I was able to at least have the firmware downloaded to the device after commenting out devd rule from /etc/devd/iwmbtfw.conf and powering off the machine. But still no success with attaching ubt device node: adapter seems to lock itself somehow, so now I have 2 states: 1) Default. When devd rule is active something tries to start ng_ubt, fails with timeout and adapter locks. All download attempts fail. 2) Manual. When devd rule is inactive and nothing tries to start ng_ubt, so adapter seems unlocked. Manual firmware downloading succeeds. I may even do `usbconfig reset` and then successfully re-download the firmware. No locking happen, but still no ubt device node appear. When trying to start bluetooth service manually adapter locks so any following download attempts fail until power cycle. Looks similar to #237083 ? Some race condition during BT activation? Should I try to comment out devd rule for automatic service bluetooth quietstart? I may even try to apply some patches to test, would you advice me to do so… Thanks in advance
(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
Don't forget to do power off after each try. It is required to remove old firmware at least on 8260/8265.
YES!!! Thank you very much!! It really helped! Exactly this: fw_patch_num 0x36 and only this. fw_patch_num 0x34: Works fw_patch_num 0x36: Works fw_patch_num 0x41: Fails fw_patch_num 0x42: Fails fw_patch_num 0x43: Fails Tested with full power-off, just as you've said. May it be back-ported to 13.1, please? Thanks once again! Andrey
Created attachment 238316 [details] iwmbtfw for fw_patch_num 0x34 (Works)
Created attachment 238317 [details] iwmbtfw for fw_patch_num 0x36 (Works)
Created attachment 238318 [details] iwmbtfw for fw_patch_num 0x41 (Fails)
Created attachment 238319 [details] iwmbtfw for fw_patch_num 0x42 (Fails)
Created attachment 238320 [details] iwmbtfw for fw_patch_num 0x43 (Fails)
(In reply to Andrey Korobkov from comment #16) > May it be back-ported to 13.1, please? Done in https://cgit.freebsd.org/ports/commit/?id=7aa0e0a09cfad876f9a5a1ff70e31c9614e88fb6