Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #226063
| From | George Shuklin <george.shuklin@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | No scancodes for some buttons |
| Date | 2020-08-10 15:10 +0200 |
| Message-ID | <ACfIR-6Ab-1@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
I've got a very odd wireless keyboard. It look like TV remote, but is an actual keyboard inside. Some buttons work perfectly (VolumeUp, VolumeDown), some are not. I've dug into this topic, and found that there is a set of buttons which does not produce both scancodes and input events (scancodes in console ignores them, evtest ignores them). As the last effort I used usmon kernel module and Wireshark, and I found that 'silent' keys are actually cause the same number of USB events as working ones. The problem is that I have no idea how to read wireshark/usb output. I've started from 'working keys' and I can't understand a thing. What is URB? How to read dump if I can't find a 'button code' (for working keys) in the dump? Can someone help me with 101 on usb keyboards? Some kind of high-level overview with terminology, etc...
Back to linux.debian.user | Previous | Next | Find similar | Unroll thread
No scancodes for some buttons George Shuklin <george.shuklin@gmail.com> - 2020-08-10 15:10 +0200
csiph-web