On Thu, 17 Jan 2008, Taneli Vähäkangas wrote: > Thanks for prompt reply Jiri. Now I get some information for extra > function keys at the top row, but still nothing for the "piano" keys.
That's strange. Could you please try to snoop the traffic on USB, to see if the keys that don't produce any HID debugging output at all at least produce some USB traffic? See Documentation/usb/usbmon.txt for details. > Here's the output for two previously non-functioning keys: > Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report (size 4) > (numbered) > Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report 4 (size 3) = 02 > 00 00 > Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0 > Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 1 > Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0 > Jan 17 00:27:13 newer last message repeated 13 times > Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report (size 4) > (numbered) > Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report 4 (size 3) = 00 > 00 00 > Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0 > Jan 17 00:27:13 newer last message repeated 15 times Hmm, this looks only like output for on key, is it really for two? > Is this the information you asked? I can make you the full mapping of > non-working keys to log messages. However, I don't think that's very > useful if the "piano" keys don't work, as they're the main reason for > having such a keyboard in the first place. Yes, we'll need to figure out where the data from these keys are getting lost. > (I think all the log entries after 00:23:59 are key presses, but > couldn't tell for sure.) Yes, they are. > BTW, here's a picture of the keyboard in question ... just in case my > descriptions don't seem to make sense: > http://images.tw.creative.com/images/corporate/artwork/hires_prodikeyspcmidiusb.jpg Could it be that the keyboard is a totally separate device? Does alsa report anything, when you connect it, for example? -- Jiri Kosina
