Arch Linux

tbitai

Member

Registered: 2014-04-11

Posts: 10

Touchpad correctly recognized only after resume from hibernation

I am trying to get working my ThinkPad X300's touchpad.

By default it was recognized as a mouse, so I played around with various drivers, and at a point I managed to have recognized it as a "PS/2 ALPS DualPoint Touchpad" (I am writing this by memory now, not sure it was exactly the same) by xinput list.

Now, following https://wiki.archlinux.org/index.php/To … _Touchpads I inserted ServerLayout and InputDevice sections to my 50-synaptics.conf like this:

# Example xorg.conf.d snippet that assigns the touchpad driver
# to all touchpads. See xorg.conf.d(5) for more information on
# InputClass.
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
# Additional options may be added in the form of
#   Option "OptionName" "value"
#

# I put this here following https://wiki.archlinux.org/index.php/Touchpad_Synaptics#ALPS_Touchpads
# T. Bitai
Section "ServerLayout"
	InputDevice "USB Mouse" "CorePointer"
	InputDevice "Touchpad" "SendCoreEvents"
EndSection

#
# I put this here following https://wiki.archlinux.org/index.php/Touchpad_Synaptics#ALPS_Touchpads
# T. Bitai
Section "InputDevice"
	Identifier "Touchpad"
	Driver "synaptics"
	Option "Device" "/dev/input/mouse0"
	Option "Protocol" "auto-dev"
	Option "VertEdgeScroll" "on"
        Option "VertTwoFingerScroll" "on"
        Option "HorizEdgeScroll" "on"
        Option "HorizTwoFingerScroll" "on"
EndSection

Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
        MatchIsTouchpad "on"
        Option "TapButton1" "1"
        Option "TapButton2" "2"
        Option "TapButton3" "3"
# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
        MatchDevicePath "/dev/input/event*"
# A kovetkezoket addoltam en. T. Bitai
	Option "VertEdgeScroll" "on"
        Option "VertTwoFingerScroll" "on"
        Option "HorizEdgeScroll" "on"
        Option "HorizTwoFingerScroll" "on"
EndSection

Section "InputClass"
        Identifier "touchpad ignore duplicates"
        MatchIsTouchpad "on"
        MatchOS "Linux"
        MatchDevicePath "/dev/input/mouse*"
        Option "Ignore" "on"
EndSection

# This option enables the bottom right corner to be a right button on
# non-synaptics clickpads.
# This option is only interpreted by clickpads.
Section "InputClass"
        Identifier "Default clickpad buttons"
        MatchDriver "synaptics"
        Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
#       To disable the bottom edge area so the buttons only work as buttons,
#       not for movement, set the AreaBottomEdge
#       Option "AreaBottomEdge" "82%"
EndSection

# This option disables software buttons on Apple touchpads.
# This option is only interpreted by clickpads.
Section "InputClass"
        Identifier "Disable clickpad buttons on Apple touchpads"
        MatchProduct "Apple|bcm5974"
        MatchDriver "synaptics"
        Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
EndSection

With this config, X wouldn't start after boot, so I restored the original version, and after a reboot xinput list recognizes my touchpad as "PS/2 Generic Mouse"! (That is, with the same config with wich it was recognized as an ALPS touchpad previously.) This is crazy!

Does anyone have any idea what's going on here?

Last edited by tbitai (2014-06-19 10:48:16)

tbitai

Member

Registered: 2014-04-11

Posts: 10

Re: Touchpad correctly recognized only after resume from hibernation

Hello everyone, I observed a new correlation: last time when my touchpad was recognized as "PS/2 ALPS DualPoint TouchPad" (instead of "PS/2 Generic Mouse") happend *after resuming from hibernation*, and also with the concomitant phenomenon of having no sound after resuming. (Sorry for the oversophisticated language, I have just had a philosophy of mind exam ) After this I hibernated the laptop again and resumed, and I *had* sound, but had the touchpad recognized as "PS/2 Generic Mouse", so it seems that I am lucky with the touchpad just when I am unlucky with sound. And, as far as I remember, the earlier occasions when I was lucky with the touchpad were also after resuming from hibernation. So it seems that something else than psmouse sometimes fails to restart after the hibernation, and this is what causes psmouse to work as expected! I am not an expert in kernel, so could someone help me, what to look for? An obvious guess would be sound-related modules, but it would be really weird if they had anything to do with the touchpad, so for now I don't start to learn how sound is handled in Linux (it looks like a lot to learn...)

tbitai

Member

Registered: 2014-04-11

Posts: 10

Re: Touchpad correctly recognized only after resume from hibernation

I edited the topic title to reflect better the issue.