Goodix Touchscreen support?

[fiatisdead]

Hi,
I'm new to Void, a friend introduced last week and also mentioned work ongoing with PlagueOS.
I just come to test the void-live-x86_64-musl-20210218-mate.iso but noticed touchscreen isnt working.

This works out the box on Ubuntu Mate 20.04.1 LTS and I wonder if you can add support for Goodix Touchscreen or whether you can point me in the right direction to try to get it working. Hardware: GPD P2 Max

My plan is to move from Ubuntu Mate as daily driver to Void Linux hopefully if I can get everything working.

[ericonr]

It should be working, I think... Our kernels have CONFIG_TOUCHSCREEN_GOODIX=m. Can you try modprobe goodix to see if it does anything?

[fiatisdead]

It should be working, I think... Our kernels have CONFIG_TOUCHSCREEN_GOODIX=m. Can you try modprobe goodix to see if it does anything?

It returns nothing.

[biopsin]

what does lsmod | grep goodix show after loading the module?
also check dmesg to see if issues

[fiatisdead]

lsmod | grep goodix returns:
goodix 32768 0

sudo dmesg returns a large amount of output but I think this is what you probably need to see:

4.351333] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    4.369687] Goodix-TS i2c-GDIX1002:00: supply AVDD28 not found, using dummy regulator
[    4.369726] Goodix-TS i2c-GDIX1002:00: supply VDDIO not found, using dummy regulator
[    4.370131] Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121
[    4.392201] Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121
[    4.415552] usb 2-3.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[    4.456656] r8152 2-3.3:1.0: load rtl8153a-4 v2 02/07/20 successfully
[    4.481447] r8152 2-3.3:1.0 eth0: v1.11.11
[    4.500219] Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121
[    4.522265] Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121
[    4.544040] Goodix-TS i2c-GDIX1002:00: I2C communication failure: -121
[    4.544663] Goodix-TS: probe of i2c-GDIX1002:00 failed with error -121
[    4.553892] usb 1-1.2: new high-speed USB device number 5 using xhci_hcd

[biopsin]

did not dig futher but [bug] seems unresolved

[fiatisdead]

I believe this may fix the issue but I unfortunately don't have the knowledge and skills to be able to work out what to do to apply this patch.
Any help would be very much appreciated.

[biopsin]

@fiatisdead You'll have to help yourself as no one has the hardware.
Start with https://github.com/void-linux/void-packages#quick-start, then
save the patch in ..void-packages/srcpkgs/linux5.XX/patches and build the kernel with xbps-src
and install from ..void-packages/hostdir/binpkgs

[Wesley-Chan]

Hi, @fiatisdead. Would you please try the followings?

1. Kindly tell us the version of the kernel you are using with uname -a. Try to install version 5.6 (sudo xbps-install linux5.6) or earlier to see if that brings the touchscreen back to life.
2. Try to blacklist (# echo "blacklist goodix" >> /etc/modprobe.d/blacklist) Goodix module, then manually load it after boot (# modprobe goodix), see if it does anything. You may want to monitor dmesg output in the process.

[fiatisdead]

Thanks Wesley Current Kernel: 5.13.19_1 I installed linux5.6 but it appeared to make no difference at all even after a reboot. I then blacklisted as per your point 2. The dmesg still gives the same error as #33277 (comment) #33277 (comment) blacklisting and following a reboot checking dmesg output. I also tried manually loading by issuing modprobe goodix and nothing happens. The dmesg output doesn’t really change. Same errors as previously mentioned. Appreciate your efforts in trying to assist.

…

On Thu, Oct 21, 2021 at 14:17, Wesley ***@***.***> wrote: Hi, ***@***.***(https://github.com/fiatisdead). Would you please try the followings? - Kindly tell us the version of the kernel you are using with uname -a. Try to install version 5.6 (sudo xbps-install linux5.6) or earlier to see if that brings the touchscreen back to life. - Try to blacklist (# echo "blacklist goodix" >> /etc/modprobe.d/blacklist) Goodix module, then manually load it after boot (# modprobe goodix), see if it does anything. You may want to monitor dmesg output in the process. — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#33277 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AV4NVKS7LOPPALGLI4IOILDUIAHFNANCNFSM5FG4XFHQ). Triage notifications on the go with GitHub Mobile for [iOS](https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or [Android](https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).

[Wesley-Chan]

Sorry I did not help.
Can you confirm that flashing Ubuntu Mate 20.04.1 LTS makes the device back to a working state?
At that point, perhaps try some new versions of Ubuntu Mate, see if the latest kernel breaks it.
Also you can try copying the kernel of Ubuntu Mate 20.04.1 LTS to your Void installation (/boot), and make Grub (or is it U-Boot?) load it instead of stock Void Linux kernel, see if that makes any difference.
If you need any help performing those steps, please do not hesitate to ask.

[github-actions]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.