← Back to team overview

kernel-packages team mailing list archive

[Bug 1354604] Re: Regression: touchscreen-as-input not recognized in recent kernels (Dell Venue 11 Pro 7130)


Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Regression: touchscreen-as-input not recognized in recent kernels
  (Dell Venue 11 Pro 7130)

Status in “linux” package in Ubuntu:

Bug description:
  Due to bug #1354598, my Dell Venue 11 Pro 7130 tablet is unusable as a
  tablet with the current Trusty kernel, so I have been attempting to
  find a more recent kernel for which the screen functions both as a
  display and a touch input device. No luck so far.

  (Well, actually, oddly enough, that's not quite true: I installed the
  05-Aug-2014 01:21 daily live CD of Kubuntu Active, which is i386 only,
  and *that* worked just fine, from a kernel/hardware perspective. But
  I'm hoping to get an amd64 kernel working.)

  When booting either of the most recent Utopic kernel (3.16.0-6) and
  the kernel team's latest build of upstream (3.16.0-031600), the
  touchscreen is unresponsive to touch input, and inspection of the logs
  confirms that the multitouch device is not recognized as such.

  Will run apport-collect. Also the udev logs attached to bug #1354598
  may be interesting.

To manage notifications about this bug go to: