Hi, I got it to work with mine, by copying the bluetooth link key. Here is what I did:
- Find the bluetooth address of the PC/dongle (let's say AA:11:11:11:11:11).
- Find the bluetooth address of the keyboard (let's say BB:22:22:22:22:22).
- Pair the device normally, under Linux (via the Gnome panel).
There should be a file called /var/lib/bluetooth/AA:11:11:11:11:11/linkkeys, which contains a line like this:
Here, xxxx is 16 bytes written continuously in hexadecimal, that's the link key.
BB:22:22:22:22:22 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0 6
- Pair the device normally, under Windows (this will change the key). Get the key from Windows. In my case, it was in this registry entry:
Unfortunately, RegEdit says "access is denied" when I get to Keys, even when logged on as administrator. (I suppose it might be in another ControlSet in some cases.)
- Reboot under Linux, install chntpw. The version packaged with Lucid (0.99.5) doesn't seem to support registry in 64-bit. The latest version in the Debian repo (0.99.6-2) worked for me.
- To avoid unwanted modifications of the Windows registry from Linux, I've copied the SYSTEM file somewhere else, from: /path/to/Windows/System32/config/SYSTEM
- I've then opened it with chntpw (browse registry with ls/cd; help with ?):
chntpw -e SYSTEM
> cd ControlSet002\services\BTHPORT\Parameters\Keys
> cd aa1111111111
> hex bb2222222222
This produces something like this:
:00000 xx xx xx xx xx xx xx
Here, "xx xx xx" is another 16 bytes, in hexadecimal, represented the link key set up in Windows.
Finally, I copied that (and removed the spaces) to replace the value already in /var/lib/bluetooth/AA:11:11:11:11:11/linkkeys.
I had to disconnect and reconnect (via the Gnome applet), but I had to do that sometimes anyway. (It doesn't seem to work before being logged on either, but that the same, it was happening even with being paired under Linux only. That's probably a different problem.)
It worked for me. It's probably a bit complex for people who are not comfortable editing config files. I think it's safer to work on a copy of the SYSTEM registry file too, just in case something goes wrong.