[Fujitsu Amilo] Synaptics touchpad ceases functioning after suspend and resume

[Philipp Wendler]

I'm opening a new bug for bug 59867 as that one was closed, but the problem still exists in Natty.

I have a Fujitsu Amilo Pro V3205 with a synaptics touchpad, which does not work after I got to suspend and resume. A reboot is needed to get it working again.

WORKAROUND: If I add "atkbd.reset" to the kernel commandline, it works.

There are several other reports in the comments of the old bug.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: philipp 1700 F.... pulseaudio
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), DFS
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xdc240000 irq 44'
   Mixer name : 'Conexant CX20549 (Venice)'
   Components : 'HDA:14f15045,173410ad,00100100'
   Controls : 20
   Simple ctrls : 9
Date: Thu Jul 14 10:38:09 2011
HibernationDevice: RESUME=LABEL=Swap
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU SIEMENS AMILO Pro V3205
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=/dev/mapper/nb--username-root ro quiet splash atkbd.reset vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.52
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-06-17 (26 days ago)
WpaSupplicantLog:

dmi.bios.date: 02/14/2007
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.20
dmi.board.name: 10AD
dmi.board.vendor: FUJITSU
dmi.board.version: 03
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr1.20:bd02/14/2007:svnFUJITSUSIEMENS:pnAMILOProV3205:pvrREV1:rvnFUJITSU:rn10AD:rvr03:cvnFUJITSUSIEMENS:ct10:cvrN/A:
dmi.product.name: AMILO Pro V3205
dmi.product.version: REV1
dmi.sys.vendor: FUJITSU SIEMENS

[Bryce Nesbitt (bryce2)]

See also
https://help.ubuntu.com/community/SynapticsTouchpad#Touchpad not working after login

[Jamie Lokier (jamie-shareable)]

I have the same issue on a Fujitsu-Siemens Amilo Si-1520, which is the same motherboard as V3205. Running Ubuntu Natty, touchpad doesn't respond after resume.

I can confirm that adding atkbd.reset=1 to the boot kernel command line fixes it for me too.
I'm using a kernel.org vanilla kernel, 2.6.39-rc7-00211-gc1d10d1.
(I was quite surprised that I couldn't find anywhere else to set the flag other than the boot command line, so I had to reboot to find out. Is this not one of the purposes of sysfs?)

It is reported elsewhere that downgrading the BIOS version to 1.10 also fixes the problem of touchpad unavailable after resume, however that isn't an option if using certain newer CPUs on these laptops, the manufacturer claims that Vista requires a later BIOS, and (worst of all) searching for the BIOS upgrade on the manufacturer's support site reveals a program that only runs on Windows Vista.

I did not have this problem for several years, but a couple of days ago I replaced the motherboard due to a broken power connector, and then I noticed touchpad not working after resume. It seems very likely this is because the replacement had a newer BIOS.

[Jamie Lokier (jamie-shareable)]

And thank you to Philipp Wendler for mentioning that atkbd.reset fixes it, so that I was able to solve it on mine! Otherwise I would have been rather dismayed and wondered if the new motherboard was faulty.

[Jonathan Davies (jpds)]

This bug is also present on a Dell Vostro V13 running Natty.

[Andy Whitcroft (apw)]

Ok it may be possible to quirk this keybaord reset from the kernel automatically. For those who are able to reproduce this on Natty could you test the kernels below and report back here. Please remember to remove any GRUB modifications to turn on the atkbd.reset flag. Please indicate whether this kernel works for you and please include a dmesg command output from a boot in your report with this kernel whether it works or not. Test kernels are at the URL below:

    http://people.canonical.com/~apw/lp810327-natty/

Thanks.

[Philipp Wendler (philw85)]

The test kernel from linux-image-2.6.38-11-generic_2.6.38-11.49~lp810327v201108091824_i386.deb works on my Amilo Pro V3205 and fixes the problem.

Thanks very much for solving it, even after so long time (the original bug report stated it was present at least since Dapper)! Hope it will make it into the Ubuntu kernels.

[Andy Whitcroft (apw)]

@Philipp -- could you include the output of the command "dmesg" from the machine when booted with the test kernel. That has diagnostics to confirm the patch is working in the intended way; as it could affect quirking for key release and I do not have any of the affected h/w to confirm.

[Philipp Wendler (philw85)]

Here is the dmesg output for booting the kernel and going to hibernate (STD) because that's what I can provide without rebooting. If you need the output of just a single boot or perhaps including a standby, I could also produce that.

[Daniel Manrique (roadmr)]

Hi,

I have here 3 Dell Vostro V13s on which I was able to reproduce the original problem, by suspending them and upon resume, the mouse pointer would not work.

My workaround was to rmmod psmouse and then modprobe psmouse, this reenables the mouse functionality.

Of note, David Bensimon tried reproducing this problem on Lucid (10.04) with the 2.6.32 kernel and was unable to recreate this issue. However, I got hit by it under both Natty (2.6.38-11 from proposed and the original 2.6.38-8 kernel from Natty release) and Oneiric (3.0.0-7.9).

I also have a Dell Latitude 13, it's almost 100% identical to the Vostros, and also reports a Synaptics touchpad, but this one seems unaffected by the problem, I can suspend/resume and the pad keeps working. David suspects the BIOS revision might also be a factor in whether the touchpad restores correctly or not.

On my test systems the patched kernel (Linux version 2.6.38-11-generic (root@gomeisa) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) ) #49~lp810327v201108091824 SMP Tue Aug 9 17:25:25 UTC 2011) does NOT reenable the mouse after resuming.

I'll attach dmesg from both Vostro V13s to see if any useful information comes up.

Andy, these machines live for testing so if you need either me or David to run tests or provide hardware and/or debugging information, please don't hesitate to ask. We can install and test anything you need.

Also, if a separate bug would be better for the Dell Vostros, let me know so I can file accordingly.

Thanks!

[Daniel Manrique (roadmr)]

Retested and confirmed to be happening with Oneiric, on kernel 3.0.0-11.18.

[David Wonderly (david.wonderly)]

I also have a Dell Vostro V13 and am dealing with this issue. I have found a decent workaround for it though.

What you want to do is make a script that will execute on resume.

Have a look at folder /etc/pm/sleep.d/ - all scripts within this folder are automatically run as root-user after/before suspend or hibernate.

The script needs to fit this example:

#!/bin/bash
case "$1" in
    hibernate|suspend)
        ACTION BEFORE SUSPEND/HIBERNATE
        ;;
    thaw|resume)
        ACTION AFTER RESUME
        ;;
    *)
        ;;
esac
exit $?

I had already made this script as ps.sh:

#!/bin/bash
rmmod psmouse
modprobe psmouse

So, I just tossed the two together and this is how it works:

sudo touch /etc/pm/sleep.de/99-touchpad-restart.sh
sudo chmod +x /etc/pm/sleep.de/99-touchpad-restart.sh
sudo nano /etc/pm/sleep.de/99-touchpad-restart.sh

#!/bin/bash
case "$1" in
    thaw|resume)
        /home/darkwingduck/ps.sh>/dev/null
        ;;
    *)
        ;;
esac
exit $?

Works like a charm. I know it's not a perm fix, but it works.

[Torsten Casselt (blu2lz)]

Confirmed with Kubuntu 11.10 on PackardBell EasyNote TK85 with kernel 3.0.0.13.
Both workarounds work.

[David Wonderly (david.wonderly)]

Wanted to note, with 12.04 daily and the kernel updates (Or, what ever update was added...) This issue is fixed. aaaaand there was much rejoicing!

Cheers!

[Torsten Casselt (blu2lz)]

Also fixed on PackardBell EasyNote TK85 with kernel 3.2.0.24. Thank you!