Touchpad gets recognized as mouse by 10-evdev.conf

Carpetsmoker · 2014-05-24 23:26:16

How can I make my touchpad on my Dell XPS 13 work with the synaptics driver?

/etc/X11/xorg.conf.d/10-evdev.conf catches it as a mouse pointer, probably due to the crappy device name:

# /var/log/Xorg.0.log

[  2265.924] (II) config/udev: Adding input device DLL060A:00 06CB:2734 (/dev/input/event6)
[  2265.924] (**) DLL060A:00 06CB:2734: Applying InputClass "evdev pointer catchall"
[  2265.924] (II) Using input driver 'evdev' for 'DLL060A:00 06CB:2734'
[...]
[  2265.957] (**) Option "config_info" "udev:/sys/devices/pci0000:00/INT33C3:00/i2c-0/i2c-DLL060A:00/0018:06CB:2734.0001/input/input8/event6"
[  2265.957] (II) XINPUT: Adding extended input device "DLL060A:00 06CB:2734" (type: MOUSE, id 11)
[...]
[  2265.958] (II) config/udev: Adding input device DLL060A:00 06CB:2734 (/dev/input/mouse0)

[~]% dmesg | grep DLL060

[    0.414884] pnp 00:0a: Plug and Play ACPI device, IDs DLL060a PNP0c50 (active)
[    1.442758] i2c_hid i2c-DLL060A:00: failed to retrieve report from device.
[    1.442909] input: DLL060A:00 06CB:2734 as /devices/pci0000:00/INT33C3:00/i2c-0/i2c-DLL060A:00/0018:06CB:2734.0001/input/input8
[    1.442993] hid-generic 0018:06CB:2734.0001: input,hidraw0: <UNKNOWN> HID v1.00 Pointer [DLL060A:00 06CB:2734] on

[/home/martin]# udevadm info /dev/input/event6

P: /devices/pci0000:00/INT33C3:00/i2c-0/i2c-DLL060A:00/0018:06CB:2734.0001/input/input8/event6
N: input/event6
S: input/by-path/platform-INT33C3:00-event-mouse
E: DEVLINKS=/dev/input/by-path/platform-INT33C3:00-event-mouse
E: DEVNAME=/dev/input/event6
E: DEVPATH=/devices/pci0000:00/INT33C3:00/i2c-0/i2c-DLL060A:00/0018:06CB:2734.0001/input/input8/event6
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_PATH=platform-INT33C3:00
E: ID_PATH_TAG=platform-INT33C3_00
E: ID_SERIAL=noserial
E: MAJOR=13
E: MINOR=70
E: SUBSYSTEM=input
E: USEC_INITIALIZED=37688

I've tried making my own xorg.conf (Xorg -configure) no matter which device name I choose (/dev/input/event6, /dev/hidraw0, /dev/input/mouse*), the touchpad does nothing....

I've also tried disabling the generic pointer catchall, and adding my own specific for this device, but this does nothing also.

Section "InputClass"
    Identifier "My Touchpad"
    MatchDevicePath "/dev/input/event6"
    driver "synaptics"
EndSection

Section "InputClass"
    Identifier "My Touchpad 2"
    MatchUSBID "0b95:1790"
    driver "synaptics"
EndSection
#Section "InputClass"
#        Identifier "evdev pointer catchall"
#        MatchIsPointer "on"
#        MatchDevicePath "/dev/input/event*"
#        Driver "evdev"
#EndSection

#Section "InputClass"
#        Identifier "evdev touchpad catchall"
#        MatchIsTouchpad "on"
#        MatchDevicePath "/dev/input/event*"
#        Driver "evdev"
#EndSection

PS.
I'd prefer to have 10-evdev.conf remain working, as I use it for my trackball & keyboard.

ewaller · 2014-05-24 23:33:34

First, welcome to Arch Linux.

That said, I have no way of knowing your experience except by a reasonable first post So, bear with me while I ask a silly question. Did you install the xf86-input-synaptics package?

Carpetsmoker · 2014-05-24 23:39:01

ewaller wrote:

First, welcome to Arch Linux.
That said, I have no way of knowing your experience except by a reasonable first post So, bear with me while I ask a silly question. Did you install the xf86-input-synaptics package?

Thanks.

I should have mentioned it in my OP, yeah, it's installed

[~]% pacman -Q | grep synaptics
xf86-input-synaptics 1.8.0-1

The entire system is up-to-date (pacman -Syu).

[~]% synclient
Couldn't find synaptics properties. No synaptics driver loaded?
Exit 1

[~]% syndaemon
Unable to find a synaptics device.
Exit 1

ewaller · 2014-05-25 00:46:52

I have been looking at your output, and I am not quite sure what to do. I am very concerned about this line from your dmesg:

[    1.442758] i2c_hid i2c-DLL060A:00: failed to retrieve report from device.

i2c is a two wire bus for communicating with devices (Inter Integrated Circuit https://en.wikipedia.org/wiki/I%C2%B2C)
HID is Human Interface Device https://en.wikipedia.org/wiki/Human_interface_device. HID devices have the ability to tell their host about their capability. It appears your system is not able to retrieve the report about that touchpad, so the kernel assumes a generic mode in which includes "mouse" reports. I don't think that any of the higher level PNP configuration is going to work without that capabilities report.

Let me ponder this some more...

Last edited by ewaller (2014-05-25 00:53:09)

ewaller · 2014-05-25 01:34:25

Does this apply to your situation?

Also (This is another sanity check) please check that the output of uname -a and of pacman -Qi linux report the exact same kernel version.
I want to make sure the kernel is finding its modules.

Last edited by ewaller (2014-05-25 01:56:10)

Carpetsmoker · 2014-05-25 11:11:27

Thank you ewaller; that's a different line of reasoning I hadn't considered yet, I just mucked about with the X configuration.

Following up on this, I eventually got it working disabling the i2c_hid driver, by making /etc/modprobe.d/no-touchscreen.conf :

blacklist i2c_hid

The device is now reported as `SynPS/2 Synaptics TouchPad', and works with the synaptics driver.

Installing the various psmouse-* drivers from AUR didn't help.

This also disabled the touchscreen, which I don't really mind (touchscreens on laptops are completely useless, IMHO).

This is apparently a known problem:
http://www.spinics.net/lists/linux-input/msg27768.html

*edit*: I also updated the wiki entry...

Last edited by Carpetsmoker (2014-05-25 11:29:50)

chronos · 2014-06-19 10:25:44

It's a comon Problem on the Dell XPS 13. I blacklisted i2c_hid right away.

But since the Kernel Update yesterday (3.15.1-1-ARCH) My system did not recognise the Trackpad at all anymore.
I removed the blacklisting and I was very happy to have it working again.
It even detected klicking in the VERY lower left corner now. It felt like a Bug fix.

But also it is now recognises it agan as a mouse and not a trackpad. So it has ben a pain to not have natural scrolling working.
Is anybody experiencing the same problem?

The result of xinput:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  	id=14	[slave  pointer  (2)]
⎜   ↳ DLL060A:00 06CB:2734                    	id=9	[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)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]
    ↳ Dell WMI hotkeys                        	id=11	[slave  keyboard (3)]
    ↳ Integrated_Webcam_HD                    	id=12	[slave  keyboard (3)]

p.s. the blacklisting never disabled my touchscreen

heldenhaft · 2014-06-19 18:30:37

Hi,
i have the same problem with my xps 13....if have a solution please post it ...

cu

delcypher · 2014-06-20 06:57:34

Yep. Exactly the same problem here.

chronos · 2014-06-20 18:33:16

It is definetly the kernel.

I did a downgrade to 3.14.6-1 and everything runs smothly again. (btw. did any of you solve palm rejection?)
You can go to

 /var/cache/pacman/pkg/

and see if any of your old kernels are still there and install them with

 pacman -U [filename]

.
Even easyer is (using yaourt) download the downgrade script from AUR and run

 downgrade linux

and

 downgrade linux-headers

.
Otherwhise see (archwiki) Downgrading the kernel
(backlisting i2c-hid is of course still necessary)

I'm quite busy right now so it might take some days untill I can file a bug report (have never done so). Has any of you more time and/or experience with that?

heldenhaft · 2014-06-20 19:28:37

Maybe...you can use this patches for the new kernel:?
https://github.com/gunzy83/linux-xps13-archlinux

Tomin · 2014-06-20 20:12:02

chronos wrote:

It's a comon Problem on the Dell XPS 13. I blacklisted i2c_hid right away.
But since the Kernel Update yesterday (3.15.1-1-ARCH) My system did not recognise the Trackpad at all anymore.
I removed the blacklisting and I was very happy to have it working again.
It even detected klicking in the VERY lower left corner now. It felt like a Bug fix.
But also it is now recognises it agan as a mouse and not a trackpad. So it has ben a pain to not have natural scrolling working.
Is anybody experiencing the same problem?

I've got this problem too. I'm running 3.15.1-1 on Dell XPS 13 (9333) and if I don't blacklist i2c_hid my touchscreen works fine but I can't scroll with my touchpad and I can't use synaptics settings. If I blacklist i2c_hid I can't use touchscreen or touchpad at all which is very bad.

Edit: I wrote a bug report: https://bugs.archlinux.org/task/40921

Last edited by Tomin (2014-06-21 05:29:36)

chronos · 2014-06-21 08:51:33

Tomin wrote:

chronos wrote:
It's a comon Problem on the Dell XPS 13. I blacklisted i2c_hid right away.
But since the Kernel Update yesterday (3.15.1-1-ARCH) My system did not recognise the Trackpad at all anymore.
I removed the blacklisting and I was very happy to have it working again.
It even detected klicking in the VERY lower left corner now. It felt like a Bug fix.
But also it is now recognises it agan as a mouse and not a trackpad. So it has ben a pain to not have natural scrolling working.
Is anybody experiencing the same problem?
I've got this problem too. I'm running 3.15.1-1 on Dell XPS 13 (9333) and if I don't blacklist i2c_hid my touchscreen works fine but I can't scroll with my touchpad and I can't use synaptics settings. If I blacklist i2c_hid I can't use touchscreen or touchpad at all which is very bad.
Edit: I wrote a bug report: https://bugs.archlinux.org/task/40921

Thanks a lot!!!
I added aome more information I could come up with.
Currently it's "Extra" can you move it to Kernel? Because it's definetly a kernel Problem.

Everybody else having that Problem add your vote there so it becomes ha higher priority.!!!

firesock · 2014-06-29 17:32:39

Hit this problem, for me blacklisting i2c_hid was causing no touchpad at all, but touchscreen carried on working. Removing the blacklist allows hid_generic to pick up the touchpad (no advanced features), and hid_multitouch carries on picking up the touchscreen. (Tested this by modprobing in/out and the corresponding things stopped working and back with correct dmesg entries)

I think https://bugzilla.redhat.com/show_bug.cgi?id=1048314#c5 is implying that https://github.com/torvalds/linux/commi … f24bde846f is causing things to stop working without i2c_hid.

The previous bug and https://bugs.launchpad.net/ubuntu/+sour … omments/61 onwards sort of keep an eye on the new module needed for i2c touchpads.

The temporary version (see previous links) can be built from here https://github.com/bentiss/hid-rmi and has been accepted upstream for 3.16 kernel inclusion: http://git.kernel.org/cgit/linux/kernel … eeda32c736, already in the rc's:

$ git tag --contains 9fb6bf02e3ad04c20edb8e46536ce3eeda32c736     
v3.16-rc1
v3.16-rc2

adhok · 2014-07-03 15:42:13

Just wanted to reply and let everyone know that the above fix proposed by firesock does indeed work. I'm running 3.16.0-rc3 atm and the hid_rmi module is running for the touchpad. When you go to configure your kernel, Device Drivers -> HID support -> Special HID drivers -> <M> Synaptics RMI4 device support.

You don't have to blacklist i2c_hid either with this fix. Touchscreen, and Touchpad (w/ horizontal and vertical 2 finger scrolling) is working perfectly and the touchpad is picked up in gnome3 Settings -> mouse and touchpad as well.

The only issue is that for me, xinput still displays it as DLL060A instead of a synaptics device. But it does work great.

Last edited by adhok (2014-07-03 18:50:51)

crmullins · 2014-07-26 03:59:57

I think I've tried firesock's solution correctly, but nothing happened. Blacklisting i2c_hid disabled the touchpad completely, and after installing the patch, hid_rmi doesn't enable the touchpad (but it did break the touchscreen). So now I've blacklisted hid_rmi and I'm at least back to a working touchscreen, but still no two-finger scrolling.

hid_generic and hid_multitouch are both loaded so those are clearly not doing the trick:

[chris@shiny running-config]$ lsmod | grep hid
hid_multitouch 10041 0
usbhid 41250 0
hid_generic 1217 0
mac_hid 3273 0
i2c_hid 11675 0
hid 93052 4 i2c_hid,hid_multitouch,hid_generic,usbhid
i2c_core 41648 8 drm,i915,i2c_i801,i2c_hid,i2c_designware_platform,drm_kms_helper,i2c_algo_bit,videodev
usbcore 188381 6 btusb,uvcvideo,ehci_hcd,ehci_pci,usbhid,xhci_hcd

I'm trying to compile and upgrade the kernel to 3.16rc6 now.

EDIT: 3.16.0rc6 appears to work - touchpad and touchscreen are now functional. So glad I found this thread!

Last edited by crmullins (2014-07-28 18:06:20)

pexino · 2014-07-31 17:43:19

Hi all,

with my XPS 13 I had the known problem with the synaptics drivers. I solved compiling and upgrating the kernel to the last 3.16rc7 with "<M> Synaptics RMI4 device support" option. Touchpad is now completely functional but the touchscreen works just as a pointer without recognizing taps or gestures. Do you have the same problem or there is something wrong with my config?

[fabio@elizaveta ~]$ xinput
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ DLL060A:00 06CB:2734                      id=9    [slave  pointer  (2)]
⎜   ↳ SYNAPTICS Synaptics Large Touch Screen    id=12   [slave  pointer  (2)]

[...]

[fabio@elizaveta ~]$ cat /proc/bus/input/devices

[...]

I: Bus=0003 Vendor=06cb Product=0af8 Version=0111
N: Name="SYNAPTICS Synaptics Large Touch Screen"
P: Phys=usb-0000:00:14.0-3/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:06CB:0AF8.0002/input/input15
U: Uniq=
H: Handlers=event13 mouse1 
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=260800000000003

[...]

[fabio@elizaveta ~]$ lsmod | grep hid
hid_multitouch          9721  0 
usbhid                 41251  0 
hid_rmi                 8694  0 
i2c_hid                11163  0 
hid                    97340  4 i2c_hid,hid_multitouch,hid_rmi,usbhid
mac_hid                 3273  0 
usbcore               192792  6 btusb,uvcvideo,ehci_hcd,ehci_pci,usbhid,xhci_hcd
i2c_core               41648  9 drm,i915,i2c_i801,i2c_hid,i2c_designware_platform,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev

Thank you very much guys!

Fabio

Edit:

Forget me. The problem is that I was testing the touch screen in Chromium and, in this case, it works properly just setting the device as "floating slave" in xinput (command: xinput float #id).

Last edited by pexino (2014-07-31 22:14:29)

mthed · 2015-03-03 01:30:15

Ran into this similar problem under AVLINUX (an offshot of Debian Squeeze)... Turned out there was a file called touchpad.conf in /etc/modprobe.d. Deleted it and now it works great, just want to spread the word because it took a lot of effort to figure this out...

cedeel · 2015-03-03 01:53:00

How Debian and their derivatives do things is vastly different from how it's done in Arch. My modprobe.d directory is completely empty, which is the default.'

Your comment was meant to be helpful, but without you checking to see if your advice is applicaple to Arch users, it would probably be better to not give any.

wildfowl · 2015-06-09 23:41:29

Debian is cloest thing to Arch that you can get. Packaging philosophy aside.

Arch Linux

#1 2014-05-24 23:26:16

Touchpad gets recognized as mouse by 10-evdev.conf

#2 2014-05-24 23:33:34

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#3 2014-05-24 23:39:01

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#4 2014-05-25 00:46:52

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#5 2014-05-25 01:34:25

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#6 2014-05-25 11:11:27

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#7 2014-06-19 10:25:44

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#8 2014-06-19 18:30:37

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#9 2014-06-20 06:57:34

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#10 2014-06-20 18:33:16

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#11 2014-06-20 19:28:37

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#12 2014-06-20 20:12:02

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#13 2014-06-21 08:51:33

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#14 2014-06-29 17:32:39

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#15 2014-07-03 15:42:13

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#16 2014-07-26 03:59:57

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#17 2014-07-31 17:43:19

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#18 2015-03-03 01:30:15

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#19 2015-03-03 01:53:00

Re: Touchpad gets recognized as mouse by 10-evdev.conf

#20 2015-06-09 23:41:29

Re: Touchpad gets recognized as mouse by 10-evdev.conf

Board footer