[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#655621: linux-image-3.1.0-1-amd64: ALT - ALT GR -2 and others are not recognized in toshiba Satellite Pro L300 keyboard

On Fri, Jan 13, 2012 at 5:57 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
On Thu, 2012-01-12 at 21:08 +0100, Javier Barroso wrote:
> Package: linux-2.6
>  Version: 3.1.8-2
>  Severity: normal
>  Hi,
>  showkey nor xev show nothing when I type "ALT - ALT GR - 2" (and
> nothing too
>  with "ALT - ALT GR - 1"), I would like to
>  use complete-hostname bash functionality with the default key combo.
> "ALT - ALT
>  GR - 3" is working
>  I'm attaching image from my keys because this behaviour could be
> caused by
>  extra function associated to that keys (it is like magnifiers keys).
> I'm attaching too showkey output when I type "ALT-ALT GR - 3" and then
> try "ALT-ALT GR -2"
>  Please reassign this bug to other package if this issue is not
> directly
>  related to kernel

It probably does need to be fixed in the kernel.  If these
key-combinations are special then I would expect the toshiba_acpi driver
should probably handle them.  However, the driver hasn't been loaded on
your system, and since this model appears to be a few years old I
suspect this is not just a case of adding a new device ID to the driver
- there is probably some protocol difference.

You could try running 'acpi_listen' (as root) and then pressing those
keys to see whether it reports any events.  However, I don't know
whether acpi_listen will receive any events that are not recognised by
the kernel.

I'm not sure, if you are not ok with CC, please tell me

Thank you very much, acpi_listen didn't help, and module won't load in my computer:

insmod /lib/modules/3.1.0-1-amd64/kernel/drivers/platform/x86/toshiba_acpi.ko
insmod: error inserting '/lib/modules/3.1.0-1-amd64/kernel/drivers/platform/x86/toshiba_acpi.ko': -1 No such device

But I discover keymaps udev rules, though there is not one for my laptop:

Maybe I need to load a different keymap ... but I have to investigate how udev does that ...

Thank you again.


Reply to: