I'm afraid I have to reassign this back to the kernel. In comment 4 it
is shown that the Fn+Fx keys work, but the topmost keys (labelled "3" in
your image) all generate the same scan code 0x8D, so it's impossible to
assign these to a keycode. These scan codes need to be fixed in the
driver, or it could even be possible that the non-Windows ACPI tables of
these Samsung models are just broken.
The other issue is that the keyboard backlight key produces the correct
keycode, but userspace does not actually handle it. That is tracked in
bug 1203592.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: In Progress => New
** Summary changed:
- [keymap] Toshiba satellite A660: backlight key does not work
+ Toshiba satellite A660: topmost keys all produce the same scancode
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1169386
Title:
Toshiba satellite A660: topmost keys all produce the same scancode
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Toshiba satellite A660 backlight just never worked on ubuntu.
Here is an outline of some of the LEDS in a toshiba
http://i.imgur.com/l54s5CP.jpg
When i press Fn+Z the ubuntu keyboard LED notification shows up,
however nothing changes.
so i navigated to
/sys/devices/pci0000:00/0000:00:1c.4/0000:16:00.0/firmware_node/subsystem/devices/TOS1900:00/leds/toshiba::illumination/device/leds/toshiba::illumination
found files
brightness device max_brightness power subsystem trigger uevent
when i changed the value in brightness from 0 to 1
LED 1, 2, and 3 in the above picture turns on, and led 1 turns off
when touch bad is off.
However there is no keyboard backlight.upon boot the backboard
backlight works while posting and shutdown when grub loads. When i
disable acpi the keyboard backlight works however ill lose other
functionalities like brightness.
Any way to fix it?
There is also another directory.
/sys/devices/pci0000:00/0000:00:1c.4/0000:16:00.0/firmware_node/subsystem/devices/TOS1900:00/leds/toshiba::illumination/device/leds/toshiba::illumination/subsystem/mmc0::
with files brightness device max_brightness power subsystem trigger uevent
nothing happens when brightness value changes.
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
Codename: raring
Linux mouhanad-Satellite-A660 3.8.0-18-generic #28-Ubuntu SMP Thu Apr 11
19:38:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
#Problem also exists in older version of ubuntu, new kernel in 13.04
does not solve the problems.
xev shows a key being pressed and being mapped to kbdbacklight. A a
notification that keyboard is being turned on appears when Fn+Z is
pressed. Also unlike other manufactures toshiba doesn't have
brightness on backlit keyboards, its either on or off or a timer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169386/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
