Ubuntu
linux package

ASUS F8SV: touchpad hotkey not handled

Bug #218598 reported by dl.zerocool on 2008-04-17

Affects		Status	Importance	Assigned to	Milestone
	acpi-support (Ubuntu)	Fix Released	Medium	Unassigned
	linux (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

Binary package hint: acpi

Hello,
Actually there is only one way to turn off the touchpad is by manualy turn it off in Bios.

Here is details:
ASUSTeK Computer Inc.
F8SV
1.0

Here is the result of tail -f /var/log/acpid
[Thu Apr 17 12:32:39 2008] received event "hotkey ATKD 0000008a 00000001"
[Thu Apr 17 12:32:39 2008] notifying client 5408[107:116]
[Thu Apr 17 12:32:39 2008] notifying client 5735[0:0]
[Thu Apr 17 12:32:39 2008] notifying client 5735[0:0]
[Thu Apr 17 12:32:39 2008] completed event "hotkey ATKD 0000008a 00000001"

The hotkey is actually supposed to turn off/on the touchpad.

The other hotkey (a little man running, sorry I didn't find any description for what is it...)
Here is the result of tail -f /var/log/acpid
[Thu Apr 17 12:46:56 2008] received event "hotkey ATKD 0000005c 00000001"
[Thu Apr 17 12:46:56 2008] notifying client 5408[107:116]
[Thu Apr 17 12:46:56 2008] notifying client 5735[0:0]
[Thu Apr 17 12:46:56 2008] notifying client 5735[0:0]
[Thu Apr 17 12:46:56 2008] executing action "/etc/acpi/lockbtn.sh"
[Thu Apr 17 12:46:56 2008] BEGIN HANDLER MESSAGES
[Thu Apr 17 12:46:56 2008] END HANDLER MESSAGES
[Thu Apr 17 12:46:56 2008] action exited with status 0
[Thu Apr 17 12:46:56 2008] completed event "hotkey ATKD 0000005c 00000001"

I didn't really know what the lockbtn.sh does
It apparently just do nothing " Fake Key".

Well I really hope someone can help me to add the hotkey for to turn on/off touchpad
Because it's a really anoying thing.

Related branches

lp://staging/acpi-support

lp://staging/ubuntu/lucid/acpi-support

Revision history for this message

dl.zerocool (dl.zerocool) wrote on 2008-04-18:

There is nobody who can help me ?

Revision history for this message

Daniel T Chen (crimsun) wrote on 2008-12-13:

Is this symptom still reproducible in 8.10 or 9.04?

Changed in acpi:
status:	New → Incomplete

Revision history for this message

Martin Pitt (pitti) wrote on 2009-02-10:

ACPI event, needs to be handled in acpi-support.

Steve Langasek (vorlon) on 2009-10-06

Changed in acpi-support (Ubuntu):
importance:	Undecided → Medium
status:	Incomplete → Triaged
summary:	- Hotkeys touchpad on/off : + ASUS F8SV: touchpad hotkey not handled

Revision history for this message

dl.zerocool (dl.zerocool) wrote on 2009-10-06:

Yes symptom is reproductible on 8.10 9.04 and even 9.10

Revision history for this message

Steve Langasek (vorlon) wrote on 2009-10-12:

There are two bugs here, for two separate hotkeys; one is an acpi-support bug, the other is a kernel bug.

[Thu Apr 17 12:46:56 2008] received event "hotkey ATKD 0000005c 00000001"
[Thu Apr 17 12:46:56 2008] notifying client 5408[107:116]
[Thu Apr 17 12:46:56 2008] notifying client 5735[0:0]
[Thu Apr 17 12:46:56 2008] notifying client 5735[0:0]
[Thu Apr 17 12:46:56 2008] executing action "/etc/acpi/lockbtn.sh"
[Thu Apr 17 12:46:56 2008] BEGIN HANDLER MESSAGES
[Thu Apr 17 12:46:56 2008] END HANDLER MESSAGES
[Thu Apr 17 12:46:56 2008] action exited with status 0
[Thu Apr 17 12:46:56 2008] completed event "hotkey ATKD 0000005c 00000001"

lockbtn.sh doesn't work any more because it depends on acpi_fakekey. This needs to be handled in the kernel.

[Thu Apr 17 12:32:39 2008] received event "hotkey ATKD 0000008a 00000001"
[Thu Apr 17 12:32:39 2008] notifying client 5408[107:116]
[Thu Apr 17 12:32:39 2008] notifying client 5735[0:0]
[Thu Apr 17 12:32:39 2008] notifying client 5735[0:0]
[Thu Apr 17 12:32:39 2008] completed event "hotkey ATKD 0000008a 00000001"

This needs to be implemented in acpi-support (at least, as long as we're still using acpi-support for this).

Steve Langasek (vorlon) on 2009-10-12

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	New → Triaged

Steve Langasek (vorlon) on 2009-10-12

Changed in acpi-support (Ubuntu):
status:	Triaged → Fix Committed

Revision history for this message

dl.zerocool (dl.zerocool) wrote on 2009-10-12:

thanks for the fixes

Revision history for this message

Launchpad Janitor (janitor) wrote on 2009-10-13:

This bug was fixed in the package acpi-support - 0.128

---------------
acpi-support (0.128) karmic; urgency=low

  [ Steve Langasek ]
  * Get laptop-mode-tools out of Suggests. Finally-really-fixes LP: #74683.
  * Fix the touchpad handler to use xinput instead of (unreliable)
    synclient, and add a corresponding Recommends; and call getXconsole so
    we can actually talk to the X server. LP: #447211.
  * new events/asus-f8sv-touchpad: handle another touchpad ACPI event on
    another ASUS model. LP: #218598.
  * lib/power-funcs: adjust getXconsole to work when the tty number is not
    present on the X commandline.

  [ Felix Geyer ]
  * lib/policy-funcs: Recognize KDE4 PowerDevil as a power manager.
    LP: #387750.

-- Steve Langasek <email address hidden> Mon, 12 Oct 2009 16:49:00 -0700

Changed in acpi-support (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

dl.zerocool (dl.zerocool) wrote on 2009-10-23:

Excellent it work properly thank you a lot !

Revision history for this message

Erik Andrén (erik-andren) wrote on 2010-01-03:

acpi-support_0.131ubuntu2_i386.deb Edit (33.6 KiB, application/x-debian-package)

Bonsai,
The attached debian package merges the support for your machine with all other asus laptops.
It would be great if you could download attached file and install it with dpkg -i <file> and verify that you still can disable the touchpad via the hotkey.

Revision history for this message

dl.zerocool (dl.zerocool) wrote on 2010-01-03:

#10

I would like to help you, but I'm under a 64bit version.
So I cannot install it and I doubt it's the same acpi for 64bit.

Revision history for this message

penalvch (penalvch) wrote on 2013-11-23:

#11

dl.zerocool, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.