Re: Activating Bluetooth on intel AX200,AX201,AX210 modules
Date: Tue, 22 Jul 2025 08:07:33 UTC
HI , the Shell trace i showed previously is not detailed enough. it is the hccontrol 'reset' command on line 130 of the bluetooth start script that times out. being used to Solaris I created the attached TRUSS trace which on line 3213 and above shows the failing hccontrol task. After applying the provided Patch the bluetooth stack can be setup and torn down. root@h7510:/etc/rc.d # service bluetooth start ubt0 /etc/rc.d/bluetooth: WARNING: Reset failed, retrying. root@h7510:/etc/rc.d # ngctl show ubt0: Name: ubt0 Type: ubt ID: 00000003 Num hooks: 1 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- hook ubt0hci hci 00000053 drv root@h7510:/etc/rc.d # service bluetooth stop ubt0 root@h7510:/etc/rc.d # ngctl show ubt0: Name: ubt0 Type: ubt ID: 00000003 Num hooks: 0 root@h7510:/etc/rc.d # service bluetooth start ubt0 /etc/rc.d/bluetooth: WARNING: Reset failed, retrying. root@h7510:/etc/rc.d # ngctl show ubt0: Name: ubt0 Type: ubt ID: 00000003 Num hooks: 1 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- hook ubt0hci hci 00000062 drv On 7/21/25 5:43 PM, Bjoern A. Zeeb wrote: > On Mon, 21 Jul 2025, Bjoern A. Zeeb wrote: > >> On Mon, 21 Jul 2025, Lars Tunkrans wrote: >> >>> >>> HI >>> >>> this command in the /etc/rc.d/bluetooth start script >>> fails with exit status 1 , unless mutilple iwmbt firmware >>> loads is executed beforehand, >>> >>> >>> * # ngctl mkpeer ubt0: hci hook drv* >>> >>> ngctl mkpeer ubt0: hci hook drv >>> + return 1 >>> + bluetooth_shutdown_stack ubt0 >>> + dev=ubt0 >>> + ngctl shutdown ubt0hci: >>> + ngctl shutdown ubt0l2cap: >>> + return 0 >>> + err 1 'Unable to setup Bluetooth stack for device ubt0' >> >> Can you try this change which is left from an ealrier review which never >> was committed as an alternate implementation made it into the tree: >> >> https://reviews.freebsd.org/differential/changeset/?ref=1332283 >> >> If this works, I'll just commit it. > > Hmm, seems this is too late for your error case? Sorry for the noise. >