Missing hotkeys on Toshiba Tecra A4

[Greg Taylor]

All of the FN+ keys are currently not working on the Toshiba Tecra A4. You may
find a full list of the keys at my Toshiba Tecra page:
http://wiki.ubuntu.com/LaptopTestingTeam/ToshibaTecraA4 near the bottom.

[Matthew Garrett (mjg59)]

Does pressing them generate anything in /var/log/acpid?

[Greg Taylor (gtaylor)]

Created an attachment (id=3577)
Collection of Toshiba Tecra A4 log files.

No /var/log/acpid output is seen when I hit the special function keys. Here is
a collection of logfiles for you to peruse.

[Matthew Garrett (mjg59)]

Ok. Is the toshiba_acpi module loaded?

[Greg Taylor (gtaylor)]

No, and I can't modprobe it because "the hardware doesn't exist."

[Matthew Garrett (mjg59)]

Interesting. Can you please attach /proc/acpi/dsdt ?

[Matthew Garrett (mjg59)]

Ping?

[Greg Taylor (gtaylor)]

All attempts to attach a dsdt file have failed since whenever I put it on a USB
drive to transfer over, it vanishes when I remount. I was unable to tar it up or
move it at all and the Tecra A4 has no wired NIC support and very bad wireless
support (as in it is only usable 5-6 seconds for each 60 seconds it's on).

I'm not sure what to do from here, the shakey driver situation is really killing
my ability to troubleshoot.

[Greg Taylor (gtaylor)]

Got wireless working long enough to attempt to attach the dsdt file and got this:
 The file you are trying to attach is empty!
Not sure what to do here.

[Matthew Garrett (mjg59)]

The latest Tecras have different BIOSes, so we can't support the hotkeys right now.

[Matthew Garrett (mjg59)]

Ok. Can you please grab the driver from http://www.gesal.org/tecra/ , push a hotkey and let me know if it shows up in /proc/acpi/tecra/hotkey ?

[Greg Taylor (gtaylor)]

Here's what I found:

gtaylor@gtecra:/proc/acpi/tecra$ ls
aerial displaykey hotkey lcd version video
gtaylor@gtecra:/proc/acpi/tecra$ cat hotkey
Fn hotkey interface: 0
Hotkey stick: 0
Hotkey double press to lock: 0
Docking interface: 0
Hotkey last scan: 0

Pressing function key combinations had no affect on any of the files under the tecra directory. I did a tail -f and watched them all.

[Timothy Smith (tas50)]

Can you test this on Dapper 6.06.1 or Edgy Beta 1 so we can see if the bug still exists?

[Greg Taylor (gtaylor)]

On Edgy, 'xev' doesn't show any output for the hotkeys and /var/log/acpid is also not showing anything new. Should I try the gesal.org driver again?

[Michael Steel (boozezela)]

Hello everyone.

I have a Tecra A4 PTA42E with Bios 1.10 (no new bios is available) and with an integrated ATI X700 (my guess is that Greg has a PTA40 that is slight different).

With Ubuntu 7.10 final, running as a LiveCD I have the following results.

I'm using the following boot paramaters: lapic pci=routeirq

- /var/log/acpid does not record any keypress
- using xfe both Fn+F10 and Fn+11 are incorrectly recorded as "numlock", and keys from the virtual numeric pad are recorded too
- Fn+F5 even if not recorded will try to swith to an external monitor, corrupting the X display (don't if the external display works, I haven't one handy).

Installing the gesal drivers the hotkeys are still dead, anyway during the compile I receive the following warning, maybe the fn keypress is never detected?

      /home/ubuntu/Desktop/tecra_acpi-0.1/tecra_acpi.c: In function ‘read_fn_interface’:
     /home/ubuntu/Desktop/tecra_acpi-0.1/tecra_acpi.c:297: warning: unused variable ‘fn_pressed’

It is anyway possible to change the LCD brightness level echoing values from 0 to 7 in /proc/acpi/tecra/lcd.

if you take a look at /proc/acpi/tecra/aerial you will see that the bluetooth module is considered OFF even if actually it isn't.

Bluetooth adapter: 1
Bluetooth status: 0
Wireless adapter: 1
Wireless status: 1

You can also try the following:

echo 0 > /proc/acpi/tecra/aerial
Turns Bluetooth OFF, turns WIFI OFF

echo 2 > /proc/acpi/tecra/aerial
Turns Bluetooth OFF, turns WIFI ON

echo 1 > /proc/acpi/tecra/aerial
Turns Bluetooth ON, turns WIFI OFF

echo 3 > /proc/acpi/tecra/aerial
Turns Bluetooth ON, turns WIFI ON

But if you change the status of the Bluetooth module, it will stay disabled (I haven't tried to unload and reload all the modules).

Attached you can find the /proc/acpi/dsdt file.

Regards.

[Michael Steel (boozezela)]

Forgot to mention that enabling and disabling the WIFI card modifying /proc/acpi/tecra/aerial works.

[Michael Steel (boozezela)]

Maybe this page could be useful in order to improve Toshibs support:

http://linux.toshiba-dme.co.jp/linux/eng/develop.php3

[Greg Taylor (gtaylor)]

Issue is still present on Ibex stable.

[kernel-janitor (kernel-janitor)]

Hi gtaylor,

This bug was reported while ago and there hasn't been any activity in it recently. We were wondering is this still an issue? Can you try with the latest development release of Ubuntu? (ISO CD images are available from http://cdimage.ubuntu.com/releases/)

If it remains an issue, could you 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-`uname -r` 20727

Also, if you could 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.]

[RivalComp (rival)]

I think it's the same issue as reported in #128320.
https://bugs.launchpad.net/bugs/128320

[rusivi2 (rusivi2-deactivatedaccount)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!