|
From: Ping C. <pin...@gm...> - 2017-08-25 22:25:21
|
Hi Matthieu, Thank you for the detailed report. As you guessed, it is indeed a kernel driver issue. I'm working on the upstream patch. Once the patch is accepted upstream, we'll backport it into input-wacom for those who can not wait for the next distribution update. Stay tuned... Ping On Fri, Aug 18, 2017 at 9:42 AM, Matthieu Robin <mat...@ma...> wrote: > Hi everybody > > I'm trying to configure my Wacom tablet on a Ubuntu 17.4 installation. > Everything works like a charm... Except that 2 buttons (out of 10) don't > work at all. > > Tablet is DTZ-1200W, aka. Ltd Cintiq 12WX > > It's the model referenced here: > https://sourceforge.net/p/linuxwacom/libwacom/ci/master/tree/data/cintiq-12wx.tablet > > All buttons work except the upper ones, named I and J in the file above. > > When using xsetwacom, I can see all 10 buttons in the list of parameters: > > $ xsetwacom -s get 21 all > Property 'Wacom Tablet Area' does not exist on device. > xsetwacom set "21" "Button" "1" "key +a -a " > xsetwacom set "21" "Button" "2" "key +b -b " > xsetwacom set "21" "Button" "3" "key +c -c " > xsetwacom set "21" "Button" "8" "key +d -d " > xsetwacom set "21" "Button" "9" "key +e -e " > xsetwacom set "21" "Button" "10" "key +f -f " > xsetwacom set "21" "Button" "11" "key +g -g " > xsetwacom set "21" "Button" "12" "key +h -h " > xsetwacom set "21" "Button" "13" "key +i -i " > xsetwacom set "21" "Button" "14" "key +j -j " > ... > > > Buttons 1 to 12 work like a charm. However, nothing happens if I press > button 13 or 14. So I'll never see "i" nor "j". > > Let's try to see what xinput tells us: > > $ xinput test-xi2 > > => events are dumped for the 8 buttons that work. However, nothing happens > for the 2 faulty ones. > > Let's dig a little deeper: > > # cat /dev/input/by-id/usb-Tablet_DTZ-1200W-mouse > > Same here: I see data only for 8 buttons out of 10. > > > Time for some USB debugging. Let's see what usbmon tells us: > > root@hostname:/sys/kernel/debug/usb/usbmon# cat 2u > > --- When I press one "faulty" button > ffff9aec50e8dcc0 2743584310 C Ii:2:004:1 0:1 10 = 0c000000 00100000 0000 > ffff9aec50e8dcc0 2743584344 S Ii:2:004:1 -115:1 10 < > ffff9aec50e8dcc0 2743793276 C Ii:2:004:1 0:1 10 = 0c000000 00000000 0000 > ffff9aec50e8dcc0 2743793303 S Ii:2:004:1 -115:1 10 < > > -- When I press one working button > ffff9aec50e8dcc0 2763111318 C Ii:2:004:1 0:1 10 = 0c000000 00010000 0000 > ffff9aec50e8dcc0 2763111346 S Ii:2:004:1 -115:1 10 < > ffff9aec50e8dcc0 2763290315 C Ii:2:004:1 0:1 10 = 0c000000 00000000 0000 > ffff9aec50e8dcc0 2763290343 S Ii:2:004:1 -115:1 10 < > > -- When I press another working button > ffff9aec50e8dcc0 2787169353 C Ii:2:004:1 0:1 10 = 0c000000 00040000 0000 > ffff9aec50e8dcc0 2787169393 S Ii:2:004:1 -115:1 10 < > ffff9aec50e8dcc0 2787377332 C Ii:2:004:1 0:1 10 = 0c000000 00000000 0000 > ffff9aec50e8dcc0 2787377352 S Ii:2:004:1 -115:1 10 < > > So, hardware sends a signal when pressing faulty button. Signal seems > similar to other buttons, as far I can tell... > > I ran these tests with Linux kernel 4.10 and 4.12. > > Is it an issue in wacom kernel driver? > How can I go further in troubleshooting it? > I can provide usbmon dump for all 10 buttons. Would it help? > > Thanks a lot > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Linuxwacom-discuss mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss > |