Latest ASUS trackpad doesn't work in Ubuntu

[Ian Newborn]

It seems there might be a new hardware variant of the elan trackpad in the newer ASUS machines.

The issue is the shown here with some reasonably deep investigation. Is this something that I can do or am I reduced to having to find out a mouse if I want to use Linux?

https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/

user@TUF-GAMING-FX504GD-FX80GD:~$ xinput
 Virtual core pointer id=2 [master pointer (3)]
   ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
   ↳ Logitech USB Receiver id=12 [slave pointer (2)]
   ↳ Logitech USB Receiver id=13 [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)]
    ↳ Asus Wireless Radio Control id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Video Bus id=9 [slave keyboard (3)]
    ↳ Power Button id=10 [slave keyboard (3)]
    ↳ Sleep Button id=11 [slave keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)]
    ↳ Asus WMI hotkeys id=15 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)]
    ↳ Logitech USB Receiver id=17 [slave keyboard (3)]

[soundhermit (soundhermit-linux-kernel-bugs)]

Razer Blade 15 2018 touchpad support [1532:0233]

Bus 001 Device 005: ID 1532:0233 Razer USA, Ltd
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x1532 Razer USA, Ltd
  idProduct 0x0233
  bcdDevice 2.00
  iManufacturer 1 Razer
  iProduct 2 Razer Blade
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 0x0054
    bNumInterfaces 3
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 3 Human Interface Device
      bInterfaceSubClass 1 Boot Interface Subclass
      bInterfaceProtocol 1 Keyboard
      iInterface 0
        HID Device Descriptor:
          bLength 9
          bDescriptorType 33
          bcdHID 1.11
          bCountryCode 0 Not supported
          bNumDescriptors 1
          bDescriptorType 34 Report
          wDescriptorLength 61
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 3 Human Interface Device
      bInterfaceSubClass 0
      bInterfaceProtocol 1 Keyboard
      iInterface 0
        HID Device Descriptor:
          bLength 9
          bDescriptorType 33
          bcdHID 1.11
          bCountryCode 0 Not supported
          bNumDescriptors 1
          bDescriptorType 34 Report
          wDescriptorLength 159
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 2
      bAlternateSet...

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 276785
Files collected during investigation

[soundhermit (soundhermit-linux-kernel-bugs)]

Investigation done by alkersan
-----------------------------------

The touchpad of the Razer Blade 15 (2018) laptop is unresponsive after boot.

After shallow investigation of hardware identifiers, the touchpad seems to be present the USB and I2C buses.

The USB part is visible as a HID device and includes a mouse interface, but it probably handles just the keys of the laptop, including the keyboard, media/function buttons and RGB backlight programming.
The detailed output of lsusb is attached. It has an ID [1532:0233] where 1532 stands for Razer Inc. and 0233 is a yet unknown device. Similarly to 0232, which Openrazer project identifies as a keybard of the previous 2017 Blade laptop (https://github.com/openrazer/openrazer/blob/master/driver/razerkbd_driver.h#L143). Thus a USB HID part is probably out of interest for now.

The i2c interface is presumably responsible for the touch positioning. It's mentioned in the dmesg.log surrounded with the vdd supply and interrupt errors of the so called i2c-1A582000 device. The i2c bus tree and the i2cdetect output is attached.

Another interesting detail lies in the touchpad behavior in the Windows OS. The laptop is bundled with a plenty of drivers and is fully functional from the factory. But after the clean Windows installation - touchpad is unresponsive also. The required driver to enable the touchpad is an Intel Serial IO Driver (http://drivers.razersupport.com//index.php?_m=downloads&_a=viewdownload&downloaditemid=2878&nav=0,350,765,766). It's comprised of 4 parts: GPIO, I2C, SPI and UART. Only GPIO and I2C are required for the touchpad to become responsive without reboot (INF files of these drivers are attached). Right after installation Windows detects the touchpad as an I2C HID Device and HID-Complaint touch pad (the device manager screenshots are attached). Both devices has a id 1A58:2000, appeared previosly in the kernel log.

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 276789
dmesg

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 276791
i2cdetect

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 276793
i2c_hw_id

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 276795
windows_gpio2_inf

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 276797
windows_i2c_inf

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 276799
lsusb

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 276801
touchpad_hw_id

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 277029
acpi dump

[mika.westerberg (mika.westerberg-linux-kernel-bugs)]

Can you also attach content of /sys/kernel/debug/pinctrl/INT3450:00/pins and /sys/kernel/debug/pinctrl/INT3450:00/gpio-ranges?

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 277051
pins

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 277053
gpio-ranges

[soundhermit (soundhermit-linux-kernel-bugs)]

added pins and gpio-ranges

[mika.westerberg (mika.westerberg-linux-kernel-bugs)]

Created attachment 277055
Add more debugging to gpiolib-acpi.c

Can you try the attached patch and then attach dmesg again? It should print the GPIO number we get from the BIOS.

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 277057
dmesg_with gpiolib-acpi_patch

[soundhermit (soundhermit-linux-kernel-bugs)]

pin = 100

[andy.shevchenko (andy.shevchenko-linux-kernel-bugs)]

This pin is configured by BIOS as GPIO direct interrupt to IOAPIC (SCI mode).
So, there is coupled GpioInt() and Interrupt() resources. If I read DSDT correctly the IRQ resource, which must be used, depends on the setting of some internal variable. My understanding that, since the pin is configured to generate SCI, the driver should respect BIOS settings.

[andy.shevchenko (andy.shevchenko-linux-kernel-bugs)]

Okay, more investigation on the message "flag is output". It seems that in the driver we missed the fact of IRQ to pin translation in one case. That's why we are actually talking to hadrware pin 100 (ACPI 129) instead of pin 79 (ACPI 100). And that pin is indeed configured as output.

But I need to confirm this, because it's early morning and I even managed to send a patch to mailing list (related to this, but not fixing) with a completely wrong commit message. Need some sleep for sure.

[andy.shevchenko (andy.shevchenko-linux-kernel-bugs)]

Take the bug as it seems to be related to our GPIO/pinctrl driver.

[soundhermit (soundhermit-linux-kernel-bugs)]

Let me know if you need me to try out anything.

[andy.shevchenko (andy.shevchenko-linux-kernel-bugs)]

(In reply to jamir from comment #21)
> Let me know if you need me to try out anything.

Can you add to the top of gpiochip_lock_as_irq() the following hack and try to boot again (we need dmesg with 'ignore_loglevel' added to the kernel command line):

if (offset == 100)
 offset = 79;

[soundhermit (soundhermit-linux-kernel-bugs)]

Created attachment 277159
dmesg with overriding pin 100 with 79

[soundhermit (soundhermit-linux-kernel-bugs)]

the touchpad is still not functional I have attached the dmesg after the change.

[soundhermit (soundhermit-linux-kernel-bugs)]

The error code is different this time though -

i2c_hid: probe of i2c-1A582000:00 failed with error -1 instead of -22

[Manavjeet Singh (singhji31)]

I am also facing the same problem on the same model. I have tried everything I could find on the Internet. If anyone has a solution please post.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/

[Ian Newborn (saurbaum)]

kernel-bug-exists-upstream

[Kai-Heng Feng (kaihengfeng)]

Please attach dmesg under linux kernel v4.19-rc1.

[Ian Newborn (saurbaum)]

TUF-GAMING-FX504GD-FX80GD:~$ dmesg
[ 0.000000] microcode: microcode updated early to revision 0x96, date = 2018-05-02
[ 0.000000] Linux version 4.19.0-041900rc1-generic (kernel@kathleen) (gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1)) #201808262231 SMP Sun Aug 26 22:33:11 UTC 2018
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc1-generic root=UUID=7960da4f-2b4c-4e1a-b8d7-d8eb005249aa ro nouveau.modeset=0 i8042.nomux=1 i8042.reset i8042.kbdreset=1 quiet splash vt.handoff=1
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000079049fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007904a000-0x000000007a4e0fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007a4e1000-0x000000007a55dfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000007a55e000-0x000000007a649fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000007a64a000-0x000000007ac40fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007ac41000-0x000000007ad0dfff] type 20
[ 0.000000] BIOS-e820: [mem 0x000000007ad0e000-0x000000007ad0efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007ad0f000-0x000000007fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000027dffffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] efi: EFI v2.60 by American Megatrends
[ 0.000000] efi: ACPI 2.0=0x7a4fa000 ACPI=0x7a4fa000 SMBIOS=0x7aa89000 SMBIOS 3.0=0x7aa88000 ESRT=0x75e26d18 MEMATTR=0x75868018
[ 0.000000] SMBIOS 3.1.1 present.
[ 0.000000] DMI: ASUSTeK COMPUTER INC. TUF GAMING FX504GD_FX80GD/FX504GD, BIOS FX504GD.312 07/13/2018
[ 0.000000] tsc: Detected 2300.000 MHz processor
[ 0.000687] tsc: Detected 2304.000 M...

[Hieu Cao (mrhieu059)]

I have the same model and got the same problem. Did you fix?

[Kai-Heng Feng (kaihengfeng)]

The error happens at here:
[ 4.224268] cannonlake-pinctrl INT3450:00: pin 225 cannot be used as IRQ
[ 4.224277] genirq: Setting trigger mode 8 for irq 128 failed (intel_gpio_irq_type+0x0/0x140 [pinctrl_intel])
[ 4.224422] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
[ 4.224436] i2c_hid i2c-ELAN1200:00: Linked as a consumer to regulator.0
[ 4.224438] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vddl not found, using dummy regulator

[sarath (sarathmr)]

Yes I am also facing the same issue.

[Roman (vanesyan)]

My Asus FX504 laptop is also affected by the issue, I'm on Ubuntu 18.04.1 (kernel 4.15), tried kernel 4.18, nothing changes, still doesn't work

[Roman (vanesyan)]

Can confirm that on linux v4.19.0-041900rc7 touchpad is working (doesn't sure if anything is supported) in terms of basic operations (clicks, cursor, etc.)

Can you please backport the patch to linux v4.15 on Ubuntu 18.04

[janus.reith (janus.reith-linux-kernel-bugs)]

Accordingly to comments 144-147 I compiled the kernel from v4.19-rc5 branch and applied the two patches that were attached by Mika 2018-09-25.

Contrary to what Bo posted in 148, my Touchpad still works as it used to do with the other kernels(except some 4.15 kernel that shipped with a latest ubuntu live stick I tried).

Touchscreen still doesn't work.

[mika.westerberg (mika.westerberg-linux-kernel-bugs)]

Hi Janus,

Do you still see the message "GPIO can't be used as IRQ" when you boot the system? If not, it may be another issue and in that case I suggest you to file a bug against input subsystem/HID instead.

[janus.reith (janus.reith-linux-kernel-bugs)]

dmesg | grep -i "GPIO" does not return anything, neither does dmesg --level=err
I guess my issue is not directly related then.

[benjamin.tissoires (benjamin.tissoires-linux-kernel-bugs)]

Janus, IIRC, lat time I checked, CONFIG_PINCTRL_CANNONLAKE was not set in the default configuration of Fedora kernels. Can you double check?

If CONFIG_PINCTRL_CANNONLAKE is not set, the device will not show up at all in the dmesg.

[jwrdegoede (jwrdegoede-linux-kernel-bugs)]

(In reply to Benjamin Tissoires from comment #156)
> Janus, IIRC, lat time I checked, CONFIG_PINCTRL_CANNONLAKE was not set in
> the default configuration of Fedora kernels. Can you double check?
>
> If CONFIG_PINCTRL_CANNONLAKE is not set, the device will not show up at all
> in the dmesg.

This sounds like something which we need to fix in the Fedora kernels. Benjamin, can you ask the Fedora kernel team to enable this ?

[janus.reith (janus.reith-linux-kernel-bugs)]

@Benjamin, That seems to be right, the config file includes the comment "# CONFIG_PINCTRL_CANNONLAKE is not set".

This is also the case for their latest 4.19-0-0.rc8 vanilla kernel they provide in the repos.

When compiling myself I took over that configuration. Will enable it and give feedback after compilation finished!

(Hope I'm not going beyond the scope of this bug too far)

[benjamin.tissoires (benjamin.tissoires-linux-kernel-bugs)]

(In reply to Hans de Goede from comment #157)
> This sounds like something which we need to fix in the Fedora kernels.
> Benjamin, can you ask the Fedora kernel team to enable this ?

done: https://bugzilla.redhat.com/show_bug.cgi?id=1641057
I'll ping Laura if she doesn't take it in the next few days.

(In reply to janus.reith from comment #158)
> (Hope I'm not going beyond the scope of this bug too far)

No worries, it's better to understand why the fix is not working for you, and hopefully, the problem is just in the config file.

[janus.reith (janus.reith-linux-kernel-bugs)]

Touchreen works now!

I built the kernel using the same setup I tried before, v4.19-rc5 with the two patches, now with CONFIG_PINCTRL_CANNONLAKE enabled.

I might be wrong, but it seems like the touchpad cursor speed seems to be faster? It already worked before, including multitouch gestures.

Just to clarify: If I compile the latest 4.19-0-0.rc8, will I still need the two patches?

[benjamin.tissoires (benjamin.tissoires-linux-kernel-bugs)]

(In reply to janus.reith from comment #160)
> I might be wrong, but it seems like the touchpad cursor speed seems to be
> faster? It already worked before, including multitouch gestures.

That's possible. Haven't paid much attention to this as the test setup I have is not my primary machine.

>
> Just to clarify: If I compile the latest 4.19-0-0.rc8, will I still need the
> two patches?

IIRC, you should be good with a vanilla 4.19-rc8, yes. So no need for extra patches.

[gschram (gschram-linux-kernel-bugs)]

I have compiled the 4.19-rc8 kernel today (using the mainline kernel package in Arch User Repository) on my HP ZBOOK G5 x360. And I can confirm the touchpad works way smoother (faster) now. This might be because libinput is now recognizing it, but I haven't been able to confirm this yet.
I didn't need any patches, so the touchscreen, pen and touchpad now work out of the box.

The only issue I still have is that GDM seems to have a problem starting with the new kernel (keep having a blinking cursor till I press the power button and then it goes to sleep, after sleep GDM works fine.

When I replaced GDM with Lightdm everything worked fine without going to sleep first.

[Denis (den4ikept1)]

It's true. Linux kernel v4.19 support touchpad. Also scroll works.

[Ian Newborn (saurbaum)]

Added kernel-fixed-upstream as it now is with the released 4.19

[Roman (vanesyan)]

Any possibility the fix will be backported to Ubuntu 18.04?

[qiao.bo (qiao.bo-linux-kernel-bugs)]

Hello,

Touchpad on my HP Zbook Studio G5 works great under the new 4.19 stable release. Thanks for the effort.

[eug5ne (eug5ne-linux-kernel-bugs)]

(In reply to Marc Landolt from comment #68)
> (In reply to Andy Shevchenko from comment #66)
> > Created attachment 277553 [details]
> > Fix community ordering for H variant
> >
> > Another patch for Cannonlake PCH-H.
>
> Yay, GREAT, Andy you're a Genius, the Touchpad is working :)
>
> After Downloading Kernel 4.18.RC6, patching with
> https://bugzilla.kernel.org/attachment.cgi?id=277507&action=diff and
> https://bugzilla.kernel.org/attachment.cgi?id=277553&action=diff it's
> working.
>
> -Tap to click works
> -2 Finger scroll works (only Natural Scrolling, always on)
> -2 Finger right click works
> -left mouse button works
> -right mouse button does not work but with 2 finger click it works
> -Edge Scrolling does not work
> -it disconects from time to time (rmmod -r hid-multitouch && modprobe
> hid-multitouch helps)
>
> shall I test other patches and do you still need the outputs from Comment 67
> (interrupts, iomem, ranges, pins?
>
> With kind regards and many thanks so far
> Marc Landolt

Thanks @Marc!

The same solution worked for GL503-GE ;-)

Cheers!

[mrhieu059 (mrhieu059-linux-kernel-bugs)]

Hi everyone.
Any news here, does the the disconnecting randomly has been fix?

[2009 (2009-linux-kernel-bugs)]

(In reply to Hieu Cao from comment #165)
> Hi everyone.
> Any news here, does the the disconnecting randomly has been fix?

Hello Hieu Cao

on my GL703GE it's not randomly but when you put the palm or 5 or more fingers on it.

i opened another bug but not assigned yet and i did not hear from any solution so far: https://bugzilla.kernel.org/show_bug.cgi?id=200663

With kind regards
Marc

[mrhieu059 (mrhieu059-linux-kernel-bugs)]

Thanks Marc Landolt
I'll following that bug, I hope it will be fix in the future.

[Jay Chakra (jaychakra)]

Pardon me for being newbie in the linux world. But I have the same issue. I am using Ubuntu 18.04.1 with linux kernel v4.19.1 but still my trackpad doesn't work. The result of xinput is same as the OP has posted.

`
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Dell Dell Universal Receiver Consumer Control id=14 [slave pointer (2)]
⎜ ↳ Dell Dell Universal Receiver Mouse id=19 [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)]
    ↳ Asus Wireless Radio Control id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Video Bus id=9 [slave keyboard (3)]
    ↳ Power Button id=10 [slave keyboard (3)]
    ↳ Sleep Button id=11 [slave keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)]
    ↳ Asus WMI hotkeys id=17 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)]
    ↳ Dell Dell Universal Receiver id=12 [slave keyboard (3)]
    ↳ Dell Dell Universal Receiver System Control id=13 [slave keyboard (3)]
    ↳ Dell Dell Universal Receiver Consumer Control id=15 [slave keyboard (3)]
`

[Kai-Heng Feng (kaihengfeng)]

Please see if this Bionic kernel works for you:
https://people.canonical.com/~khfeng/lp1781879/

[[e-mail] (posix4e)]

@Kai, that totally fixed me

[Kieran Robinson (krobbo)]

Hi there,

I have the same issue with ASUS TUF FX504

Output from 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)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Video Bus id=9 [slave keyboard (3)]
    ↳ Power Button id=10 [slave keyboard (3)]
    ↳ Sleep Button id=11 [slave keyboard (3)]
    ↳ Asus Wireless Radio Control id=7 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=13 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
    ↳ Asus WMI hotkeys id=14 [slave keyboard (3)]

Any fix?

Thanks

[Ian Newborn (saurbaum)]

While the latest kernels do at least work in some form they aren't quite right.

The sensitivity doesn't respond to the GUI settings. Also after some time the touchpad stops responding. Sometimes it recovers others it does not.

[Kieran Robinson (krobbo)]

What did you run to get it to work in some fashion ?

[Kieran Robinson (krobbo)]

FIX

wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/linux-headers-4.19.0-041900_4.19.0-041900.201810221809_all.deb

wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/linux-headers-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb

wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/linux-image-unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb

wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/linux-modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb

sudo dpkg -i *.deb

[Kai-Heng Feng (kaihengfeng)]

Oops, I forgot what commits I backported.

So please test the following kernels,
Bionic: https://people.canonical.com/~khfeng/lp1781879-bionic/
Cosmic: https://people.canonical.com/~khfeng/lp1781879-cosmic/

[Roman (vanesyan)]

Hello there! I cannot boot provided kernel because of signature issue. How to sign kernel?

[Kai-Heng Feng (kaihengfeng)]

Please disable Secure Boot in the BIOS.

[Roman (vanesyan)]

I've been able to use touchpad for about 15 minutes. Then, when I turned on two-finger scrolling option in settings touchpad stopped working with following error printed in logs:

Message: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Kernel device: +i2c:i2c-ELAN1200:00

[Roman (vanesyan)]

Also can report that right click (context menu) is not working correctly, when clicking with it acts like a left click (selecting items, etc.)

[Roman (vanesyan)]

I've also noticed that system constantly reports logs somehow related to touchpad with following context:

sender: gdm-x-sesion
message: See https://wayland.freedesktop.org/libinput/doc/1.12.1/touchpad-jumping-cursors.html for details

sender: gdm-x-session
message: (EE) event17 - ELAN1200:00 04F3:3090 Touchpad: kernel bug: Touch jump detected and discarded.

[Roman (vanesyan)]

Can also confirm that previous message with i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) context, appears independently from settings change, and occurs randomly.

If you need other info feel free to ask. Thx.

[Kai-Heng Feng (kaihengfeng)]

It's a different issue. If the the touchpad start working, then the original bug "GPIO can't be used as IRQ" is solved.

[Roman (vanesyan)]

I'm still not sure, do I need to open a new ticket for issue, or what?

[andy.shevchenko (andy.shevchenko-linux-kernel-bugs)]

This bug has been fixed in v4.20.

[Adrien (adrien-du)]

Hi all,

I'm new on ubuntu with an fx-504-gm.

My keyboard works well but my touchpad don't work.

Can you help me to fix this issue? Can you show me the test I have to make?

Sorry for my english, I'm french and sorry for my ignorance on this system, I’m really new!

Thanks

[mrhieu059 (mrhieu059-linux-kernel-bugs)]

It worked on v4.20 automatically. Few days ago, but I also uninstalled it either. Because the annoyning of disconnecting. I wonder if it fixed the disconnecting? I just want to make sure that to reinstall linux again.

(In reply to Andy Shevchenko from comment #168)
> This bug has been fixed in v4.20.
Does it fix the disconnecting problem?

[Andre Bonna (andre.bonna)]

Thanks! The new kernel release worked perfectly!

[Ian Newborn (saurbaum)]

Perfect is a bit much. It still doesn't obey the settings for sensitivity but it does at least work most of the time.

[Kai-Heng Feng (kaihengfeng)]

Does #201 #202 mean the new kernel from Ubuntu archive already fixes the issue?

[2009 (2009-linux-kernel-bugs)]

(In reply to Hieu Cao from comment #169)
> It worked on v4.20 automatically. Few days ago, but I also uninstalled it
> either. Because the annoyning of disconnecting. I wonder if it fixed the
> disconnecting? I just want to make sure that to reinstall linux again.
>
> (In reply to Andy Shevchenko from comment #168)
> > This bug has been fixed in v4.20.
> Does it fix the disconnecting problem?

in my case (Asus GL703GE) it does not. Disconnection Problem persists, but you can take now a 4.20 Kernal without patch and the Touchpad will work except if you put 5 Fingers or the Palm on it (on GL703GE)

with kind regards
Marc Landolt

[Dirk-Jan van Vliet (dirkjanvanvliet)]

I'm running Ubuntu 18.10 with kernel 4.20.6 and I've got a Asus FX503VD with the same touchpad as other people in this thread. I'm experiencing these problems with libinput:

- Sloppy mouse pointer movements (moves very slow, not precise and the pointer jumps sometimes)
- The mousepad stops working sometimes suddenly for a few seconds or minutes (this could be the 5 fingers/palm problem)

I can fix the first problem by replacing libinput with mtrack. But the disconnecting still happens with mtrack. Is this the same problem as mentioned in this thread? The latest kernel update did not fix this for me.

[qiao.bo (qiao.bo-linux-kernel-bugs)]

This problem is not completely resolved: touchpad is not full functional after waking from suspend. This has been confirmed by multiple users as reported in #201175.