0

I connect (using console approach, gui doesn't work) "ThinkPad Compact Bluetooth Keyboard" (US layout) to thinkpad t420.

Trackpoint on this external keyboard and most of the buttons work well, except -, p, 0, [ not recognized at all, and pressing / outputs a sequence smth like "bn/". Sometimes, if press p and some other symbols, then p is also printed.

Here is the output of xinput -list (notice that there is no second keyboard, but there is a new slave pointer -- it is marked with ** below):

⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=13   [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                     id=14   [slave  pointer  (2)]
⎜   ↳ **ThinkPad Compact Bluetooth Keyboard with TrackPoint id=15   [slave  pointer  (2)]**
⎣ Virtual core keyboard                     id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
    ↳ Integrated Camera                         id=10   [slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                    id=12   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=11   [slave  keyboard (3)]

So far:

  • tried changing layout (via keyboard layout settings), but no luck.
  • tried showkey --scancodes on that problematic symbols: returns nothing!

If we cannot get even scancodes -- does it mean no chance to get them working? (i mean no "easy" way, writing a driver is not considered.)

Any ideas?

(running Ubuntu 12.04)

This question is related (about need to press Fn to make work f1-f12), but also not answered.

7
  • If you google some more you will find out that without a linux driver it won't work. e.g. link. Maybe write to Lenovo, and send them this link from their own forum. But I doubt they would do anything.
    – falconer
    Dec 14, 2013 at 19:42
  • Or file a bug against the Bluez link.
    – falconer
    Dec 14, 2013 at 19:58
  • @falconer thanks for the link! it inspired to try schowkey. Although your link doesn't have my problem of not recognizing the symbols 'p','0', etc.
    – Ayrat
    Dec 14, 2013 at 20:46
  • Hmm. Did you try this keyboard on other computers? And if showkey --scancodes returns nothing please also look in the /var/log/syslog file whether it reports unkown keys, like "atkbd serio0: Unknown key pressed (translated set 2, code 0x55 on isa0060/serio0)"
    – falconer
    Dec 14, 2013 at 21:00
  • @falconer 1) haven't tried, but will try, looks suspicious, 2) No such messages or others 'suspicious' mentioning 'key' or 'pressed' or 'unknown' in any of /var/log/*.log files
    – Ayrat
    Dec 14, 2013 at 21:25

1 Answer 1

0

Based on comments with Ayrat we deduced that the particular keyboard is defective.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .