Fujitsu T4410 hotkeys not bubbling up from kernel

[Bryce Harrington]

Hotkeys on Fujitsu Lifebook T4410 appear to be lacking kernel support.

Pitti, apw, and I poked at it, but couldn't see any response via xinput, lsinput, dmesg, /var/log/syslog, etc. on either maverick or natty.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.35
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bryce 1805 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2800000 irq 46'
   Mixer name : 'Intel Cantiga HDMI'
   Components : 'HDA:10ec0269,10cf0000,00100004 HDA:80862802,80860101,00100000'
   Controls : 21
   Simple ctrls : 12
Date: Fri Jan 14 13:08:04 2011
HibernationDevice: RESUME=UUID=51d8749f-38e9-45f4-b568-4f4422844fd2
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
MachineType: FUJITSU LifeBook T4410
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=2a5afac8-e748-4f4a-b9c9-a202fff06735 ro quiet splash
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=C
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 09/30/2009
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.05
dmi.board.name: FJNB206
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: A40R8CE708EA1001
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd09/30/2009:svnFUJITSU:pnLifeBookT4410:pvr:rvnFUJITSU:rnFJNB206:rvr:cvnA40R8CE708EA1001:ct10:cvr:
dmi.product.name: LifeBook T4410
dmi.sys.vendor: FUJITSU

[Jeremy Foshee (jeremyfoshee)]

dropped myself as the assignee as this is now on our hotlist.

~JFo

[Jeremy Foshee (jeremyfoshee)]

Hi Bryce,

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

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

Bryce, ignore the above. :)

[Herton R. Krzesinski (herton)]

I had a look into the DSDT from the attached acpi tables, and fujitsu-laptop should be handling hotkeys, and indeed from posted dmesg it loads succesfuly and register the input device for hotkeys:

[ 29.212978] input: Fujitsu FUJ02B1 as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:43/FUJ02B1:00/input/input4
[ 29.213034] ACPI: Fujitsu FUJ02B1 [FJEX] (on)
[ 29.213848] input: Fujitsu FUJ02E3 as /devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02E3:00/input/input5
[ 29.213888] ACPI: Fujitsu FUJ02E3 [FEXT] (on)
[ 29.214569] fujitsu-laptop: BTNI: [0xf0001]
[ 29.214808] fujitsu-laptop: driver 0.6.0 successfully loaded.

The input device which receives input events is input5, FUJ02E3, which is Device (FEXT) in DSDT.

Probably fujitsu-laptop needs an update to work with this machine, can be the case of newer hardware which needs more handling in the code.

My bet is that on acpi_fujitsu_hotkey_notify function, switch (irb & 0x4ff) doesn't match any option on switch, so it goes to default which sets keycode = -1 and thus no keycode is reported. I think this make sense, probably this laptop reports different/new codes.

To confirm, we need to enable CONFIG_FUJITSU_LAPTOP_DEBUG, then load the module with parameter debug=0xf to catch all debug messages, press hotkey and check dmesg output. Of interest will be the messages with "Unknown GIRB result"..., which then means that indeed keycode was set to -1 and nothing reported.

Can you handle rebuilding the module with CONFIG_FUJITSU_LAPTOP_DEBUG=y? Otherwise I can provide a test kernel, so you can enable debug and report back the dmesg.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

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

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu Natty) because there has been no activity for 60 days.]

[Bryce Harrington (bryce)]

"Can you handle rebuilding the module with CONFIG_FUJITSU_LAPTOP_DEBUG=y? Otherwise I can provide a test kernel, so you can enable debug and report back the dmesg."

Sorry, only just noticed the request. Yes please provide a test kernel.

[Herton R. Krzesinski (herton)]

I built a kernel with CONFIG_FUJITSU_LAPTOP_DEBUG enabled, and placed at http://people.canonical.com/~herton/lp703020/

It's a natty-i386 build, let me know if you need something else.

Just install that kernel and remember to load fujitsu-laptop with option 'debug=0xf', press the hotkeys which aren't working, and look at dmesg output for new messages like "Unknown GIRB result"... Then attach here dmesg output, thanks. This should confirm if we have new keycodes which fujitu-laptop must handle.

[Bryce Harrington (bryce)]

Thanks, here's the dmesg after booting this kernel.

[Herton R. Krzesinski (herton)]

Bryce, I need that you boot the kernel, and reload fujitsu-laptop with option 'debug=0xf', press the hotkeys and then grab the dmesg output. It seems your dmesg misses the debug output from fujitsu-laptop, so just confirming have you done that?

[Bryce Harrington (bryce)]

Fwiw, I retested against precise. Enabled CONFIG_FUJITSU_LAPTOP_DEBUG in the kernel config, then after installing and booting the kernel, reloaded fujitsu-laptop with 'debug=0xf'. I can see debug output added to dmesg when closing the lid, but still nothing gets printed when I press the 5 buttons on the lid.

[Joseph Salisbury (jsalisbury)]

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.