Bug 1337675
| Summary: | Wacom Penabled 2FG touchscreen on Lenovo X201 not accepting pen input | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nick Booker <nmb+rhbz> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 23 | CC: | bperkins, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, nmb+rhbz | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-09-25 19:14:15 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Nick Booker
2016-05-19 19:11:44 UTC
Created attachment 1159612 [details]
Initial debug output from both kernels
I've attached lsmod, xsetwacom and xinput output under both kernels.
Created attachment 1159613 [details]
Spreadsheet comparing working features on both tested kernels
Results of running on each kernel: dmesg | grep -i -e wacom -e touch 4.4 kernel from Fedora 23: [ 1.617136] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd047b3/0xb40000/0xa0000/0x0, board id: 0, fw id: 616291 [ 1.675160] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 8.252143] input: Wacom Serial Penabled 2FG Touchscreen as /devices/pnp0/00:05/tty/ttyS4/serio3/input/input15 4.6 kernel from rawhide: [ 1.854422] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd047b3/0xb40000/0xa0000/0x0, board id: 0, fw id: 616291 [ 1.913056] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 6.555321] input: Wacom Serial Penabled 2FG Touchscreen Pen as /devices/pnp0/00:05/tty/ttyS4/serio3/input/input15 [ 6.555875] input: Wacom Serial Penabled 2FG Touchscreen Finger as /devices/pnp0/00:05/tty/ttyS4/serio3/input/input16 Created attachment 1160308 [details]
Details of investigation into raised events under /dev/input
I've just been doing some further digging, and found that events are being raised in /dev/input/event* nodes for all touch and stylus features of the touchscreen. I've attached my method and more detailed findings.
I also did git log and git diff on wacom_w8001.c in the upstream kernels on git.kernel.org and the work between 4.4 and 4.5 to split the device into separate device nodes for 'Pen' and 'Finger' events does provide a plausible partial explanation for the change of behaviour between the kernels, but doesn't explain why X doesn't support the full range of available features under either.
Perhaps this isn't a kernel issue after all...
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. 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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those. I've since upgraded to Fedora 24 and this issue has recently been fixed in that release (see Bug 1349686). *** This bug has been marked as a duplicate of bug 1349686 *** |