Date: Tue, 10 May 2022 18:41:11 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 263900] Bluetooth dysfunction with TP-Link UB500 Message-ID: <bug-263900-21060-1yd6NbSKeF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263900-21060@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263900 --- Comment #1 from xyesbee@protonmail.com --- I dug up a little bit and found out /etc/rc.d/bluetooth uses ngctl (Netgraph API) to configure the Bluetooth stack for a certain device. So I ran through man pages and decided what was most appropriate and ran "ngctl ls" whose results are the following if they help debugging the issue. There are 8 total nodes: Name: ubt0 Type: ubt ID: 00000001 Num hooks: 1 Name: ubt0hci Type: hci ID: 00000022 Num hooks: 3 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: ubt0l2cap Type: l2cap ID: 00000026 Num hooks: 3 Name: ngctl8974 Type: socket ID: 0000002c Num hooks: 0 -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263900-21060-1yd6NbSKeF>