From: Sailor Jerry <sailorjerry@scmarinetech.com>
To: linux-bluetooth@vger.kernel.org
Subject: HID problem on Raspberry PI (Failed to initialize gatt-client)
Date: Sat, 13 Feb 2021 15:57:55 -0800 [thread overview]
Message-ID: <CAFwzm1JbsDeQ-wtp+SH1V=iUT=PVKOX0WZYNWGd39SV0PPO3gQ@mail.gmail.com> (raw)
I'm trying to pair the remote control to the Raspberry PI running:
Linux 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux
The BT remote is connected and I see the input coming in btmon, but it
fails to appear as HID input.
This is the output of bluetoothd:
src/gatt-client.c:btd_gatt_client_connected() Device connected.
src/adapter.c:new_conn_param() hci0 C7:A3:E8:B2:B1:EB (1) min 0x0006
max 0x0006 latency 0x0063
src/device.c:gatt_debug() MTU exchange complete, with MTU: 23
src/device.c:gatt_debug() Primary services found: 5
src/device.c:gatt_debug() start: 0x0001, end: 0x0004, uuid:
00001801-0000-1000-8000-00805f9b34fb
src/device.c:gatt_debug() start: 0x0005, end: 0x000b, uuid:
00001800-0000-1000-8000-00805f9b34fb
src/device.c:gatt_debug() start: 0x000c, end: 0x000e, uuid:
0000180a-0000-1000-8000-00805f9b34fb
src/device.c:gatt_debug() start: 0x000f, end: 0x0027, uuid:
00001812-0000-1000-8000-00805f9b34fb
src/device.c:gatt_debug() start: 0x002b, end: 0x002f, uuid:
00010203-0405-0607-0809-0a0b0c0d1912
src/device.c:gatt_debug() Characteristics found: 3
src/device.c:gatt_debug() start: 0x0028, end: 0x002b, value: 0x0029,
props: 0x12, uuid:
src/device.c:gatt_debug() start: 0x002c, end: 0x002d, value: 0x002d,
props: 0x06, uuid:
src/device.c:gatt_debug() start: 0x002e, end: 0x002f, value: 0x002f,
props: 0x02, uuid:
src/device.c:gatt_debug() Failed to insert characteristic at 0x0029
src/device.c:gatt_debug() service disappeared: start 0x002b end 0x002f
src/device.c:gatt_debug() Failed to initialize gatt-client
src/device.c:gatt_client_ready_cb() status: failed, error: 10
src/device.c:device_svc_resolved() /org/bluez/hci0/dev_C7_A3_E8_B2_B1_EB err -5
reply other threads:[~2021-02-13 23:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFwzm1JbsDeQ-wtp+SH1V=iUT=PVKOX0WZYNWGd39SV0PPO3gQ@mail.gmail.com' \
--to=sailorjerry@scmarinetech.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).