LinuxQuestions.org - HP Mini 210-1100, Slackware 14.1: touchpad right button behavior.

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - HP Mini 210-1100, Slackware 14.1: touchpad right button behavior. (https://www.linuxquestions.org/questions/slackware-14/hp-mini-210-1100-slackware-14-1-touchpad-right-button-behavior-4175550780/)

HP Mini 210-1100, Slackware 14.1: touchpad right button behavior.

The right button behaves exactly like the left one. Example: in Xfce 4, consider a link to download/read a PDF file. If I press the left button over it, okular is started with that file loaded. If instead I press the right button, I expect a menu to pop up, giving me options liked just downloading the file. However,the effect will be as if I had pressedd the left button. So, this states the problem.

I have no files in /etc/X11/xorg.conf.d/. I could copy the /etc/X11/ xorg.conf-vesa, or just the pointing device section to that directory, with some modification. I understand the xorg.conf-vesa file is written to duplicate the X settings defined somewhere else in the file hierarchy. [EDIT: rather not to alter those settings.] This is the mouse section:

Code:

 



# **********************************************************************

# Core Pointer's InputDevice section

# **********************************************************************



Section "InputDevice"



# Identifier and driver



    Identifier        "Mouse1"

    Driver        "mouse"



# On platforms where PnP mouse detection is supported the following

# protocol setting can be used when using a newer PnP mouse:



#    Option    "Protocol"      "Auto"



# The available mouse protocols types that you can set below are:

#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2

#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2

#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse

#    ThinkingMouse ThinkingMousePS/2 Xqueue

    Option "Protocol"    "PS/2"



# The mouse device.  The device is normally set to /dev/mouse,

# which is usually a symbolic link to the real device.



    Option "Device"      "/dev/mouse"

#  Option "Device"      "/dev/psaux"

#  Option "Device"      "/dev/ttyS0"

#  Option "Device"      "/dev/ttyS1"



# When using XQUEUE, comment out the above two lines, and uncomment

# the following line.



#    Option "Protocol"        "Xqueue"



# Baudrate and SampleRate are only for some Logitech mice. In

# almost every case these lines should be omitted.



#    Option "BaudRate"                "9600"

#    Option "SampleRate"        "150"



# Emulate3Buttons is an option for 2-button Microsoft mice

# Emulate3Timeout is the timeout in milliseconds (default is 50ms)



#    Option "Emulate3Buttons"

#    Option "Emulate3Timeout"    "50"



# ChordMiddle is an option for some 3-button Logitech mice



#    Option "ChordMiddle"



EndSection



# Some examples of extended input devices

Is there anything I could change in that section to make the touchpad to correctly behave? On the other hand, in Xfce Settings>Mouse and Touch- pad, seeing what is displayed in the dialog box makes me think things are correctly set, except for the aforementioned problem.

Note: whereas HP has all its drivers for this notebook written for Windows operating systems, it has none for others, as it expressly states.
bill@server:/almacen/sma_/info/clear/cl1/correo/lq$

Have a look at this thread.

They basically state that the following options for the psmouse module should fix it.

Code:

echo options psmouse proto=exps > /etc/modprobe.d/psmouse.modprobe

Then just either reboot or rmmod the psmouse module and then modprobe it again.

Great thread! Shouldn't I be copying to /etc/modprobe.d/psmouse.conf instead? Because there is a /lib/modprobe.d/psmouse.conf (with all lines commented out). In /etc/modprobe.d/README it says a file here with the same name as one in /lib/modprobe.d overrides it.

Quote:

Originally Posted by stf92 (Post 5405840)

If you have a look in /lib/modprobe.d/psmouse.conf, everything is commented out. So, you can just create a new file in /etc/modprobe.d/psmouse.conf with those options, or you can copy the from from /lib over, it's up to you, but with this file, it doesn't matter.

Aha. Thanks for your posts. In the upper left corner of the touchpad there is a LED. Double clicking it disables/enables the touchpad. Do you know of a psmouse option to enable the that behavior? I am reading /usr/src/linux-3.10.17/drivers/input/mouse/synaptics.h but can't find something to the point. But there are many C headers in the directory. I should first find out which model my touchpad is, perhaps, and look in the corresponding header. In that sense, I have

Code:

$ cat /proc/bus/input/devices

[..................]

I: Bus=0011 Vendor=0002 Product=0001 Version=0000

N: Name="PS/2 Synaptics TouchPad"

P: Phys=isa0060/serio1/input0

S: Sysfs=/devices/platform/i8042/serio1/input/input12

U: Uniq=

H: Handlers=mouse0 event8 

B: PROP=0

B: EV=7

B: KEY=70000 0 0 0 0 0 0 0 0

B: REL=3

Code:

bash-4.2# modinfo psmouse|grep parm:

parm:          proto:Highest protocol extension to probe (bare, imps, exps, any). Useful for KVM switches. (proto_abbrev)

parm:          resolution:Resolution, in dpi. (uint)

parm:          rate:Report rate, in reports per second. (uint)

parm:          smartscroll:Logitech Smartscroll autorepeat, 1 = enabled (default), 0 = disabled. (bool)

parm:          resetafter:Reset device after so many bad packets (0 = never). (uint)

parm:          resync_time:How long can mouse stay idle before forcing resync (in seconds, 0 = never). (uint)

bash-4.2# modinfo synaptics_usb|grep parm:

bash-4.2#

That's all I know.

The module psmouse is quite simple in terms of what it supports option-wise. I'd have a look at synclient, as that is able to deal with the mountain of options needed for touchpads. synclient -l will show you all the options for your device. See man synaptics for a mind-boggling list of options and what they do.

If you decide you want them permanent, you can create a 50-synaptics.conf under /etc/X11/xorg.conf.d/ to override the very basic synaptics options that Slack includes under /usr/share/X11/xorg.conf.d/50-synaptics.conf.

Have a look at ArchWiki's page on synaptics for more info.

https://wiki.archlinux.org/index.php/Touchpad_Synaptics

Code:

root@server:~# synclient -l

Couldn't find synaptics properties. No synaptics driver loaded?

root@server:~# lsmod|grep synaptics

root@server:~# grep -irl synapti /var/log/packages/

/var/log/packages/gpm-1.20.7-i486-2

/var/log/packages/kernel-source-3.10.17_smp-noarch-3

/var/log/packages/kdeartwork-4.10.5-i486-1

/var/log/packages/xf86-input-synaptics-1.7.1-i486-2

/var/log/packages/kernel-modules-smp-3.10.17_smp-i686-3

/var/log/packages/kernel-modules-3.10.17-i486-3

root@server:~#

So, the package is installed, but not the module!

OK. I replaced
Driver "mouse"
by
Driver "synaptics"

in /etc/X11/xorg.conf.d/xorg.conf. But still the driver is not loaded.

What does /var/log/Xorg.0.log show with the mouse driver?

Code:

[    98.864] (II) LoadModule: "synaptics"

[    98.865] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so

[    98.893] (II) Module synaptics: vendor="X.Org Foundation"

[    98.893]    compiled for 1.14.2, module version = 1.7.1

[    98.893]    Module class: X.Org XInput Driver

[    98.893]    ABI class: X.Org XInput driver, version 19.1

[...................]

[  102.121] (II) Using input driver 'synaptics' for 'Mouse1'

[  102.121] (**) Option "CorePointer"

[  102.121] (**) Mouse1: always reports core events

[  102.121] (**) Option "Protocol" "PS/2"

[  102.121] (**) Option "Device" "/dev/mouse"

[  102.121] (EE) synaptics: Mouse1: Synaptics driver unable to detect protocol

[  102.121] (EE) PreInit returned 11 for "Mouse1"

[  102.121] (II) UnloadModule: "synaptics"

[...........................]

[  102.227] (II) Using input driver 'evdev' for 'PS/2 Synaptics TouchPad'

[..........................]

And xorg.conf is

Code:

Section "InputDevice"



# Identifier and driver



    Identifier        "Mouse1"

    Driver        "synaptics"



# On platforms where PnP mouse detection is supported the following

# protocol setting can be used when using a newer PnP mouse:



#    Option    "Protocol"      "Auto"



# The available mouse protocols types that you can set below are:

#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2

#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2

#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse

#    ThinkingMouse ThinkingMousePS/2 Xqueue

    Option "Protocol"    "PS/2"



# The mouse device.  The device is normally set to /dev/mouse,

# which is usually a symbolic link to the real device.



    Option "Device"      "/dev/mouse"

#  Option "Device"      "/dev/psaux"

#  Option "Device"      "/dev/ttyS0"

#  Option "Device"      "/dev/ttyS1"



# When using XQUEUE, comment out the above two lines, and uncomment

# the following line.



#    Option "Protocol"        "Xqueue"



# Baudrate and SampleRate are only for some Logitech mice. In

# almost every case these lines should be omitted.



#    Option "BaudRate"                "9600"

#    Option "SampleRate"        "150"



# Emulate3Buttons is an option for 2-button Microsoft mice

# Emulate3Timeout is the timeout in milliseconds (default is 50ms)



#    Option "Emulate3Buttons"

#    Option "Emulate3Timeout"    "50"



# ChordMiddle is an option for some 3-button Logitech mice



#    Option "ChordMiddle"



EndSection

It seems rather strange that a touchpad be connected through a PS/2 adapter. That's what X seems to think, so it gives up using the synaptic driver for that and falls back to evdev. At least, that's what I understand.

But

Code:

I: Bus=0011 Vendor=0002 Product=0001 Version=0000

N: Name="PS/2 Synaptics TouchPad"

P: Phys=isa0060/serio1/input0

S: Sysfs=/devices/platform/i8042/serio1/input/input8

U: Uniq=

H: Handlers=mouse0 event8 

B: PROP=0

B: EV=7

B: KEY=70000 0 0 0 0 0 0 0 0

B: REL=3

Anyways, I changed to Option "Protocol" "Auto" with no different response. Besides,

Code:

root@server:/usr/share/X11/xorg.conf.d# cat 50-synaptics.conf 



Section "InputClass"

        Identifier "touchpad"

        Driver "synaptics"

        MatchDevicePath "/dev/input/event*"

        MatchIsTouchpad "on"

        Option "TapButton1" "1"

        Option "TapButton2" "2"

        Option "TapButton3" "3"

EndSection

and /etc/X11/xorg.conf.d/ empty does not load the driver (module).

What if you remove the options for the psmouse module? You're forcing, what I'm assuming is, the exps protocol. This may conflict with what the synaptics driver expects. Does the synaptics pad get recognized properly then? If it does, it's possible we're able to adjust the right click with xinput or synclient. Does the Xorg.0.log errors change?

No it doesn't. And Xorg.0.log is still the same.

Code:

bill@server:/dev$ ls -l mouse

lrwxrwxrwx 1 root root 10 Aug 17 16:29 mouse -> input/mice

bill@server:/dev$ ls -l input 

total 0

drwxr-xr-x 2 root root    60 Aug 17 13:28 by-id/

drwxr-xr-x 2 root root    120 Aug 17 13:28 by-path/

crw-r----- 1 root root 13, 64 Aug 17 16:29 event0

crw-r----- 1 root root 13, 65 Aug 17 16:29 event1

crw-r----- 1 root root 13, 66 Aug 17 16:29 event2

crw-r----- 1 root root 13, 67 Aug 17 16:29 event3

crw-r----- 1 root root 13, 68 Aug 17 16:29 event4

crw-r----- 1 root root 13, 69 Aug 17 16:29 event5

crw-r----- 1 root root 13, 70 Aug 17 16:29 event6

crw-r----- 1 root root 13, 71 Aug 17 16:29 event7

crw-r----- 1 root root 13, 72 Aug 17 16:29 event8

crw-r----- 1 root root 13, 73 Aug 17 16:29 event9

crw-r----- 1 root root 13, 63 Aug 17 16:29 mice

crw-r----- 1 root root 13, 32 Aug 17 16:29 mouse0

bill@server:/dev$

In xorg.conf, I have

Option "Device" "/dev/mouse".

As shown above, it has major number 13. But Xorg.0.log says "Preinit returned 11 for "Mouse1" (Mouse1 is an arbitrary id).

To further investigate, I suggest that you get rid of xorg.conf (just renaming it tentatively as xorg.conf.back, for instance). After all, in most case X works well without it and so we'll now which driver is used as default.

Then restart X and post (or better, link to it through pastebin.com or some other file sharing service) your full /var/log/Xorg.0.log.