LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Laptop and Netbook (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)
-   -   touchpad recognized as "PS/2 Generic Mouse" on Debian (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/touchpad-recognized-as-ps-2-generic-mouse-on-debian-4175646128/)

ZestieBumwhig 01-13-2019 02:13 PM

touchpad recognized as "PS/2 Generic Mouse" on Debian
 
Hello there

My touchpad is only recoginzed as "PS/2 Generic Mouse." It works, but only like a mouse - so I can't do two-finger scroll, etc. I'm running AVLinux2018 on an Asus K55-A laptop.

I know others have had this problem, but I haven't yet found a solution that works for me. I have been using this for about a year... but I've finally decided to tackle the problem.

The most obvious solution seems to be to use backports to install a newer kernel image. But those suggestions are from a few years ago - don't I already have a newer kernel than what they're talking about?

$ uname -r
4.9.76-lowlatency-avl2

$ cat /etc/debian_version
9.6

I've also tried some other kernels, just for fun...
$ uname -r
4.19.0-14.1-liquorix-amd64

but no change.

I KNOW it can work properly. I used to run KXStudio (ie, KDE/Ubuntu) on this laptop; also, I recently tried a USB live-boot of KDE Neon and, indeed, I had full touchpad functionality.

Any suggestions? I guess I could "roll my own kernel" but I don't even really know what that means...

Thanks!

BW-userx 01-13-2019 05:32 PM

xinput to see if it even shows a touchpad
synaptics search your cache repo for something referencing that for a "driver"

camorri 01-13-2019 06:49 PM

This link -->https://wiki.archlinux.org/index.php...s#Installation
is the best information I have found and used to get my touchpad working.

Have a look at it, and post any questions you still have.

ZestieBumwhig 01-13-2019 06:49 PM

Thanks User X. I believe that xinput is getting the same info as my System Settings... ie, calling my touchpad a mouse. But before I was running Debian, my touchpad was properly identified.

$ xinput

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PS/2 Generic Mouse id=14 [slave pointer (2)]
⎣ Virtual core keyboard

ondoho 01-14-2019 01:34 AM

^ what were you running before debian?

you can test more with
Code:

synclient
- what does it say?

also, now we know the id, try
Code:

xinput list 14
to get some more info.

ZestieBumwhig 01-14-2019 05:31 PM

Thanks for the responses.

When I run synclient:

Code:

~$ synclient
Couldn't find synaptics properties. No synaptics driver loaded?

I do have xserver-xorg-input-libinput installed.

Previously I ran KXStudio on this laptop, which is built on KDE4/Ubuntu 14.04.5. More recently I live-booted off of a KDE Neon USB stick (based on Ubuntu 18.04) and had a normally-functioning touchpad then as well.

Cliff - I have tried copying 70-synaptics.conf (and renamed 50-synaptics.conf) into /etc/X11/xorg.conf.d (with the suggested lines from your link) but I haven't had any change. Well, except for this once when I must have had a typo, and SLiM wouldn't load and I only booted to a text screen... luckily I was able to cp and rm my way to safety (I had a backup 70-synaptics.conf which I used to replace my bad one).

ondoho 01-15-2019 01:18 AM

you say it worked on ubuntu 14.04; that would suggest that a newer kernel won't fix the problem.

maybe you DO have a synaptics touchpad, but the driver isn't loaded.

try to switch from libinput back to synaptics.

https://wiki.debian.org/SynapticsTouchpad

the article focuses on the opposite case (people should switch to libinput from synaptics), but you want to get synaptics driver working.

ZestieBumwhig 01-15-2019 11:47 PM

I appreciate the help. Unfortunately, I'm still pretty lost.

Following the debian.org notes,
Code:

egrep -i 'synap|alps|etps|elan' /proc/bus/input/devices
gives me nothing... but (egrep -i 'mouse') gives me
Code:

N: Name="PS/2 Generic Mouse"
H: Handlers=mouse0 event1

If I'm understanding your suggestion correctly, I want to use synaptics, not libinput. I don't want to remove libinput though, right? I think that might break many things. I've already done this:
Quote:

You can make the synaptics driver take precedence over libinput by copying /usr/share/X11/xorg.conf.d/50-synaptics.conf into /etc/X11/xorg.conf.d, so as to make it take precendence over the libinput configuration file found at /usr/share/X11/xorg.conf.d/90-libinput.conf.
I think the problem I'm having is in the kernel. This Debian kernel, while newer, may still be very different from the Ubuntu 14.04 kernel, no? From "man 4 synaptics":
Code:

If your device is recognized
as  "PS/2  Mouse"  or  similar, the kernel driver does not support your
device and this driver will only provide limited functionality.

And that looks like what I've got.

ondoho 01-16-2019 01:02 AM

Quote:

Originally Posted by ZestieBumwhig (Post 5949664)
I think the problem I'm having is in the kernel. This Debian kernel, while newer, may still be very different from the Ubuntu 14.04 kernel, no?

it's unlikely that a newer kernel removed support for a device.
however, debian, as compared to ubuntu, has a different policy for 3rd party software.

whatever may be the case, i think we should get more information about the device itself.
how old is it?

can you provide the information requested here (don't file a bug reprot just yet).
additionally, also this:
Code:

uname -rv
cat /etc/*release*
dmesg
# if you want to upload that, use:
dmesg > dmesg.txt

you might want to upload larger output to a pastebin.

feel free to look at the output yourself.
once we know the make and model of the touchpad it should be easier to formulate searches.

PS: maybe you can (live-)boot ubuntu 14.04 and provide more information?

ZestieBumwhig 01-16-2019 11:12 PM

OK... here's a massive info-dump, which I understand about 3% of...

(Also, my current KDE Neon thumb drive (aka, 18.04, but touchpad works) is not here right now - but if you want this info from THAT live-boot, I can have it tomorrow.)

uname -rv
Code:

4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27)
(incidentally, I've tried different kernels, including the AVLinux RT and Low-Latency... in the interest of the touchpad, and general curiosity. No change in touchpad between them.)

cat /etc/*release*
Code:

PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

dmesg.txt:
https://pastebin.com/BVpL1GFF

xinput:
Code:

⎡ Virtual core pointer                            id=2        [master pointer  (3)]
⎜  ↳ Virtual core XTEST pointer                      id=4        [slave  pointer  (2)]
⎜  ↳ PS/2 Generic Mouse                              id=13        [slave  pointer  (2)]
⎣ Virtual core keyboard                          id=3        [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                    id=5        [slave  keyboard (3)]
    ↳ Power Button                                    id=6        [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control                    id=7        [slave  keyboard (3)]
    ↳ Video Bus                                      id=8        [slave  keyboard (3)]
    ↳ Sleep Button                                    id=9        [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam                            id=10        [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                                id=11        [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard                    id=12        [slave  keyboard (3)]
    ↳ lircd-uinput                                    id=14        [slave  keyboard (3)]

Xorg.0.log:
https://pastebin.com/RMeQ8gJ9

proc/bus/input/devices:
https://pastebin.com/m53bKgaV

ondoho 01-17-2019 01:07 AM

i start going through the 3 larger files now.

but i just remembered that we never saw the output of

Code:

xinput list 13
(strangely, the id has changed from 14 to 13?)

also, i will assume that all output is from your (fairly normal, apart from your kernel adventures, but it looks like you're back to debian's vanilla kernel now) debian stable system, unless you label it very clearly to be from another OS.

ondoho 01-17-2019 01:37 AM

so.
you're using AVLinux.
that certainly isn't vanilla debian, and i'll have to refer you to AVLinux documentation about how it ticks and, importantly, how it differs from vanilla debian 9.
my fault, i missed this from your first post.

first things first:
your dmesg suggests a failed resume from hibernation:
Code:

[    1.626894] PM: Starting manual resume from disk
[    1.626898] PM: Hibernation image partition 8:2 present
[    1.626900] PM: Looking for hibernation image.
[    1.627194] PM: Image not found (code -22)
[    1.627196] PM: Hibernation image not present or could not be loaded.

please make a full reboot, and don't use hibernation if it doesn't work.
just being cautious.

more dmesg:
Code:

[    1.308652] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[    1.308656] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.309027] hub 1-1:1.0: USB hub found
[    1.309210] hub 1-1:1.0: 6 ports detected
[    1.328813] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[    1.328816] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.329289] hub 2-1:1.0: USB hub found
[    1.329470] hub 2-1:1.0: 6 ports detected
[    1.331096] input: PS/2 Generic Mouse as /devices/platform/i8042/serio4/input/input8
[    1.595977] usb 1-1.1: new full-speed USB device number 3 using ehci-pci

could this mean that your touchpad is a usb device?
please provide output of
Code:

sudo lsusb -v

Xorg.log:
Code:

[    3.557] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event1)
[    3.557] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
[    3.557] (**) PS/2 Generic Mouse: Applying InputClass "libinput pointer catchall"
[    3.557] (II) Using input driver 'libinput' for 'PS/2 Generic Mouse'
[    3.557] (**) PS/2 Generic Mouse: always reports core events
[    3.557] (**) Option "Device" "/dev/input/event1"
[    3.557] (**) Option "_source" "server/udev"
[    3.557] (II) input device 'PS/2 Generic Mouse', /dev/input/event1 is tagged by udev as: Mouse
[    3.557] (II) input device 'PS/2 Generic Mouse', /dev/input/event1 is a pointer caps
[    3.616] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input8/event1"
[    3.616] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 13)
[    3.616] (**) Option "AccelerationScheme" "none"
[    3.616] (**) PS/2 Generic Mouse: (accel) selected scheme none/0
[    3.616] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
[    3.616] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
[    3.616] (II) input device 'PS/2 Generic Mouse', /dev/input/event1 is tagged by udev as: Mouse
[    3.617] (II) input device 'PS/2 Generic Mouse', /dev/input/event1 is a pointer caps
[    3.617] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)
[    3.617] (II) No input driver specified, ignoring this device.
[    3.617] (II) This device may have been added with another device file.

doesn't seem to help much either; it's seen as a genric mouse.

/proc/bus/input/devices:
Code:

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input8
U: Uniq=
H: Handlers=mouse0 event1
B: PROP=1
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

not much help for me.

by now i was hoping to get at some vendor/product id at least.

____________________________________________


i recommend to try a backported kernel; the version that is in debian stretch-backports, nothing fancy!

ZestieBumwhig 01-17-2019 08:04 PM

You're right - the problem does seem to be AVLinux-specific. I'd been assuming it was Debian-wide all along.

Now I'm booting off of a Debian/XFCE USB stick, and I have a working touchpad (and boy I've missed it). The kernel is the same, I think? I don't know much about computers, but I guess I'd incorrectly assumed that using the same kernel would give me the same hardware interface.
Code:

uname -r
4.9.0-8-amd64

The touchpad is ETPS/2 Elantech Touchpad.
Code:

I: Bus=0011 Vendor=0003 Product=000e Version=0000
N: Name="ETPS/2 Elantech Touchpad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input9
U: Uniq=
H: Handlers=mouse0 event5
B: PROP=5
B: EV=b
B: KEY=e420 10000 0 0 0 0
B: ABS=661800011000003

I wonder if the "hibernation" thing is some oddity of AVL, or my SSD, because it says it even when dmesg is the first thing I do:
https://pastebin.com/6sEkH6z6 (second dmesg, from just now)

Here's xinput 13 (although maybe it's not useful now that we know what the touchpad is, and that it's OK with Debian)
https://pastebin.com/KGgvdjA2

And... even though I probably need to go straight over to Linux Musicians and ask for AVL-specific help, here's the lsusb -v:
https://pastebin.com/nxyizmdg

You've been such a help. Even if this is as far as you can take me, I really appreciate all the time you've spent.

ondoho 01-18-2019 01:23 AM

Quote:

Originally Posted by ZestieBumwhig (Post 5950371)
You're right - the problem does seem to be AVLinux-specific. I'd been assuming it was Debian-wide all along.

Now I'm booting off of a Debian/XFCE USB stick, and I have a working touchpad (and boy I've missed it). The kernel is the same, I think? I don't know much about computers, but I guess I'd incorrectly assumed that using the same kernel would give me the same hardware interface.
Code:

uname -r
4.9.0-8-amd64


glad to hear it.
no, your assumption is not completely wrong.
I'm guessing that AVLinux developer(s) have skimped somewhere to make the system lighter and more focused on media processing.

Please keep in mind that AVLinux states very clearly & prominently that it is not so much a distro, as rather something cobbled together to work as an A/V editing system.
I'm paraphrasing, but that's the gist of it.

Quote:

The touchpad is ETPS/2 Elantech Touchpad.
Code:

I: Bus=0011 Vendor=0003 Product=000e Version=0000
N: Name="ETPS/2 Elantech Touchpad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input9
U: Uniq=
H: Handlers=mouse0 event5
B: PROP=5
B: EV=b
B: KEY=e420 10000 0 0 0 0
B: ABS=661800011000003


great.
with that information, it should be much easier to get it working.
just searching "elantech" on AVLinux forums brings me this.
Please go through it thoroughly, not sure it applies to your situation.
If not, I strongly encourage you to start a new thread about it, on their forums.
I'm sure the developers will want to know about this - and fix it.

BW-userx 01-18-2019 07:15 AM

yes remember what brand your touch pad is so if you run into this again, you will have a much better starting point to fixing it.


All times are GMT -5. The time now is 07:53 AM.