On Tue, Sep 22, 2020 at 07:07:42AM -0000, Stuart Henderson wrote: > On 2020-09-22, Tito Mari Francis Escaño <titomarifran...@gmail.com> wrote: > > Hi misc, > > I'm building an OpenBSD desktop PC and would like to use my Royal Kludge > > RK71 mechanical keyboard with it via USB Bluetooth dongle. > > Can somebody please point me to USB Bluetooth dongles tested working with > > OpenBSD? > > The only way to do bluetooth on OpenBSD is with an adapter that runs > the bluetooth stack internally and presents as a standard USB device. > > There are several that do this for audio, Creative BT-W2 definitely > works but there are others that may work too. > > Some bluetooth devices can theoretically do this for human-interface devices > (mice/keyboards) too - it's how Apple has bluetooth working pre-boot - > but I'm not aware of anyone having got them to work with OpenBSD. > > https://www.businesswire.com/news/home/20030811005013/en/CSR-Saves-Stranded-Mice-HID-Proxy-Firmware > ttps://www.0xf8.org/2014/02/the-crux-of-finding-a-hid-proxy-capable-usb-bluetooth-adapter/ >
I found a Belkin adapter (model F8T016) that presents itself as a uhid device (among other things): I've read about other adapters that can switch between "OS managed" (i.e. that show up as ugen) and "HID proxy" modes, but never got one. In theory, my Belkin should be able to be paired to a bluetooth keyboard and stay that way even across reboots. The problem is that that requires a keyboard that pairs without using a PIN, and my Logitech K380 doesn't, so I've never been able to get it to work as I wanted, nor test if that is entirely true. Even if I booted linux and paired the keyboard with it, it won't stick across reboots, not even warm ones. The keyboard was never available before the linux kernel and BT daemons were loaded. Sep 22 16:14:30 prionace /bsd: uhub8 at uhub0 port 13 configuration 1 interface 0 "Broadcom BCM2046B1" rev 2.00/1.00 addr 7 Sep 22 16:14:31 prionace /bsd: uhidev4 at uhub8 port 1 configuration 1 interface 0 "Broadcom product 0x4502" rev 2.00/1.00 addr 8 Sep 22 16:14:31 prionace /bsd: uhidev4: iclass 3/1, 1 report id Sep 22 16:14:31 prionace /bsd: ukbd1 at uhidev4 reportid 1: 8 variable keys, 6 key codes Sep 22 16:14:32 prionace /bsd: wskbd2 at ukbd1 mux 1 Sep 22 16:14:32 prionace /bsd: wskbd2: connecting to wsdisplay0 Sep 22 16:14:32 prionace /bsd: uhidev5 at uhub8 port 2 configuration 1 interface 0 "Broadcom product 0x4503" rev 2.00/1.00 addr 9 Sep 22 16:14:32 prionace /bsd: uhidev5: iclass 3/1, 125 report ids Sep 22 16:14:32 prionace /bsd: ums1 at uhidev5 reportid 2: 3 buttons Sep 22 16:14:32 prionace /bsd: wsmouse1 at ums1 mux 0 Sep 22 16:14:32 prionace /bsd: uhid5 at uhidev5 reportid 125: input=2, output=0, feature=0 Sep 22 16:14:33 prionace /bsd: ugen0 at uhub8 port 3 "Broadcom Corp BLUETOOTH USB +EDR ADAPTER v2.1 UHE" rev 2.00/3.88 addr 10 In summary: not only it is hard to find a device that works, you'd also have to find a keyboard that pairs without a PIN and keep your fingers firmly crossed. --
