Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WACF2200 sensors in new Lenovo tablet PCs are not detected by Wacom driver #218

Closed
jigpu opened this issue Nov 30, 2020 · 127 comments
Closed

Comments

@jigpu
Copy link
Member

jigpu commented Nov 30, 2020

It seems that many recent Lenovo devices are not having their touchscreen / pen sensor detected by the Wacom driver. The common thread so far seems to be the use of the WACF2200 ACPI ID in these devices. This issue will centralize the multiple bug reports that have been flowing in.

Affected devices:

Notes:

  • Reported to be "partially working" on the 14ARE05 by @Weewoolad (sysinfo.fGWhYaLpPe; Lubuntu 20.10, Linux 5.8.0-29-generic)

Hypotheses:

  • ACPI issue? (no obvious ACPI issues discovered so far)
  • 8250 "serial" driver taking control of all "WACF" devices?
@jigpu
Copy link
Member Author

jigpu commented Nov 30, 2020

@Weewoolad, you said:

Partially working on Lubuntu with kernel 5.8.0-29. Attempted and failed with Void Linux with kernel 5.8 (no detection). Attempted and failed with Lubuntu with kernel 5.10 (no detection).

Can you give me a little more information about the kernel 5.8 versus 5.10 installs of Lubuntu? Were they both Lubuntu 20.04? Were you running Lubuntu-provided kernels both times, or did you get them from some other source (or built yourself)?

@jigpu
Copy link
Member Author

jigpu commented Nov 30, 2020

I haven't been able to find anything suspicious in the ACPI tables so far, unfortunately. I've continued digging and am now growing suspicious of the kernel's 8250 serial port driver. Back in the ancient days there were several Wacom sensors which connected to the system via an (internal) serial port. It looks like the kernel's serial port driver has a wildcard match for any "WACF" device, which could cause problems for these new "WACF2200" devices that are actually connected over I2C. If anyone is comfortable with compiling and testing custom kernels, try using a version of the kernel with your current configuration (usually found at /proc/config.gz) but with the following patch applied:

diff --git a/drivers/tty/serial/8250/8250_pnp.c b/drivers/tty/serial/8250/8250_pnp.c
index de90d681b64c..b1536d564f09 100644
--- a/drivers/tty/serial/8250/8250_pnp.c
+++ b/drivers/tty/serial/8250/8250_pnp.c
@@ -331,7 +331,7 @@ static const struct pnp_device_id pnp_dev_table[] = {
 	/* U.S. Robotics 56K Voice INT PnP*/
 	{	"USR9190",		0	},
 	/* Wacom tablets */
-	{	"WACFXXX",		0	},
+//	{	"WACFXXX",		0	},
 	/* Compaq touchscreen */
 	{       "FPI2002",              0 },
 	/* Fujitsu Stylistic touchscreens */

@BFH-ktt1
Copy link

@jigpu , Thanks for all your effort! I would be happy to build a custom kernel, but unfortunately the coming three weeks I am still "swamped" with preparing on-line exams, etc. due to the Covid situation. I would have some time in three weeks (during the Xmas holiday period). If nobody can test it before than I'll be happy to dig into it in three weeks.

@richibrics
Copy link

I haven't been able to find anything suspicious in the ACPI tables so far, unfortunately. I've continued digging and am now growing suspicious of the kernel's 8250 serial port driver. Back in the ancient days there were several Wacom sensors which connected to the system via an (internal) serial port. It looks like the kernel's serial port driver has a wildcard match for any "WACF" device, which could cause problems for these new "WACF2200" devices that are actually connected over I2C. If anyone is comfortable with compiling and testing custom kernels, try using a version of the kernel with your current configuration (usually found at /proc/config.gz) but with the following patch applied:

diff --git a/drivers/tty/serial/8250/8250_pnp.c b/drivers/tty/serial/8250/8250_pnp.c
index de90d681b64c..b1536d564f09 100644
--- a/drivers/tty/serial/8250/8250_pnp.c
+++ b/drivers/tty/serial/8250/8250_pnp.c
@@ -331,7 +331,7 @@ static const struct pnp_device_id pnp_dev_table[] = {
 	/* U.S. Robotics 56K Voice INT PnP*/
 	{	"USR9190",		0	},
 	/* Wacom tablets */
-	{	"WACFXXX",		0	},
+//	{	"WACFXXX",		0	},
 	/* Compaq touchscreen */
 	{       "FPI2002",              0 },
 	/* Fujitsu Stylistic touchscreens */

Then I have to comment the WACFXXXX line right ? Like this
From

       **Beginning of 8250_pnp.c**
	/* U.S. Robotics 56K Voice INT PnP*/
	{	"USR9190",		0	},
	/* Wacom tablets */
	{	"WACFXXX",		0	},
	/* Compaq touchscreen */
	{       "FPI2002",              0 },
	/* Fujitsu Stylistic touchscreens */
       **End of 8250_pnp.c**

To

       **Beginning of 8250_pnp.c**
	/* U.S. Robotics 56K Voice INT PnP*/
	{	"USR9190",		0	},
	/* Wacom tablets */
//	{	"WACFXXX",		0	},
	/* Compaq touchscreen */
	{       "FPI2002",              0 },
	/* Fujitsu Stylistic touchscreens */
       **End of 8250_pnp.c**

@Weewoolad
Copy link

Weewoolad commented Nov 30, 2020

@Weewoolad, you said:

Partially working on Lubuntu with kernel 5.8.0-29. Attempted and failed with Void Linux with kernel 5.8 (no detection). Attempted and failed with Lubuntu with kernel 5.10 (no detection).

Can you give me a little more information about the kernel 5.8 versus 5.10 installs of Lubuntu? Were they both Lubuntu 20.04? Were you running Lubuntu-provided kernels both times, or did you get them from some other source (or built yourself)?

Yes, all three kernels were booted against the same install of kubuntu 20.10. I used kernel 5.10rc5 from a .Deb package from kernel.ubuntu.com/kernel-ppa/mainline. The 5.8 kernels (5.8.0-25 and 5.8.0-29) came from kubuntu's gui package manager. The live cd of kubuntu 20.10 works as well. It's usable until the tablet is assigned a profile in kde's settings, where touch gestures are finicky, but it's servicable after gestures are turned off. Pressure sensitivity also works in krita after a profile is assigned.

Important edit: I initially said lubuntu, but it's actually kubuntu. I apologise for the confusion.

@jigpu
Copy link
Member Author

jigpu commented Dec 1, 2020

@richibrics -- that's correct

@Weewoolad -- thanks, I'll follow up on those leads!

@Weewoolad
Copy link

@jigpu

I initially said lubuntu, but it's actually kubuntu. I apologise for the confusion.

@BFH-ktt1
Copy link

BFH-ktt1 commented Dec 1, 2020

@jigpu , I had some spare minutes and tried 2 things on my Yoga Duet:
I compiled a new kernel (5.7.5) with the provided patch: no change.
I tried the Kubuntu 20.10 live cd (kernel 5.8.0-29): same as with Ubuntu 20.04 LTS.
What Information would you require to continue your search?

@jigpu
Copy link
Member Author

jigpu commented Dec 1, 2020

Thanks @BFH-ktt1. This morning I also a look at the Kubuntu 20.10 kernel config (kernel 5.8.0-25) and see that it has the 8250 drivers enabled. I was thinking that maybe they disabled the 8250 driver entirely, which would cause a similar effect to commenting out the one line. Its looking less and less like the 8250 wildcard is at fault...

Kubuntu 20.10 working for @Weewoolad but not you is also especially interesting since that implies some kind of hardware or firwmare difference. I'll be making a second comparison of the logs you two have gathered to see if anything stands out...

@richibrics
Copy link

I try Kubuntu and let you know

@richibrics
Copy link

richibrics commented Dec 1, 2020

Does not work on Kubuntu with kernel 5.8.0-29-generic both installed or live
Dmesg attached
dmesg.log

@neonfighter28
Copy link

@jigpu I compiled a custom kernel (5.9.11) with your patch, but I had no success in getting anything related to the touchscreen to work. Do you need any outputs/logs? I will happily provide them, just let me know! Also, would you like me to try out the partially working Kubuntu?

@jigpu
Copy link
Member Author

jigpu commented Dec 1, 2020

@neonfighter28 thanks for the report; no logs necessary. A test of Kubuntu would be appreciated though

@Alexfebbraio
Copy link

Alexfebbraio commented Dec 1, 2020

I try Kubuntu and let you know

I try Without success with:
Ubuntu 20.10
Kubuntu 20.10
Lubuntu 20.10
Fedora 33
Deepin 20
Manjaro gnome 20.1.2
Manjaro kde 20.1.2
Opensuse15.2
ChromeOS branch kernel 4.4
ChromeOS branch next kernel 5.4

@neonfighter28
Copy link

neonfighter28 commented Dec 1, 2020

@jigpu No success on Kubuntu 20.10 with kernel 5.8.0-25, xinput --list shows the same as on arch

@Alexfebbraio
Copy link

I try Kubuntu and let you know

I try Without success with:
Ubuntu 20.10
Kubuntu 20.10
Lubuntu 20.10
Fedora 33
Deepin 20
Manjaro gnome 20.1.2
Manjaro kde 20.1.2
Opensuse15.2
ChromeOS branch kernel 4.4
ChromeOS branch next kernel 5.4

Today i installed the 5.10 rc6 kernel on ubuntu 20.10 but the result is always the same

@Alexfebbraio
Copy link

nothing news?

@ghost
Copy link

ghost commented Dec 13, 2020

I did some reasearch, because I'm going to get a Lenovo IdeaPad Flex 5 to christmas and found out something interesting. In the Archwiki under discussion of the tablet is somebody who wrote, that the touch is working (At least with a pen).
His output of dmesg|grep wacom

[    5.155680] input: Wacom HID 5218 Pen as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input25
[    5.155794] input: Wacom HID 5218 Finger as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input26
[    5.155884] wacom 0018:056A:5218.0001: hidraw0: I2C HID v1.00 Mouse [WACF2200:00 056A:5218] on i2c-WACF2200:00

Link: https://wiki.archlinux.org/index.php/Talk:Lenovo_IdeaPad_Flex_5_(Ryzen)

@Alexfebbraio
Copy link

I did some reasearch, because I'm going to get a Lenovo IdeaPad Flex 5 to christmas and found out something interesting. In the Archwiki under discussion of the tablet is somebody who wrote, that the touch is working (At least with a pen).
His output of dmesg|grep wacom

[    5.155680] input: Wacom HID 5218 Pen as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input25
[    5.155794] input: Wacom HID 5218 Finger as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input26
[    5.155884] wacom 0018:056A:5218.0001: hidraw0: I2C HID v1.00 Mouse [WACF2200:00 056A:5218] on i2c-WACF2200:00

Link: https://wiki.archlinux.org/index.php/Talk:Lenovo_IdeaPad_Flex_5_(Ryzen)

Flex 5 Ryzen it doesn't have the wacom 2200. It is different from flex 5 i3 10gen

@ghost
Copy link

ghost commented Dec 13, 2020

Are you sure?
The Path is /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input26
which includes WACF2200 and as far as I followed this issue this is the sensor. Also on top it says, that the Lenovo Idea Pad Flex 5 14ARE05 has this problem, even though it's a amd.
To the naming:
ARE = amd and IIL = intel as far as I saw it

@Alexfebbraio
Copy link

Alexfebbraio commented Dec 13, 2020

Are you sure?
The Path is /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input26
which includes WACF2200 and as far as I followed this issue this is the sensor. Also on top it says, that the Lenovo Idea Pad Flex 5 14ARE05 has this problem, even though it's a amd.
To the naming:
ARE = amd and IIL = intel as far as I saw it

I'm sorry, you're right. I got confused with ideapad 5 amd which uses elan's touchscreen

In any case I had installed manjaro with no success. I'll try with arch linux

@Alexfebbraio
Copy link

[https://wiki.archlinux.org/index.php/Talk:Lenovo

Are you sure?
The Path is /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input26
which includes WACF2200 and as far as I followed this issue this is the sensor. Also on top it says, that the Lenovo Idea Pad Flex 5 14ARE05 has this problem, even though it's a amd.
To the naming:
ARE = amd and IIL = intel as far as I saw it

I did some reasearch, because I'm going to get a Lenovo IdeaPad Flex 5 to christmas and found out something interesting. In the Archwiki under discussion of the tablet is somebody who wrote, that the touch is working (At least with a pen).
His output of dmesg|grep wacom

[    5.155680] input: Wacom HID 5218 Pen as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input25
[    5.155794] input: Wacom HID 5218 Finger as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0001/input/input26
[    5.155884] wacom 0018:056A:5218.0001: hidraw0: I2C HID v1.00 Mouse [WACF2200:00 056A:5218] on i2c-WACF2200:00

Link: https://wiki.archlinux.org/index.php/Talk:Lenovo_IdeaPad_Flex_5_(Ryzen)

the owner uses manjaro 20.0.1 with the 5.6.12-1-MANJARO kernel

This is his hd-probe:
https://linux-hardware.org/index.php?probe=cd3c373e02

@ccontrer
Copy link

I have an IdeaPad Flex 5 Rayzen, the issue with the touchscreen seems to be solved for me with kernel 5.10.0-051000-generic on Ubuntu 20.04.

@Alexfebbraio
Copy link

I have an IdeaPad Flex 5 Rayzen, the issue with the touchscreen seems to be solved for me with kernel 5.10.0-051000-generic on Ubuntu 20.04.

I just installed kernel 5.10.0-051000-generic on Ubuntu as you did but, no touchscreen recognition :-(

@ccontrer
Copy link

ccontrer commented Dec 14, 2020

Interesting...

I have an IdeaPad Flex 5 Rayzen, the issue with the touchscreen seems to be solved for me with kernel 5.10.0-051000-generic on Ubuntu 20.04.

I just installed kernel 5.10.0-051000-generic on Ubuntu as you did but, no touchscreen recognition :-(

My outputs,

  • dmesg | grep wacom
[    2.337434] wacom 0018:056A:5218.0002: hidraw1: I2C HID v1.00 Mouse [WACF2200:00 056A:5218] on i2c-WACF2200:00
  • lsinput
/dev/input/event8
   bustype : BUS_I2C
   vendor  : 0x56a
   product : 0x5218
   version : 256
   name    : "Wacom HID 5218 Pen"
   phys    : "i2c-WACF2200:00"
   uniq    : ""
   bits ev : (null) (null) (null) (null)

/dev/input/event9
   bustype : BUS_I2C
   vendor  : 0x56a
   product : 0x5218
   version : 256
   name    : "Wacom HID 5218 Finger"
   phys    : "i2c-WACF2200:00"
   uniq    : ""
   bits ev : (null) (null) (null)
  • I get readings with sudo mtdev-test /dev/input/event9 using my finger. I don't have a pen.

  • xinput --list

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Wacom HID 5218 Pen stylus               	id=12	[slave  pointer  (2)]
⎜   ↳ Wacom HID 5218 Finger touch             	id=13	[slave  pointer  (2)]
⎜   ↳ MSFT0001:00 06CB:CE2D Mouse             	id=14	[slave  pointer  (2)]
⎜   ↳ MSFT0001:00 06CB:CE2D Touchpad          	id=15	[slave  pointer  (2)]
⎜   ↳ Wacom HID 5218 Pen eraser               	id=17	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C         	id=10	[slave  keyboard (3)]
    ↳ Ideapad extra buttons                   	id=11	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=16	[slave  keyboard (3)]
  • I don't have the usbtouchscreen module installed.

@neonfighter28
Copy link

@Alexfebbraio this patch will be applied in the 5.11-rc kernel. The merge window closes in a week, I think, so I doubt we have to wait too long for the testing repos to be updated

@f-krull
Copy link

f-krull commented Dec 21, 2020

Maybe relevant? https://patchwork.kernel.org/project/linux-acpi/patch/20201211021814.36193-1-hui.wang@canonical.com/

This also helped with WACF4233 - I just recompiled the kernel for Ubuntu 20.04 on an HP EliteBook x360 830 G7

@ftsiadimos
Copy link

Thank you aditsu. It is so cool to use the touchscreen :)

@yogeshtewari
Copy link

Umm, really? Ok.
I have the kernel sources in /usr/src/linux, so I did:

cd /usr/src/linux
cd drivers/acpi
nano acpi_pnp.c

(replace nano with your favorite text editor if different)
then I found the line with if (memcmp(idstr, list_id, 3)) and inserted those 2 lines before it:

if (strlen(idstr) != strlen(list_id))
        return false;

saved the file, then compiled the kernel

cd /usr/src/linux
make -j5

Then installed it with make modules_install, make install etc

Thanks @aditsu .

I bought the new Lenovo ThinkBook 14s Yoga ITL with Core i7-1165G7. Patching with the latest kernel code fixes the touchscreen.

Now I just need to figure out screen rotation (it seems to work with Pop OS 20.04) and finger print on the power button.

@ghost
Copy link

ghost commented Dec 30, 2020

With a kernel, that has the Patch Applied the Touchscreen is working on my device (Ideapad Flex 5 15IIL05 81X3) too.
I also saw, that the Patch is already in the rc-kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/acpi/acpi_pnp.c?id=v5.11-rc1&id2=v5.10

@ghost
Copy link

ghost commented Jan 5, 2021

The patch is in the stable kernel 5.10.4 too. So upgrading to that kernel should work now so that you don't have to compile the kernel by yourself, if your distrobution has a package.

@jigpu
Copy link
Member Author

jigpu commented Jan 5, 2021

Good to see that the issue has been diagnosed and fixed. Hopefully the more-restrictive match won't cause problems for existing devices. The only working device I see in wacom-hid-descriptors which use the WACFXXXX format is itself also a WACF2200, similar to some of the limited success reports above. I'm assuming this should be fine...

Once people start to get the fix on their systems (either by patching their kernel manually or waiting for one of the stable kernels like 5.10.4 to be installed) I'd appreciate if they could attach updated sysinfo logs to their various wacom-hid-descriptor issues. I'll post reminders to each issue after a week or so if there's no update.

@Alexfebbraio
Copy link

Good to see that the issue has been diagnosed and fixed. Hopefully the more-restrictive match won't cause problems for existing devices. The only working device I see in wacom-hid-descriptors which use the WACFXXXX format is itself also a WACF2200, similar to some of the limited success reports above. I'm assuming this should be fine...

Once people start to get the fix on their systems (either by patching their kernel manually or waiting for one of the stable kernels like 5.10.4 to be installed) I'd appreciate if they could attach updated sysinfo logs to their various wacom-hid-descriptor issues. I'll post reminders to each issue after a week or so if there's no update.

which logs would you like?

@jigpu
Copy link
Member Author

jigpu commented Jan 6, 2021

@Alexfebbraio see the "Contributing" instructions on our wacom-hid-descriptors repository. Anyone who has a patched kernel is encouraged to submit the sysinfo logs described so that we have a record in the future of the hardware that is shipped with each device. I also use use the logs to generate a libwacom tablet definition for each sensor so that the devices show up properly in the control panel.

I seem to remember that some people may have already opened an issue for their device, and if that's the case, they can just submit the logs from their now-working system to their existing issue.

@Alexfebbraio
Copy link

Alexfebbraio commented Jan 6, 2021

ok
Lenovo ideapad Flex 5-15IIL05 Laptop - Type 81X3
intel core i3-1005G1
ubuntu 20.10
kernel 5.8.17 (recompiled with patch)
sysinfo.1gly9NWqi8.tar.gz

@ghost
Copy link

ghost commented Jan 7, 2021

Touchscreen works for my Lenovo YOGA Duet 2020 now!

For Debian/Ubuntu distro:

  1. Turn off the secure boot option in my laptop's BIOS/UEFI menu.
  2. Download and install linux 5.11.0-rc2 unsigned kernel image from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc2/

Out of curiosity, is sound working also working fine? That has been a big issue with the Duet 7i and the only distro that I've found to work "mostly" out of the box is Arch for some reason.
Thanks

@Alexfebbraio
Copy link

Out of curiosity, is sound working also working fine? That has been a big issue with the Duet 7i and the only distro that I've found to work "mostly" out of the box is Arch for some reason.
Thanks

on my lenovo the sound continues to work properly
Ubuntu 20.10
fedora 33
ChromeOS 88 beta (Brunch project)

jigpu added a commit to linuxwacom/wacom-hid-descriptors that referenced this issue Jan 11, 2021
@jigpu
Copy link
Member Author

jigpu commented Jan 11, 2021

It appears that this patch has now landed in all the stable trees upstream and should automatically roll out to distros soon:

  • Linux 5.10.4
  • Linux 5.4.86
  • Linux 4.19.164
  • Linux 4.14.213
  • Linux 4.9.249
  • Linux 4.4.249

@tarmacalastair
Copy link

tarmacalastair commented Jan 15, 2021

Many thanks for the work on this. Just bought my wife a Lenovo IdeaPad Flex 5 15IIL05 and was sad to see no touchscreen in Ubuntu 20.04. I updated after install from kernel 5.4.0-42 to 5.8.0-38 and it was still not working.

I then used the suggestions here to update to 5.10.4-051004 (following https://itsubuntu.com/update-linux-kernel-in-ubuntu-20-04-lts/) and yipee, the touchscreen works. I did install Ubuntu to dual boot with the pre-installed Windows 10S. This meant that I had to disable secure boot in the BIOS to get it to recognise the kernel (instructions for signing the kernel look way beyond my knowledge).

Whilst the touchscreen does work for clicking and selecting, it does not work for scrolling with a single finger. Can anyone suggest anything for this please? I've found this helpful page (https://itectec.com/ubuntu/ubuntu-how-to-make-touch-screen-scrolling-work-in-firefox-quantum/) for Firefox which is a good start but I'd like to be able to scroll everywhere so we can ditch Windows.
Thanks.

PS. Just noticed that scrolling works in one or two places, eg Settings, Ubuntu Software, but not Terminal, or Thunderbird. And the Firefox tip above does not work for Thunderbird for me either.

@saikat0511
Copy link

saikat0511 commented Jan 22, 2021

I installed 20.10 ubuntu on Flex-5 14IIL05 which shipped with 5.8 kernel. Touchscreen wasn't working out of the box but after some googling I landed on this page and installed 5.10 kernel.

It "kinda" fixed the problem. Now my touchscreen works after fresh reboot but most of the time stops working after I try to use the pen (which still doesn't work at all btw). Any help?

@ghost
Copy link

ghost commented Jan 22, 2021

You can test other kernels (LTS or self-compiled 5.11; I had some minor problems with the newest 5.10 kernel too). Also you can check journalctl -b -p 3.
journalctl = logs
b = current boot
p 3 = errors and above

@bleaktwig
Copy link

bleaktwig commented Jan 24, 2021

I have the same issue as @saikat0511, all touchscreen functionalities crash after using the stylus pen. I ran journalctl -b -p 3 and this is the
log (The PulseAudio messages are most likely unrelated, and probably are from another issue with the notebook).

I'm using the Kernel version 5.10.10-051010-generic. I tried compiling 5.11-rc4, but no matter what I try update-initramfs fails due to lack of space in /boot despite the fact that I have 222MB free in the boot partition.

I'll try other LTS kernels to see if the issue persists as @Donald4444 suggests, but any help is of course welcome.

P.D: I'm running KDE Neon over Ubuntu 20.04.

@jigpu
Copy link
Member Author

jigpu commented Jan 25, 2021

@saikat0511 @bleaktwig the issue of pen and touch breaking after trying to use the pen can be found at #230. The issue has been fixed, but we're waiting for the fix to make its way upstream and into distributions. For now, you should be able to compile the fixed version of input-wacom using the instructions described in that issue. I'll be posting an update over there once the patch is finally upstream.

@saikat0511
Copy link

Kernel 5.10.12 seems to have fixed the pen issue on 14IIL05. Pen touch works as expected now though I still cant scroll with pen swipe ( I am assuming that's how it just works in linux ).

@jigpu
Copy link
Member Author

jigpu commented Feb 4, 2021

Marking as closed since the fix for this is now upstream.

@saikat0511 the scroll behavior you observe is indeed "normal". Most software treats the pen more like a mouse than a finger so it highlights or draws selections rather than dragging. The driver has a feature to send scroll events while dragging, however. Use xsetwacom set "<stylus>" button [2|3] pan to map either pen button 2 or 3 to the "pan" function and then hold down that button while dragging.

@james454g
Copy link

@jigpu maybe it's more appropriate to mention this here - this is still an issue on the latest Fedora with kernel 6.8.10. Touchscreen does not work at all. Are we still expected to manually recompile the kernel to fix this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests