From: Isaac M. B. <isa...@ud...> - 2014-10-29 16:47:52
|
I tried with the hid-recorder but there are no events when I move the pen. sudo hid-recorder -d /dev/hidraw6 R: 215 05 0d 09 02 a1 01 85 02 09 02 a1 00 05 01 09 30 09 31 15 00 26 80 07 35 00 46 00 78 65 11 55 0e 75 10 95 02 81 02 05 0d 09 42 09 45 09 44 09 32 15 00 25 01 75 01 95 04 65 00 81 02 05 09 19 01 29 04 15 00 25 01 75 01 95 04 81 02 05 0d 09 30 15 00 26 00 04 75 10 95 01 81 02 05 0d 09 3d 09 3e 15 81 25 7f 75 08 95 02 81 02 c0 05 01 09 00 85 04 15 00 26 ff 00 75 08 95 0c 81 02 05 01 09 00 85 08 15 00 26 ff 00 75 08 95 3b 81 02 09 01 85 80 75 08 95 20 b1 02 c0 05 01 09 02 a1 01 85 01 09 01 a1 00 05 01 09 30 09 31 15 00 26 80 07 35 00 46 00 78 65 11 55 0e 75 10 95 02 81 02 05 09 19 01 29 03 15 00 25 01 75 01 95 03 65 00 81 02 95 05 81 01 c0 c0 N: Wacom, Inc. MSC Device P: usb-0000:00:1d.0-1.1/input0 I: 3 056a 0221 reading debug interface /sys/kernel/debug/hid/0003:056A:0221.000A/events instead of /dev/hidraw6 ^C No events where recorded. You may need to remove the option "--debugfs" to get more recordings. 2014-10-29 1:53 GMT+01:00 Jason Gerecke <kil...@gm...>: > Hmmm. It could need to be prodded to send the appropriate report > (which is the case with most Wacom tablets) before anything useful > comes out. You might try using the "hid-recorder" tool from [1] with > its "-d" option. That'll get data from debugfs instead of the hidraw > device, and might produce some output. > > [1]: https://bentiss.github.io/hid-replay-docs/ > > Jason > --- > Now instead of four in the eights place / > you’ve got three, ‘Cause you added one / > (That is to say, eight) to the two, / > But you can’t take seven from three, / > So you look at the sixty-fours.... > > > > On Tue, Oct 28, 2014 at 10:36 AM, Isaac Marco Blancas > <isa...@ud...> wrote: > > 2014-10-28 17:54 GMT+01:00 Jason Gerecke <kil...@gm...>: > >> > >> > >> Alternatively, you /might/ have some luck having the HID driver > >> control the device. See what happens if you add > >> 'usbhid.quirks=0x056a:0x0221:0x40000000' to the kernel commandline in > >> GRUB. You might get a new /dev/input/eventN device, or at least have > >> some interesting dmesg logs... > >> > > > > Thank you for your answer... > > > > I have boot after adding this to GRUB and there was no kernel panic but > > there's no response when I move the pen. > > > > [ 112.868335] usb 2-1.1: new high-speed USB device number 6 using > ehci-pci > > [ 112.961270] usb 2-1.1: New USB device found, idVendor=056a, > > idProduct=0221 > > [ 112.961274] usb 2-1.1: New USB device strings: Mfr=1, Product=2, > > SerialNumber=5 > > [ 112.961276] usb 2-1.1: Product: MSC Device > > [ 112.961288] usb 2-1.1: Manufacturer: Wacom, Inc. > > [ 112.961292] usb 2-1.1: SerialNumber: 3B33000032EB5A090002DD01A3CC9A09 > > [ 112.962798] usb-storage 2-1.1:1.1: USB Mass Storage device detected > > [ 112.962868] scsi7 : usb-storage 2-1.1:1.1 > > [ 112.994997] input: Wacom, Inc. MSC Device as > > /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input22 > > [ 112.995168] hid-generic 0003:056A:0221.0008: input,hidraw5: USB HID > v1.01 > > Mouse [Wacom, Inc. MSC Device] on usb-0000:00:1d.0-1.1/input0 > > [ 113.961633] scsi 7:0:0:0: Direct-Access Wacom Inkling > > 1256 PQ: 0 ANSI: 4 > > [ 113.961872] sd 7:0:0:0: Attached scsi generic sg3 type 0 > > [ 113.963123] sd 7:0:0:0: [sdc] 963840 2048-byte logical blocks: (1.97 > > GB/1.83 GiB) > > > > > > The device is on /dev/hidraw5 but if I make a > > > > cat /dev/hidraw5 > > > > and move the pen... nothing is returned > > > > -- > > Isaac Marco Blancas > > Universidad a Distancia de Madrid (UDIMA) > > 902 02 00 03 > -- Isaac Marco Blancas Universidad a Distancia de Madrid (UDIMA) 902 02 00 03 |