Touchpad incorrectly being detected by kernel as PS/2 mouse

[Apicultor]

The touchpad in the Panasonic Toughbook CF-30 (specifically CF-30K, also known as "CF30", "CF30-3", "CF-30 Mk3", "CF-30 Mark 3", etc) is being detected as only a generic PS/2 mouse, not a touchpad of any kind.

Pointing and clicking (also tapping to click) works, but scrolling doesn't work -- and there is no touchpad options in the relevant control panel, only pointer speed.

This appears to be happening in the kernel, not in X.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: kernel-common (not installed)
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
Date: Tue Dec 26 11:54:48 2017
InstallationDate: Installed on 2017-12-17 (8 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: kernel-package
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: apicultor 2966 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=d85b6945-0c3c-4696-b5c1-b2b010d524c8
InstallationDate: Installed on 2017-12-17 (23 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Panasonic Corporation CF-30KAPAXAM
Package: linux (not installed)
PccardctlStatus:
 Socket 0:
   5.0V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "serial_cs"
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-42-generic N/A
 linux-backports-modules-4.10.0-42-generic N/A
 linux-firmware 1.157.14
Tags: xenial
Uname: Linux 4.10.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.00L19
dmi.board.name: CF30-3
dmi.board.vendor: Panasonic Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Panasonic Corporation
dmi.chassis.version: 001
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.00L19:bd04/27/2009:svnPanasonicCorporation:pnCF-30KAPAXAM:pvr003:rvnPanasonicCorporation:rnCF30-3:rvr1:cvnPanasonicCorporation:ct10:cvr001:
dmi.product.name: CF-30KAPAXAM
dmi.product.version: 003
dmi.sys.vendor: Panasonic Corporation

[Apicultor (apicultor)]

[ 4.450585] input: PS/2 Generic Mouse as /devices/platform/i8042/serio2/input/input9

[Apicultor (apicultor)]

Removing specificity to kernel-package

[Apicultor (apicultor)]

More info:

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Fujitsu Component USB Touch Panel id=9 [slave pointer (2)]
⎜ ↳ PS/2 Generic Mouse id=11 [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)]
    ↳ Panasonic Laptop Support id=12 [slave keyboard (3)]

$ xinput list-props 11 | grep /dev/input/event
 Device Node (256): "/dev/input/event6"

$ udevadm info -q path -n /dev/input/event6
/devices/platform/i8042/serio2/input/input9/event6

$ udevadm info -a -p /devices/platform/i8042/serio2/input/input9/event6
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/i8042/serio2/input/input9/event6':
    KERNEL=="event6"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device '/devices/platform/i8042/serio2/input/input9':
    KERNELS=="input9"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{name}=="PS/2 Generic Mouse"
    ATTRS{phys}=="isa0060/serio2/input0"
    ATTRS{properties}=="1"
    ATTRS{uniq}==""

  looking at parent device '/devices/platform/i8042/serio2':
    KERNELS=="serio2"
    SUBSYSTEMS=="serio"
    DRIVERS=="psmouse"
    ATTRS{bind_mode}=="auto"
    ATTRS{description}=="i8042 AUX1 port"
    ATTRS{firmware_id}=="PNP: FJC6001 PNP0f13"
    ATTRS{protocol}=="PS/2"
    ATTRS{rate}=="100"
    ATTRS{resetafter}=="5"
    ATTRS{resolution}=="200"
    ATTRS{resync_time}=="0"

  looking at parent device '/devices/platform/i8042':
    KERNELS=="i8042"
    SUBSYSTEMS=="platform"
    DRIVERS=="i8042"
    ATTRS{driver_override}=="(null)"

  looking at parent device '/devices/platform':
    KERNELS=="platform"
    SUBSYSTEMS==""
    DRIVERS==""

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Apicultor (apicultor)]

This might be a duplicate of bug 1708852, but the upstream kernel 4.14.9 does NOT fix the issue.

[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.15 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.15-rc6/

[Apicultor (apicultor)]

Linux machine 4.15.0-041500rc6-generic #201712312330 SMP Sun Dec 31 23:31:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

[Apicultor (apicultor)]

Issue still exists upstream; tagging and confirming.

[Kai-Heng Feng (kaihengfeng)]

Please run `apport-collect 1740116`.

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Apicultor (apicultor)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Please try http://people.canonical.com/~khfeng/lp1740116/

[Apicultor (apicultor)]

Unfortunately this didn't fix the problem. The mouse pointer moves much more slowly, and it's being detected as a touchpad by xinput, but the control panel still only offers mouse pointer speed and no touchpad options.

It also looks like the touchscreen is being detected twice now, once as USB as before but now also as PS/2 (?!), which might be an error. FWIW, it was working fine before testing your custom kernel, when only the USB enumeration was present.

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Fujitsu Component USB Touch Panel id=9 [slave pointer (2)]
⎜ ↳ LBPS/2 Fujitsu Lifebook Touchpad id=11 [slave pointer (2)]
⎜ ↳ LBPS/2 Fujitsu Lifebook TouchScreen id=12 [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)]
    ↳ Panasonic Laptop Support id=13 [slave keyboard (3)]

$ xinput list-props 11 | grep /dev/input/event
 Device Node (258): "/dev/input/event6"

$ udevadm info -q path -n /dev/input/event6
/devices/platform/i8042/serio2/input/input12/event6

$ udevadm info -a -p /devices/platform/i8042/serio2/input/input12/event6

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/i8042/serio2/input/input12/event6':
    KERNEL=="event6"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device '/devices/platform/i8042/serio2/input/input12':
    KERNELS=="input12"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{name}=="LBPS/2 Fujitsu Lifebook Touchpad"
    ATTRS{phys}=="isa0060/serio2/input1"
    ATTRS{properties}=="0"
    ATTRS{uniq}==""

  looking at parent device '/devices/platform/i8042/serio2':
    KERNELS=="serio2"
    SUBSYSTEMS=="serio"
    DRIVERS=="psmouse"
    ATTRS{bind_mode}=="auto"
    ATTRS{description}=="i8042 AUX1 port"
    ATTRS{firmware_id}=="PNP: FJC6001 PNP0f13"
    ATTRS{protocol}=="LBPS/2"
    ATTRS{rate}=="100"
    ATTRS{resetafter}=="5"
    ATTRS{resolution}=="200"
    ATTRS{resync_time}=="0"

  looking at parent device '/devices/platform/i8042':
    KERNELS=="i8042"
    SUBSYSTEMS=="platform"
    DRIVERS=="i8042"
    ATTRS{driver_override}=="(null)"

  looking at parent device '/devices/platform':
    KERNELS=="platform"
    SUBSYSTEMS==""
    DRIVERS==""

[Kai-Heng Feng (kaihengfeng)]

FWIW I just added your model string in drivers/input/mouse/lifebook.c, struct dmi_system_id lifebook_dmi_table[].

Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Input Devices

[Apicultor (apicultor)]

Which model string did you add? "FJC6001" for the touchpad, or the model string of the machine itself?

[Kai-Heng Feng (kaihengfeng)]

> On 22 Jan 2018, at 4:16 AM, Apicultor <email address hidden> wrote:
>
> Which model string did you add? "FJC6001" for the touchpad, or the model
> string of the machine itself?
The DMI string of the machine.

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1740116
>
> Title:
> Touchpad incorrectly being detected by kernel as PS/2 mouse
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> The touchpad in the Panasonic Toughbook CF-30 (specifically CF-30K,
> also known as "CF30", "CF30-3", "CF-30 Mk3", "CF-30 Mark 3", etc) is
> being detected as only a generic PS/2 mouse, not a touchpad of any
> kind.
>
> Pointing and clicking (also tapping to click) works, but scrolling
> doesn't work -- and there is no touchpad options in the relevant
> control panel, only pointer speed.
>
> This appears to be happening in the kernel, not in X.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: kernel-common (not installed)
> ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
> Uname: Linux 4.10.0-42-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2.14
> Architecture: amd64
> Date: Tue Dec 26 11:54:48 2017
> InstallationDate: Installed on 2017-12-17 (8 days ago)
> InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
> SourcePackage: kernel-package
> UpgradeStatus: No upgrade log present (probably fresh install)
> ---
> ApportVersion: 2.20.1-0ubuntu2.15
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: apicultor 2966 F.... pulseaudio
> CurrentDesktop: Unity
> DistroRelease: Ubuntu 16.04
> HibernationDevice: RESUME=UUID=d85b6945-0c3c-4696-b5c1-b2b010d524c8
> InstallationDate: Installed on 2017-12-17 (23 days ago)
> InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
> MachineType: Panasonic Corporation CF-30KAPAXAM
> Package: linux (not installed)
> PccardctlStatus:
> Socket 0:
> 5.0V
> 16-bit
> PC Card
> Subdevice 0 (function 0) bound to driver "serial_cs"
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
> RelatedPackageVersions:
> linux-restricted-modules-4.10.0-42-generic N/A
> linux-backports-modules-4.10.0-42-generic N/A
> linux-firmware 1.157.14
> Tags: xenial
> Uname: Linux 4.10.0-42-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 04/27/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: V3.00L19
> dmi.board.name: CF30-3
> dmi.board.vendor: Panasonic Corporation
> dmi.board.version: 1
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: Panasonic Corporation
> dmi.chassis.version: 001
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.00L19:bd04/27/2009:svnPanas...

[seba (5-admin-starepro-info)]

Hello
I have exactly same problem in Ubuntu 19.04 and Toughbook CF-19
5.0.0-16-generic
Because touchpad is detected as mouse i'm unable disable click while touching touchpad (i want use only hardware keys)
This is make so hard to use, slightly touch while moving finger cause text to be selected or item to be selected and moved... that make word processing or simple tasks very inefficient.

I know it's a Year old bug report, but maybe some updates?
Maybe some dirty fix?
just to disable clicking by touch of touchpad?

I would greatly appreciate fix.

Regards