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"
H: Handlers=mouse0 event4
B: KEY=e520 10000 0 0 0 0
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
case "$1" in
modprobe -r psmouse;
Now, the computer refuse to suspen. At least, the touchpad keep working so it does something but I can't make my conputer sleeping...
(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
> case "$1" in
> modprobe -r psmouse;
> modprobe psmouse;
> Now, the computer refuse to suspen. At least, the touchpad keep working so
> it does something but I can't make my conputer sleeping...
can you please check if this patch solves this problem for you?
(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:
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
Manufacturer: ASUSTeK COMPUTER INC.
Lock: Not Present
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
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!
This fix was already merged into mainline by  and this bug is an duplicated one from this one .
Thanks for the report!