Hi
Yes, there is something rather odd in system logs :(
Trying to connect with bluetooth using feature pack gives the following
messages:
Mar 5 21:55:33 milliways brltty[28409]: Error while initializing socket 0
Mar 5 21:55:33 milliways brltty[28409]: kernel module not installed:
pcspkr
Mar 5 21:55:34 milliways hcid[27953]: pin_code_request
(sba=00:1E:4C:DB:BB:C1, dba=00:A0:96:2A:E7:5F)
Mar 5 21:55:34 milliways brltty[28409]: RFCOMM socket connect error 111:
Connection refused.
Mar 5 21:55:34 milliways brltty[28409]: NoSpeech Speech Driver:
Mar 5 21:55:40 milliways hcid[27953]: pin_code_request
(sba=00:1E:4C:DB:BB:C1, dba=00:A0:96:2A:E7:5F)
Mar 5 21:55:40 milliways brltty[28409]: RFCOMM socket connect error 111:
Connection refused.
Mar 5 21:55:46 milliways hcid[27953]: pin_code_request
(sba=00:1E:4C:DB:BB:C1, dba=00:A0:96:2A:E7:5F)
Mar 5 21:55:46 milliways brltty[28409]: RFCOMM socket connect error 111:
Connection refused.
Mar 5 21:55:52 milliways hcid[27953]: pin_code_request
(sba=00:1E:4C:DB:BB:C1, dba=00:A0:96:2A:E7:5F)
Mar 5 21:55:52 milliways brltty[28409]: RFCOMM socket connect error 111:
Connection refused.
The last two messages are being printed continuously.
Perhaps there is something wrong with authentication?
Btw, when I connected the display and feature pack via USB, system log
tells that the system has detected HID keyboard. When I press any key of
that keyboard, the only result is a number of more log messages saying
[brltty] Ignoring bytes XX (XX seems to be a hexa code).
-Teemu K
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://mielke.cc/mailman/listinfo/brltty
