Special Laptop Keys don't work anymore (Toshiba M200)

Bug #210222 reported by Vince
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned
Nominated for Lucid by Tyrael
Nominated for Maverick by Tyrael

Bug Description

Most special Keys of my laptop don't work anymore since I switched to hardy (Clean install) (All of these worked previously)

What works:
Fn-F3 : Suspend to RAM
Fn-F4 : Suspend to Disk
Fn-F6 : Brightness +
Fn-F7 : Brightness -
Numlock and stuff

What doesn't work
Fn-F1 : Lock the computer
This has no effect in "xev", I'm not sure whether that's relevant
Fn-F5 : Switch Display
xev output
[code]
KeymapNotify event, serial 27, synthetic NO, window 0x0,
    keys: 4294967239 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[/code]
Fn-F2 : Power State : Used to display a notification bubble about the powersource
Nothing in Xev either

I don't see anything relevant in dmesg

[code]
~$ lsb_release -rd
Description: Ubuntu hardy (development branch)
Release: 8.04
[/code]

[code]
~$ dmesg | grep toshiba_acpi
[ 57.883432] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19a-dev
[ 57.883437] toshiba_acpi: HCI method: \_SB_.VALZ.GHCI
[ 57.883816] toshiba_acpi: Toshiba hotkeys are sent as ACPI events
[ 57.883819] toshiba_acpi: ktoshkeyd will check 2 times per second
[ 57.884152] toshiba_acpi: Dropped 0 keys from the queue on startup
[/code]

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

Thank you for reporting this issue.

For completenesses sake, could you please post the output of dmesg while you are pressing those keys?

Also, please perform method 2 from this page: https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

Thanks!

Revision history for this message
Vince (v-brz) wrote :
Download full text (4.3 KiB)

---Lock Screen---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 10 sec)...
Nothing (except return key release which I deleted)

---Battery State---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 2 sec)...
Nothing

---Suspend to RAM---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 2 sec)...
0xe0 0x5f 0xe0 0xdf

---Suspend to DISK---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 2 sec)...
Nothing

---Change Screen---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 2 sec)...
0xe0 0x56 0xe0 0xd6

---Brighness down---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 2 sec)...
Nothing

---Brighness up---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 2 sec)...
Nothing

---Wireless select---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 2 sec)...
Nothing

---Touchpad on/off---
Appuyez sur une touche (le programme s'arrêtera ensuite au bout de 2 sec)...
Nothing

As for 'ACPI keys', here they are

---Lock Screen---
[Wed Apr 9 17:17:32 2008] received event "hkey VALZ 00000001 0000013b"
[Wed Apr 9 17:17:32 2008] notifying client 5745[110:122]
[Wed Apr 9 17:17:32 2008] notifying client 5929[0:0]
[Wed Apr 9 17:17:32 2008] notifying client 5929[0:0]
[Wed Apr 9 17:17:32 2008] executing action "/etc/acpi/lockbtn.sh"
[Wed Apr 9 17:17:32 2008] BEGIN HANDLER MESSAGES
[Wed Apr 9 17:17:32 2008] END HANDLER MESSAGES
[Wed Apr 9 17:17:32 2008] action exited with status 0
[Wed Apr 9 17:17:32 2008] completed event "hkey VALZ 00000001 0000013b"

---Battery State---
[Wed Apr 9 17:17:52 2008] received event "hkey VALZ 00000001 0000013c"
[Wed Apr 9 17:17:52 2008] notifying client 5745[110:122]
[Wed Apr 9 17:17:52 2008] notifying client 5929[0:0]
[Wed Apr 9 17:17:52 2008] notifying client 5929[0:0]
[Wed Apr 9 17:17:52 2008] executing action "/etc/acpi/batterybtn.sh"
[Wed Apr 9 17:17:52 2008] BEGIN HANDLER MESSAGES
[Wed Apr 9 17:17:52 2008] END HANDLER MESSAGES
[Wed Apr 9 17:17:52 2008] action exited with status 0
[Wed Apr 9 17:17:52 2008] completed event "hkey VALZ 00000001 0000013c"

---Switch Screen---
[Wed Apr 9 17:18:09 2008] received event "video VGA 00000080 00000000"
[Wed Apr 9 17:18:09 2008] notifying client 5745[110:122]
[Wed Apr 9 17:18:09 2008] notifying client 5929[0:0]
[Wed Apr 9 17:18:09 2008] notifying client 5929[0:0]
[Wed Apr 9 17:18:09 2008] executing action "/etc/acpi/videobtn.sh"
[Wed Apr 9 17:18:09 2008] BEGIN HANDLER MESSAGES
[Wed Apr 9 17:18:09 2008] END HANDLER MESSAGES
[Wed Apr 9 17:18:09 2008] action exited with status 0
[Wed Apr 9 17:18:09 2008] completed event "video VGA 00000080 00000000"
[Wed Apr 9 17:18:09 2008] received event "hkey VALZ 00000000 0000013f"
[Wed Apr 9 17:18:09 2008] notifying client 5745[110:122]
[Wed Apr 9 17:18:09 2008] notifying client 5929[0:0]
[Wed Apr 9 17:18:09 2008] notifying client 5929[0:0]
[Wed Apr 9 17:18:09 2008] completed event "hkey VALZ 00000000 0000013f"
[Wed Apr 9 17:18:09 2008] received event "hkey VALZ 00000001 0000013f"
[Wed Apr 9 17:18:09 2008] notifying client 5745[110:122]
[Wed Apr 9 17:18:09 2008] notify...

Read more...

Revision history for this message
Vince (v-brz) wrote :

and dmesg gives not special output for any of those which don't work.

Changed in linux:
importance: Undecided → Low
status: Incomplete → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
David Sterratt (david-c-sterratt) wrote :

I can report that this is still an issue with intrepid ibex. I particularly would like the hotkey for switching screens to work. It looks like it should be fairly straightforward. It is a question of creating scripts in /etc/acpi and registering the key codes in /etc/acpi/events. See the examples at:
http://www.thinkwiki.org/wiki/Xorg_RandR_1.2
http://www.thinkwiki.org/wiki/Sample_Fn-F7_script

Revision history for this message
David Sterratt (david-c-sterratt) wrote :

P.S. I think this bug really belongs to acpi-support, as that is the package that supplies the existing tosh helper scripts.

Revision history for this message
David Sterratt (david-c-sterratt) wrote :

P.P.S. An invocation of sudo toshset -video both may be necessary in the script... Hmmm... come to think of it, the need to sudo may be why the script doesn't exist... Perhaps there is a way of achieving the same effect by writing to the /proc filesystem (see e.g. the tosh brightness scripts).

Revision history for this message
RivalComp (rival) wrote :

I think it's the same issue as reported in #128320.
https://bugs.launchpad.net/bugs/128320

Revision history for this message
Shang Wu (shangwu) wrote :

Has any of you guys tried the article here yet?

https://help.ubuntu.com/community/LaptopSpecialKeys

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Please test the steps lined out in https://wiki.ubuntu.com/Hotkeys/Troubleshooting against a lucid live CD and report your findings.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Tyrael (marco-crociani) wrote :

I tested the steps lined out in https://wiki.ubuntu.com/Hotkeys/Troubleshooting with my current Lucid installation (beta2 with updates at 18 April 2010).

The result is that there are ACPI event but not keypress.

Only Fn-F8, Wifi-Bluetooth switch, is working.

Revision history for this message
Tyrael (marco-crociani) wrote :

I tested recent kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/

WIth 2.6.33-020633-generic same as 2.6.32.

With 2.6.34-020634rc4-generic special laptop keys are working. Fn-F6 : Brightness + Fn-F7 : Brightness - bring up the notification on the desktop but the brightness doesn't change.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Tyrael (marco-crociani)
tags: added: lucid regression-potential
Gary M (garym)
tags: added: hw-specific
Gary M (garym)
tags: added: regression-release
removed: regression-potential
Revision history for this message
Tyrael (marco-crociani) wrote :

with linux-image-2.6.35-996-generic_2.6.35-996.201007131224_i386.deb (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/current/)
special laptop keys are working. Fn-F6 : Brightness + Fn-F7 : Brightness - bring up the notification on the desktop but the brightness doesn't change. Fn-F1 locks screen.

Revision history for this message
Tyrael (marco-crociani) wrote :

Tested with Maverick Alpha 3 updated today (20100817)
$ uname -a
Linux toshinux 2.6.35-15-generic #21-Ubuntu SMP Wed Aug 11 16:41:40 UTC 2010 i686 GNU/Linux

Some special laptop keys are working: Fn-F1 locks screen, Fn-Esc toggle volume...
but "Fn-F6 : Brightness" and "Fn-F7 : Brightness -" DON'T bring up the notification on the desktop and DON'T change brightness.

I also tested with fwts (log attacched) and the brightness changed with the tests that automatically change brightness (but not when you press the keys).

tags: added: maverick
Revision history for this message
penalvch (penalvch) wrote :

Vince, 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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

tags: added: needs-upstream-testing
tags: added: hardy
removed: lucid maverick
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Gary M (garym)
tags: added: lucid maverick
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.