| [AD] Problems with keyboard |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
I'm having problems with the keyboard in Debian Sarge.
Before, when I have Debian Woody (stable), all works fine, now that I
updated some packages to Debian Sarge (testing) all start going
wrong. The main problem is when I execute an Allegro (4.0.3) program
in the console (not in X), the result of some key pressed are:
Key pressed: <a>
readkey = 0x00001e61 (7777)
ascii = 0x61 (97)
scancode = 0x1e (30) [KEY 3]
Key pressed: <s>
readkey = 0x00001f73 (8051)
ascii = 0x73 (115)
scancode = 0x1f (31) [KEY 4]
Key pressed: <d>
readkey = 0x00002064 (8292)
ascii = 0x64 (100)
scancode = 0x20 (32) [KEY 5]
Key pressed: <f>
readkey = 0x00002166 (8550)
ascii = 0x66 (102)
scancode = 0x21 (33) [KEY 6]
Key pressed: <ESC>
readkey = 0x0000011b (283)
ascii = 0x1b (27)
scancode = 0x01 (1) [KEY A]
Key pressed: <F1>
readkey = 0x00003b00 (15104)
ascii = 0x00 (0)
scancode = 0x3b (59) [KEY ESC]
I don't know if this can be useful:
Linux 2.4.19 i586
console-tools 0.2.3
$ getkeycodes
Plain scancodes xx (hex) versus keycodes (dec)
0 is an error; for 1-88 (0x01-0x58) scancode equals keycode
0x58: 88 89 125 126 127 0 0 0
0x60: 0 0 0 0 0 0 0 0
0x68: 0 0 0 0 0 122 0 123
0x70: 0 0 0 89 120 0 0 90
0x78: 91 92 93 94 95 124 121 0
Escaped scancodes e0 xx (hex)
e0 00: 0 0 0 0 0 0 0 0
e0 08: 0 0 0 0 0 0 0 0
e0 10: 0 0 0 0 0 0 0 0
e0 18: 0 0 0 0 96 97 0 0
e0 20: 0 0 0 0 0 0 0 0
e0 28: 0 0 0 0 0 0 0 0
e0 30: 0 0 0 0 0 98 0 99
e0 38: 100 0 0 0 0 113 114 115
e0 40: 116 117 0 0 0 0 101 102
e0 48: 103 104 0 105 124 106 118 107
e0 50: 108 109 110 111 0 0 0 0
e0 58: 0 0 0 125 126 127 0 0
e0 60: 0 0 0 0 0 0 0 0
e0 68: 0 0 0 0 0 0 0 112
e0 70: 0 0 0 0 0 0 0 0
e0 78: 0 0 0 0 0 0 0 0
PS: Someone can tell me what should be the getkeycodes output?
--
http://www.davidcapello.com.ar