Hi Dave, On 03/05/17 19:02, Robert Schneider wrote: > Hi, > I'm trying to get my KORG nanoKONTROL Studio working with the current > BlueZ stack (GIT as of May 3rd). > However, it seems the bonding fails for some reason. > > May 3 19:48:30 Maui bluetoothd[32743]: > src/adapter.c:bonding_attempt_complete() hci0 bdaddr 60:F1:89:28:DA:1F > type 1 status 0x5 > May 3 19:48:30 Maui bluetoothd[32743]: > src/device.c:device_bonding_complete() bonding (nil) status 0x05 > May 3 19:48:30 Maui bluetoothd[32743]: > src/device.c:device_bonding_failed() status 5 > May 3 19:48:30 Maui bluetoothd[32743]: src/adapter.c:resume_discovery() > May 3 19:48:30 Maui bluetoothd[32743]: src/adapter.c:dev_disconnected() > Device 60:F1:89:28:DA:1F disconnected, reason 2 > May 3 19:48:30 Maui bluetoothd[32743]: > src/adapter.c:adapter_remove_connection() > May 3 19:48:30 Maui bluetoothd[32743]: plugins/policy.c:disconnect_cb() > reason 2 > May 3 19:48:30 Maui bluetoothd[32743]: > src/adapter.c:bonding_attempt_complete() hci0 bdaddr 60:F1:89:28:DA:1F > type 1 status 0xe > May 3 19:48:30 Maui bluetoothd[32743]: > src/device.c:device_bonding_complete() bonding (nil) status 0x0e > May 3 19:48:30 Maui bluetoothd[32743]: > src/device.c:device_bonding_failed() status 14 > May 3 19:48:30 Maui bluetoothd[32743]: src/adapter.c:resume_discovery() > May 3 19:48:30 Maui bluetoothd[32743]: MIDI I/O: Failed to read initial > request > > I do not have any thorough bluetooth skill. Could somebody look at the > attached log and point me into some direction? > I restarted bluetoothd freshly with nothing in /var/lib/bluetooth. I looked into the log, and it appears that the driver is working correctly. It setups the profile for each device that it knows, it accepts the connection when that happens. Then it tries to make the initial MIDI I/O characteristic read, which returns an error. Apparently the nanoKONTROL is not allowing the central to read the initial value, which is defined in the specification as part of the connection procedure. Another problem I also noticed is that it does connect/disconnect very often, which might indicate a connection parameter problem. I am currently working on that at the Kernel level. To work-around it, try doing this[1] as described in my blog post. [1] https://blog.felipetonello.com/2017/01/13/midi-over-bluetooth-low-energy-on-linux-finally-accepted/ -- Felipe
Attachment:
0x92698E6A.asc
Description: application/pgp-keys
