[SOLVED] LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

[SOLVED] LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Mon Sep 08, 2014 10:45 pm

Hi guys,
I searched around on the internet for a while but I cannot seem to find a solution to this :evil:

I was using my Microsoft Bluetooth Mobile Keyboard 6000 with Linux Mint 15 no problems, however after migrating from 15 to Linux Mint 17 the keyboard can no longer pair.
* see attached picture *

I know the device is detected by bluetooth

Code: Select all

$ hcitool scan
Scanning ...
	7C:1E:52:A9:43:01	Microsoft Bluetooth Mobile Keyboard 6000
Attempting to connect to the device via the terminal didn't work either, I don't know the pin code of my device, usually I let Linux Mint select the pin code automatically.
I believe linux mint 15 usually tries the following pin codes (0000, 1111, 1234) with success, the connection times out in each case (see attached file).

I know the keyboard is still working as I have tested it on another device.
I know my laptops bluetooth is still working with linux mint 17 as I have paired my laptop with other devices.


I dont really know how to continue investigating the problem on my own, maybe a more experienced linux mint user or dev can offer some advice?

Thanks!
Attachments
attempting to pair device via terminal
attempting to pair device via terminal
Error message when attempting to pair: Microsoft Bluetooth Mobile Keyboard 6000
Error message when attempting to pair: Microsoft Bluetooth Mobile Keyboard 6000
Last edited by LoveMIntLinux on Sat Sep 13, 2014 3:38 pm, edited 1 time in total.

User avatar
PatH57
Level 13
Level 13
Posts: 4576
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by PatH57 » Tue Sep 09, 2014 4:25 am

looks like the agent may not be running

Code: Select all

bluez-simple-agent
leave it open and then, try to pair it again using the Bluetooth settings in system settings.
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Tue Sep 09, 2014 7:53 am

PatH57 wrote:looks like the agent may not be running

Code: Select all

bluez-simple-agent
leave it open and then, try to pair it again using the Bluetooth settings in system settings.
Thanks for the response PatH.
I restarted my computer and ran the following:

Code: Select all

lm17@lm17 ~ $ bluez-simple-agent
Traceback (most recent call last):
  File "/usr/bin/bluez-simple-agent", line 138, in <module>
    adapter.RegisterAgent(path, capability)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.AlreadyExists: Already Exists
Regardless of the error message I attempted to pair the device as I usually would and pairing failed as it did in my original post.
Remember that pairing between Linux Mint 17 and other devices (my Samsung Galaxy) works fine, it is just pairing with the keyboard that doesn't work.
Pairing between the keyboard and other devices (e.g same machine running Linux Mint 15 and my smartphone) also works fine - implying there is some software based bug in Linux Mint 17 which wasn't present in Linux Mint 15 which is preventing pairing between the OS and device.

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Tue Sep 09, 2014 8:18 am

The output of hcidump -at when running the following commands:
http://forums.linuxmint.com/download/fi ... &mode=view

is here http://pastebin.com/Qkg5T8kK

The error occurs after selecting pin codes (see below) exactly same output with pin codes 1111 and 1234 (see the pastebin file).
The same default pin code selection works fine with Linux Mint 15, when pairing the keyboard with my phone a pin code is not required for pairing (leading me to assume the pin code of the keyboard is one of the default: 1111, 1234, or 0000).

Code: Select all

2014-09-09 13:10:29.646193 < HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
    bdaddr 7C:1E:52:A9:43:01 len 4 pin '0000'
2014-09-09 13:10:29.651820 > HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
2014-09-09 13:11:00.055612 > HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
2014-09-09 13:11:00.056485 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout

User avatar
PatH57
Level 13
Level 13
Posts: 4576
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by PatH57 » Tue Sep 09, 2014 10:50 am

let's try to force it

Code: Select all

bluez-simple-agent hci0 7C:1E:52:A9:43:01
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Tue Sep 09, 2014 1:49 pm

PatH57 wrote:let's try to force it

Code: Select all

bluez-simple-agent hci0 7C:1E:52:A9:43:01
Thanks for the quick response:

Code: Select all

lm17@lm17 ~ $ bluez-simple-agent hci0 7C:1E:52:A9:43:01
RequestPinCode (/org/bluez/727/hci0/dev_7C_1E_52_A9_43_01)
Enter PIN Code: 1111
Creating device failed: org.bluez.Error.ConnectionAttemptFailed: Connection Timeout
lm17@lm17 ~ $ bluez-simple-agent hci0 7C:1E:52:A9:43:01
RequestPinCode (/org/bluez/727/hci0/dev_7C_1E_52_A9_43_01)
Enter PIN Code: 1234
Creating device failed: org.bluez.Error.ConnectionAttemptFailed: Connection Timeout
lm17@lm17 ~ $ bluez-simple-agent hci0 7C:1E:52:A9:43:01
RequestPinCode (/org/bluez/727/hci0/dev_7C_1E_52_A9_43_01)
Enter PIN Code: 0000
Creating device failed: org.bluez.Error.ConnectionAttemptFailed: Connection Timeout
lm17@lm17 ~ $ 
and the hcidump:

Code: Select all

lm17@lm17 ~ $ hcidump -at
HCI sniffer - Bluetooth packet analyzer ver 2.5
device: hci0 snap_len: 1500 filter: 0xffffffff
2014-09-09 18:40:13.511937 > HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
2014-09-09 18:40:13.810028 > HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 7C:1E:52:A9:43:01 type ACL encrypt 0x00
2014-09-09 18:40:13.811969 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
2014-09-09 18:40:13.812930 > HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
2014-09-09 18:40:13.815011 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2014-09-09 18:40:13.849990 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 7C:1E:52:A9:43:01 name 'Microsoft Bluetooth Mobile Keyboard 6000'
2014-09-09 18:40:13.851928 > HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
2014-09-09 18:40:13.853989 > HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
2014-09-09 18:40:16.566035 > HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
2014-09-09 18:40:46.738716 > HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
2014-09-09 18:40:46.739721 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout
2014-09-09 18:40:58.024624 > HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
2014-09-09 18:40:58.745746 > HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 7C:1E:52:A9:43:01 type ACL encrypt 0x00
2014-09-09 18:40:58.747665 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
2014-09-09 18:40:58.748624 > HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
2014-09-09 18:40:58.750663 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2014-09-09 18:40:58.782689 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 7C:1E:52:A9:43:01 name 'Microsoft Bluetooth Mobile Keyboard 6000'
2014-09-09 18:40:58.784710 > HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
2014-09-09 18:40:58.787619 > HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
2014-09-09 18:41:00.859657 > HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
2014-09-09 18:41:31.097515 > HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
2014-09-09 18:41:31.098413 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout
2014-09-09 18:41:35.393386 > HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
2014-09-09 18:41:36.778497 > HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 7C:1E:52:A9:43:01 type ACL encrypt 0x00
2014-09-09 18:41:36.780375 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
2014-09-09 18:41:36.781371 > HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
2014-09-09 18:41:36.783436 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2014-09-09 18:41:36.818434 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 7C:1E:52:A9:43:01 name 'Microsoft Bluetooth Mobile Keyboard 6000'
2014-09-09 18:41:36.820391 > HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
2014-09-09 18:41:36.822459 > HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
2014-09-09 18:41:39.147492 > HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
2014-09-09 18:42:09.845158 > HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
2014-09-09 18:42:09.846155 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Tue Sep 09, 2014 2:11 pm

I ran hcidump -a while running the bluetooth wizard (receiving the same error message from the wizard as in the original post image)

Code: Select all

HCI sniffer - Bluetooth packet analyzer ver 2.5
device: hci0 snap_len: 1500 filter: 0xffffffff
> HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout
In every case (whether it be terminal commands or bluetooth wizard) the error seems to be "LMP Response Timeout".

User avatar
PatH57
Level 13
Level 13
Posts: 4576
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by PatH57 » Wed Sep 10, 2014 3:01 am

check this
https://bugs.launchpad.net/ubuntu/+sour ... ug/1035431
some people got it fixed using a ppa and backported gnome-bluetooth - 3.8.2.1-0ubuntu9 (the one in synaptic is gnome-bluetooth - 3.8.2.1-0ubuntu4) or with kernel 3.16.1.
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Wed Sep 10, 2014 7:28 pm

PatH57 wrote:check this
https://bugs.launchpad.net/ubuntu/+sour ... ug/1035431
some people got it fixed using a ppa and backported gnome-bluetooth - 3.8.2.1-0ubuntu9 (the one in synaptic is gnome-bluetooth - 3.8.2.1-0ubuntu4) or with kernel 3.16.1.
I ran the following while in root and restarted my computer:

Code: Select all

add-apt-repository -y ppa:timchen119/bluez4-ssp && apt-get update && apt-get install gnome-bluetooth bluez
The problem does not seem to have been solved, I'm not sure how to proceed from here :(
Do you think that this problem warrants a bug report submission on launchpad?

EDIT: I haven't tried upgrading from kernel 3.13.0-24-generic to 3.16.1, doing that now and will get back to you here.

User avatar
PatH57
Level 13
Level 13
Posts: 4576
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by PatH57 » Thu Sep 11, 2014 1:48 am

let's see how the kernel upgrade works.
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Thu Sep 11, 2014 7:39 pm

PatH57 wrote:let's see how the kernel upgrade works.
Upgraded to Kernel 3.16.2-031602-generic and pairing still isn't working.

Initially tried with the bluetooth wizard with hcidump -a running in the background:

Code: Select all

lm17@lm17 ~ $ hcidump -a
HCI sniffer - Bluetooth packet analyzer ver 2.5
device: hci0 snap_len: 1500 filter: 0xffffffff
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 7C:1E:52:A9:43:01 mode 1 clkoffset 0x73e7 class 0x002540 rssi -65
> HCI Event: Command Complete (0x0e) plen 4
    Inquiry Cancel (0x01|0x0002) ncmd 1
    status 0x00
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 7C:1E:52:A9:43:01 type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 7C:1E:52:A9:43:01 name 'Microsoft Bluetooth Mobile Keyboard 6000'
> HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
> HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
> HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout
I then tried the bluez-simple-agent hci0 7C:1E:52:A9:43:01 command
hcidump -a:

Code: Select all

lm17@lm17 ~ $ hcidump -a
HCI sniffer - Bluetooth packet analyzer ver 2.5
device: hci0 snap_len: 1500 filter: 0xffffffff
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 7C:1E:52:A9:43:01 type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 7C:1E:52:A9:43:01 name 'Microsoft Bluetooth Mobile Keyboard 6000'
> HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
> HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
> HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 7C:1E:52:A9:43:01 type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 7C:1E:52:A9:43:01 name 'Microsoft Bluetooth Mobile Keyboard 6000'
> HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
> HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
> HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 7C:1E:52:A9:43:01 type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 7C:1E:52:A9:43:01 name 'Microsoft Bluetooth Mobile Keyboard 6000'
> HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
> HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 7C:1E:52:A9:43:01
> HCI Event: Auth Complete (0x06) plen 3
    status 0x22 handle 12
    Error: LMP Response Timeout
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x22
    Reason: LMP Response Timeout

Very frustrating, it looks like I am not the only one with bluetooth problems on LM 17:
http://forums.linuxmint.com/viewtopic.php?f=49&t=168079

User avatar
PatH57
Level 13
Level 13
Posts: 4576
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by PatH57 » Fri Sep 12, 2014 2:28 am

have seen this one also
did you try the suggested:

Code: Select all

pactl load-module module-bluetooth-discover
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Fri Sep 12, 2014 12:49 pm

PatH57 wrote:have seen this one also
did you try the suggested:

Code: Select all

pactl load-module module-bluetooth-discover
I get the following error:

Code: Select all

$ load-module module-bluetooth-discover
Failure: Module initialisation failed

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Fri Sep 12, 2014 1:07 pm

By complete fluke I managed to fix the problem:

Code: Select all

lm17@lm17 ~ $ bluez-simple-agent hci0 7C:1E:52:A9:43:01
RequestPinCode (/org/bluez/727/hci0/dev_7C_1E_52_A9_43_01)
Enter PIN Code: 0000
At this point enter 0000 into the keyboard and press enter.
Then run the following commands to link the keyboard to the OS:

Code: Select all

sudo hciconfig hci0 up
sudo hidd --connect 7C:1E:52:A9:43:01
Not sure how this works, but it does so I am going to run with it. :D :D :D

EDIT:
Alternatively I can use the bluetooth GUI, but I have to keep pressing 0000 [ENTER] on the keyboard while the GUI shows the loading screen for connecting to the keyboard.

User avatar
PatH57
Level 13
Level 13
Posts: 4576
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by PatH57 » Fri Sep 12, 2014 3:49 pm

seems the combination of force (witch we tried) and the new kernel may have done the trick?
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Fri Sep 12, 2014 7:25 pm

PatH57 wrote:seems the combination of force (witch we tried) and the new kernel may have done the trick?
Nope, I made a fresh installation of Linux Mint 17 and the latest version of Ubuntu - same deal with both.
The keyboard wouldn't pair until I entered 1111 [ENTER] into the keyboard AFTER the 1111 pincode had been sent from bluetooth on the OS to the keyboard.

Note: before I used the 0000 pincode to unlock the keyboard now I used 1111.
It seems like it doesnt matter what pincode you send from the OS to the device as long as you reciporicate that by entering the same pincode into the device and pressing enter.
This seems like a very strage phenomenon it would be good if somebody could replicate.

User avatar
PatH57
Level 13
Level 13
Posts: 4576
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by PatH57 » Sat Sep 13, 2014 2:06 am

It seems like it doesnt matter what pincode you send from the OS to the device as long as you reciporicate that by entering the same pincode into the device and pressing enter
that sounds normal to me, I kind of assumed it was what you were doing? I have 3 phones that I connect using bluetooth and on all I have to enter the same pin code as the one displayed on Mint 17 (else anyone could just connect to them) It may have now been enforced for all items including kb.
Edit: tried a logitech kb on Mint 13 no need to enter pin, on Mint 17 had to enter pin.
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.

LoveMIntLinux
Level 1
Level 1
Posts: 30
Joined: Mon Sep 08, 2014 10:22 pm

Re: LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by LoveMIntLinux » Sat Sep 13, 2014 3:50 pm

PatH57 wrote:
It seems like it doesnt matter what pincode you send from the OS to the device as long as you reciporicate that by entering the same pincode into the device and pressing enter
that sounds normal to me, I kind of assumed it was what you were doing? I have 3 phones that I connect using bluetooth and on all I have to enter the same pin code as the one displayed on Mint 17 (else anyone could just connect to them) It may have now been enforced for all items including kb.
Edit: tried a logitech kb on Mint 13 no need to enter pin, on Mint 17 had to enter pin.
No, previously the pass key that I enter into the keyboard is one which is displayed on the screen on the laptop for me to submit - the passkey is different 4 - 5 digit integer every time you pair the keyboard.
Prior to being shown the passkey by the GUI in LM 15 I have to enter a pincode into the bluetooth GUI (which I leave as default):

LM 15
Open bluetooth GUI -> select device to pair -> enter pin code into GUI -> loading takes place -> 5 digit number appears on OS screen, instructions to enter this into the keyboard and press enter -> pairing complete

However currently (LM 17) I enter the pin code into the GUI then while the pairing process is taking place I enter the same pin code into the keyboard and press enter.
In LM 15 I would wait for the GUI to show me the aforementioned 4 - 5 digit integer which I would enter into the keyboard then pairing would complete:

LM 17
Open bluetooth GUI -> select device to pair -> enter pin code into GUI -> loading takes place -> enter pin code into keyboard and press enter (there are no instructions indicating that I have to do this, up to this point everything displayed on the GUI is the same as what was shown in LM 15) -> pairing complete

I am sure this can be replicated as I have been using fresh installations of Linux Mint 17 and 15 - but it works so I can't complain.
Unfortunately I cannot get screenshots because I have removed my LM 15 installation.

Thanks for your help PatH

Note:
A quote from another thread describing pairing bluetooth devices in linux:
http://forums.linuxmint.com/viewtopic.php?f=42&t=125166

Code: Select all

Now in the hcidump terminal you will see a few things scroll past until you get something that looks like:
2013-02-07 15:35:40.653393 > HCI Event: User Passkey Notification (0x3b) plen 10
bdaddr XX:XX:XX:XX:XX:XX passkey xxxxxx

Type the 'passkey' in and press ENTER
I do not get the 'passkey xxxxx' string in my hcidump -a (as documented in this thread).
This paskey xxxx value is the integer which (in LM 15) is displayed in the bluetooth GUI with instructions to enter the integer into the keyboard and press enter.
In my case I simply enter the pincode and press enter.

User avatar
PatH57
Level 13
Level 13
Posts: 4576
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Re: [SOLVED] LM 15 -> 17, Bluetooth Keyboard Cannot Pair

Post by PatH57 » Sun Sep 14, 2014 1:56 am

so it it still a bug (it's not working as expected) but seems to affect only some kb (my logitec one is fine)
Did you fill a bug report? or submit your workaround? it could help others.
I would open another thread with subject: your kb Mint 17 pairing bluetooth [solved]
and describe your steps.
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.

Post Reply

Return to “Hardware Support”