Start a Conversation

Unsolved

This post is more than 5 years old

67035

November 9th, 2015 19:00

xps9350: touchscreen stops working after sleep

Running a 4.3 kernel: touchscreen works great on boot, but fails after sleep/resume. I've tried the following to no avail:

 * rmmod hid_multitouch  && sleep 5 && modprobe hid_multitouch

This does reveal in /var/log/syslog:

Nov 9 22:44:16 morel kernel: [32441.878773] input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:20D0.0001/input/input34
Nov 9 22:44:16 morel kernel: [32441.932623] hid-multitouch 0003:04F3:20D0.0001: input,hiddev0,hidraw0: USB HID v1.10 Device [ELAN Touchscreen] on usb-0000:00:14.0-4/input0

-- no errors visible, but the touchscreen simply doesn't work.

Thoughts on how I can debug or report further?

11 Posts

April 15th, 2016 06:00

Same problem for me - on 16.04.

13 Posts

April 24th, 2016 14:00

Apparently (I haven't tested), your fix works with kernel 4.6.  See bbs.archlinux.org/viewtopic.php

2 Posts

April 27th, 2016 15:00

After some experiments, this did work for me:

$ sudo inputattach --daemon -w8001 /dev/ttyS4

...what I don't understand, because my ELAN Touchscreen is definitely not on serial port so there should not be reason to use inputattach at all.

The problem with this is that inputattach process gets D status (uninterruptible sleep) so it makes the suspend/resume to take about 20 seconds (which is some timeout) and sometimes it does not work at all. Since you cannot kill this proccess, it is quite sad and it might imply any other issues eventually.

So this is not solution but might be some indice to find out what the real problem is. I also see this:

$ dmesg | grep -ie elan
[ 7.637031] usb 1-4: Manufacturer: ELAN
[ 10.101754] input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:20D0.0001/input/input12
[ 10.101852] hid-multitouch 0003:04F3:20D0.0001: input,hiddev0,hidraw0: USB HID v1.10 Device [ELAN Touchscreen] on usb-0000:00:14.0-4/input0
[ 698.403796] input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:20D0.0001/input/input18
[ 698.404299] hid-multitouch 0003:04F3:20D0.0001: input,hiddev0,hidraw0: USB HID v1.10 Device [ELAN Touchscreen] on usb-0000:00:14.0-4/input0

...I wonder why it is input18 instead of input12 after first resume (might change after another suspend/resume?!). So maybe, there is something waiting for input12 but it has changed to input18 while something expects it on 12? I don't know.

That's just my two cents, and I am hefeby joining the question how to fix this completely and properly :)

5 Practitioner

 • 

274.2K Posts

June 17th, 2016 01:00

same problem here  with xps 13 DE 9350 running ubuntu 16.04 kernel 4.4 (or latest kernel 4.7).

I have found a weird workaround:

close the lid just to enter suspend state, but then reopen it quickly, so that it stays in suspend state even when the lid is open. Then press power button to wake it up. Then the touchscreen works again ! 

11 Posts

June 17th, 2016 02:00

Yes, I confirm that works for me too.  With the 4.4 kernel, 16.04.

13 Posts

June 17th, 2016 03:00

Awesome find :-)  Works well.

2 Posts

June 17th, 2016 17:00

Wonderful! I did it very quickly so that I didn't have to press the power button and it just locked screen and started to work again. Given this, we may be able to do some kernel debugging now...

5 Posts

June 29th, 2016 18:00

Yeah, the quick lid close works for me as well. Weird.

Any luck debugging this further?

3 Posts

July 4th, 2016 00:00

Can also confirm same workaround works. Don't even have to close the lid fully, just move it down a bit then up - the display doesn't even go dark - and touch is working again.

5 Posts

July 4th, 2016 19:00

This seems to still be an issue with the latest 1.4.4 firmware. It's not that big of a deal to me given the workaround of closing it and then opening it again right away seems to fix it.

1 Message

September 4th, 2016 11:00

Did you solve the problem?

11 Posts

October 3rd, 2016 13:00

Apart from this minor problem - for which there is an easy fix, I think its a good laptop, and well supported...

at least compared with other laptops I've had...

1 Message

October 3rd, 2016 13:00

Same problem here.  Close lid briefly and then power button also works for me, but clearly that's not a long term solution.

Ubuntu 16.04 LTS - latest updates.

Wondering if I made a mistake buying this.  16.04 is still not yet officially supported...

2 Posts

October 24th, 2016 08:00

I get this on the official Dell ubuntu 14.04 that came with my laptop. It has only been a problem since I accepted the ubuntu "hardware enablement" stack thing recently.

3 Posts

November 10th, 2016 16:00

This is now fixed in the kernel. I reached out to the developer who fixed it and he was able to help me make a more reasonable workaround while we wait for that code to be released.

gist.github.com/.../16d07928e3d5d60960aa91dc67f0ad32

No Events found!

Top