Next, let the controller scan the Bluetooth frequencies for a suitable device: Please note that this discoverability of a device is time limited some devices are only visible for 30 seconds, other for 2 minutes. Some keyboards have a special button for this on the underside, or require a special key combination to be pressed. Next, put your keyboard in an active mode, where it is discoverable, i.e. # pairable on Changing pairable on succeeded Next, put your controller (the local dongle) in pairable mode: # default-agent Default agent request successful Next, tell bluetoothctl to look only for keyboards, and make that the default agent: While in bluetoothctl power up the controller:
Note: If you are on a color console: the word "bluetooth" is in the default color as long as no devices are available, and blue as soon as required devices and/or controllers have been found. We will use bluetoothctl for the pairing process. Same for connecting, either bluetoothctl or hcitool can be used, the latter is more useful for scripting. Power up can be done with bluetoothctl, or automatically in /etc/bluetooth/nf, see below. We will use the bluetoothctl command from bluez-utils to pair our dongle and the keyboard. There are Bluetooth keyboards sold with a Bluetooth dongle which come already paired, but that is not certain. Pairing is a one time process, required only once.
# lsusb Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. a Bluetooth dongle the built in Bluetooth radio) is recognized: Login to the affected computer by a wired keyboard or by ssh.įirst, make sure the local Bluetooth controller (e.g. (Discuss in Talk:Bluetooth#Merging general setup from Keyboard, Mouse, Headset pages) Keyboard-specific info would stay on this page. Notes: Pairing process, and some troubleshooting related to it, are redundant with general device setup on Bluetooth page, and should be merged there.
0 kommentar(er)
