Bug 1383154 - Acer E5 Elantech touchpad not detected in xinput
Summary: Acer E5 Elantech touchpad not detected in xinput
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 05:03 UTC by Brian Evans
Modified: 2018-07-25 03:07 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-23 18:29:16 UTC
Type: Bug


Attachments (Terms of Use)
Output of dmesg from default configuration (85.60 KB, text/plain)
2016-10-10 05:03 UTC, Brian Evans
no flags Details
cat /proc/bus/input/devices > input.devices.txt (3.22 KB, text/plain)
2016-10-10 05:04 UTC, Brian Evans
no flags Details
i2cdetect output with smbus details (3.30 KB, text/plain)
2016-10-10 05:05 UTC, Brian Evans
no flags Details
acpidump output (788.64 KB, text/plain)
2016-10-10 05:07 UTC, Brian Evans
no flags Details
journalctl -b output (331.87 KB, text/plain)
2016-10-10 05:09 UTC, Brian Evans
no flags Details

Description Brian Evans 2016-10-10 05:03:26 UTC
Created attachment 1208701 [details]
Output of dmesg from default configuration

Description of problem:
Fedora 24 does not recognize my Elantech trackpad/touchpad on my Acer Aspire E5-553G. A USB mouse is happy, and it does I've been digging into the issue, and can say the following:

* Live image did not have it working. I installed anyway, as I figured an update may work
* Update did not allow for functionality
* The device is i2c-hid, as seen on Windows 10.
* When testing different distros, I did get it working on Mint after installing updates. But I'm not a Mint fan, and Mint had other issues on the laptop, so going to try and get Fedora working.
* dmesg shows: i2c_hid: probe of i2c-ELAN0501:00 failed with error -2
* The Secure Boot setting in UEFI being enabled or disabled makes no difference

Version-Release number of selected component (if applicable):
Linux humperdinck 4.7.5-200.fc24.x86_64 #1 SMP Mon Sep 26 21:25:47 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
Always on current system

Steps to Reproduce:
1. Install Fedora alongside Windows on Acer Aspire E5-553G non LVM
2. Note behavior of touchpad in live environment
3. Note behavior of touchpad after installation
4. dnf upgrade environment to latest
5. Note behavior of touchpad after upgrade

Actual results:
Touchpad is non functional and not listed in xinput or Settings. USB mouse works.

Expected results:
Touchpad is detected and functional in environment

Additional info:
Items tried (and failed, so reverted as needed):

* Setting /etc/modprobe.d/blacklist.conf to "blacklist i2c-hid", and then rebooting
* Full update of system
* reinstalling xorg-x11-drv-synaptics
* copied /etc/modprobe.d/blacklist*.conf from Mint into Fedora
* Using combination of above, tried launching with appending to the grub commands:
   psmouse.proto=base
   psmouse.proto=imps i8042.reset i8042.nomux=1

In all cases, the xinput list does not display the touchpad. On Mint, xinput lists the touchpad as:
↳ ELAN0501:00 04F3:3019 Touchpad          	id=13	[slave  pointer  (2)]


Terminal output various things:

$ cat /etc/redhat-release 
Fedora release 24 (Twenty Four)

$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ PIXART USB OPTICAL MOUSE                	id=12	[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)]
    ↳ Video Bus                               	id=8	[slave  keyboard (3)]
    ↳ Power Button                            	id=9	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=10	[slave  keyboard (3)]
    ↳ HD WebCam                               	id=11	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=13	[slave  keyboard (3)]
    ↳ Acer WMI hotkeys                        	id=14	[slave  keyboard (3)]

Relevant sections of dmesg (I think, from grep, with manual input of a Call Trace)
$ dmesg | grep -iE 'input|pnp|i8042|i2c'
[    0.324276] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.324381] acpi PNP0A08:00: _OSC: platform does not support [PCIeCapability]
[    0.324429] acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[    0.324431] acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug PME AER PCIeCapability]
[    0.324433] acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug PME AER]
[    0.324435] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
[    0.324447] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[    0.358815] pnp: PnP ACPI init
[    0.359070] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.359187] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.359214] pnp 00:02: Plug and Play ACPI device, IDs FUJ7401 PNP0303 (active)
[    0.359290] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.359346] system 00:04: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.359793] pnp: PnP ACPI: found 5 devices
[    0.756753] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[    0.756793] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
[    0.756826] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
[    0.756881] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[    0.798298] i8042: PNP: PS/2 Controller [PNP0303:KBC0] at 0x60,0x64 irq 1
[    0.798299] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    0.800321] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.807685] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
[    0.848867]  pnp0: hash matches
[    1.589990] input: PIXART USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:12.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:093A:2510.0001/input/input5
[    1.591340] hid-generic 0003:093A:2510.0001: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:12.0-1.1/input0
[    8.950783] i2c /dev entries driver
[    9.200722] ------------[ cut here ]------------
[    9.200731] WARNING: CPU: 1 PID: 584 at drivers/i2c/busses/i2c-designware-core.c:280 i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core]
[    9.200732] Modules linked in: i2c_designware_platform(+) i2c_designware_core tpm_crb pcc_cpufreq(-) acpi_cpufreq tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc i2c_dev amdkfd amd_iommu_v2 amdgpu rtsx_pci_sdmmc mmc_core crc32c_intel i2c_algo_bit drm_kms_helper serio_raw uas ttm usb_storage 8021q garp drm stp llc mrp r8169 rtsx_pci mii fjes i2c_hid
[    9.200754] CPU: 1 PID: 584 Comm: systemd-udevd Not tainted 4.7.5-200.fc24.x86_64 #1
[    9.200756] Hardware name: Acer Aspire E5-553G/Wasp_BR, BIOS V1.06 05/18/2016
[    9.200758]  0000000000000286 00000000e7db00c8 ffff8800bdb07a08 ffffffffb63daaaf
[    9.200761]  0000000000000000 0000000000000000 ffff8800bdb07a48 ffffffffb60a0b0b
[    9.200764]  00000118b648c521 ffff880212470828 0000000000000000 000000000000012c
[    9.200766] Call Trace:
[    9.200774]  [<ffffffffb63daaaf>] dump_stack+0x63/0x84
[    9.200778]  [<ffffffffb60a0b0b>] __warn+0xcb/0xf0
[    9.200781]  [<ffffffffb60a0c3d>] warn_slowpath_null+0x1d/0x20
[    9.200783]  [<ffffffffc0555091>] i2c_dw_clk_rate+0x41/0x50 [i2c_designware_core]
[    9.200786]  [<ffffffffc0555321>] i2c_dw_init+0x111/0x430 [i2c_designware_core]
[    9.200788]  [<ffffffffc0556019>] i2c_dw_probe+0x39/0x1d0 [i2c_designware_core]
[    9.200792]  [<ffffffffc05d94a2>] dw_i2c_plat_probe+0x1e2/0x420 [i2c_designware_platform]
[    9.200796]  [<ffffffffb652534b>] platform_drv_probe+0x3b/0xa0
[    9.200798]  [<ffffffffb651f170>] ? devices_kset_move_last+0x50/0x90
[    9.200801]  [<ffffffffb652313c>] driver_probe_device+0x22c/0x440
[    9.200803]  [<ffffffffb6523421>] __driver_attach+0xd1/0xf0
[    9.200805]  [<ffffffffb6523350>] ? driver_probe_device+0x440/0x440
[    9.200807]  [<ffffffffb6520a6c>] bus_for_each_dev+0x6c/0xc0
[    9.200809]  [<ffffffffb652282e>] driver_attach+0x1e/0x20
[    9.200811]  [<ffffffffb6522273>] bus_add_driver+0x1c3/0x280
[    9.200813]  [<ffffffffc05e8000>] ? 0xffffffffc05e8000
[    9.200815]  [<ffffffffb6523d70>] driver_register+0x60/0xe0
[    9.200817]  [<ffffffffc05e8000>] ? 0xffffffffc05e8000
[    9.200819]  [<ffffffffb65252c6>] __platform_driver_register+0x36/0x40
[    9.200822]  [<ffffffffc05e8017>] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform]
[    9.200825]  [<ffffffffb6002190>] do_one_initcall+0x50/0x180
[    9.200828]  [<ffffffffb6220152>] ? kmem_cache_alloc_trace+0x182/0x1d0
[    9.200831]  [<ffffffffb61b468b>] ? do_init_module+0x27/0x1d8
[    9.200833]  [<ffffffffb61b46c3>] do_init_module+0x5f/0x1d8
[    9.200836]  [<ffffffffb612b820>] load_module+0x1fd0/0x27e0
[    9.200839]  [<ffffffffb6128700>] ? __symbol_put+0x60/0x60
[    9.200842]  [<ffffffffb612c17e>] SYSC_init_module+0x14e/0x190
[    9.200844]  [<ffffffffb612c2ee>] SyS_init_module+0xe/0x10
[    9.200847]  [<ffffffffb6003d52>] do_syscall_64+0x62/0x110
[    9.200850]  [<ffffffffb67ec621>] entry_SYSCALL64_slow_path+0x25/0x25
[    9.200852] ---[ end trace 0ede74c44e0243f4 ]---
[    9.206613] i2c_hid i2c-ELAN0501:00: Failed to get GPIO interrupt
[    9.216526] i2c_hid: probe of i2c-ELAN0501:00 failed with error -2
[    9.219360] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
[    9.220737] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:07/LNXVIDEO:01/input/input7
[    9.465780] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card0/input8
[    9.476965] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[    9.488578] input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:09.2/sound/card1/input9
[    9.512292] input: HD WebCam as /devices/pci0000:00/0000:00:10.0/usb2/2-1/2-1:1.0/input/input10
[    9.579183] input: Acer WMI hotkeys as /devices/virtual/input/input11
[    9.585519] input: Acer BMA150 accelerometer as /devices/virtual/input/input12


Behavior different than Bug 1326577, as in that bug has device detected, just not used.
Behavior different than Bug 1246732, as that defect left closed when problem not present in Secure boot

Attaching logs

Comment 1 Brian Evans 2016-10-10 05:04:43 UTC
Created attachment 1208702 [details]
cat /proc/bus/input/devices > input.devices.txt

Comment 2 Brian Evans 2016-10-10 05:05:57 UTC
Created attachment 1208703 [details]
i2cdetect output with smbus details

Comment 3 Brian Evans 2016-10-10 05:07:14 UTC
Created attachment 1208704 [details]
acpidump output

Comment 4 Brian Evans 2016-10-10 05:09:19 UTC
Created attachment 1208705 [details]
journalctl -b output

Comment 5 Brian Evans 2016-10-16 03:44:13 UTC
While I had set the severity of the bug to Medium initially, that was more in terms of how I grant this is likely not a huge issue in the grand scheme of things, but that is more of a priority question. While I can work around the issue by plugging in a USB mouse, this is far from ideal, and retroactively wish I would have set it to High instead, as it is getting increasingly frustrating.

Having a laptop that has to have an external input device defeats some of the purpose of a stand alone unit. So if someone could change that (as I don't see how), that would be wonderful.

Additionally, if there would have been some better component to use, I'd love for this to be in the appropriate location.

Thanks.

Comment 6 Brian Evans 2016-12-05 03:38:44 UTC
Bug exists on a clean install of Fedora 25. Had to do fresh install due to Wayland issues, but after fresh install (as well as in Fedora 25 install media), bug persists.

Also, I consider this severity High.

Comment 7 Brian Evans 2016-12-07 07:54:50 UTC
BIOS contains an option to change the touchpad from Advanced to Basic. This just sets the device to PS/2 on boot. This does make the touchpad functional, just non default for other users who may buy this model.

Able to boot with i8042.nopnp=1 in boot command. Have to fn+F7 to enable touchpad this way.

When either on i8042.nopnp=1 or without, there is a /sys/bus/i2c/devices/i2c-ELAN0501\:00/ path which is populated. I've been unable to figure out how to try and re-attempt using it. i2cdetect -l did not list it as an available option (just had i2c-0 through i2c-5).

So not vital at this point, but still busted.

Comment 8 Laura Abbott 2017-01-17 01:19:18 UTC
*********** 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 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 9 Brian Evans 2017-02-02 08:33:32 UTC
Changed BIOS setting back to the default setting of "Advanced" on 4.9.5-200.fc25.x86_64 and problem still exists. Workaround continues to work, but is not how a new user would be using the device out of the box.

Comment 10 Justin M. Forbes 2017-04-11 14:49:07 UTC
*********** 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 25 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 11 Brian Evans 2017-04-16 04:15:51 UTC
Bug still exists in 4.10.9-200.fc25.x86_64

Comment 12 Francisco de la Peña 2017-04-27 17:50:50 UTC
This also happens to me, but seems to happen to me when booting with battery. When this happens, the dmesg output differs. This does not seem to happen when booting with power cable plugged. The "basic" setting in BIOS workaround works for me, too.

Comment 13 Dmitry Teplyakov 2017-06-13 21:54:03 UTC
I have a same problem on acer extensa 2510g.
On ubuntu gnome with xinput it's work!

Comment 14 Dmitry Teplyakov 2017-06-13 21:54:45 UTC
For up comment:
i have a synaptics.

Comment 15 Fedora End Of Life 2017-11-16 15:43:52 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 16 Brian Evans 2017-12-06 08:47:43 UTC
Bug still exists in 4.13.13-300.fc27.x86_64 . Bumping the major version of bug.

Comment 17 Laura Abbott 2018-02-20 19:51:41 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  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 experience different issues, please open a new bug report for those.

Comment 18 Brian Evans 2018-02-22 06:16:46 UTC
Bug still exists in 4.15.3-300.fc27.x86_64. Workaround of disabling advanced trackpad continues to work.

Comment 19 Justin M. Forbes 2018-07-23 15:19:06 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are 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 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  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 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 20 Francisco de la Peña 2018-07-23 18:01:14 UTC
I can't reproduce this issue anymore since some major kernel versions. I did also a BIOS firmware update time ago, not sure if this helped with the fix.

Comment 21 Justin M. Forbes 2018-07-23 18:29:16 UTC
Okay, closing this bug then. Thanks for the response. Feel free to reopen if others are still experiencing the issue.

Comment 22 Brian Evans 2018-07-25 03:07:37 UTC
On original machine, it is fixed. I don't normally set the touchpad to advanced, but to verify, I did. So I don't know if it was a major kernel version, and I didn't do a BIOS update.

Looks to be a change in how wayland detects. xinput doesn't show the touchpad as ELAN (as seen on Mint 2 years ago), but now as:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ xwayland-pointer:13                     	id=6	[slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:13            	id=7	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ xwayland-keyboard:13                    	id=8	[slave  keyboard (3)]

So confirmed good on 4.17.7-100.fc27.x86_64. If it is broken on someone else's machine, it isn't this same bug (or a regression, I suppose).


Note You need to log in before you can comment on or make changes to this bug.