LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Arch
User Name
Password
Arch This Forum is for the discussion of Arch Linux.

Notices


Reply
  Search this Thread
Old 08-28-2018, 01:04 PM   #1
xdyz5mx6
LQ Newbie
 
Registered: Aug 2018
Posts: 3

Rep: Reputation: Disabled
Touchpad not working since 4.18.3


Hi guys,

I'm using Arch Linux now for about half a year and it is working like a charm. Seems like I found my distro of choice.
Last week I updated the system and the kernel got updated from 4.17.14 to 4.18.3.
After the next reboot the touchpad of my Lenovo ThinkPad L470 (lsusb defines it as 'Synaptics...') stopped working.

Under the 4.17.14 kernel it worked like it should. Now only 'lsusb' shows the device, 'xinput list' does not anymore.
After manully downgrading the kernel to the previous one, the touchpad works again. So I guess it has to do with the newer kernel.

But now I really dont know where to start with finding a solution for that. I read about compiling a custom kernel or write a dkms module,
but that stuff is brand new to me, so I dont know where to start or even debug the error.

Thanks for ur help
 
Old 08-28-2018, 01:37 PM   #2
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Arch, KDE Neon, & ROSA
Posts: 2,949

Rep: Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880
The thing I do to avoid this is use a LTS kernel. While not as "techy" as recompiling the modern kernel with the support for the offending hardware in question, if the LTS kernel supports what I need (it has on all 3 laptops I've had Arch on in the last year), I stick with the LTS kernel.
 
Old 08-28-2018, 02:35 PM   #3
xdyz5mx6
LQ Newbie
 
Registered: Aug 2018
Posts: 3

Original Poster
Rep: Reputation: Disabled
Good point using a LTS kernel, but not mine. I want to use the leatest and 'greatest'. Do you have any idea why the touchpad does not work under the newer kernel?
Till today I thought, that if a kernel supports some piece of hardware, a newer kernel will do that, too.
Is this wrong, or could it just be a bug?
I want to understand why this happens.
 
Old 08-28-2018, 02:58 PM   #4
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Arch, KDE Neon, & ROSA
Posts: 2,949

Rep: Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880
90% of the time it's a regression bug that something was missed. But I got tired enough of it that I don't fight it anymore and I will never run the current kernel anymore in Arch. This happened far too often for me on the current kernel with sound drivers and touchpads.
 
Old 08-28-2018, 03:11 PM   #5
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,721
Blog Entries: 6

Rep: Reputation: 1384Reputation: 1384Reputation: 1384Reputation: 1384Reputation: 1384Reputation: 1384Reputation: 1384Reputation: 1384Reputation: 1384Reputation: 1384
If you don't mind a lot of hard work, you could do a kernel bisection. I had to do this when I found that kernels later than the 4.13 series wouldn't boot on my machine unless I switched off acpi (which for obvious reasons I was unwilling to do).

What this involves is downloading the kernel git tree (it's about 3 GB) and running git bisect on it repeatedly. You need to start with two known endpoints: a kernel that definitely works and one that definitely doesn't, as close to each other as possible. Each bisection gives you a new halfway kernel to build and test. Eventually you find the change that caused the problem. Then you can write a patch to reverse it.

Curiously the problem in my case turned out to be a change in the way memory was mapped. But it was a function in the acpi driver that triggered it.
 
Old 08-29-2018, 01:17 AM   #6
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 11,018
Blog Entries: 7

Rep: Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772
have you checked if the touchpad works better with libinput or synaptics?
https://wiki.archlinux.org/index.php/Touchpad#Touchpad
this suggests that libinput should be preferred, but maybe you would benefit from synaptics.
who knows.
honestly, from an archlinux user i would expect much, much more output and troubleshooting information.
all you are saying is, basically, that the touchpad doesn't work after a kernel upgrade...
your arch forums thread was likely met with stony silence.

Quote:
Originally Posted by xdyz5mx6 View Post
Good point using a LTS kernel, but not mine. I want to use the leatest and 'greatest'.
why?
it's not "greater" just because it's newer (as you are experiencing right now), and your laptop isn't getting any newer either.

you could try skipping this one kernel upgrade and see if it gets better after the next.
not a biggie for an archlinux user.
 
1 members found this post helpful.
Old 08-29-2018, 12:52 PM   #7
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,336
Blog Entries: 30

Rep: Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532
Moderator response

Moved: This thread is more suitable in <Arch> and has been moved accordingly to help your thread/question get the exposure it deserves.
 
Old 11-14-2018, 02:35 PM   #8
xdyz5mx6
LQ Newbie
 
Registered: Aug 2018
Posts: 3

Original Poster
Rep: Reputation: Disabled
Update 4.19.1

Still not working.
 
Old 11-16-2018, 11:44 AM   #9
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 11,018
Blog Entries: 7

Rep: Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772Reputation: 2772
Quote:
Originally Posted by xdyz5mx6 View Post
Update 4.19.1

Still not working.
bumping a thread without providing new information is usually frowned upon; certainly by me, esp. since you still haven't reacted on my suggestion of trying synaptics instead of libinput, and haven't actually shown us any effort/output.
 
Old 11-16-2018, 12:44 PM   #10
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,336
Blog Entries: 30

Rep: Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532Reputation: 2532
Moderator Response

@xdyz5mx6


From LQ Rules
Quote:
While almost every question does get an answer, we cannot guarantee a response. If your thread does not receive any responses, it will automatically be bumped twice.Threads should not be manually bumped without including additional information.
I do suggest that you re-read LQ Rules so you can insure that rules are followed.
 
Old 11-25-2018, 03:24 PM   #11
WFV
Member
 
Registered: Apr 2012
Location: CA
Distribution: Arch
Posts: 166

Rep: Reputation: Disabled
I think OP was saying updated kernel to 4.19.1 and still not working.
@ xdyz5mx6 - Have you tried hazel's suggestion in #5? or ondoho's in #6? or looked for any related bug report in Arch?

Last edited by WFV; 11-25-2018 at 03:27 PM.
 
Old 01-18-2019, 11:16 AM   #12
Rickkkk
Senior Member
 
Registered: Dec 2014
Location: Montreal, Quebec, CANADA
Distribution: Arch
Posts: 1,080

Rep: Reputation: 407Reputation: 407Reputation: 407Reputation: 407Reputation: 407
Hi xdyz5mx6,

Please see ondoho's above post #6. The last time I had a touchpad / pointing device issue after a kernel update on one of my Arch systems, it had to do with the libinput vs. synaptics issue. For that particular system, the solution was to switch to synaptics. In other cases, it was necessary to edit the appropriate conf file and make sure the evdev driver was specified ... Could be various things.

It is fairly simple to fix once you zero in on the specific cause, which may vary depending on your hardware.

Investigate along this path and let us know how you make out.

Cheers.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Touchpad recognized as "PS/2 Elantech Touchpad", multitouch - not working on latest Linux distros (Mint,Ubuntu,Fedora,Manjaro) Chripcikas Linux - Hardware 13 09-28-2017 03:04 AM
Wireless keyboard (working) with integral touchpad (no longer working) tharmar Ubuntu 0 07-21-2011 03:38 PM
installing Linux....touchpad scroll not working, touchpad options missing Ubunoob001 Linux - Newbie 2 10-24-2010 01:30 PM
Touchpad not working. htccst Linux - Hardware 1 04-23-2010 04:48 PM
Touchpad not working RockmanExe Slackware 3 11-25-2005 08:34 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Arch

All times are GMT -5. The time now is 10:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration