Gutsy Gibbon and FN keys on Sony Vaio

[André Barmasse]

Hello

Sorry to open another bug report about non-working FN keys on a Sony Vaio, but as I am trying to get these suckers to work on my Vaio VGN-FS196VP for some time now I get more and more confused. Let me explain in short:

With Dapper Drake the FN keys didn't work out of the box, but at least I could dim the screen within the gnome power manager and the sound over the gnome volume manager. After Installing Edgy Eft the FN keys didn't work out of the box (again) and suddenly I was no more able to dim the screen from within the gnome power manager. So, after reading in some fora about manually compiling the modules sony_acpi and fsfn I succeeded in getting the keys to work! Great!!

After upgrading to Feisty Fawn I was suddenly no more able to control the brightness within the gnome power manager nor to install the sony_acpi and fsfn modules. I was very disappointed. Then I read about the new sony-laptop module, which is integrated in the new kernel 2.6.22 and so I compiled a brand new kernel 2.6.22-rc4 with this module activated and - surprisingly enough - I was at least again able to dim the screen with my Feisty Fawn from within the gnome power manager. Heureka!

Then I thought upgrading to Gutsy Gibbon - though still under heavy development - would be no problem as it already uses the new kernel 2.6.22-rc4, which would let me me at least dim the screen brightness over the gnome power manager. About the FN keys I don't care anymore. Well, upgrading to Gutsy was really no problem and went smoothly, but I was very stunned, when the switch for the screen brightness within the gnome power manager has disappeared again. Since then I remain unable to dim the screen.

I hope you understand my state of confusion. At the moment there seems to be no right way to get the dimming process work permanently (letting aside the bloody FN keys)! It's really about try and error - it might work or not, but as user you don't really seem to have any control over it. Hopefully, some day you don't need half a dozen modules to compile, install and pray, but everything will work with the sony-lapotp kernel module.

Please, understand me the right way: this strange confusion is neither a fault of the kernel development team, which has done a really great job with the new ultra fast kernel 2.6.22, nor of the Ubuntu development team. There is only one to blame - and that's Sony.

[André Barmasse (barmassus)]

Well, well, well. A small surprise has happened today after upgrading my Gutsy Gibbon. The gnome-power-manager suddenly has the long gone slider for "display brightness" back again. I was very happy ... until I realized that moving the slider didn't dim the brightness of my Sony Vaio VGN-FS196V at all. So, I'll wait again until it becomes possible to dim the brightness again at least over the gnome-power-manager slider - without the need of compiling and trying different tools and patches that, in the end, do not work. And maybe, some someday in the future, the FN keys will work, too ...

[Michel Pelletier (pelletier-michel)]

I have the same problem on a VGN-TX850P. The Fn brightness keys worked on Feisty, but stopped working in Gutsy. I could never get the gnome brightness slider or brightness applet to work with either.

[Ignacio Martin Rodriguez (newwen)]

I have a VGN-FE31M and have exacly the same problem. I was excited when I upgraded to gutsy as i had the brightness slider back, but i got dissapointed when I realised that i doesn' have any effect at all. It doesn'k work right now. I thought the 2.6.22 kernel came rewritten vaio support.

[Brian Murray (brian-murray)]

This bug may be a duplicate of bug 125881.

[Centaur5 (djacks555)]

I have the same problem with only the brightness keys but the sound keys work fine. It didn't start until upgrading to 2.6.22-9-generic. Is there a reason why the sony_pi module no longer exists?

[Henrik Nilsen Omma (henrik)]

Hi, could you try following the debugging instructions at https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch ?

Michel, you say you had this working on Feisty; could you perform the above keytests on both Gutsy and a Feisty Live CD? That would be great!

[Centaur5 (djacks555)]

Brightness keys work with Gutsy 2.6.22-11-generic and all other updates yet when I close my screen (set for blank screen not sleep or hibernate) they no longer function til I reboot. This is on a Sony Vaio VGN-SZ140P and here are the requested keytests:

brightness down: sony/hotkey SPIC 00000001 00000010"
brightness up: sony/hotkey SPIC 00000001 00000011
volume mute: sony/hotkey SPIC 00000001 0000000d
volume down: sony/hotkey SPIC 00000001 0000000e
volume up: sony/hotkey SPIC 00000001 0000000f
video to vga: sony/hotkey SPIC 00000001 00000012 (I've never actually used this one)

[André Barmasse (barmassus)]

Upgrading to the latest kernel 2.6.22-11 didn't change anything. I've tried the debugging instructions (https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch) to get any hotkey informations or key codes out of my Sony Vaio - but I failed with all three different BIOS key settings (type1, type2, and type3) as awen did in bug 125881. I can give the following information, but they won't help any further, I fear ...
-----------------------------------------------------
Laptop identification:
Sony Corporation
VGN-FS195VP
C2002JR
 --------------------------------------------------------
What the keys should do:
Fn+F2: Mute (looks like: crossed out speaker)
Fn+F3: Volume down (looks like: triangle -)
Fn+F4: Volume up (loks like: triangle +)
Fn+F5: Brightness down (looks like: sun -)
Fn+F6: Brightness up (looks like: sun +)
------------------------------------------------------------
"tailing -f" the acpid.log remains silent, but "tailing -f" syslog gives at least the following messages, when pressing any of the above mentioned Fn key combinations:

Sep 11 15:43:24 ubuntu-vaio kernel: [26405.572000] atkbd.c: Unknown key pressed (translated set 2, code 0xf7 on isa0060/serio0).
Sep 11 15:43:24 ubuntu-vaio kernel: [26405.572000] atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
Sep 11 15:43:24 ubuntu-vaio kernel: [26405.720000] atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
Sep 11 15:43:24 ubuntu-vaio kernel: [26405.720000] atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.

[André Barmasse (barmassus)]

Yesterday, something very strange happened. After my first update in the early morning (trying to fix a broken openoffice.org) there were some new versions of dbus, hotkey-setup, and gnome-power-manager installed. Rather coincidentily I switched off the power supply to my Sony Vaio ... and the display dimmed!! I was rather surprised, and after checking the gnome-power-manager I was really able to dim the display with the slide bar again. Hooray!!! But now comes the odd part: after my second update in the evening I was no more able to dim the display by hand in the gnome-power-manager nor does it dim when the power supply is cut off! The mystery continues ...

[André Barmasse (barmassus)]

Yipeeeeee! After today's update the slider for dimming the screen in the gnome-power-manager 2.20.0 is working again - and I hope it will continue to work on my Sony Vaio VGN-FS195VP forever!! Even more, I think also the cpu fan is now stepping more often and smoothier than before. Great work, guys!! It almost makes me forget the *ç%&+" Fn keys ...

[getaceres (getaceres)]

Brightness and FN keys does not work on a VAIO FE31Z laptop. It didn't work in Feisty but I was hoping Gutsy to support this laptop with the new sony-laptop driver :(

[André Barmasse (barmassus)]

Ohhh, crap! My joy was spread a little bit too early. It seens that the slider for dimming the brightness on my Sony Vaio VGN-FS195VP only worked just after the update. After rebooting my machine I was - once again - not able to dim the brightness within gnome-power-manager 2.20.0. Very strange! Because of the eloquent dmesg output (see below) I blacklisted the sonypi module, but that doesn't seem to do the trick. Are the modules sonypi and sony-laptop (both are loaded during startup) disturbing each other or lies the problem deeper in the dbus and hal area? I have no idea! Well, let's wait and see what the next update brings ...

[ 32.928000] sonypi: Sony Programmable I/O Controller Driver v1.26.
[ 32.928000] sonypi: please try the sony-laptop module instead and report failures, see also http://www.linux.it/~malattia/wiki/index.php/Sony_drivers
[ 32.928000] sonypi: detected type3 model, verbose = 0, fnkeyinit = off, camera = off, compat = off, mask = 0xffffffff, useinput = on, acpi = on
[ 32.928000] sonypi: enabled at irq=11, port1=0x1080, port2=0x1084
[ 32.928000] sonypi: device allocated minor is 63
[ 33.416000] input: Sony Vaio Jogdial as /class/input/input8
[ 33.612000] input: Sony Vaio Keys as /class/input/input9
[ 33.684000] sonypi command failed at /build/buildd/linux-source-2.6.22-2.6.22/drivers/char/sonypi.c : sonypi_call1 (line 652)
[ 33.732000] sonypi command failed at /build/buildd/linux-source-2.6.22-2.6.22/drivers/char/sonypi.c : sonypi_call2 (line 663)
[ 33.780000] sonypi command failed at /build/buildd/linux-source-2.6.22-2.6.22/drivers/char/sonypi.c : sonypi_call2 (line 665)
[ 33.828000] sonypi command failed at /build/buildd/linux-source-2.6.22-2.6.22/drivers/char/sonypi.c : sonypi_call1 (line 652)
[ 33.872000] sony-laptop: Sony Notebook Control Driver v0.5.
[ 34.140000] input: Sony Vaio Keys as /class/input/input10
[ 34.156000] input: Sony Vaio Jogdial as /class/input/input11

[getaceres (getaceres)]

I've moved the sonypi and sony_acpi modules (since I cannot blacklist them due to bug Bug #133434) and now I only have the sony-laptop module. Anyway neither the Fn keys or the brightness control works for me.

[Christian Schneiker (chrisschneiker)]

Since kernel update to 2.6.22-12-generic the FN-UP/DOWN for brightness controll aren't working anymore on my Dell XPS m1330. With 2.6.22-10-generic they worked well.

[Wen (wen)]

It is always nice to see other users having the same problems as I do. On my Vaio FE-21S laptop my fn-keys (including the brightness-ones) were working on Edgy. After a few workarounds, sure, but nevertheless. Then, after upgrading to Feisty, they failed to work again, and nothing helped. Now I was looking forward to Gutsy and, as far as I can see, it doesn't look like we are getting this feature back. But why?

[Matt Sicker (jvz)]

Neither the ACPI nor the showkey methods work on my laptop.

matt@vaio:~$ sudo dmidecode -s system-manufacturer
Sony Corporation
matt@vaio:~$ sudo dmidecode -s system-product-name
VGN-FS550
matt@vaio:~$ sudo dmidecode -s system-version
C20010U

I was able to get the Fn keys working in Feisty via fsfn and the *correct* sony_acpi module (rather than the broken/incomplete one that was in Feisty), but now they don't work anymore...

[Mathieu Laurent (mla)]

Vaio VGN-FS315B :

FN keys didn't work with sony-laptop module in gusty.

lsmod | grep sony
sony_laptop 32088 0

In Ubuntu Dapper, It worked with sony-acpi and fsfn.

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch , I try this, but no value is return when I press fn key.

I can update Brightness with the command line :

echo "0" > /sys/class/backlight/sony/brightness
echo "7" > /sys/class/backlight/sony/brightness

But it doesn't work with screen brightness over the gnome power manager.

[Mathieu Laurent (mla)]

André Barmasse >I blacklisted the sonypi module, but that doesn't seem to do the trick. Are the modules sonypi and sony-laptop (both are loaded during startup) disturbing each other or lies the problem deeper in the dbus and hal area? I have no idea! Well, let's wait and see what the next update brings ...

Hi,

Put in comment modprobe sonypi in hotkey-setup

grep sony /etc/init.d/*
/etc/init.d/hotkey-setup: #modprobe sonypi; # Needed to get hotkey events
/etc/init.d/hotkey-setup: modprobe sony-laptop

Regards

Mathieu

[André Barmasse (barmassus)]

Well, well, well, I have to bow before you, Mathieu!! It seems that your solution holds up tight - even against system updates, rebooting and multiple power supply on and off switching :-) To be absolutely sure that the sonypi is out of the system I blacklisted it again in /etc/modprobe.d/blacklist. I hope you don't mind me reporting if someday it should stop working. Thanks again!

[André Barmasse (barmassus)]

Grrrrrrrrr, today the *ç%& dimming didn't work again!! But comparing the output "lsmod | grep sony" with the line in /etc/init.d/hotkey-setup mentioned by Mathieu above, I found out that the kernel module itself is called "sony_laptop" (with UNDERSCORE!!), but in the hotkey-setup the modprobe is set against "sony-laptop" (with HYPHEN!!). So, after replacing "sony-laptop" with "sony_laptop" in the hotkey-setup, the dimming is working again. I hope this time for more than one reboot ...

[André Barmasse (barmassus)]

Ooooooh, crap!! Neither Mathieu's tip nor my spelling correction nor blacklisting or un-blacklisting the sonypi have changed anything! After my next reboot everything was still the same. No dimming at all! So back to where we started ....

[André Barmasse (barmassus)]

The strange thing is that when the gnome power manager sensor for dimming the screen is working (at least for that one magic moment) there is also the small on-screen sign visible that tells you that the power has been switched off and that the computer is now running in power save mode. But even this sign only works from time to time on my Sony Vaio! Very strange!! I have no idea if the sign for the gnome power manager comes from the ACPI or only from the sony laptop module. It seems to me that the way is ACPI -> sony laptop module -> gnome-power-manager, and that if one of these steps fails to initialize you can flush your hope for dimming right down the toilet. It would be nice to learn more about the way the sony hotkeys (should) work.

[André Barmasse (barmassus)]

One week ago I installed the new Ubuntu Hardy Heron Alpha 1 on my Sony Vaio VGN-FS195VP and since then dimming the screen manually and automatically by switching off the power is working flawlessly! And this not only with the older 2.6.22 kernel but also with the new 2.6.24. It is now even possible to use Mathieu Laurent's tip from above and prevent the unnecessary sonypi module from loading by commenting it out of /etc/init.d/hotkey-setup, too. Great work!!

[André Barmasse (barmassus)]

Aaaah, crap!! Since last weeks hardy heron update to kernel 2.6.24-10-generic the power management on my Sony Vaio VGN-FS195VP seems again rather broken.

First of all the possibility to set the dimming precentage for battery mode in the gnome-power-manager has simply disappeared! Why the hell did this happen? It was there since I first installed the Hardy Heron Alpha 1 and it was working perfectly. And second: If I pull out the power cable the computer goes into power save mode - but there is no dimming of the screen which - as I recall - should be part of the power saving process.

To me, it is sometimes an enigma why things that are working perfectly are changed again to the worse. I am well aware that the seems to be major challenge to get the kernel, the sony modules, hal and finally gnome together to work smoothly. So I hope this will be solved again with some of the next updates ... fingers crossed, folks!!

[getaceres (getaceres)]

I've tried Hardy Alpha 6 and still the FN keys and brightness does not work on a Sony Vaio FE31Z

[Trip (djturner)]

While testing the Beta version of Hardy Heron, I've just noticed something about the FN keys. Could you guys check this and see if you get the same results please?

I opened up a terminal and entered..
sudo showkey -u

I got the following message..
WARNING: Unicode mode is experimental -- output may be wrong
kb mode was RAW

I pressed some keys to make sure that they registered ok and the showkey software detected them fine.
I then pressed the FN key but got no response at all, as expected.

Now comes the interesting part..

The key's F2, F3, F4, F5, F6, F7, F10 and F12 didn't register anything either when used with the FN key but they do when not used with the FN key.

If I press the FN key + the other F keys that aren't supposed to have any special functions (F1, F8, F9, F11), they work the same as if the FN key isn't even being held down.

This tells me that the FN key is actually making a difference to the special keys and Ubuntu's detecting when it's pressed down :)

I hope I've explained this clear enough for everyone?

------------------------------------------------------------------------

Here's a list of the special key's on the FS series of laptops, along with a description of what they do & what they look like..

Fn key= modifier (Fn written on key)
Fn+F2 key= Mute Speakers (picture of speaker with + inside it)
Fn+F3 key= Volume Down (increasing slope with - next to it)
Fn+F4 key= Volume Up (increasing slope with + next to it)
Fn+F5 key= Brightness Down (picture of sun with - next to it)
Fn+F6 key= Brightness Up (picture of sun with + next to it)
Fn+F7 key= Swap Between LCD & External Monitor (2 square's separated by / with LCD wrote in the first one & an arrow facing out of the right side from the middle of the second box)
Fn+F10 key= Zoom (picture of magnifying glass with + inside it)
Fn+F12 key= Sleep (picture of a battery with an arrow going in it & 2 z's coming out like snore signs)
S1= Programable Key (S1 written on key)
S2= Programable Key (S2 written on key)

----------------------------------------------------------

[Toufik (toufik2)]

I want to make some comment about my researches in sony-laptop
* Vaio are not equal in front of the driver: FE et specially FS series are not handled correctly, for the others it works much better (with fn keys, webcam, jodial,...). Therefore, the distinction should be made between FE and FS series on one side and the others on the other side as the problems are probably completely different.

* As explained, there is a bug in the hotkey-setup package, "modprobe sonypi" should be removed from "/etc/init.d/hotkey-setup"

* sony-laptop works partially with FS (mine laptop): as Trip said it understand the FN keys but cannot correctly transfer them (see next point)

* They are 3 method used to transfer the FN keys

 1) Writing in a file (sony_acpi way): /sys/class/backlight/sony/fnevent (not sure it is the correct path and name as I'm not using my Vaio right now but you'll surely find the file). Prepare "$ cat /sys/class/backlight/sony/fnevent" in a terminal, press a FN key and press ENTER just after, you'll see a number (a power of 2) which is different for each FN keys. As this was the method used by sony_acpi, I rewrote fsfn, the daemon which was looking for the same kind of file for sony_acpi, to work with sony_laptop. And it works perfectly! But this is not really a viable solution: there is already a daemon (hal) which is designed to the job in a much better way (via Dbus rather than writing to a file). There should be no use to rewrite such a daemon. Anyway, this can be a temporary fix.

 2) The FN keys should be transformed into scancodes. These scancodes should be recognised by hal and translated into a command after looking for a correspondence in /usr/share/hal/fdi/information/10freedesktop/30-keymap-module-sony-laptop.fdi This file is rather not complete, you can try to add your laptop. I've used the word "should" here because, it doesn't work :) try "$ dmesg | tail" after pressing a couple of FN keys, you'll see the the scancodes are unrecognised. To see what should be the output, press the power button (and when ask for confirmation: cancel) and look at the message. It should be something like this: sony/hotkey SPIC 00000001 00000010 To conclude this method, I think fixing this part of the driver should do the trick. I try to tweak the driver but I didn't manage :( Some expertise in acpi (what I've not) would be great!

 3) The fn keys are also transfer to the X system via a new input devices called Sony Vaio Keys. I try to use this features but all my tests failed. I'm not sure but I think this is related to the issue present in method 2

* It could be interesting to check if method 1 works for you.
* I guess method 2 doesn't work (on the contrary you wouldn't be reading this bug), but what are your error message in dmesg (or acpid) ?
* Have you try method 3? I'll post what kind of messages I get from Xorg and dmesg when I'll be back on my Vaio this evening.

Toufik
Vaio FS-315B

[Toufik (toufik2)]

Precisions to my previous post as I'm back on my laptop :)

* the file in method 1 is "/sys/devices/platform/sony-laptop/fnkey" (and not /bla/bla/bla/fnevent" as explained). The answers for each key are in parenthesis: FN_F2 MUTE (1), FN_F3 VOLUME DOWN (2), FN_F4 VOLUME UP (4), FN_F5 BRIGHTNESS DOWN (8), FN_F6 BRIGHTNESS UP (16), FN_F7 SWITCH DISPLAY (32), FN_F10 ZOOM (128), FN_F12 HIBERNATE (64), S1 (4096) AND S2 (8192). These numbers are the same as for sony_acpi.

* in method 2, you may also look in "/var/log/acpid" for useful messages. If it worked, you should see something in acpid. I only get an error in dmesg:
[ 81.400910] atkbd.c: Unknown key pressed (translated set 2, code 0xf5 on isa0060/serio0).
[ 81.400920] atkbd.c: Use 'setkeycodes e075 <keycode>' to make it known.
[ 81.512947] atkbd.c: Unknown key released (translated set 2, code 0xf5 on isa0060/serio0).
[ 81.512957] atkbd.c: Use 'setkeycodes e075 <keycode>' to make it known.

The message is the same, whichever key I pressed.

* Method 3: See http://www.linux.it/~malattia/wiki/index.php/Sony-laptop#Fn_keys_.28hotkeys.29
Output of "/var/log/Xorg.0.log":
...
(**) Vaio keys: always reports core events
(II) Vaio keys: Found 1 relative axes.
(II) Vaio keys: Configuring as pointer.
(II) Vaio keys: Found 1 mouse buttons
(II) Vaio keys: Configured 6 mouse buttons.
...
So it seems to work at this stage, but I don't know what to do after in order to check if the fn-keys send signal to the X

[André Barmasse (barmassus)]

Hi Toufik

Thank you for your extensive explanations and congratulations for your great fsfn-script (http://ubuntuforums.org/showthread.php?p=4743422). I have installed it with high hopes on Hard Heron ... and everything works like a charm now! Brightness dims perfectly and the volume goes up and down and mutes without stumbling. The on-screen display is very nice, too. The other keys I have not tried as they seem rather pointless to me! I hope very, very, very much that your script will continue to work after my next Hardy updates, too. If something should not work anymore ... I'll be back!!

Thanks again and keep up the good work! Best wishes! André

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[darylb (darylblanc)]

I have installed Intrepid Alpha 4 on my VGN-SZ71WN Vaio. With latest updates installed the Fn key situation is quite dim:

root@lappytoppy:~# acpi_listen
mute (Fn-F2)
(no acpi event recorded, no effect)

vol- (Fn-F3)
(no acpi event recorded, no effect)

vol+ (Fn-F)
(no acpi event recorded, no effect)

bri- (Fn-F5)
sony/hotkey SPIC 00000001 00000010
sony/hotkey SPIC 00000001 0000003b
(this key however has no effect - not even the gnome brightness thing pops up)

bri+ (Fn-F6)
sony/hotkey SPIC 00000001 00000011
sony/hotkey SPIC 00000001 0000003b
(this key however has no effect - not even the gnome brightness thing pops up)

lcd/projector (Fn-F7)
sony/hotkey SPIC 00000001 00000012
sony/hotkey SPIC 00000001 0000003b
(this key however has no effect)

Marking as "new" as requested.

[getaceres (getaceres)]

I've installed Intrepid Alpha 4 on a Sony Vaio VGN-FE31Z and I can confirm that Fn keys do not work.

I get the following:

jose@ubuntu-vaio:~$ acpi_listen

Fn+F5: Brightness down:
sony/hotkey SNC 00000001 00000010
sony/hotkey SNC 00000001 0000003b

Fn+F6: Brightness up:
sony/hotkey SNC 00000001 00000011
sony/hotkey SNC 00000001 0000003b

Fn+F7: Change output screen:
sony/hotkey SNC 00000001 00000012
sony/hotkey SNC 00000001 0000003b

Fn+F12: Hibernate:
sony/hotkey SNC 00000001 00000017
sony/hotkey SNC 00000001 0000003b

Fn+BlNum or Insert or Supr don't give any output (they should activate BlDespl, Pause and Inter).

[Leann Ogasawara (leannogasawara)]

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.

[Julius (caesar-bs)]

fn keys work on VGN-FE21B. i added to /etc/X11/xorg.conf

Section "InputDevice"
       Identifier "Vaio keys"
        Driver "evdev"
        Option "Name" "Sony Vaio Keys"
        Option "XkbLayout" "jp"
          Option "XkbModel" "jp106"
EndSection

Section "ServerLayout"
   InputDevice "Vaio keys" "SendCoreEvents"
EndSection

Further i downloaded a patch from
https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/277589

Still i am having major issues with battery detection and runtime.
As i can dim the display now, it is not dimmed automatically, when the power plug is pulled. Battery life is like 20 min, even with low display brightness!
Im updateing to ibex now, to test ...

[Leann Ogasawara (leannogasawara)]

Has anyone been able to test Intrepid's final release? Is this still an issue? Thanks.

[Julius (caesar-bs)]

This is still an issue in intrepid. But the patch from above works. It changes hal. The changes in the xorg.conf are not needed it seems

[Julius (caesar-bs)]

Sorry, i forgot to mention:
The display is dimmed automatically now, when the plug is pulled. Battery life is still an issue, as well as battery charge. Essentially the notebook dies after 20 minutes or so, without shutting down or anything. I got a VGN-FE21B

[Keng-Yu Lin (lexical)]

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . If the issue remains in Jaunty, Please 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-image-2.6.28-11-generic <bug #>

If you could also test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine this 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.

[Toufik (toufik2)]

Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=54753992-5b38-497d-ba8a-d9947141582f
MachineType: Sony Corporation VGN-FS315B
Package: linux-image-2.6.28-11-generic 2.6.28-11.42 [modified: lib/modules/2.6.28-11-generic/kernel/drivers/media/common/ir-common.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/saa7146.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/saa7146_vv.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/mt2060.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/mt20xx.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/mt2131.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/mt2266.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/mxl5005s.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/mxl5007t.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/qt1010.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tda18271.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tda827x.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tda8290.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tda9887.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tea5761.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tea5767.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tuner-simple.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tuner-types.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/tuner-xc2028.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/common/tuners/xc5000.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/b2c2/b2c2-flexcop-pci.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/b2c2/b2c2-flexcop-usb.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/b2c2/b2c2-flexcop.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/bt8xx/bt878.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/bt8xx/dst.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/bt8xx/dst_ca.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/bt8xx/dvb-bt8xx.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dm1105/dm1105.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-core/dvb-core.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-a800.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-af9005-remote.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-af9005.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-af9015.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-anysee.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-au6610.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-cinergyT2.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-cxusb.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dib0700.ko lib/modules/2.6.28-11-generic/kernel/drivers/media/dvb/dvb-usb/...

[Brad Figg (brad-figg)]

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.