Sony VGN-FZ21M, some hotkeys not working (video/graphics related)

[Panagiotis Mirmigkis]

This report is about the Sony Vaio VGN-FZ21M. It is about which hotkeys work and which are not.

I have a problem with the connection to external monitor. The Fn key (to change monitor display doesn't work, Fn keys are working are for sound and HD snooze). When I connect my laptop in my TV with HDMI, TV says "No Singal". The HDMI input working fine because I have my XBOX360 connected. Also brightness function keys not working.

1. Fn+F5, reduces the brightness of the screen [NOT WORKING]
scan code: 0x10 key code: brightnessdown

2. Fn+F6, increase the brightness of the screen [NOT WORKING]
scan code: 0x11 key code: brightnessup

3. Fn+F7, switch video mode [NOT WORKING]
scan code: 0x12 key code: switchvideomode

4. Fn+F10, zoom in to cursor [NOT WORKING]
scan code: 0x15 key code: zoom

5. Fn+F12, suspend the pc [WORKING]
scan code: 0x17 key code: suspend

Fn+NumLk (ScrLk) not working either, but does not produce a scancode/keycode
Fn+Insert (Pause) not working either, but does not produce a scancode/keycode
Fn+Delete (Break) not working either, but does not produce a scancode/keycode

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: udev 175-0ubuntu9.1
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27
Uname: Linux 3.2.0-30-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
Date: Sat Sep 8 21:47:30 2012
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MachineType: Sony Corporation VGN-FZ21M
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-30-generic-pae root=UUID=3ac24008-bee2-41f4-bc6e-6116c88fdfe0 ro quiet splash vt.handoff=7
SourcePackage: udev
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R1120J7
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR1120J7:bd07/04/2007:svnSonyCorporation:pnVGN-FZ21M:pvrC3LQ2V5W:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FZ21M
dmi.product.version: C3LQ2V5W
dmi.sys.vendor: Sony Corporation

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

nobody knows?

[Martin Pitt (pitti)]

Please follow the "fixing broken keys" section in /usr/share/doc/udev/README.keymap.txt.gz to find out the broken scan codes and what their function should be. Thanks!

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

Thanks for answering Martin Pitt. I am newbie so if you want, i would appreciate to tell me what exactly should I do! :)

[Simos Xenitellis  (simosx)]

We discuss this issue at http://forum.ubuntu-gr.org/viewtopic.php?f=37&t=24538
Panagiotis, try out the instructions at /usr/share/doc/udev/README.keymap.txt.gz and as soon as you get stuck, ask a question on the specific issue you got stuck at, at the forum.

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

I have scan the broken keys.

scan code: 0x10 key code: brightnessdown
scan code: 0x11 key code: brightnessup
scan code: 0x12 key code: switchvideomode

But I dont understand what should I do after that.........

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

scan code: 0x10 key code: brightnessdown Fn+F5 not working
scan code: 0x11 key code: brightnessup Fn+F6 not working
scan code: 0x12 key code: switchvideomode Fn+F7 not working
scan code: 0x15 key code: zoom Fn+F10 not working
scan code: 0x17 key code: suspend Fn+F12 working

Fn+NumLk (ScrLk) not working also i couldnt scan it
Fn+Insert (Pause) not working also i couldnt scan it
Fn+Delete (Break) not working also i couldnt scan it

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

1. Fn+F5, reduces the brightness of the screen [NOT WORKING]
scan code: 0x10 key code: brightnessdown

2. Fn+F6, increase the brightness of the screen [NOT WORKING]
scan code: 0x11 key code: brightnessup

3. Fn+F7, switch video mode [NOT WORKING]
scan code: 0x12 key code: switchvideomode

4. Fn+F10, zoom in cursos [NOT WORKING]
scan code: 0x15 key code: zoom

5. Fn+F12, suspend the pc [WORKING]
scan code: 0x17 key code: suspend

[Simos Xenitellis  (simosx)]

I updated the title and description of the report with the information that Panagiotis provided in the comments.

It appears that udev sends the correct key codes, however the graphics card driver is not responding to these commands.

@Panagiotis, do you use the open-source graphics driver or is it the closed-source graphics driver?

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 8400M GT/PCI/SSE2
OpenGL version string: 2.1.2 NVIDIA 173.14.35

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes

[Martin Pitt (pitti)]

Ah, thanks. So the keymaps are correct, they are just not working with the nvidia driver, presumably because of the lack of decent XRandR support.

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

What should I do?

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

Now I have the open drivers?

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 8400M GT/PCIe/SSE2
OpenGL version string: 3.3.0 NVIDIA 295.49

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes

[Panagiotis Mirmigkis (panagiotis-mirmigkis)]

Problem fixed with nouveau drivers....!

[Simos Xenitellis  (simosx)]

I am closing the bug report. I chose the option 'Invalid' as we did not have to write code to fix the issue.

Thanks for the report Panagiotis!