FN-Keys not working on Sony Vaio VGN-S3HP

[Maulwurf]

Binary package hint: udev

fn keys for sound and brightness don't work.
fn keys for pageup/down, pos1, end, break, roll do work.

I followed /usr/share/doc/udev/README.keymap.txt

 /lib/udev/findkeyboards
AT keyboard: input/event3
module: input/event7

I was not able to get a scan code for the mentioned keys using
 sudo /lib/udev/keymap -i input/event3 or
 sudo /lib/udev/keymap -i input/event7

cat /sys/class/dmi/id/sys_vendor
Sony Corporation
cat /sys/class/dmi/id/product_name
VGN-S3HP

further information:
karmic koala running from live cd.
Description: Ubuntu 9.10
Release: 9.10

udev: 147~-6

[Martin Pitt (pitti)]

> I was not able to get a scan code for the mentioned keys

That means that nothing happened when you pressed those keys? Or it said something weird?

On other Sony models that I saw, the "Sony Vaio Keys" module had all the Fn keys.

I looked through your udev dump, and there is also an input device called ""Sony Vaio Jogdial". Can you try whether you get the scan codes on input/event8? (Hint: "sudo lsinput" gives you a mapping from input device number to name, just in case the enumeration is different after a reboot)

[Maulwurf (w-launchpad-raimund-hofmann-de-deactivatedaccount)]

> That means that nothing happened when you pressed those keys? Or it said something weird?

right, absolutely nothing happened. no hex code and no movement on the shell.

I found out, the two s-keys, S1 and S2, are located on input/event7 (Sony Vaio Keys) which work without pressing fn:

scan code: 0x00 key code: prog1
scan code: 0x20 key code: prog2

on input/event8 (Sony Vaio Jogdial) nothing happened.

the weird thing is, the fn keys for volume and brightness stopped working with ubuntu 9.04. ubuntu 8.10 is still ok.

i now tested input numbers 0 to 9 but no code for volume or brightness.

[Martin Pitt (pitti)]

Can you please try "sudo acpi_listen" and check whether you get any events there if you press the sound/brightness keys? Please copy&paste the output. Thanks!

[Maulwurf (w-launchpad-raimund-hofmann-de-deactivatedaccount)]

sorry, no output at all.
The S1 and S2 buttons produce

sony/hotky SPIC 00000001 00000020
sony/hotky SPIC 00000001 00000021

none of the missing FN keys produce any output.(they are on F2 ... F6)
the functioning fn combos produce:
fn-pos1: (arrow left)
^[0H

fn-end: (arrow right)
^[0F

fn-pageup:(arrow up)
^[[5~

fn-pagedown:(arrow down)
^[[6~

[Martin Pitt (pitti)]

If they produce no input nor ACPI events, this needs to be fixed in the kernel. Reassigning.

[Jeremy Foshee (jeremyfoshee)]

Hi Maulwurf,

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 from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 473328

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 . 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]