Description of problem: Built-in wacom touch panel does not work after updating to Fedora 31 beta. My laptop is Fujitsu T904. Version-Release number of selected component (if applicable): libwacom-1.1-1.fc31.x86_64 How reproducible: Just start the system and the touch screen does not work. Actual results: Neither touch screen nor stylus work. Expected results: Expect the touch screen and stylus work without any modification.
did it work under F30? if so, it's more likely to be a kernel regression than a userspace bug. Things I'll need here - dmesg - libinput record output for stylus and touch
Yes, it worked perfectly under F30. Both in x11 and wayland. dmesg output: https://paste.fedoraproject.org/paste/Kcce44uAyZB2Qc11U~f3rA/deactivate/RmhRS0WrTb9bd2xIV840v6X6XObCQSWj4yIaD9HYkULHq6wXFPzHcTSsTftYig9e I can't get the output of libinput record, it says "libinput: record is not a libinput command or not installed. See 'libinput --help'", although it is part of the commands in man page.
(In reply to master.mhn1388 from comment #2) > Yes, it worked perfectly under F30. Both in x11 and wayland. > dmesg output: > https://paste.fedoraproject.org/paste/Kcce44uAyZB2Qc11U~f3rA/deactivate/ > RmhRS0WrTb9bd2xIV840v6X6XObCQSWj4yIaD9HYkULHq6wXFPzHcTSsTftYig9e > > I can't get the output of libinput record, it says "libinput: record is not > a libinput command or not installed. See 'libinput --help'", although it is > part of the commands in man page. Sorry, I pasted the wrong link (There is no way to edit the comment). Here it is: https://paste.fedoraproject.org/paste/Kcce44uAyZB2Qc11U~f3rA
please always **attach** files like dmesg, pastebins have a tendency to disappear when we need them the most. libinput record is in the libinput-utils rpm package.
Created attachment 1618626 [details] dmesg report
Created attachment 1618639 [details] libinput record, captures no event I see this line in dmesg report: input input16: Absolute device without dev->absinfo, refusing to register [ 4.571267] wacom: probe of 0003:056A:5002.0001 failed with error -22 It may be of use.
Hello, Is there any news?
Apologies for the delay, we have been traveling around for various conferences, and now it's the email catch-up phase, where things need to be prioritized. Do you happen to have by any chances a F30 kernel around? I would need the dmessg traces there to compare and guess why the device doesn't send any events now. The "[ 4.571267] wacom: probe of 0003:056A:5002.0001 failed with error -22" might not be an issue, as the second HID device manages to get a Pen and Touch input node, so maybe the first one is not wacom Pen compatible. Does `sudo hexdump /dev/hidraw0` gives any output when you touch the wacom panel or use the pen?
Don't need to apologize. It is ok. "Does `sudo hexdump /dev/hidraw0` gives any output when you touch the wacom panel or use the pen?" No, There is no output. "Do you happen to have by any chances a F30 kernel around?" Unfortunately no. Only keep 3 recent kernels and there has been a few kernel updates recently which removed previous ones.
fwiw, the list of kernels built for fedora is here: https://koji.fedoraproject.org/koji/packageinfo?packageID=8, you can download and install the desired kernel from there. https://fedoramagazine.org/install-kernel-koji/ has some info (including the comments, the koji commandline tool makes this even easier).
Created attachment 1625604 [details] dmesg report from kernel 5.2.13.fc30 which touch screen and stylus works
Thanks for the logs. So the first interface (the one which fails) is the touch part, and I guess having this one messed up kills the tablet. The only patch that has been introduced in v5.3 which changes the init path is 184eccd40389 ("HID: wacom: generic: read HID_DG_CONTACTMAX from any feature report"). Jason, do you have any ideas if this patch could have such a side effect or if this is something else?
Similar symptoms (absinfo error starting with the 5.3 kernel) reported for the Motion Computing R12 laptop with Puppy Linux (puppy_bionicpup64) at https://github.com/linuxwacom/input-wacom/issues/121#issuecomment-542239353. I will be testing the updated driver on a few devices over here to see what I can learn.
This device (056a:5002) and the one from my link above (056a:4004) are both rather old touchscreens. I've gone through the library of hardware on hand to find something from the same vintage, but have come up short. Even older devices (e.g. 056a:00e3 and 056a:00e6) as well as the current crop of AES hardware seem to be unaffected. OP, now that you have a working kernel again, would you mind trying to install the "input-wacom" driver according to the instructions at [1]? If the current version of the driver breaks touch in the same way again, that would strongly indicate that it is the wacom driver at fault rather than some other change to the kernel. We can then work on bisecting to figure out which commit is responsible for the breakage. [1]: https://github.com/linuxwacom/input-wacom/wiki/Installing-input-wacom-from-source
Created attachment 1628918 [details] dmesg report I've followed the instructions on the [1] and installed the driver. But nothing breaks and everything works perfectly as before. I attached again the dmesg output after installing the driver from [1].
Interesting. The reporter on Github had the opposite experience and tracked the issue down to the "HID: wacom: generic: read HID_DG_CONTACTMAX from any feature report" commit that Benjamin suspected. His device uses a different sensor (056a:4004 instead of 056a:5002) but given the similarity of symptoms I would have expected the same behavior... Can you please confirm the version number of the loaded kernel driver by running `grep "" /sys/module/wacom*/version` for me?
Yeah, sure: v2.00 Is the output of your command. Also, running "modinfo wacom | grep version" gives this result: version: v2.00-0.44.0 srcversion: 158A607B42851BD4CBB5A83
Thanks. It appears that while the updated driver is installed, it is the (working) *stock* driver that is actually loaded. This usually is a result of the `make install` step not updating the initrd for some reason... As a workaround, open a terminal and navigate to the input-wacom directory. Next, run `sudo rmmod wacom` to unload the driver and then `sudo insmod 4.5/wacom.ko` to manually load the compiled driver. Run `grep "" /sys/module/wacom*/version` to verify that v2.00-0.44.0 of the driver is loaded. Finally, touch the screen to see if it responds (it shouldn't) and check the last dozen or so lines of `dmesg` to see if the `Absolute device without dev->absinfo` error was printed out (it should be).
Created attachment 1629834 [details] dmesg report Yes, you are right. The touch is not working again. I attached the dmesg report again and here is the line you mentioned: [ 4453.500523] input input37: Absolute device without dev->absinfo, refusing to register [ 4453.500538] wacom: probe of 0003:056A:5002.0001 failed with error -22
Hi Kernel 5.4 is out and the problem still persist. dmesg output for touchscreen is: [ 2.306302] input input15: Absolute device without dev->absinfo, refusing to register [ 2.306319] wacom: probe of 0003:056A:5002.0002 failed with error -22 [ 2.321503] input: Wacom ISDv4 5002 Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:056A:5002.0003/input/input17 [ 2.321641] wacom 0003:056A:5002.0003: hidraw1: USB HID v1.11 Device [Wacom Co.,Ltd. MultiTouch Sensor ] on usb-0000:00:14.0-4/input1
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
Hi, kernel 5.5.7-200.fc31.x86_64. The issue is still present.
Hi, Kernel 5.5.8-200.fc31.x86_64. The issue is still present.
Created attachment 1670913 [details] dmesg report of kernel 5.6-rc5 I've updated to Fedora 32 beta with kernel 5.6.0-0.rc5.git0.2.fc32.x86_64. Still, the touch screen and pen do not work, but in gnome settings, wacom tablet section, tablet tab, recognizes the wacom model "Wacom ISDv4 5002". There are two tracking modes available, relative and absolute which were absent in gnome settings 3.34, maybe an improvement in gnome settings or something changed here, I don't know. I attached the dmesg report, this time, it seems different to me: [ 4.500391] input input17: Absolute device without dev->absinfo, refusing to register [ 4.500403] wacom: probe of 0003:056A:5002.0002 failed with error -22 [ 4.522611] input: Wacom ISDv4 5002 Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:056A:5002.0003/input/input19 [ 4.522714] wacom 0003:056A:5002.0003: hidraw1: USB HID v1.11 Device [Wacom Co.,Ltd. MultiTouch Sensor ] on usb-0000:00:14.0-4/input1
According to this GitHub issue [1], this bug has been fixed in kernel 5.6.13-300.fc32. Thanks. [1]: https://github.com/linuxwacom/input-wacom/issues/121
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.