Some missing Fn key scancodes on Sony Vaio VGN-CR120E

Bug #275267 reported by Walter_Wittel
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

May be related (or dupe) of: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/29987

I'm running the latest Intrepid (have been updating through several Alphas):
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux waltwld5 2.6.27-4-generic #1 SMP Wed Sep 24 01:29:06 UTC 2008 x86_64 GNU/Linux

The brightness Fn + F5 (with blue sun - symbol) and Fn + F6 (with blue sun + symbol) do not produce scancodes.

dmidecode info for the system per https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch is:
Sony Corporation
VGN-CR120E
C1018UFC

I am able to press the Fn <up arrow> (with blue PgUp) and get the following scancodes reported:
0xe0 0x49
0xe0 0xc9

However there is no output for the Fn+F5 or Fn+F6 combinations (and perhaps others). I also tried method 1 from the wiki article and got no response when pressing these combinations, and method 3 failed because I have no /var/log/acpid (maybe it is moved, however method 2 worked for the navigation Fn keys (after I replaced the showkey -u with showkey -s).

If more info is needed please give me some pointers to gather. Thanks!

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
Package: linux-image-2.6.27-4-generic 2.6.27-4.6 [modified: lib/modules/2.6.27-4-generic/modules.pcimap lib/modules/2.6.27-4-generic/modules.dep lib/modules/2.6.27-4-generic/modules.ieee1394map lib/modules/2.6.27-4-generic/modules.usbmap lib/modules/2.6.27-4-generic/modules.isapnpmap lib/modules/2.6.27-4-generic/modules.inputmap lib/modules/2.6.27-4-generic/modules.seriomap lib/modules/2.6.27-4-generic/modules.alias lib/modules/2.6.27-4-generic/modules.symbols]
ProcCmdLine: root=UUID=3e9f1a2d-7a95-40e7-b586-47223d2b574c ro quiet splash
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-4.6-generic
SourcePackage: linux

Revision history for this message
Walter_Wittel (wittelw) wrote :
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi Walter_Wittel,

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/karmic .

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 275267

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.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Walter_Wittel (wittelw) wrote :

These keys (Fn-F5 and Fn-F6) now control the brightness correctly on my Vaio VGN-CR120E when booted from the Karmic Alpha 4 LiveCD. I'll assume this means the fix is already upstream and won't attempt to test that kernel.

If there is a regression in subsequent milestones or when upgrading to the release I'll reactivate this bug.

Thanks for the fix!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the update. Marking this Fix Released for now based on the previous comment from Walter.

Indeed if this is already fixed in Ubuntu, should be fixed in upstream as well.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.