hibernate, suspend, monitor switch keys don't work in Panasonic CF-Y7 laptop

This appears to be a case of ACPI events not being mapped to input events yet in the kernel.

ACPI events for these are:

sleep: pcc HKEY 00000080 00000007
hibernate: pcc HKEY 00000080 0000000a

This is affecting mine Asus M50SV too.
All other FN+ keys are working.
Its really annoyin since I dont know the command to issue ("echo something > somewhere") to make my screen brighter.
Now im using suspend->resume (which sets my brightness to a good level).
If anyone knows where to set brightness manually, please let me know.

   1. Ubuntu
   2. 9.10
   3. “linux” source package
   4. Bugs
   5. Bug #392692

> I'm installed Ubuntu *9.04* at my laptop and found that some FN+* keys not working, but others works fine.

Is this about Jaunty or Karmic?

Ubuntu 9.04 is named Jaunty.

I can confirm this bug exists for jaunty and karmic on my Panasonic CF-T4 laptop. This laptop model uses the same kernel module (panasonic-laptop) for this functionality. Since the switch from pcc_acpi.ko to panasonic_laptop.ko these laptops no longer use acpid for the function keys so the bug appears to be in the kernel module.

First things to check up, does panasonic_laptop get loaded? Also we probably should look at the DSDT to find whether the IDs match with the driver. So could you post the output of "sudo acpidump -o acpidump.txt" together with "sudo dmidecode" output. Thanks.

Panasonic CF-Y7 acpidump.txt attached.

Panasonic CF-Y7 dmidecode.txt attached.

From the BIOS it should be supported. So if the module is loaded, there should be an input device listed by lsinput that relates to it ("Panasonic Laptop Support" / "Hotkey" / "panasonic/hkey0"). When using input-event <device>, this should at least generate output for the working keys. Does something show up for the non-working too?

>So if the module is loaded, there should be an input device listed by lsinput...
There is no such device in lsinput output. See attached lsinput.txt.

>When using input-event <device>, this should at least generate output for the working keys.
>Does something show up for the non-working too?
How can I check it?

Panasonic CF-Y7 lsinput.txt attached.

It was sort of dumb question, sorry. From your modules list, the panasonic_laptop module is not loaded. Is it possible for you to load it manually (sudo modprobe panasonic_laptop)? If yes, does this enable your fn keys? If no, could you attach the dmesg, after the module fails to load?

>Is it possible for you to load it manually (sudo modprobe panasonic_laptop)?
Yes, it was OK, after it lsinput output contain:
/dev/input/event8
   bustype : BUS_HOST
   vendor : 0x1
   product : 0x1
   version : 256
   name : "Panasonic Laptop Support"
   phys : "panasonic/hkey0"
   bits ev : EV_SYN EV_KEY

>If yes, does this enable your fn keys?
Yap, now all keys work, but it seems that FN-keys that already works before now produces 2 appropriate events at one keypress :(

@Vitaliy -- that may well be due to acpid and the kernel handling those keys. Could you try stopping acpid and then testing the buttons.

So there are two questions:
1) why does the module not get loaded
2) where do the duplicates come from

1) could you do an "sudo ls /sys/bus/acpi/devices/" and post the output here
2) I noticed that in the initial description you found multiple files name *panasonic* in /etc/acpi/events. When I look at a Karmic system here, I only find one (the panasonic-lockbtn). I wonder whether you still have the other files and whether they belong to any package (dpkg -S /etc/acpi/events/<file>)

>that may well be due to acpid and the kernel handling those keys. Could you try stopping acpid and then testing the buttons.
With these steps:
1. sudo modprobe panasonic_laptop
2. sudo /etc/init.d/acpid stop
There is also double handling of FN+ keys.

> 1) could you do an "sudo ls /sys/bus/acpi/devices/" and post the output here
Panasonic CF-Y7 acpi-devices.txt attached.

>I wonder whether you still have the other files and whether they belong to any package (dpkg -S /etc/acpi/events/<file>)
All of them belongs to acpi-support (my version is 0.121) package.

Panasonic CF-Y7 acpi-devices.txt attached.

Mine is 0.126, from the following it seem like you should update:

acpi-support (0.126) karmic; urgency=low

  * Drop events/panasonic-brightness-{down,up}, events/panasonic-mute,
    events/panasonic-volume-{down,up}, and panabright.sh, confirmed to be
    implemented now by the panasonic-laptop kernel driver.

Now for the module loading, there is a "MAT0019:00" which matches the module alias
"alias: acpi*:MAT0019:*"
I need to check with the udev rules and will update about that later. Could you try to update your acpi-support package and see whether that with the module loaded is working as expected?

Actually I got acpi-support 0.127, but I cannot type... :-P

OK, i will try to update and check it soon.

For the module probing part can you:
a) run in one window " udevadm monitor --udev --kernel --property 2>&1|tee udev.log"
b) while that runs open another window and type "sudo udevadm trigger --subsystem-match=acpi"

Then stop the command from a) and attach the generated udev.log

I just loaded my notebook from Ubuntu 9.10 beta live CD and checked all FN keys, everything works out of the box, but there is one problem with "mute" FN key, it is doublepressed and sound remains unmuted, but if I press this button very quickly, then it pressed 1 time, so it is different problem than described above, i will file it as separate bug.

So finally what we have:

Jaunty:
1. Out of the box: "sleep", "hibernate" and "monitor" FN buttons didn't work.
2. If user loaded module "panasonic_laptop" manually, then all FN buttons work, but some of them double handles (by acpi and kernel).

Karmic:
1. All FN buttons works out of the box.
2. "Mute" button is double handles, not by 2 different processes, but by one, it seems like it's repeate delay is very small.

> a) run in one window " udevadm monitor --udev --kernel --property 2>&1|tee udev.log"
It produces error "monitor: unrecognized option '--property'". Checked in Jaunty (all latest official updates).

Ok, now this get a bit less confused. We were looking at different releases. Somehow there was only a task defined for Karmic, but you did your report and test in Jaunty. So checking back there, it is clear why the module did not get loaded. It had no alias elements there.

So this issue should have the karmic task as fixed and a jaunty task being added. For Jaunty, if you run the acpi_listen (without the module loaded), do you get output for the non-working keys and if yes, please add this to the bug report. As the module does not offer ways to be automatically loaded and the acpi-support package includes the panasonic definitions, I guess the preferred fix would be to make it working without the module (if that is possible).

closing karmic task as per Stefan and assigning him to the Jaunty task which is actually working on.

This bug was nominated against a series that is no longer supported, ie jaunty. The bug task representing the jaunty nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.