[SOLVED] Laptop with Synaptics not working after update

boriscougar · 2014-10-23 15:15:08

-- EDIT
This was solved with latest update (Linux Kernel 4 and latest xf86-input drivers.

-- END OF EDIT
Yesterday I upgraded my laptop (hp split 13 x2), it used to have touchscreen and touchpad working, at least i could do two finger scrolling on touchpad... now after update i'm missing that.

dmesg output:

[boris@arch ~]$ dmesg|grep Synaptics
[    8.754747] input: Synaptics Touch Pad V 103S  as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/0003:06CB:5710.0002/input/input14
[    8.755147] hid-generic 0003:06CB:5710.0002: input,hiddev0,hidraw0: USB HID v1.11 Pointer [Synaptics Touch Pad V 103S ] on usb-0000:00:14.0-6/input0

My xorg.0.log shows the following

[boris@arch ~]$ cat /var/log/Xorg.0.log |grep Syn
[  1551.787] (II) config/udev: Adding input device Synaptics Touch Pad V 103S  (/dev/input/event14)
[  1551.787] (**) Synaptics Touch Pad V 103S : Applying InputClass "evdev pointer catchall"
[  1551.833] (II) config/udev: Adding input device Synaptics Touch Pad V 103S  (/dev/input/mouse0)

journalctl shows the following (or may i say nothing)

[boris@arch ~]$ journalctl -a -e | grep Synaptics
[boris@arch ~]$ journalctl -a -e | grep synaptics
[boris@arch ~]$ journalctl /usr/bin/Xorg
-- Logs begin at mié 2014-10-22 15:38:13 CST, end at jue 2014-10-23 09:01:20 CST
[boris@arch ~]$ journalctl /usr/bin/X
-- Logs begin at mié 2014-10-22 15:38:13 CST, end at jue 2014-10-23 09:01:20 CST

and trying to use synclient shows the following:

[boris@arch ~]$ synclient 
Couldn't find synaptics properties. No synaptics driver loaded?

So basically i'm clueless on how to get back my two finger scroll that i miss so much... any hints would be gladly appreciated
(i dislike so much having to move my cursor to the edge to find the scrollbar... )

Last edited by boriscougar (2015-05-12 12:06:07)

lukasm · 2014-10-24 12:06:39

I can confirm this on HP Spectre x2. Since the latest update yesterday, Synaptics isn't loaded again...

It also applies evdev pointer catchall.

optagon · 2014-10-25 01:14:45

I made a similar post today, but the difference is I updated several days ago (last Monday I think). So it could be an unrelated issue.

Xabre · 2014-10-25 01:25:48

I actually had the same issue with my ProBook when using linux-ck, version 3.16.5 and 3.16.6, 3.16.4 and lower work just fine.
However, stock arch kernel works flawlesly, currently 3.17.1. May not be related, but if you're not on stock kernel, I'd give it a try.

boriscougar · 2014-10-27 22:16:55

I'm currently on linux-lts (Linux arch 3.14.22-1-lts) and still i have no double finger scroll
Edit:

When i started having this issue i was on kernel 3.17.1-1 I thought that going to linux-lts would perhaps fix it but no change, any more hints i would be glad to hear them

Last edited by boriscougar (2014-10-27 23:06:59)

TE · 2014-11-02 19:18:03

3.14.22 lts was released right about the same time as 3.17.1 -- 3.14.21 lts is what aligns better to 3.16.4. You're still in the same boat though, having to use an older kernel... so maybe you could download linux-lts and headers-lts 3.14.21 and then blackball them in /etc/pacman.conf (IgnorePkgs) so that you could have one kernel that works (LTS) which playing with the other kernel. 3.17.2 seems to have just been released...

http://seblu.net/a/arm/packages/l/linux-lts/
http://seblu.net/a/arm/packages/l/linux-lts-headers/

lukasm · 2014-11-03 18:56:24

So I've now tried 3.17.2, which still doesn't work. Afterwards I downgraded to 3.16.4 (not lts) which seems to work.

Probably it's the same for you?

So I think this is a bug, but I don't know where I should submit this and what information I can add.

Last edited by lukasm (2014-11-03 18:56:36)

ewaller · 2014-11-03 19:18:40

I am trying to figure out if this might be related to another bug. What is the output of journalctl --boot | grep i2c

lukasm · 2014-11-03 20:58:04

So I don't get any ouput from this command. I tried it with 3.16.4 (where Synaptics works) and 3.17.2 (where it does not work).

ewaller · 2014-11-03 21:56:59

Okay thanks. There had been a bug associated with machines that have both touch screens and trackpads. If I interpreted the bug correctly, both devices shared an i2c bus, but the drivers for the two devices did not play nicely together. One of the drivers would throw messages about the conflict. That there is no output means that this is not the same issue. Thanks.

boriscougar · 2014-11-05 15:22:57

I have the same output from journalctl --boot | grep i2c as @lukasm --nothing

I'm somehow clueless on where to search, i'll downgrade to older kernel (3.16.4) hopefully it will work again.

Thanks alot for your help, i guess it is a bug but i can't trace it down to anything (only the fact that on 3.16.4 things worked)

-- Edited
I've just downgrade to 3.16.4 and it is working again... any more hints would be great to at least correctly report this bug, any more info you could need i would be glad to give feedback

Last edited by boriscougar (2014-11-05 15:32:07)

boriscougar · 2014-11-18 22:26:23

Has anyone tried linux 3.17.3 to see if there is any change on this issue?
Ill try updating perhaps in weekend but if anyone knows something it will be gladly appreciated

lukasm · 2014-11-20 07:07:41

The time you wrote this message I did not yet try it - but anyway in the meanwhile I tried linux 3.17.3 and it's still the same issue. It only recognizes a PS Mouse.

So I downgraded once again.

Hope that answers your question.

boriscougar · 2014-11-20 12:07:05

Thanks alot for the info so we are still stuck with older kernel hopefully someone finds something soon

boriscougar · 2014-12-12 18:07:01

Hi all

I've not heard any updates on this subject (I'm still stuck at kernel 3.16.4) but as I updated today I saw there is 3.17.6 has anyone tried if any improvements? or have you heard/read of some sort of solution or debugging or anything?

This feels as if we are the few ones with this bug... and that sucks

Thanks!

TE · 2014-12-12 22:50:34

boriscougar wrote:

I've not heard any updates on this subject (I'm still stuck at kernel 3.16.4) but as I updated today I saw there is 3.17.6 has anyone tried if any improvements? or have you heard/read of some sort of solution or debugging or anything?

I'm no longer affected (yay) but created AUR packages of 3.16.x that you can install alongside the mainline (real) kernel:

https://aur.archlinux.org/packages/linux-stable316/

That way it's easy to try the latest kernel and if it's not working, just reboot into the older 3.16.x one without having to go through the package downgrade mambo. Kernel takes an hour or so to compile on my laptops...

lukasm · 2014-12-16 13:39:03

I have tried the last feq versions sporddically but 3.17.6 still does not work for me unfortunately. Dis you change anything else except installing @TE?

Regards

TE · 2014-12-16 16:52:42

lukasm wrote:

I have tried the last feq versions sporddically but 3.17.6 still does not work for me unfortunately. Dis you change anything else except installing @TE?

I did not for the one laptop -- I suspect that the issues are highly hardware specific. One of my laptops is a Dell Precision m4600 (personal), the other is a Dell E7440 (work) - the E7440 still has wonky problems, however on that one I was able to force the trackpad to use the more basic protocol:

/etc/modprobe.d/touchpad.conf

options psmouse proto=imps

That at least allows my touchpad on the E7440 to work at a basic regular level, I don't like that funky two-finger scrolling and edge-tapping stuff anyways. Based on my years of Linux-on-laptops use (first was a Dell i7000 w/RH5 around '95) the problems are always intrinsic to the hardware the vendor has decided to stuff in them. I *still* can't get the multi-function SDcard/Firewire device to work on the m4600, some sort of O2Micro junk...

lukasm · 2015-02-06 16:11:47

I've just tried once again the newest Kernel version, but unfortunately it seems not to work.

@boriscougar: Did you find a fix?

boriscougar · 2015-02-24 14:33:10

Update on the issue!

With Kernel 2.18 I started debugging around to find out what is broken with this soft/hard configuration... I found out the following:

1. Synaptics driver was never loaded by X (as you can see by the output of X log file, it was using evdev driver)

feb 21 11:42:13 arch gdm-Xorg-:0[387]: (II) config/udev: Adding input device Synaptics Touch Pad V 103S  (/dev/input/event13)
feb 21 11:42:13 arch gdm-Xorg-:0[387]: (**) Synaptics Touch Pad V 103S : Applying InputClass "evdev pointer catchall"
feb 21 11:42:13 arch gdm-Xorg-:0[387]: (II) Using input driver 'evdev' for 'Synaptics Touch Pad V 103S '
...
feb 21 11:42:13 arch gdm-Xorg-:0[387]: (II) config/udev: Adding input device Synaptics Touch Pad V 103S  (/dev/input/mouse0)
feb 21 11:42:13 arch gdm-Xorg-:0[387]: (II) No input driver specified, ignoring this device.
feb 21 11:42:13 arch gdm-Xorg-:0[387]: (II) This device may have been added with another device file.

2. Configuration for synaptics wasn't loaded because of the "MatchIsTouchPad" on the default synaptics config (/etc/X11/xorg.conf.d/50-synaptics.conf) I commented that out and well it conflicted with my touchscreen so everything went frozen; then I matched over /dev/input/mouse0 as follows (just for testing):

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/mouse0"
EndSection

and now X tries to load up the synaptics driver and... fails!:

feb 24 08:01:16 arch gdm-Xorg-:0[381]: (II) config/udev: Adding input device Synaptics Touch Pad V 103S  (/dev/input/mouse0)
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (**) Synaptics Touch Pad V 103S : Applying InputClass "touchpad catchall"
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (**) Synaptics Touch Pad V 103S : Applying InputClass "Default clickpad buttons"
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (II) LoadModule: "synaptics"
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (II) Module synaptics: vendor="X.Org Foundation"
feb 24 08:01:16 arch gdm-Xorg-:0[381]: compiled for 1.16.0, module version = 1.8.1
feb 24 08:01:16 arch gdm-Xorg-:0[381]: Module class: X.Org XInput Driver
feb 24 08:01:16 arch gdm-Xorg-:0[381]: ABI class: X.Org XInput driver, version 21.0
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (II) Using input driver 'synaptics' for 'Synaptics Touch Pad V 103S '
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (**) Synaptics Touch Pad V 103S : always reports core events
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (**) Option "Device" "/dev/input/mouse0"
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (EE) synaptics: Synaptics Touch Pad V 103S : Synaptics driver unable to detect protocol
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (EE) PreInit returned 11 for "Synaptics Touch Pad V 103S "
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (II) UnloadModule: "synaptics"

The interesting part is this one:

feb 24 08:01:16 arch gdm-Xorg-:0[381]: (EE) synaptics: Synaptics Touch Pad V 103S : Synaptics driver unable to detect protocol
feb 24 08:01:16 arch gdm-Xorg-:0[381]: (EE) PreInit returned 11 for "Synaptics Touch Pad V 103S "

And now, again, I'm out of clues, i found some russian guy who had the same issues with my same laptop-touchpad model (on archlinux)
http://www.linux.org.ru/forum/linux-hardware/11263333

also on Ubuntu they fixed out some weird errors, touchpad related with usbhid.quirk kernel parameter (that didn't worked on my system, i didn't had the same issues of USB errors while booting)
https://bugs.launchpad.net/ubuntu/+sour … ug/1312489

But anything beyond that I haven't found, I'm quite clueless, but perhaps someone more experienced can guide me trough finding out why is this happening (I don't like being on an older kernel)

Thanks!

uselessfire · 2015-02-26 08:27:51

Hello, i am that russian guy
I also posted it in other forums:
https://bbs.archlinux.org/viewtopic.php?pid=1502534
http://www.linux.org.ru/forum/linux-hardware/11263333
https://archlinux.org.ru/forum/topic/14452/
but got no response on any

Last edited by uselessfire (2015-02-26 13:04:30)

uselessfire · 2015-02-28 15:53:40

I just boot ubuntu 14.10 and touchpad (two-finger scrolling) works fine!

[    58.913] (II) config/udev: Adding input device Synaptics Touch Pad V 1.03P (/dev/input/event7)
[    58.913] (**) Synaptics Touch Pad V 1.03P: Applying InputClass "evdev touchpad catchall"
[    58.913] (**) Synaptics Touch Pad V 1.03P: Applying InputClass "touchpad catchall"
[    58.913] (**) Synaptics Touch Pad V 1.03P: Applying InputClass "Default clickpad buttons"
[    58.913] (II) LoadModule: "synaptics"
[    58.913] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[    58.913] (II) Module synaptics: vendor="X.Org Foundation"
[    58.914]    compiled for 1.16.0, module version = 1.8.99
[    58.914]    Module class: X.Org XInput Driver
[    58.914]    ABI class: X.Org XInput driver, version 21.0
[    58.914] (II) Using input driver 'synaptics' for 'Synaptics Touch Pad V 1.03P'
[    58.914] (**) Synaptics Touch Pad V 1.03P: always reports core events
[    58.914] (**) Option "Device" "/dev/input/event7"
[    58.924] (II) synaptics: Synaptics Touch Pad V 1.03P: found clickpad property
[    58.924] (--) synaptics: Synaptics Touch Pad V 1.03P: x-axis range 1 - 4058 (res 45)
[    58.924] (--) synaptics: Synaptics Touch Pad V 1.03P: y-axis range 1 - 2574 (res 45)
[    58.924] (--) synaptics: Synaptics Touch Pad V 1.03P: pressure range 0 - 255
[    58.924] (II) synaptics: Synaptics Touch Pad V 1.03P: device does not report finger width.
[    58.924] (--) synaptics: Synaptics Touch Pad V 1.03P: buttons: left double triple
[    58.924] (--) synaptics: Synaptics Touch Pad V 1.03P: Vendor 0x6cb Product 0x5710
[    58.924] (--) synaptics: Synaptics Touch Pad V 1.03P: invalid finger width range.  defaulting to 0 - 15
[    58.924] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[    58.924] (--) synaptics: Synaptics Touch Pad V 1.03P: touchpad found
[    58.924] (**) Synaptics Touch Pad V 1.03P: always reports core events
[    58.936] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6:1.0/0003:06CB:5710.0002/input/input6/event7"
[    58.936] (II) XINPUT: Adding extended input device "Synaptics Touch Pad V 1.03P" (type: TOUCHPAD, id 10)
[    58.936] (**) synaptics: Synaptics Touch Pad V 1.03P: (accel) MinSpeed is now constant deceleration 2.5
[    58.936] (**) synaptics: Synaptics Touch Pad V 1.03P: (accel) MaxSpeed is now 1.75
[    58.936] (**) synaptics: Synaptics Touch Pad V 1.03P: (accel) AccelFactor is now 0.042
[    58.936] (**) Synaptics Touch Pad V 1.03P: (accel) keeping acceleration scheme 1
[    58.936] (**) Synaptics Touch Pad V 1.03P: (accel) acceleration profile 1
[    58.936] (**) Synaptics Touch Pad V 1.03P: (accel) acceleration factor: 2.000
[    58.936] (**) Synaptics Touch Pad V 1.03P: (accel) acceleration threshold: 4
[    58.936] (--) synaptics: Synaptics Touch Pad V 1.03P: touchpad found

lukasm · 2015-03-03 20:26:03

How is then your synaptic file. Or does anyone has a clue why this could happen?

I did what you have written you changed in the 50-synaptics.conf. It now shows the same error

[     3.723] (II) config/udev: Adding input device Synaptics Touch Pad V 103u9 (/dev/input/event14)
[     3.723] (**) Synaptics Touch Pad V 103u9: Applying InputClass "evdev pointer catchall"
[     3.723] (II) Using input driver 'evdev' for 'Synaptics Touch Pad V 103u9'
[     3.724] (**) Synaptics Touch Pad V 103u9: always reports core events
[     3.724] (**) evdev: Synaptics Touch Pad V 103u9: Device: "/dev/input/event14"
[     3.724] (--) evdev: Synaptics Touch Pad V 103u9: Vendor 0x6cb Product 0x5711
[     3.724] (--) evdev: Synaptics Touch Pad V 103u9: Found 3 mouse buttons
[     3.724] (--) evdev: Synaptics Touch Pad V 103u9: Found relative axes
[     3.724] (--) evdev: Synaptics Touch Pad V 103u9: Found x and y relative axes
[     3.724] (II) evdev: Synaptics Touch Pad V 103u9: Configuring as mouse
[     3.724] (**) evdev: Synaptics Touch Pad V 103u9: YAxisMapping: buttons 4 and 5
[     3.724] (**) evdev: Synaptics Touch Pad V 103u9: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[     3.724] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:06CB:5711.0002/input/input14/event14"
[     3.724] (II) XINPUT: Adding extended input device "Synaptics Touch Pad V 103u9" (type: MOUSE, id 8)
[     3.724] (II) evdev: Synaptics Touch Pad V 103u9: initialized for relative axes.
[     3.724] (**) Synaptics Touch Pad V 103u9: (accel) keeping acceleration scheme 1
[     3.724] (**) Synaptics Touch Pad V 103u9: (accel) acceleration profile 0
[     3.724] (**) Synaptics Touch Pad V 103u9: (accel) acceleration factor: 2.000
[     3.724] (**) Synaptics Touch Pad V 103u9: (accel) acceleration threshold: 4
[     3.724] (II) config/udev: Adding input device Synaptics Touch Pad V 103u9 (/dev/input/mouse0)
[     3.724] (**) Synaptics Touch Pad V 103u9: Applying InputClass "touchpad catchall"
[     3.724] (**) Synaptics Touch Pad V 103u9: Applying InputClass "Default clickpad buttons"
[     3.724] (II) LoadModule: "synaptics"
[     3.724] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[     3.725] (II) Module synaptics: vendor="X.Org Foundation"
[     3.725] 	compiled for 1.16.0, module version = 1.8.1
[     3.725] 	Module class: X.Org XInput Driver
[     3.725] 	ABI class: X.Org XInput driver, version 21.0
[     3.725] (II) Using input driver 'synaptics' for 'Synaptics Touch Pad V 103u9'
[     3.725] (**) Synaptics Touch Pad V 103u9: always reports core events
[     3.725] (**) Option "Device" "/dev/input/mouse0"
[     3.783] (EE) synaptics: Synaptics Touch Pad V 103u9: Synaptics driver unable to detect protocol
[     3.783] (EE) PreInit returned 11 for "Synaptics Touch Pad V 103u9"
[     3.783] (II) UnloadModule: "synaptics"

Does anyone know the difference?

In my 50-synaptics file i have

Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
#	MatchIsTouchpad "on"
        Option "TapButton1" "1"
        Option "TapButton2" "2"
        Option "TapButton3" "3"
		Option "VertTwoFingerScroll" "on"
		Option "HorizTwoFingerScroll" "on"

		Option "VertScrollDelta" "-96"
		Option "HorizScrollDelta" "-96"

# 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*"
        MatchDevicePath "/dev/input/mouse0"
EndSection

uselessfire · 2015-05-02 14:00:24

After last updates, touchpad is fully working! I just installed xf86-input-synaptics and it works.

lukasm · 2015-05-17 22:09:30

I can confirm this!

Thanks a lot!

Arch Linux

#1 2014-10-23 15:15:08

[SOLVED] Laptop with Synaptics not working after update

#2 2014-10-24 12:06:39

Re: [SOLVED] Laptop with Synaptics not working after update

#3 2014-10-25 01:14:45

Re: [SOLVED] Laptop with Synaptics not working after update

#4 2014-10-25 01:25:48

Re: [SOLVED] Laptop with Synaptics not working after update

#5 2014-10-27 22:16:55

Re: [SOLVED] Laptop with Synaptics not working after update

#6 2014-11-02 19:18:03

Re: [SOLVED] Laptop with Synaptics not working after update

#7 2014-11-03 18:56:24

Re: [SOLVED] Laptop with Synaptics not working after update

#8 2014-11-03 19:18:40

Re: [SOLVED] Laptop with Synaptics not working after update

#9 2014-11-03 20:58:04

Re: [SOLVED] Laptop with Synaptics not working after update

#10 2014-11-03 21:56:59

Re: [SOLVED] Laptop with Synaptics not working after update

#11 2014-11-05 15:22:57

Re: [SOLVED] Laptop with Synaptics not working after update

#12 2014-11-18 22:26:23

Re: [SOLVED] Laptop with Synaptics not working after update

#13 2014-11-20 07:07:41

Re: [SOLVED] Laptop with Synaptics not working after update

#14 2014-11-20 12:07:05

Re: [SOLVED] Laptop with Synaptics not working after update

#15 2014-12-12 18:07:01

Re: [SOLVED] Laptop with Synaptics not working after update

#16 2014-12-12 22:50:34

Re: [SOLVED] Laptop with Synaptics not working after update

#17 2014-12-16 13:39:03

Re: [SOLVED] Laptop with Synaptics not working after update

#18 2014-12-16 16:52:42

Re: [SOLVED] Laptop with Synaptics not working after update

#19 2015-02-06 16:11:47

Re: [SOLVED] Laptop with Synaptics not working after update

#20 2015-02-24 14:33:10

Re: [SOLVED] Laptop with Synaptics not working after update

#21 2015-02-26 08:27:51

Re: [SOLVED] Laptop with Synaptics not working after update

#22 2015-02-28 15:53:40

Re: [SOLVED] Laptop with Synaptics not working after update

#23 2015-03-03 20:26:03

Re: [SOLVED] Laptop with Synaptics not working after update

#24 2015-05-02 14:00:24

Re: [SOLVED] Laptop with Synaptics not working after update

#25 2015-05-17 22:09:30

Re: [SOLVED] Laptop with Synaptics not working after update

Board footer