kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #140025
[Bug 1504445] Re: FocalTech touchpad stops working after suspend
So I'm now writing to you with kernel-upstream-4.3.0-040300rc5 installed
and the Focaltech driver uninstall as requested.
My computer boot almost normaly, just a small error display, "Error
parsing PCC subspaces from PCCT” I think because of a conflict between
the new kernel and the nvidia driver. It just slow down a little bit the
boot time.
Everything works as usual. As it was the case when I tested the kernel
4.1.6, the touchpad is recognised and work without the need of any
additional driver.
However, the problem is still on. After I close the lid of my computer
or click on the button to suspend its activity, after awaking,
everything seems to work except the touchpad. The keyboard works, the
wifi reconnect but the touchpad is blocked. I have to restart to get it
working again.
I hope that was the test you wanted me to do. Should I restart under
kernel 3.19.30? and should I delete the kernel 4.3.0-rc5? or should I
keep it like that for now?
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.3.0-040300rc5
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1504445
Title:
FocalTech touchpad stops working after suspend
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have an Asus V502LX the persian version of the Asus K501LX.
I have Ubuntu 14.04 installed and the kernel 4.1.6 installed. I had to
install the kernel 4.1.6 to have the touchpad recognised. Under kernel
3.19.30, as I am running now to file in this bug, the touchpad is
recognised as a simple mouse (no two fingers scrolling...) and the
problem I am describing below is also present...
I noticed one problem. The Focaltech touchpad is not working after
suspending the computer.
Here is what I could find about the touchpad in
/proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0012 Version=0000
N: Name="FocalTechPS/2 FocalTech FocalTech Touchpad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse0 event4
B: PROP=5
B: EV=b
B: KEY=e520 10000 0 0 0 0
B: ABS=260800000000003
Before suspending the computer, I can deactivate and activate again
the touchpad with the hotkey of my keyboard without problem. However,
once the computer suspended, nothing work to re-activate the touchpad.
I tried a solution given on internet but it doesn't work properly.
I created a file here /etc/pm/sleep.d/0000trackpad
sudo gedit /etc/pm/sleep.d/0000trackpad
and add the following
#!/bin/sh
case "$1" in
suspend|hibernate)
modprobe -r psmouse;
resume|thaw)
modprobe psmouse;
esac
With this file, the computer refuse to suspend. The touchpad keep
working so it does something but I can't make my computer sleeping...
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 9 12:05:16 2015
InstallationDate: Installed on 2015-09-26 (12 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: yogo 2073 F.... pulseaudio
/dev/snd/controlC0: yogo 2073 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=943b03af-c1bf-489e-8e42-485931fc619c
InstallationDate: Installed on 2015-09-26 (12 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. K501LX
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=37bd087e-a2f6-437e-8d20-b19536eb738a ro quiet splash acpi_osi= vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
RelatedPackageVersions:
linux-restricted-modules-3.19.0-30-generic N/A
linux-backports-modules-3.19.0-30-generic N/A
linux-firmware 1.127.15
Tags: trusty
Uname: Linux 3.19.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/16/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K501LX.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K501LX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK501LX.203:bd04/16/2015:svnASUSTeKCOMPUTERINC.:pnK501LX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501LX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K501LX
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504445/+subscriptions
References