Bug 105231 - FocalTech touchpad stops working after suspend
Summary: FocalTech touchpad stops working after suspend
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-29 11:09 UTC by Thatoo
Modified: 2017-01-22 15:42 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.1.6
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Thatoo 2015-09-29 11:09:19 UTC
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 noticed one problem. The Focaltech touchpad is not working after suspending the comnputer.

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

I can deactivate and activate again the touchpad with the hotkey of my keyboard without problem.

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

Now, the computer refuse to suspen. At least, the touchpad keep working so it does something but I can't make my conputer sleeping...
Comment 1 Marcos Souza 2016-10-19 23:56:46 UTC
(In reply to Thatoo from comment #0)
> 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 noticed one problem. The Focaltech touchpad is not working after
> suspending the comnputer.
> 
> 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
> 
> I can deactivate and activate again the touchpad with the hotkey of my
> keyboard without problem.
> 
> 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
> 
> Now, the computer refuse to suspen. At least, the touchpad keep working so
> it does something but I can't make my conputer sleeping...

Hi,

can you please check if this patch solves this problem for you?
https://bugzilla.kernel.org/attachment.cgi?id=242001
(This patch is based on kernel 4.9-rc1.)

If this doesn't work, maybe you should take a look in this patch (which is already in linux 4.9-rc1) and just change one of the model entries and add V502LX:
https://git.kernel.org/cgit/linux/kernel/git/dtor/input.git/commit/?id=930e19248e9b61da36c967687ca79c4d5f977919

Also, do you mind sending the output of the command:
dmidecode --type chassis
?

The output is very similar to this:
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Type: Notebook
	Lock: Not Present
	Version: 1.0       
	Serial Number: E6N0B2019875248     
	Asset Tag: No Asset Tag    
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: To be filled by O.E.M.

The first patch is based on the premise that we skip selftest in all asus notebooks, so your dmi data will certify your case is covered by this fix.

Waiting for your response!
Comment 2 Marcos Souza 2017-01-22 15:42:52 UTC
This fix was already merged into mainline by [1] and this bug is an duplicated one from this one [2].

Thanks for the report!

[1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=77b425399f6d5f1b04c58738bc10ca6decb10c9a
[2] https://bugzilla.kernel.org/show_bug.cgi?id=107971

Note You need to log in before you can comment on or make changes to this bug.