Touchpad not working with ASUS TUF F15

Bug #1937056 reported by Lovesh
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Unassigned
Focal
Won't Fix
Undecided
Unassigned
Hirsute
Fix Released
High
Unassigned
Impish
Fix Released
High
Unassigned
linux-oem-5.10 (Ubuntu)
Invalid
Undecided
Unassigned
Focal
Fix Released
High
Unassigned
Hirsute
Invalid
Undecided
Unassigned
Impish
Invalid
Undecided
Unassigned
linux-oem-5.13 (Ubuntu)
Invalid
Undecided
Unassigned
Focal
Fix Released
High
Unassigned
Hirsute
Invalid
Undecided
Unassigned
Impish
Invalid
Undecided
Unassigned

Bug Description

== SRU Justification ==

[Impact]
Touchpad and touchscreen don't work on TGL-H laptops.

[Fix]
Update GPIO mapping so the values can match between Linux and BIOS.

[Test]
After applying the patch, both touchpad and touchscreen can work
correctly.

[Where problems could occur]
If somehow any of the new pin value is incorrect, it can break devices
that require Intel GPIO to work.

== Original Bug Report ==

I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The touchpad isn't detected in Settings and neither in xinput, nor in cat /proc/bus/input/devices.

Laptop model: ASUS TUF F15 FX506HM_FX566HM.
Manufacturer of the Touchpad: Probably ELAN1203
When the symptom first appeared: From beginning

Output of lsb_release -rd
Description: Ubuntu 21.04
Release: 21.04

Using kernel version 5.13.6. Also tried 5.11, 5.12.8, 5.12.15, 5.13.1, 5.13.2, 5.13.4, 5.13.5, 5.14-rc2, 5.14-rc3

Output of xinput

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Asus Wireless Radio Control id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Power Button id=9 [slave keyboard (3)]
    ↳ Sleep Button id=10 [slave keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)]
    ↳ Intel HID events id=12 [slave keyboard (3)]
    ↳ Intel HID 5 button array id=13 [slave keyboard (3)]
    ↳ Asus WMI hotkeys id=14 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]

Output of lspci

0000:00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
0000:00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #1 (rev 05)
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
0000:00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 05)
0000:00:06.0 System peripheral: Intel Corporation Device 09ab
0000:00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI Express Root Port #0 (rev 05)
0000:00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 05)
0000:00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01)
0000:00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB Controller (rev 05)
0000:00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI #0 (rev 05)
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller
0000:00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11)
0000:00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11)
0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11)
0000:00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11)
0000:00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11)
0000:00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11)
0000:00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller (rev 11)
0000:00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller (rev 11)
0000:00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11)
0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1)
0000:01:00.1 Audio device: NVIDIA Corporation Device 228e (rev a1)
0000:2d:00.0 Network controller: MEDIATEK Corp. Device 7961
0000:2e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
10000:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller #0 (rev 05)
10000:e1:00.0 Non-Volatile memory controller: SK hynix Device 174a
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-07-25 (1 days ago)
InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Package: linux (not installed)
Tags: hirsute
Uname: Linux 5.13.5-051305-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to hirsute on 2021-07-25 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

Logged a bug in the kernel as well https://bugzilla.kernel.org/show_bug.cgi?id=213857

Revision history for this message
Lovesh (lovesh-bond) wrote :
Lovesh (lovesh-bond)
description: updated
Lovesh (lovesh-bond)
description: updated
Lovesh (lovesh-bond)
description: updated
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please run `apport-collect 1937056`.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Lovesh (lovesh-bond) wrote : ProcCpuinfoMinimal.txt

apport information

tags: added: apport-collected hirsute
description: updated
Revision history for this message
Lovesh (lovesh-bond) wrote : ProcEnviron.txt

apport information

Lovesh (lovesh-bond)
description: updated
Revision history for this message
Lovesh (lovesh-bond) wrote :

Output of cat /proc/bus/input/devices

Revision history for this message
Lovesh (lovesh-bond) wrote :

Output of dmesg

Lovesh (lovesh-bond)
description: updated
Lovesh (lovesh-bond)
Changed in linux (Ubuntu):
status: Incomplete → New
Lovesh (lovesh-bond)
description: updated
Revision history for this message
Lovesh (lovesh-bond) wrote :

Output of udevadm info --export-db

Lovesh (lovesh-bond)
description: updated
Revision history for this message
Chris Chiu (mschiu77) wrote :

It should be due to the error message down below.
[ 0.862688] i2c_hid_acpi i2c-ELAN1203:00: Could not register for ELAN1203:00 interrupt, irq = 167, ret = -1

Can you share the output of "sudo cat /sys/kernel/debug/pinctrl/INT34C6:00/gpio-ranges"? I need to know the pin mapping between GPIO and the Intel Pinctrl.

Revision history for this message
Lovesh (lovesh-bond) wrote :

Here it is:

GPIO ranges handled:
0: INT34C6:00 GPIOS [81 - 105] PINS [0 - 24]
128: INT34C6:00 GPIOS [209 - 228] PINS [25 - 44]
32: INT34C6:00 GPIOS [113 - 138] PINS [45 - 70]
96: INT34C6:00 GPIOS [177 - 202] PINS [79 - 104]
64: INT34C6:00 GPIOS [145 - 168] PINS [105 - 128]
160: INT34C6:00 GPIOS [241 - 248] PINS [129 - 136]
192: INT34C6:00 GPIOS [273 - 289] PINS [137 - 153]
224: INT34C6:00 GPIOS [305 - 331] PINS [154 - 180]
256: INT34C6:00 GPIOS [337 - 349] PINS [181 - 193]
288: INT34C6:00 GPIOS [369 - 392] PINS [194 - 217]
320: INT34C6:00 GPIOS [401 - 424] PINS [218 - 241]
384: INT34C6:00 GPIOS [465 - 474] PINS [242 - 251]
352: INT34C6:00 GPIOS [433 - 447] PINS [252 - 266]
416: INT34C6:00 GPIOS [497 - 511] PINS [267 - 281]

Folks on my kernel bug also suggested issue with the pin mapping so sharing the link https://bugzilla.kernel.org/show_bug.cgi?id=213857

Revision history for this message
Lovesh (lovesh-bond) wrote :

Issue resolved with a patched kernel. Patch is here https://bugzilla.kernel.org/show_bug.cgi?id=213579#c56.

Revision history for this message
Chris Chiu (mschiu77) wrote :

Thanks for the information. So it means the ownership of the pin is incorrectly configured by the BIOS. I can force the host_own bit to different value, please try to install the customized kernel and give me the dmesg output. https://people.canonical.com/~mschiu77/lp1937056/
However, even it works, you may still need to upgrade to a newer BIOS for it because the system can only configure the pin based on BIOS/ACPI settings.

Revision history for this message
Lovesh (lovesh-bond) wrote :

I need atleast 5.12 for wifi to work. But I will try once I have a BIOS upgrade.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Changed in linux (Ubuntu Focal):
status: New → Won't Fix
Changed in linux (Ubuntu Hirsute):
importance: Undecided → High
status: New → Confirmed
Changed in linux (Ubuntu Impish):
importance: Undecided → High
status: New → Confirmed
Changed in linux-oem-5.10 (Ubuntu Focal):
importance: Undecided → High
status: New → Confirmed
Changed in linux-oem-5.10 (Ubuntu Hirsute):
status: New → Invalid
Changed in linux-oem-5.10 (Ubuntu Impish):
status: New → Invalid
Changed in linux-oem-5.13 (Ubuntu Focal):
importance: Undecided → High
status: New → Confirmed
Changed in linux-oem-5.13 (Ubuntu Hirsute):
status: New → Invalid
Changed in linux-oem-5.13 (Ubuntu Impish):
status: New → Invalid
description: updated
AceLan Kao (acelankao)
Changed in linux-oem-5.10 (Ubuntu Focal):
status: Confirmed → Fix Committed
Changed in linux (Ubuntu Hirsute):
status: Confirmed → Fix Committed
Revision history for this message
jazir malik (jazir1979) wrote (last edit ):

I'm having this issue on a new Metabox NH77HK (built by Clevo) on Kubuntu 20.04. Elantech touchpad. I've resolved for now with psmouse driver, but scrolling doesn't work and it doesn't disable while typing.

Today (17th Aug) I installed linux-oem-5.10 and can confirm this fix worked. It says above 'won't fix' for Focal non-OEM kernel. Does that mean I need to stick with OEM Kernel or upgraded to a non-LTS distribution?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-oem-5.10 - 5.10.0-1044.46

---------------
linux-oem-5.10 (5.10.0-1044.46) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1044.46 -proposed tracker (LP: #1939533)

  * mute/micmute LEDs no function on HP ProBook 650 G8 (LP: #1939473)
    - SAUCE: ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 650 G8
      Notebook PC

 -- Chia-Lin Kao (AceLan) <email address hidden> Wed, 11 Aug 2021 17:35:07 +0800

Changed in linux-oem-5.10 (Ubuntu Focal):
status: Fix Committed → Fix Released
Timo Aaltonen (tjaalton)
Changed in linux-oem-5.13 (Ubuntu Focal):
status: Confirmed → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-hirsute
Revision history for this message
Cameron Berkenpas (hiryu88) wrote :

This solves the problem for me.

tags: added: verification-done-hirsute
removed: verification-needed-hirsute
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-focal
jazir malik (jazir1979)
tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (62.5 KiB)

This bug was fixed in the package linux - 5.11.0-34.36

---------------
linux (5.11.0-34.36) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)

  * Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
    - Revert "ACPI: resources: Add checks for ACPI IRQ override"

linux (5.11.0-33.35) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-33.35 -proposed tracker (LP: #1940101)

  * libvirtd fails to create VM (LP: #1940107)
    - sched: Stop PF_NO_SETAFFINITY from being inherited by various init system
      threads

linux (5.11.0-32.34) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-32.34 -proposed tracker (LP: #1939769)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.08.16)

  * CVE-2021-3656
    - SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested

  * CVE-2021-3653
    - SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl

  * [regression] USB device is not detected during boot (LP: #1939638)
    - SAUCE: Revert "usb: core: reduce power-on-good delay time of root hub"

  * Support builtin revoked certificates (LP: #1932029)
    - [Packaging] build canonical-revoked-certs.pem from branch/arch certs
    - [Packaging] Revoke 2012 UEFI signing certificate as built-in
    - [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
    (LP: #1928679)
    - SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
    (LP: #1928679) // CVE-2020-26541 when certificates are revoked via
    MokListXRT.
    - SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Include product_sku info to modalias (LP: #1938143)
    - firmware/dmi: Include product_sku info to modalias

  * Fix Ethernet not working by hotplug - RTL8106E (LP: #1930645)
    - net: phy: rename PHY_IGNORE_INTERRUPT to PHY_MAC_INTERRUPT
    - SAUCE: r8169: Use PHY_POLL when RTL8106E enable ASPM

  * [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock
    (LP: #1938689)
    - SAUCE: igc: fix page fault when thunderbolt is unplugged

  * [Regression] Audio card [8086:9d71] not detected after upgrade from linux
    5.4 to 5.8 (LP: #1915117)
    - [Config] set CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC to y

  * Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop (LP: #1934557)
    - drm/amdgpu/display: only enable aux backlight control for OLED panels

  * Touchpad not working with ASUS TUF F15 (LP: #1937056)
    - pinctrl: tigerlake: Fix GPIO mapping for newer version of software

  * dev_forward_skb: do not scrub skb mark within the same name space
    (LP: #1935040)
    - dev_forward_skb: do not scrub skb mark within the same name space

  * Fix display output on HP hybrid GFX laptops (LP: #1936296)
    - drm/i915: Invoke another _DSM to enable MUX on HP Workstation laptops

  * [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung 16727
    panel (LP: #1930527)
    - SAUCE: drm/i915: Force DPCD backlight mode for Samsung 16727 pa...

Changed in linux (Ubuntu Hirsute):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16

---------------
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium

  * focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP: #1942861)

  * Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
    - SAUCE: r8169: Disable ASPM L1.2

  * CVE-2021-3609
    - can: bcm: delay release of struct bcm_op after synchronize_rcu()
    - can: j1939: j1939_sk_init(): set SOCK_RCU_FREE to call sk_destruct() after
      RCU is done

 -- Timo Aaltonen <email address hidden> Tue, 07 Sep 2021 11:49:54 +0300

Changed in linux-oem-5.13 (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 5.13.0-16.16

---------------
linux (5.13.0-16.16) impish; urgency=medium

  * impish/linux: 5.13.0-16.16 -proposed tracker (LP: #1942611)

  * Miscellaneous Ubuntu changes
    - [Config] update toolchain in configs

  * Miscellaneous upstream changes
    - Revert "UBUNTU: [Config] Enable CONFIG_UBSAN_BOUNDS"

 -- Andrea Righi <email address hidden> Fri, 03 Sep 2021 16:21:14 +0200

Changed in linux (Ubuntu Impish):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.