| Summary: | Acer E5 Elantech touchpad not detected in xinput | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian Evans <brian.r.evans> | ||||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 27 | CC: | brian.r.evans, dimon2242, gansalmon, ichavero, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda, mchehab, tbondvagyok | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2018-07-23 18:29:16 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Brian Evans
2016-10-10 05:03:26 UTC
Created attachment 1208702 [details]
cat /proc/bus/input/devices > input.devices.txt
Created attachment 1208703 [details]
i2cdetect output with smbus details
Created attachment 1208704 [details]
acpidump output
Created attachment 1208705 [details]
journalctl -b output
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. 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. 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. *********** 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. 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. *********** 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. Bug still exists in 4.10.9-200.fc25.x86_64 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. I have a same problem on acer extensa 2510g. On ubuntu gnome with xinput it's work! For up comment: i have a synaptics. 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. Bug still exists in 4.13.13-300.fc27.x86_64 . Bumping the major version of bug. 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. Bug still exists in 4.15.3-300.fc27.x86_64. Workaround of disabling advanced trackpad continues to work. *********** 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. 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. Okay, closing this bug then. Thanks for the response. Feel free to reopen if others are still experiencing the issue. 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).
|