ACPI brightness, volume (everything) won't work in Dapper (Panasonic CF-Y4)

[Mante]

I am using Panasonic Let'S Note CF-Y4.

As report in the summary, all the ACPI functions as volume control, brightness control, hybernate ecc... don't work in Dapper. With Breezy everything except the video output selection was ok, when selecting volume up and down gnome displayed a good designed indicator too. Changing brightness values from console with a sort of "echo n > /proc/acpi/..." works so probably is the key mapping to (function)+key number that is broken.

[Paul Sladen (sladen)]

Hello, many thanks for your bug report!

You've mentioned several key-combinations and I can't follow which ones do which. Could you write then out separately, eg:

  Brightness: Does nothing
  Volume: Shows indicator on screen; but no change in volume
  Hibernate: Doesn't work, doesn't show anything
  ...

You can see if the key-combations for these keys work by following the checks on:

  https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

Could you also post the dmidecode information for your laptop (see the bottom of that page).

-Paul

[John Stowers (nzjrs)]

See

https://launchpad.net/distros/ubuntu/+bug/33855

Capturing keycodes does not apply / does not work. Nothing is generated because the above fix isnt present.

This is a serious regression from breezy

[John Stowers (nzjrs)]

Should have mentioned that I am seeing this also

https://wiki.ubuntu.com/LaptopTestingTeam/PanasonicCFR4

[Matthew Garrett (mjg59)]

I'm sorry, what? That bug report is unclear. Why is a new driver
required?

--
Matthew Garrett | <email address hidden>

[John Stowers (nzjrs)]

I'm not sure if a new driver is required but after emailing the reporter of https://launchpad.net/distros/ubuntu/+bug/33855 he suggested that it fixes the problem described in this bug and more accurately described https://launchpad.net/distros/ubuntu/+source/acpi-support/+bug/31525

The actual problem is twofold.

1) acpi hotkeys only work once! That is one keypress per shutdown-restart cycle. After that nothing.
2) When they do work (occasionally) the only ones that actually do anthing are the brightness up/down key

[Mante (mante)]

Followed the checks on
https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch
as asked by Paul

A: Laptop type

#dmidecode -s system-manufacturer
Matsushita Electric Industrial Co.,Ltd.

#dmidecode -s system-product-name
CF-Y4JW8AXR

#dmidecode -s system-version
003

B) Keycodes

Keys tested
Fn-f1 brightness down (sun icon)
Fn-f2 brightness up (sun icon)
Fn-f3 display out (monitor icon)
Fn-F4 sound disabled (speaker off icon)
Fn-F5 sound down (speaker down icon)
Fn-F6 sound up (speaker up icon)
Fn-F7 hibernate (cpu zzz icon)
Fn-F8 nothing
Fn-F9 battery level (battery icon)
Fn-F10 HD sleep (storage mark icon zzzz)

All the above keys have not been recognized!
I've done the following tests:

1) gnome->keyboard shotcuts
2) showkey -u | tee -a hotkey-log.txt
3) tail -f /var/log/acpid

as described in the link.

[Paul Sladen (sladen)]

This is a regression. While it's not the greatest solution, fetching and dropping in the latest version of the driver is reported to work and that is better than the status quo which is a regression from 5.10.

[TedKisner (tskisner-public)]

This is a duplicate of bug #33855. An old version of kernel driver pcc_acpi causes a kernel oops when it receives keystrokes from the various keys (brightness, volume, etc). The fix (newer driver) has been committed by Ben, so I suggest we close this bug...

Note that the acpi-support package does not currently include scripts to handle volume changes, but that belongs in a separate bug-report (will open soon with patch).