Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

touchpad stops working

Post Reply
User avatar
Laurentius
Forum Regular
Forum Regular
Posts: 114
Joined: Sat Jan 20, 2018 9:44 pm

touchpad stops working

#1

Post by Laurentius » Sun Sep 09, 2018 12:11 pm

Hello.
From time to time, the touchpad of my laptop stops working (just the "trackpad", the buttons work).
If I close session, it works again (at the lightdm login screen) and keeps working if I log in again.

There is a button that turns it on/off but it is "on" (the buttons work)

I usually have an optical usb mouse connected (and a keyboard) most of the time but i have noticed the problem appears even when booting without connecting the usb mouse.

I have used the default 4.13 kernel and now the 4.14. Didn't seem to affect.

I remember having problems with the optical mouse when i had debian jessie installed. But not with the touchpad.
I have used other distros (ubuntu, mint) for years and did not have problems with the touchpad.

So,
1) do you know a way to solve it?
or
2) do you know a better workaround (e.g. how to restart it vía some command without having to restart session)?

Thanks.

system info:

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 4.14.0-3-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-17.1_x64 Horizon December 15  2017 
Machine:   Type: Laptop System: Hewlett-Packard product: Compaq Presario CQ40 Notebook PC 
           v: F.31 serial: <root required> 
           Mobo: Compal model: 3607 v: 99.97 serial: <root required> BIOS: Hewlett-Packard 
           v: F.31 date: 02/03/2009 
Battery:   ID-1: BAT0 charge: 10.5 Wh condition: 36.3/48.8 Wh (74%) 
CPU:       Topology: Dual Core model: Pentium T4200 bits: 64 type: MCP L2 cache: 1024 KiB 
           Speed: 1197 MHz min/max: 1200/2000 MHz Core speeds (MHz): 1: 1197 2: 1197 
Graphics:  Device-1: Intel Mobile 4 Series Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.19.2 driver: intel resolution: 1280x800~60Hz 
           OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 13.0.6 
Audio:     Device-1: Intel 82801I HD Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k4.14.0-3-amd64 
Network:   Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY driver: wl 
           IF: wlan0 state: up mac: 00:21:00:da:39:99 
           Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169 
           IF: eth0 state: down mac: 00:23:5a:9e:84:ba 
Drives:    Local Storage: total: 1.06 TiB used: 505.82 GiB (46.8%) 
           ID-1: /dev/sda vendor: Samsung model: HM160HI size: 149.05 GiB 
           ID-2: /dev/sdb type: USB vendor: Toshiba model: External USB 3.0 size: 931.51 GiB 
Partition: ID-1: / size: 14.36 GiB used: 8.90 GiB (62.0%) fs: ext4 dev: /dev/sda5 
           ID-2: /home size: 114.33 GiB used: 84.93 GiB (74.3%) fs: ext4 dev: /dev/sda6 
           ID-3: swap-1 size: 1.96 GiB used: 916 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 54.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 178 Uptime: 22h 51m Memory: 3.76 GiB used: 959.2 MiB (24.9%) Shell: bash 
           inxi: 3.0.23 

Code: Select all

$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd leds event0 
B: PROP=0
B: EV=120013
B: KEY=20000 20000000020 0 0 1500f02100000 83803078f900d401 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=0458 Product=003a Version=0111
N: Name="Genius Optical Mouse"
P: Phys=usb-0000:00:1d.7-3.3/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3.3/2-3.3:1.0/0003:0458:003A.0001/input/input3
U: Uniq=
H: Handlers=mouse0 event1 
B: PROP=0
B: EV=17
B: KEY=70000 0 0 0 0
B: REL=103
B: MSC=10

I: Bus=0003 Vendor=046d Product=c31c Version=0110
N: Name="Logitech USB Keyboard"
P: Phys=usb-0000:00:1d.7-3.4/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3.4/2-3.4:1.0/0003:046D:C31C.0002/input/input4
U: Uniq=
H: Handlers=sysrq kbd leds event2 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=c31c Version=0110
N: Name="Logitech USB Keyboard"
P: Phys=usb-0000:00:1d.7-3.4/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3.4/2-3.4:1.1/0003:046D:C31C.0003/input/input5
U: Uniq=
H: Handlers=kbd event3 
B: PROP=0
B: EV=1b
B: KEY=2010000 397ad801d001 1e000000000000 0
B: ABS=100000000
B: MSC=10

I: Bus=0011 Vendor=0002 Product=0008 Version=0200
N: Name="AlpsPS/2 ALPS GlidePoint"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input2
U: Uniq=
H: Handlers=mouse1 event4 
B: PROP=1
B: EV=b
B: KEY=420 70000 0 0 0 0
B: ABS=1000003

male

Re: touchpad stops working

#2

Post by male » Tue Sep 11, 2018 4:05 pm

It is actually a pity to leave this thread unanswered with this good background information... ;)

Could it be that the device file changes?
You have a

Code: Select all

N: Name="AlpsPS/2 ALPS GlidePoint"
with the device file

Code: Select all

H: Handlers=mouse1 event4
If it identifies another "event..." in case of failure, then one could compensate this with an udev rule

Code: Select all

SUBSYSTEM=="input", KERNEL=="event*", SYSFS{name}=="AlpsPS/2 ALPS GlidePoint", SYMLINK+="input/touchpad"
For you to be able to act, you would have to use the optical mouse constantly


I'm curious.

User avatar
Laurentius
Forum Regular
Forum Regular
Posts: 114
Joined: Sat Jan 20, 2018 9:44 pm

Re: touchpad stops working

#3

Post by Laurentius » Mon Sep 24, 2018 9:21 am

Thank you, @mate for the reply.
I don't know if i understood you.

Code: Select all

mx17-2@cq40mx:~
$ SUBSYSTEM=="input", KERNEL=="event*", SYSFS{name}=="AlpsPS/2 ALPS GlidePoint", SYMLINK+="input/touchpad"
bash: SYSFS{name}==AlpsPS/2 ALPS GlidePoint,: No such file or directory

male

Re: touchpad stops working

#4

Post by male » Mon Sep 24, 2018 4:17 pm

Hello Laurentius,

udev occasionally assigns a different device file to the touchpad when booting.
If the error occurs again, you must use the command

Code: Select all

cat /proc/bus/input/devices
check the device file and compare it with the one from your incoming mail

Code: Select all

H: Handlers=mouse1 event4
it reads differently, then confirms my assumption.
A Udev rule creates a symbolic link to the current device file
under /dev/input/touchpad, which always refers to the correct device file. If this link is used in configuration files, there is no problem anymore, even if the touchpad gets a different handler at the next boot.

Everything as root:
create the file /etc/udev/rules.d/70-touchpad-custom.rules
and add the above rule for the AlpsPS/2 touchpad.
Before saving the new file, it is recommended to use as root a terminal with the command

Code: Select all

tail -n 10 -f /var/log/syslog
because errors are displayed here immediately.

If everything is ok, the udev system is prompted to re-read the device files:

Code: Select all

sudo udevadm trigger
or restart. ;)

User avatar
Laurentius
Forum Regular
Forum Regular
Posts: 114
Joined: Sat Jan 20, 2018 9:44 pm

Re: touchpad stops working

#5

Post by Laurentius » Sat Oct 13, 2018 11:00 am

male wrote:
Mon Sep 24, 2018 4:17 pm
If the error occurs again, you must use the command

Code: Select all

cat /proc/bus/input/devices
check the device file and compare it with the one from your incoming mail

Code: Select all

H: Handlers=mouse1 event4
it reads differently, then confirms my assumption.
Hello.
Now that the problem occurred again i checked out the output of

Code: Select all

$ cat /proc/bus/input/devices
And it seems it was the same than before:

Code: Select all

mx17-2@cq40mx:~
$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd leds event0 
B: PROP=0
B: EV=120013
B: KEY=20000 20000000020 0 0 1500f02100000 83803078f900d401 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0008 Version=0200
N: Name="AlpsPS/2 ALPS GlidePoint"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input2
U: Uniq=
H: Handlers=mouse1 event4 
B: PROP=1
B: EV=b
B: KEY=420 70000 0 0 0 0
B: ABS=1000003

Post Reply

Return to “Hardware /Configuration”