Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[Ennio-Sr]

Hi all!
Has any of you benn able to pair the subject keyboard with bluetooth
under linux debian/jessie or stretch?
Using bluetoothctl 'pair xx:xx:xx:xx:xx:xx'
if I don't touch any key, nothing happens, and after a while I get:
Failed to pair: org.bluez.Error.AuthenticationTimeout

In case I enter '0000', bluetoothctl will say:
[Agent] PIN code: 939765
I enter this code and again it says
[Agent] PIN code: 118685
and so on until it stops with the AuthenticationTimeout error.

In /var/log/messages there is something like:
,,, Bluetooth-WARNING **: Could not load pin-code-database.xml

Trying old 'hidd --search' (that worked wonderfully in older Squeeze)
would say: Connecting ......
and then:

Can't get device information: function not implemented.

I'm completely lost and frustrated.
Can you help me? Thanks in advance, Ennio

--
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?//
Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ] (°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that. )=(
Do something you aren't good at!" (as Henry Miller used to say) ]

[deloptes]

Ennio-Sr wrote:

> Could not load pin-code-database.xml
this might help
http://askubuntu.com/questions/486347/bluetooth-mouse-not-auto-reconnecting-to-laptop

regards

[Leandro Noferini]

Ennio-Sr <nasr....@tin.it> writes:

> Has any of you benn able to pair the subject keyboard with bluetooth
> under linux debian/jessie or stretch?

[...]

I have a bluetooth keyboard different model (the model without numeric
keys) and to pair in a debian stable I needed to install also the
bluez-firmware package: after this I paired with standard gnome tools.

--
leandro
1A0B 125B 2E4D 2DAE 4E26 4551 88FB BBCC 7A29 640B
https://bbs.cybervalley.org/ChiaveLeandro/gpg.html
http://6xukrlqedfabdjrb.onion

[solitone]

On Monday, January 30, 2017 9:10:59 PM CET Leandro Noferini wrote:
> I have a bluetooth keyboard different model (the model without numeric
> keys) and to pair in a debian stable I needed to install also the
> bluez-firmware package: after this I paired with standard gnome tools.

I also believe you could give bluez-firmware a try. I had a pairing issue with
a different device (a speaker), and I could only solved it with that package.

[ennio]

This is just to thank deloptes, solitone, Leandro for their suggestions.
Unluckily, none of them helped solve the problem.
I'm waiting for 'stretch' to be officially the new 'stable' debian
version on 5th February so as to fully upgrade my system (now it is
partially Jessie, partially Stretch) and check again whether or not
bluetooth works with this quite old keyboard.

At present I only get a large variety of errors, depending on the
commands used to attempt pairing and may be I'm missing something:
The link suggested by Deolptes brought me to a
'pin-code-database.xml' file that should be in gnome-bluetooth
directory, not present in my system (broken dependencies).

Yes, I have the latest 'bluez-firmware' version.

AAMOF, prior to installing stretch bluetooth applications to the base
Jessie version, I got the same errors when I tried bluetooth in Jessie.

What upsets me most is that the keyboard worked nicely under
Squeeze/bluetooth running on a debian ppc on a macmini older than the
one I'm using with Jessie (intel amd64).

Thanks again to you all. Regards,

[deloptes]

ennio wrote:

> I'm waiting for 'stretch' to be officially the new 'stable' debian
> version on 5th February so as to fully upgrade my system (now it is
> partially Jessie, partially Stretch) and check again whether or not
> bluetooth works with this quite old keyboard.

You could use stretch in apt/sources.list and upgrade already. No need to
wait until 5th. Have some balls, show some character!

regards

[Ennio-Sr]

* deloptes <delo...@gmail.com> [010217, 00:46]:

OK, I did it, but nothing changed: getting more or less the same errors
as before,may be some more. But I'll come back with some consistent data...

[Ennio-Sr]

* Ennio-Sr <nasr....@tin.it> [010217, 19:33]:

>
> OK, I did it, but nothing changed: getting more or less the same errors
> as before,may be some more. But I'll come back with some consistent data...
> Regards, Ennio
>

And here we are!
The bluetooth Stretch version is bugged so I tried again with Jessie;
This is a screen dump of the commands used:
root@mcmini-4_1-deb:~# hciconfig hc10 sspmode 0 ->>> # same result not runnning this one #
root@mcmini-4_1-deb:~# bluetoothctl
[NEW] Device 00:0A:95:3F:A8:DF Apple Wireless Keyboard
[bluetooth]# show
Controller C8:BC:C8:E9:DA:AA
Name: mcmini-4_1-deb
Alias: mcmini-4_1-deb
Class: 0x0c0104
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d052B
Discovering: no <<<-
[bluetooth]# discoverable on <<< -
Changing discoverable on succeeded
[CHG] Controller C8:BC:C8:E9:DA:AA Discoverable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller C8:BC:C8:E9:DA:AA Discovering: yes
[CHG] Device 00:0A:95:3F:A8:DF RSSI: -74

[bluetooth]# pair 00:0A:95:3F:A8:DF
Attempting to pair with 00:0A:95:3F:A8:DF ->>> # not touching kb
Failed to pair: org.bluez.Error.AuthenticationTimeout
[CHG] Device 00:0A:95:3F:A8:DF RSSI: -55

[bluetooth]# pair 00:0A:95:3F:A8:DF
Attempting to pair with 00:0A:95:3F:A8:DF ->>> # input 1234
Failed to pair: org.bluez.Error.AuthenticationTimeout

[bluetooth]# pair 00:0A:95:3F:A8:DF
Attempting to pair with 00:0A:95:3F:A8:DF ->>> # input 0000
Failed to pair: org.bluez.Error.AuthenticationTimeout

[bluetooth]# pair 00:0A:95:3F:A8:DF
Attempting to pair with 00:0A:95:3F:A8:DF ->>> # input 000000
Failed to pair: org.bluez.Error.AuthenticationTimeout

[bluetooth]# exit
[DEL] Controller C8:BC:C8:E9:DA:AA mcmini-4_1-deb [default]


root@mcmini-4_1-deb:~# hidd --search
Searching ...
Connecting to device 00:0A:95:3F:A8:DF
Can't get device information: Function not implemented

root@mcmini-4_1-deb:~# dpkg -l | grep -i blue
ii bluez 5.43-1 amd64 Bluetooth tools and daemons
ii bluez-compat 4.99-2 amd64 BlueZ 3.x compatibility binaries
ii bluez-firmware 1.2-3 all Firmware for Bluetooth devices
ii bluez-hcidump 5.43-1 amd64 Analyses Bluetooth HCI packets ->>> (1)
ii gir1.2-gnomebluetooth-1.0:amd64 3.20.0-1 amd64 Introspection data for GnomeBluetooth
ii libbluetooth3:amd64 5.43-1 amd64 Library to use the BlueZ Linux Bluetooth stack
ii libgnome-bluetooth13:amd64 3.20.0-1 amd64 GNOME Bluetooth tools - support library

->>> (1) Bluetooth gave the same errors before installing this (Jessie) pckg
root@mcmini-4_1-deb:~#

# And this is part of journalctl -xb
...
Feb 02 18:03:58 mcmini-4_1-deb bluetoothd[4414]: vendor 0x0 product: 0x0
Feb 02 18:03:58 mcmini-4_1-deb bluetoothd[4414]: No agent available for request type 4
Feb 02 18:03:58 mcmini-4_1-deb bluetoothd[4414]: device_notify_pin: Operation not permitted
Feb 02 18:04:42 mcmini-4_1-deb bluetoothd[4414]: vendor 0x0 product: 0x0
Feb 02 18:04:42 mcmini-4_1-deb bluetoothd[4414]: No agent available for request type 4
Feb 02 18:04:42 mcmini-4_1-deb bluetoothd[4414]: device_notify_pin: Operation not permitted
...
Feb 02 18:05:38 mcmini-4_1-deb bluetoothd[4414]: vendor 0x0 product: 0x0
Feb 02 18:05:38 mcmini-4_1-deb bluetoothd[4414]: No agent available for request type 4
Feb 02 18:05:38 mcmini-4_1-deb bluetoothd[4414]: device_notify_pin: Operation not permitted
Feb 02 18:06:52 mcmini-4_1-deb bluetoothd[4414]: No agent available for request type 0
Feb 02 18:06:52 mcmini-4_1-deb bluetoothd[4414]: device_request_pin: Operation not permitted
...

Thanks for your attention. Regards, Ennio

[deloptes]

Ennio-Sr wrote:

> Thanks for your attention. Regards, Ennio

http://ubuntuforums.org/showthread.php?t=2276551
#!/bin/bash
bluetoothctl << EOF
power on
discoverable on
agent on
default-agent
pairable on
EOF

I think you missed agent on and so on

[Ennio-Sr]

* deloptes <delo...@gmail.com> [020217, 20:26]:

> Ennio-Sr wrote:
>
> > Thanks for your attention. Regards, Ennio
>
> http://ubuntuforums.org/showthread.php?t=2276551
>

> I think you missed agent on and so on

No, I can assure all commands were in order, including 'agent'.
In the meantime a look given to 'lsmod' in the older mcmini (the one
with squeeze ppc that paired with the kb) showed that there the
bluetooth mod was used, among others, by 'l2cap' and 'sco', which are
missing both in Jessie and Stretch kernel's modules.
OTAH I have no idea what those modules helped doing...

BTW, I red the suggested url, and so many others up to now and have no hope left ;-(

Thanks, Ennio

[deloptes]

Ennio-Sr wrote:

> No, I can assure all commands were in order, including 'agent'.
> In the meantime a look given to 'lsmod' in the older mcmini (the one
> with squeeze ppc that paired with the kb) showed that there the
> bluetooth mod was used, among others, by 'l2cap' and 'sco', which are
> missing both in Jessie and Stretch kernel's modules.
> OTAH I have no idea what those modules helped doing...
>
> BTW, I red the suggested url, and so many others up to now and have no
> hope left

Wait you say squeeze. The thing is bluetooth changed significantly since
squeeze. If I am not mistaken wheezy to jessie. So jessie has the new
version of bluez. You can read there what changed if interested.
did you have a look here?
http://askubuntu.com/questions/730316/apple-wireless-keyboard-wont-connect-in-15-10

and here they say to "trust", but well, this is after successfull pairing
http://askubuntu.com/questions/701978/how-can-a-bluetooth-keyboard-that-requires-a-code-entry-be-paired-in-the-termina

I am not familiar with bt keybards, but if it was working it should work in
stretch too. I spent time dealing with bt and my mobile phones. Now I use
blueman to manage the adapter, however I used also bluetoothctl several
times in the past. What happens if you try to connect and then pair?

FYI I have on jessie

blueman 1.99~alpha1-1+deb8u1
bluemon 1.4-6
bluetooth 5.23-2
bluez 5.23-2+b1
bluez-dbg 5.23-2+b1
bluez-firmware 1.2-3
bluez-hcidump 5.23-2+b1
bluez-obexd 5.23-2+b1
bluez-test-scripts 5.23-2
btscanner 2.1-5.1
libbluetooth-dev 5.23-2+b1
libbluetooth3:amd64 5.23-2+b1
libbluetooth3-dbg 5.23-2+b1
libgnome-bluetooth13 3.14.0-2
pulseaudio-module-bluetooth 5.0-13

[Ennio-Sr]

* deloptes <delo...@gmail.com> [020217, 23:34]:

> Ennio-Sr wrote:
>
> > No, I can assure all commands were in order, including 'agent'.

> > ...

Let me say it in one single word: 'GREAT!!!'

Following instructions reported in the first link solved the problem
(and I'm right now using the Wireless Keyboard :-)

My thanks are not enough to express my gratitude. Thank you so much
indeed. All the best for you and Heaven bless you!

[Ennio-Sr]

* Ennio-Sr <nasr....@tin.it> [030217, 00:46]:

> * deloptes <delo...@gmail.com> [020217, 23:34]:
> > Ennio-Sr wrote:
> >
> > did you have a look here?
> > http://askubuntu.com/questions/730316/apple-wireless-keyboard-wont-connect-in-15-10
> >
> > and here they say to "trust", but well, this is after successfull pairing
> > http://askubuntu.com/questions/701978/how-can-a-bluetooth-keyboard-that-requires-a-code-entry-be-paired-in-the-termina
> >

Sorry! I was so excited to forget to add 'Solved' to the subject....