This article describes the setup of bluetooth controllers.
|RFCOMM protocol support||rfcomm||RFCOMM is a requirement of the OBEX-file transfer, dialup connections and more bluetooth applications.|
|RFCOMM TTY support||-||Enables terminal emulator connections over RFCOMM.|
|BNEP protocol support||bnep||Enables network support, e.g. for the PAN profile.|
|Multicast filter support||-||Enables multicast filter support.|
|Protocol filter support||-||Enables protocol filter support.|
|HIDP protocol support||hidp||Enables input device support. See the Bluetooth Input devices article.|
Portage knows the global USE flag bluetooth for enabling support for Bluetooth in other packages. Enabling this USE flag will pull in net-wireless/bluez automatically:
The USE flags of bluez are:
|alsa||Yes||Adds support for media-libs/alsa-lib (Advanced Linux Sound Architecture)|
|cups||Yes||Add support for CUPS (Common Unix Printing System)|
|debug||No||Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml|
|gstreamer||No||Adds support for media-libs/gstreamer (Streaming media)|
|pcmcia||No||Adds support for PCMCIA slots/devices found on laptop computers|
|readline||Yes||Enables support for libreadline, a GNU line-editing library that almost everyone wants|
|selinux||No||No||!!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur|
|test-programs||No||Install tools for testing of various Bluetooth functions|
|usb||Yes||Adds USB support to applications that have optional USB support (e.g. cups)|
After setting this you want to update your system so the changes take effect:
You can now start bluetooth:
To start bluetooth at boot time, add it your default runlevel:
A broader solution is to add the user you want to be able to access bluetooth devices to the plugdev group:
Check that your bluetooth adapter is working.
Where hci0 is the first device ID and 60:D8:19:B6:C3:1F is the MAC address.
Bring interface up at bootup time
In case you need to use trusted bluetooth devices before a GUI is up and running, you can use an udev rule:
Before a device can be used, it must be attached (paired in Bluetooth-lingo). This is done by entering a PIN (or other code) on both devices.
In order to pair, you must first have the interaction agent active. Most desktop environments have bluetooth integration so will automatically support the interaction agent. For example, KDE has net-wireless/bluedevil.
After an upgrade to BlueZ 5, pairing has to be redone.
Configuration can either be performed using the BlueZ test programs (available if you enable the test-programs USE flag for net-wireless/bluez), or by using the D-Bus API. The first way is described here.
- Retrieve the address of the mouse. Most of the devices need you to press a special button, possibly for several seconds, to render them discoverable.
- Where 00:1F:20:1D:1B:4B is the MAC address for your device.
- Pair the device:
- Enter a PIN and press Enter, then enter the same PIN at the device. If you don't know the PIN, then it is probably 0000. It could be 1234.
- Mark the device as trusted so it can connect automatically:
- Devices are not trusted by default. You can check trust status by leaving off the "yes" from the previous command.
- "1" is trusted, "0" is not trusted.
- Connect the device (this only needs to be done once, it will be done automatically after that):
- Your device should now be paired. You are now ready to proceed.