|
2010-10-14
, 07:27
|
|
Posts: 4,365 |
Thanked: 2,467 times |
Joined on Jan 2010
@ Australia Mate
|
#202
|
|
2010-10-14
, 18:38
|
Posts: 992 |
Thanked: 738 times |
Joined on Jun 2010
@ Low Earth Orbit
|
#203
|
- if I use the setxkbmap command, the keyboard does work, including the number keys.
If I use the watcher script (v0.10), the number keys do not work.
Also, I had an apple wireless keyboard, and I couldn't get bt-dbus-connect to work, so I examined the script, and saw that it searches for device names with "mouse" or "keyboard" in it, and my keyboard was named ikey, so I changed that to iKeyboard, and worked flawlessly.
The Following User Says Thank You to kureyon For This Useful Post: | ||
|
2010-10-15
, 06:32
|
Posts: 561 |
Thanked: 75 times |
Joined on Jan 2010
@ Spain
|
#204
|
WhiteWolf: we need to diagnose a bit more. Your internal keyboard numbers aren't working, that means your internal keyboard is probably not being configured at all (the script must fail).
Please do not start the watcher, connect your BT keyboard, and then, from the terminal, run the following:
Please post the output from this script.Code:bt-kbd-remap
~ $ bt-kbd-remap Int: (3) Ext: (4) --- Setting ext keyboard layout: setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model pc105 -layout us -print | xkbcomp - :0.0 --- setxkbmap -device 3 Trying to build keymap using the following components: keycodes: evdev+aliases(qwerty) types: complete+nokia compat: complete symbols: nokia_vndr/rx-51(common)+nokia_vndr/rx-51(us)+inet(evdev) geometry: nokia(nokiarx51)
|
2010-10-15
, 20:37
|
Posts: 19 |
Thanked: 7 times |
Joined on Dec 2009
|
#205
|
I have the same but I lost my driver/manual CD. I don't even know how to put it in pairing mode. Idiot me
And because there is no manufacturer anywhere on the thing, I have no clue where to start looking for a copy.
Care to share how you got them talking together and configured with the correct layout ?
Thanks !
The Following User Says Thank You to splandorf For This Useful Post: | ||
|
2010-10-17
, 10:02
|
Posts: 561 |
Thanked: 75 times |
Joined on Jan 2010
@ Spain
|
#206
|
|
2010-10-21
, 17:30
|
Posts: 182 |
Thanked: 69 times |
Joined on Nov 2009
@ Netherlands
|
#207
|
OK
When Watcher script is running, and then you connect the keyboard do you get a message saying that "keyboard connected"? If not, then Watcher is not detecting your keyboard and hence not running setxkbmap and hence doesn't work. Could it be similar to the problem snakekontrol had?:
|
2010-10-21
, 21:38
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#208
|
It does not, so I suppose the keyboard is not detected. I tried renaming it in the Bluetooth menu, that didn't help.
(I now made a QB widget with the setxkbmap command, that seems to work.)
The Following User Says Thank You to qole For This Useful Post: | ||
|
2010-10-22
, 08:41
|
Posts: 182 |
Thanked: 69 times |
Joined on Nov 2009
@ Netherlands
|
#209
|
Make sure your name has "keyboard" in the name. That's what the watcher script is looking for.
|
2010-10-22
, 14:12
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#210
|
Note that the original name does contain 'Keyboard', but with a capital letter. Would that matter?
The Following User Says Thank You to qole For This Useful Post: | ||
- if I use the setxkbmap command, the keyboard does work, including the number keys.
- If I use the watcher script (v0.10), the number keys do not work.
Thanks for the patient answer though.