Further on my problem getting Ctrl to work on my dinovo mini, here's a xev output:

KeyPress event, serial 40, synthetic NO, window 0x3e00001,
root 0x44, subw 0x0, time 109249971, (598,205), root598,261),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 41, synthetic NO, window 0x3e00001,
root 0x44, subw 0x0, time 109250161, (598,205), root598,261),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

A successful key (TAB as an example) looks like this


KeyPress event, serial 26, synthetic NO, window 0x3e00001,
root 0x44, subw 0x0, time 109423817, (598,205), root598,261),
state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
XLookupString gives 1 bytes: (09) " "
XmbLookupString gives 1 bytes: (09) " "
XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3e00001,
root 0x44, subw 0x0, time 109424025, (598,205), root598,261),
state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
XLookupString gives 1 bytes: (09) " "
XFilterEvent returns: False


Does anyone know anything about XLookupString and why it is failing for Ctrl?

Anyway I can observe happens when I press the Ctrl on the N900s keyboard? (xev does not seem to log keypresses on the device itself!)

Thanks