Fn keys not working until after suspend/resume?

[Ariel Vardi]

On a sony vaio sz110, ubuntu dapper up-to-date:

Fn keys don't work unless I suspend and wake up the laptop.

Steps to reproduce:
1) Turn on the laptop and boot ubuntu.
2) Press the Fn Keys.
3) Notice none of them work.
4) Close the lid of the laptop, hence suspending it.
5) Re-open the lid and press a key to wake the laptop up.
6) Press the Fn keys and notice they now work.

[Ariel Vardi (ariel-vardi)]

Here's the acpid log when the keys actually work:

[Mon Mar 27 13:28:24 2006] completed event "sony/hotkey SPIC 00000001 0000000e"
[Mon Mar 27 13:28:25 2006] received event "sony/hotkey SPIC 00000001 0000003b"
[Mon Mar 27 13:28:25 2006] notifying client 4330[111:111]
[Mon Mar 27 13:28:25 2006] completed event "sony/hotkey SPIC 00000001 0000003b"
[Mon Mar 27 13:36:46 2006] received event "sony/hotkey SPIC 00000001 00000029"
[Mon Mar 27 13:36:46 2006] notifying client 4330[111:111]
[Mon Mar 27 13:36:46 2006] completed event "sony/hotkey SPIC 00000001 00000029"
[Mon Mar 27 13:37:00 2006] received event "sony/hotkey SPIC 00000001 0000000e"
[Mon Mar 27 13:37:00 2006] notifying client 4330[111:111]
[Mon Mar 27 13:37:00 2006] executing action "/etc/acpi/voldownbtn.sh"

[Ariel Vardi (ariel-vardi)]

the settings for the brightness of the screen set with the gnome power manager applet are forgotten when coming back from the suspend mode. It seems like the brightness is set back to its maximum

[Ariel Vardi (ariel-vardi)]

the settings of the touchpad are messed up as well when resuming from the suspend mode. The edge scrolling doesn't work anymore, and the touchpad is much more sensitive (it goes much faster).

could there be some kind of incompatibility between acpid and sonypi ?

[Ariel Vardi (ariel-vardi)]

Xorg.0.log after the suspend/wake-up

Synaptics DeviceOn called
(WW) Option "Device" requires an string value
(EE) xf86OpenSerial: No Device specified.
(WW) Option "Device" requires an string value
(EE) xf86OpenSerial: No Device specified.
(WW) Synaptics Touchpad: cannot open input device

[Paul Sladen (sladen)]

Hi Ariel, can you file separate bugs for the Synaptics pad not working after resume (it's failing to open as a synaptics pad and is switching back to working as a normal PS/2 mouse) against 'acpi-support'.

And also a separate bug for the gnome-power-manager screwing up the brightness after unsuspend (against 'gnome-power-manager').

Back to the original bug. Could you check whether 'sonypi' is loaded:

  /sbin/lsmod | grep sonypi

both before, and after suspend? The weird thing here is that the 'sonypi' module is loaded by 'hotkey-setup' on boot, but no effort is made to reload is when coming back from an unsuspend.

What happens if you manually *remove* the 'sonypi' module with:

  sudo modprobe -r sonypi

on first boot?

[Ariel Vardi (ariel-vardi)]

sonypi is load both before and after the suspend.
removing sonypi before the suspend didn't fix the fn key issue.
reloading it didn't fix it either.

Please note that the fn keys do NOT always work after a suspend. I
sometimes have to suspend the laptop several times in a row before they
start working.

Also, please note the sonypi messages in dmesg. There are some errors
after a fresh boot:

[4294702.197000] sonypi: Sony Programmable I/O Controller Driverv1.26.
[4294702.197000] sonypi: detected type2 model, verbose = 0, fnkeyinit =
off, camera = off, compat = off, mask = 0xffffffff, useinput = on, acpi
= on
[4294702.197000] sonypi: enabled at irq=11, port1=0x1080, port2=0x1084
[4294702.197000] sonypi: device allocated minor is 61
[4294806.552000] sonypi command failed at drivers/char/sonypi.c :
sonypi_call2 (line 659)
[4294806.598000] sonypi command failed at drivers/char/sonypi.c :
sonypi_call2 (line 661)
[4294806.602000] sonypi: removed.
[4294817.450000] sonypi command failed at drivers/char/sonypi.c :
sonypi_call1 (line 648)
[4294817.513000] sonypi command failed at drivers/char/sonypi.c :
sonypi_call2 (line 659)
[4294817.559000] sonypi command failed at drivers/char/sonypi.c :
sonypi_call2 (line 661)
[4294817.603000] sonypi command failed at drivers/char/sonypi.c :
sonypi_call1 (line 648)
[4294817.603000] sonypi: Sony Programmable I/O Controller Driverv1.26.
[4294817.603000] sonypi: detected type2 model, verbose = 0, fnkeyinit =
off, camera = off, compat = off, mask = 0xffffffff, useinput = on, acpi
= on
[4294817.604000] sonypi: enabled at irq=11, port1=0x1080, port2=0x1084
[4294817.604000] sonypi: device allocated minor is 61

On Thu, 2006-04-06 at 18:50 +0000, Paul Sladen wrote:
> Hi Ariel, can you file separate bugs for the Synaptics pad not working after resume (it's failing to open as a synaptics pad and is switching back to working as a normal PS/2 mouse) against 'acpi-support'.
>
> And also a separate bug for the gnome-power-manager screwing up the brightness after unsuspend (against 'gnome-power-manager').
>
> Back to the original bug. Could you check whether 'sonypi' is loaded:
>
> /sbin/lsmod | grep sonypi
>
> both before, and after suspend? The weird thing here is that the 'sonypi' module is loaded by 'hotkey-setup' on boot, but no effort is made to reload is when coming back from an unsuspend.
>
> What happens if you manually *remove* the 'sonypi' module with:
>
> sudo modprobe -r sonypi
>
> on first boot?
>
> ** Changed in: acpi-support (Ubuntu)
> Status: Unconfirmed => Needs Info

[Albert Vilella (avilella)]

I tried to force sonypi to activate fnkeyinit option with:

sudo modprobe sonypi fnkeyinit=1

But it doesn't work either.

[Arnaud (arnaud-mazin)]

see #35319 as it seems to be a kindoff solution.

[Ariel Vardi (ariel-vardi)]

The bug fix for #35319 seems to fix this bug as well.

On Mon, 2006-03-27 at 19:21 +0000, Ariel Vardi wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/34801
>
> Comment:
> Xorg.0.log after the suspend/wake-up
>
> Synaptics DeviceOn called
> (WW) Option "Device" requires an string value
> (EE) xf86OpenSerial: No Device specified.
> (WW) Option "Device" requires an string value
> (EE) xf86OpenSerial: No Device specified.
> (WW) Synaptics Touchpad: cannot open input device

[Albert Vilella (avilella)]

A bit of extra information about the BIOS. I tested it using http://www.linuxfirmwarekit.org/ and got the attached results.

[Albert Vilella (avilella)]

same thing but with resources.xml file.

[Launchpad Janitor (janitor)]

[Expired for acpi-support (Ubuntu) because there has been no activity for 60 days.]