Bug 1578573 - Touchpad not working in latest updates
Summary: Touchpad not working in latest updates
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-15 21:29 UTC by Matt Castelein
Modified: 2018-12-01 18:28 UTC (History)
20 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-10-03 20:27:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output - touchpad not working (63.35 KB, text/plain)
2018-05-18 14:31 UTC, Matt Castelein
no flags Details
dmesg output - touchpad working (64.86 KB, text/plain)
2018-05-18 14:32 UTC, Matt Castelein
no flags Details

Description Matt Castelein 2018-05-15 21:29:52 UTC
Description of problem: Since the last 2 kernels in Fedora 27 and now Fedora 28 are detecting my SynPS/2 Synaptics Touchpad as a generic mouse.  I've lost middle click, scroll, and the touchpad disable button doesn't work.


Version-Release number of selected component (if applicable):
libinput-1.10.6-1.fc28.x86_64
xorg-x11-drv-libinput-0.27.1-2.fc28.x86_64


How reproducible:Always

Additional info:
Old journalctl output: kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6

New: kernel: input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input6

Comment 1 Peter Hutterer 2018-05-16 23:44:12 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.

Comment 2 Matt Castelein 2018-05-18 14:30:54 UTC
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.

Comment 3 Matt Castelein 2018-05-18 14:31:54 UTC
Created attachment 1438680 [details]
dmesg output - touchpad not working

Comment 4 Matt Castelein 2018-05-18 14:32:58 UTC
Created attachment 1438681 [details]
dmesg output - touchpad working

This was the case where I connected my bluetooth mouse during boot.

Comment 5 Hans de Goede 2018-05-18 15:14:51 UTC
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?

Comment 6 Matt Castelein 2018-05-18 15:59:44 UTC
4.15.17-300.fc27 works 100%.  4.16.3-200.fc27 is the first version I experienced the issue with.

Comment 7 Hans de Goede 2018-05-18 19:11:55 UTC
(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.

Comment 8 Matt Castelein 2018-07-15 15:00:54 UTC
No change in 4.17.5-200.fc28.

Comment 9 Laura Abbott 2018-10-01 21:19:23 UTC
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.

Comment 10 Matt Castelein 2018-10-03 20:26:41 UTC
I am pleased to report this issue seems to be resolved in 4.18.10-200.fc28.x86_64.

Comment 11 Laura Abbott 2018-10-03 20:27:27 UTC
Thanks for letting us know

Comment 12 Matt Castelein 2018-10-04 11:50:27 UTC
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.

Comment 13 Matt Castelein 2018-12-01 18:28:13 UTC
Working in Fedora 29. (4.19.4-300.fc29.x86_64)


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