[DNS Travel 0157253 / X300V] Touchpad does not work (i8042.noloop=1 as a workaround)

[ProRunner]

The touchpad of my local-branded X300V-based notebook (DNS Travel 0157253) is not working (cursor is not moving, buttons do not function)

There is a WORKAROUND: adding i8042.noloop=1 to GRUB_CMDLINE_LINUX in /etc/default/grub

sudo nano /etc/default/grub
GRUB_CMDLINE_LINUX="i8042.noloop=1"

sudo grub-update
reboot

Can it be fixed in the kernel?

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-22-generic 4.8.0-22.24 [modified: boot/vmlinuz-4.8.0-22-generic]
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vladimir 1828 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Oct 29 10:05:38 2016
HibernationDevice: RESUME=UUID=062a9af0-97c9-4d1f-ae90-3ad30e175464
InstallationDate: Installed on 2016-10-29 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=bbbc85d7-8997-4645-b676-58088ef7131a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-22-generic N/A
 linux-backports-modules-4.8.0-22-generic N/A
 linux-firmware 1.161
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X300V DN.1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: ChiefRiver
dmi.board.vendor: INTEL Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX300VDN.1:bd08/09/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnChiefRiver:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

[ProRunner (mrprorunner)]

cat /proc/bus/input/devices

[Brad Figg (brad-figg)]

This change was made by a bot.

[ProRunner (mrprorunner)]

dmidecode

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 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: 'kernel-bug-exists-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/v4.9-rc3

[ProRunner (mrprorunner)]

No, this problem existed in earlier kernels also. I've used 16.04 before - and it was the same there.
I've also tested it with the latest upstream kernel and it still exists.