On Fri, 7 Aug 2009, Lamarque Vieira Souza wrote: > > > > - compile the kernel with CONFIG_HID_DEBUG option set > > - modprobe the 'hid' module with 'debug=2' option > > > > and provide the dmesg output that appears when the device is > > connected (so that we have contents of the HID report descriptor and > > kernel interpretation of it) and also after the data packet containing the > > mentioned sequence has been received? > Here is the dmesg output. The mouse constantly emmits those 9-bytes frames > even if I do not touch it, which probably is why it also affects my notebook's > touchpad. Hi, what kernel is this? The log seems to be very incomplete. What I am missing the most is - report descriptor dump and interpretation (we can see that the report descriptor has been successfully parsed at 408673.371808, but we don't see the descriptor dump before -- maybe it scrolled away already?) - The interpretation of input data is missing (no "hid-input" line as result of hid_dump_input() being called through hid_input_field()->hid_process_event()). Are you sure you have modprobe the hid module with 'debug=2' parameter? Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
