OK - if you open a terminal and type dmesg | grep "Bluetooth" you should see something like
Code: Select all
chris@dukla:~ $ dmesg | grep "Bluetooth"
[ 6.044142] Bluetooth: Core ver 2.21
[ 6.044258] Bluetooth: HCI device and connection manager initialized
[ 6.044286] Bluetooth: HCI socket layer initialized
[ 6.044307] Bluetooth: L2CAP socket layer initialized
[ 6.044372] Bluetooth: SCO socket layer initialized
This is from my Pi3 - as per my sig I am not using the onboard BT but that shouldn't make a huge difference. dmesg dumps the system log since the last boot, if you type it with no parameters you will see the whole gory details and can scroll up and down. grep "Bluetooth" searches for all occurances of the string Bluetooth (note it is important to use capital B)
Anyway - if you get nothing back from the above command you have a problem. Probably best to post the entire contents of a dmesg output in that case.
If you get something back then the hardware is probably OK. In which case all you need is a package called bluetooth - you can install it (or check it is already installed) by typing
Once/if that is installed then you are 99% of the way there
should start a BT command line utility (you need to type quit to exit it) and show you a default controller. If it doesn't you have a hardware/firmware problem. If it worked then type
and set your device into pairing mode. You should (after a few seconds) see a screen report that something was found. The thing to note is the reported BT address, of the form ab

ef:gh:ij:kl.
if you now type
AFTER each of the "ab" above press your TAB key - it will autocomplete the rest of the
ef:gh:ij:kl .
And you should be done.