Comment 59 for bug 1305522

Hi everybody,
I am new to this, so apologies.

I got also a Dell XPS 12 and for me, after the official kernel update to "3.13.0-27-generic" my touchpad is not working in multitouch anymore (like scrolling and so on) and oly recognized as mouse. Touchscreen works fine.
 xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ATML1000:00 03EB:842F id=10 [slave pointer (2)]
⎜ ↳ DLL05E3:01 06CB:2734 id=11 [slave pointer (2)]
⎜ ↳ PS/2 Synaptics TouchPad id=14 [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)]
    ↳ Integrated Webcam id=9 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=13 [slave keyboard (3)]

If I blacklist in the blacklist.conf i2c_hid touchpad is fully functional, but touchscreen is disabled.

Before the update I did this workaround:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218973

in more detail:
download this:
https://github.com/bentiss/hid-rmi

1. make/make install of hid-rmi
2. Manually run ‘sudo depmod -a’ (wouldn’t find it without this step).
3. Ensure that you can modprobe it and that its found now, if so proceed. No point proceeding unless you get this sorted.
4. Ensure that i2c_hid wasn’t blacklisted and was loading.
5. Create /etc/modprobe.d/hid-rmi.conf as follows (write following into this new file):
install hid_rmi rmmod hid_generic ; modprobe –ignore-install hid_rmi
6. Reboot and make sure all was loading. (If correct both touchscreen will work and touchpad will register correctly under System Settings->Mouse – otherwise touchpad just appears as regular mouse under System Settings->Mouse)

So I did not install the custom kernels here (eg. #44).

I blacklisted hid-rmi but problem remains.
Any idea how I can get rid of the workaround?
probably the same issue as arash.

How can I install the custom kernel? Or should I just wait for an official fix?