non-functioning hotkeys on Vaio TX2

I can confirm that but some more things are working.
Since Edgy the multimedia keys like Play/Pause, Stop, Previous and Next work out of the box at least in Kubuntu.
Since Feisty the eject button works too at least in Ubuntu but the other working multimedia keys are not set by default except the Play/Pause-Key which handles the Pause function (better would be the Play/Pause function). They could be easily configured but default like in Kubuntu would be better.
What is not working is the "AV MODE" button, the standard volume up and down keys which all three have the same keycode 159 according to xev.
Completly dead seems to be the crt and magnify key.
FN+F3 and FN+F4 are out of the box usable for volume up and down but it is not painted on the keys and doesn't work under Windows but it is not bad since this could replace the not working default volume keys.
The brightness keys and hibernate button works fine and according to xev the other marked FN keys worked too.
So the only problem are the "AV MODE", volume up, volume down, crt and magnify keys.

Multimedia keys are working fine out of the box in Gutsy but the buttons "AV MODE", volume up, volume down, crt and magnify keys are still not working.

AV Mode, volume up and volume down have the same keycode. I guess this is a kernel issue.

I'm retargeting this bug towards the upcoming Hardy kernel. I've tagged this as "hardy-kernel-candidate" so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

Current Hardy has still the same problem and there is a regression. The Sony Eject key which works since Feisty has no effect anymore. Should I make a new bug report for this?

I have made a new bug report #76924 for the eject issue so it doesn't get lost.

Hi unggnu,

Can you just give us a quick summary of which hotkeys and their corresponding key codes are still not working in Hardy. The following may also help: https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch . Also, can you attacht the following:

sudo dmidecode -s system-manufacturer
sudo dmidecode -s system-product-name
sudo dmidecode -s system-version

Thanks again and we appreciate your help and feedback.

AV MODE" volume up, volume down, crt and magnify keys are not working in Hardy and of course the eject button.
AV Mode, volume up and volume down have the same keycode (159). CRT, eject and magnify keys have no keycode at all.

sudo dmidecode -s system-manufacturer
Sony Corporation

sudo dmidecode -s system-product-name
VGN-TX2XP_B

sudo dmidecode -s system-version
J001BKAX

For the ones which don't generate key codes can you see if they generate ACPI events? (Method 3 of https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch) Thanks.

Yes, they do.
the magnify key:
[Sat Feb 2 12:50:48 2008] received event "sony/hotkey SPIC 00000001 00000015"
[Sat Feb 2 12:50:48 2008] notifying client 4983[0:0]
[Sat Feb 2 12:50:48 2008] notifying client 5253[108:116]
[Sat Feb 2 12:50:48 2008] completed event "sony/hotkey SPIC 00000001 00000015"
[Sat Feb 2 12:50:48 2008] received event "sony/hotkey SPIC 00000001 0000003b"
[Sat Feb 2 12:50:48 2008] notifying client 4983[0:0]
[Sat Feb 2 12:50:48 2008] notifying client 5253[108:116]
[Sat Feb 2 12:50:48 2008] completed event "sony/hotkey SPIC 00000001 0000003b"

the eject button:
[Sat Feb 2 12:52:31 2008] received event "sony/hotkey SPIC 00000001 0000001b"
[Sat Feb 2 12:52:31 2008] notifying client 4983[0:0]
[Sat Feb 2 12:52:31 2008] notifying client 5253[108:116]
[Sat Feb 2 12:52:31 2008] executing action "/etc/acpi/ejectbtn.sh"
[Sat Feb 2 12:52:31 2008] BEGIN HANDLER MESSAGES
[Sat Feb 2 12:52:31 2008] END HANDLER MESSAGES
[Sat Feb 2 12:52:31 2008] action exited with status 0
[Sat Feb 2 12:52:31 2008] completed event "sony/hotkey SPIC 00000001 0000001b"

the crt key:
[Sat Feb 2 12:52:02 2008] received event "sony/hotkey SPIC 00000001 00000012"
[Sat Feb 2 12:52:02 2008] notifying client 4983[0:0]
[Sat Feb 2 12:52:02 2008] notifying client 5253[108:116]
[Sat Feb 2 12:52:02 2008] completed event "sony/hotkey SPIC 00000001 00000012"
[Sat Feb 2 12:52:02 2008] received event "sony/hotkey SPIC 00000001 0000003b"
[Sat Feb 2 12:52:02 2008] notifying client 4983[0:0]
[Sat Feb 2 12:52:02 2008] notifying client 5253[108:116]
[Sat Feb 2 12:52:02 2008] completed event "sony/hotkey SPIC 00000001 0000003b"

Btw. the crt key problem is more a bug of the new Intel driver or acpi scripts I guess (Bug #133568)

Btw. ejecting under Gutsy works fine and gives me the follow acpi event:

[Sun Feb 10 12:02:16 2008] received event "sony/hotkey SPIC 00000001 0000001b"
[Sun Feb 10 12:02:16 2008] notifying client 5049[107:114]
[Sun Feb 10 12:02:16 2008] notifying client 5112[0:0]
[Sun Feb 10 12:02:16 2008] executing action "/etc/acpi/ejectbtn.sh"
[Sun Feb 10 12:02:16 2008] BEGIN HANDLER MESSAGES
[Sun Feb 10 12:02:16 2008] END HANDLER MESSAGES
[Sun Feb 10 12:02:16 2008] action exited with status 0
[Sun Feb 10 12:02:16 2008] completed event "sony/hotkey SPIC 00000001 0000001b"

Maybe it is just a device issue so the script isn't able to open it with Vanilla and Hardy kernel cd device path.

Hi everyone.

I've just bought a TX2HP vaio laptop and I'd like to install a minimalist debian on it.
But before, I wish to be sure the hotkeys will be functional.

I tried the live Hardy on it, but almost all the hotkeys aren't functional (eject i.e.).

Could you please tell me what's the status of this bug report ?

Thanks !

The status is the same. All keys work except the mentioned above. The bug report for the eject key is Bug #217504.

This is no duplicate of Bug #17365 since changing brightness works fine on Sony Vaio TX2.

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.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

The kernel only processes the events the upper levels tell it to do. The comments indicate that the events
are being generated/recoginzed by ACPI etc. in the kernel but there is nothing in userland to handle it properly.
Hotkeys is the place to start. Where these buttons go after that may affect other packages. The kernel was
not handling the key because there was no setkeycode done for it.

ACPI hotkey events are supposed to be mapped to input events by the kernel now. The userspace mapping of ACPI events to keypresses is defunct, because the kernel input layer now rejects events injected by the acpi_fakekey command. This is why the eject key stopped working, even though the key is known to acpi-support. Reassigning to the kernel for this.

The handler for this ACPI event should also be pulled from acpi-support, now that it's non-functional.

Can we get this tested and compared against Jaunty. The sony acpi driver got reworked by then to make use of the input framework to supply a proper input device for the hotkeys. This stopped working in Hardy as that still uses acpi_fakekey but the keyboard driver was modified in upstream to ignore key that the keyboard was not supposed to have. This had some influence on several of those laptop hotkeys.

Setting to incomplete while waiting for feedback.

The crt key works fine now but except of that nothing has changed at least with the Jaunty Live CD.

So the problems are the "AV MODE", volume up, volume down, magnify and eject keys.

First three most likely because there is no kernel support for them. They are completely dead.

unggnu,

Just to confirm that this is indeed a kernel problem (since the kernel team seems to think this should be implemented already), could you please step through steps 5-12 in https://wiki.ubuntu.com/Hotkeys/Troubleshooting? This will show us whether the kernel is generating events for each of these keys. If no events are generated, could you also run 'dmesg > dmesg.log' and attach the resulting dmesg.log file?

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

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

  [ Steve Langasek ]
  * Drop events/sony-eject, confirmed in bug reports to no longer work due
    to its use of acpi_fakekey. This needs to be implemented in the kernel
    input layer, but in the meantime there's no reason to keep this here.
    LP: #76924.
  * Drop events/panasonic-{hibernatebtn,sleepbtn}, also reported to not work
    now due to the acpi_fakekey implementation.

  [ Michael Terry ]
  * debian/copyright: Convert to DEP5 format
  * ac.d, battery.d, power.sh, debian/init.d, debian/rules:
    - Don't install power hook directories, instead just call pm-powersave
  * debian/preinst:
    - Remove ac.d and battery.d conffiles

 -- Steve Langasek <email address hidden> Fri, 26 Jun 2009 15:41:38 -0700

Anything new on this?

The eject key still doesn't work again in current Karmic.
Besides of this there is only one change. The original volume up and down keys have a different keycode but instead of the correct function they have the XF86Launch1 and 2 one.

The magnifier key is still dead and the AV button still has the same keycode as one of the original volume keys.

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.