Bug 1578573
| Summary: | Touchpad not working in latest updates | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matt Castelein <matt.castelein> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 28 | CC: | airlied, bskeggs, btissoir, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, matt.castelein, mchehab, mjg59, peter.hutterer, steved | ||||||
| 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-10-03 20:27:27 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: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Matt Castelein
2018-05-15 21:29:52 UTC
huh, weird, that means the kernel has somehow forgotten to talk to your touchpad. What laptop model is this and what's the last kernel version that worked? A dmesg is going to be useful too. It is a Dell Inspiron N5010, and I believe the last kernel that reliably worked w/ the touchpad was 4.15.17-300.fc27. I've discovered that if I connect my bluetooth mouse during the boot up, the touchpad will work during that session. Very strange. I'm attaching a dmesg for both the case where the touchpad is not detected, and also one where I attached the mouse. Created attachment 1438680 [details]
dmesg output - touchpad not working
Created attachment 1438681 [details]
dmesg output - touchpad working
This was the case where I connected my bluetooth mouse during boot.
Ok, so this is the dmesg line which we care about: not working: [ 2.348998] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input6 working: [ 2.321471] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 So definitely a kernel bug. Matt, 4.15.17-300.fc27 is the last kernel which works reliable, correct? What is the first version with problems? 4.15.17-300.fc27 works 100%. 4.16.3-200.fc27 is the first version I experienced the issue with. (In reply to Matt Castelein from comment #6) > 4.15.17-300.fc27 works 100%. 4.16.3-200.fc27 is the first version I > experienced the issue with. Thanks, I've checked all the changes under drivers/input/mouse and drivers/input/serio between 4.15 and 4.16 and nothing stands out. I've mailed the upstream maintainer asking if he has any ideas. No change in 4.17.5-200.fc28. 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 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. 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 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those. I am pleased to report this issue seems to be resolved in 4.18.10-200.fc28.x86_64. Thanks for letting us know I'm sorry, it seems I was mistaken. The problem still exists. I can only think that I must have selected the old kernel out of habit at this point.. I was sure I was on the right one! However, this is definitely still an issue. Working in Fedora 29. (4.19.4-300.fc29.x86_64) |