[Toshiba Satellite A660-0T4] Topmost keys all produce the same scancode

[Mouhanad Alkallas]

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.
---
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: mouhanad 1897 F.... pulseaudio
 /dev/snd/controlC0: mouhanad 1897 F.... pulseaudio
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-09-21 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130921)
MachineType: TOSHIBA Satellite A660
MarkForUpload: True
NonfreeKernelModules: nvidia wl
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=c0f8cd4d-48a4-485d-89d7-af4e14df5d34 ro quiet splash
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-8-generic N/A
 linux-backports-modules-3.11.0-8-generic N/A
 linux-firmware 1.114
Tags: saucy
Uname: Linux 3.11.0-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/24/11
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 2.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NWQAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 9
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvr2.30:bd11/24/11:svnTOSHIBA:pnSatelliteA660:pvrPSAW3C-0T4017:rvnTOSHIBA:rnNWQAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A:
dmi.product.name: Satellite A660
dmi.product.version: PSAW3C-0T4017
dmi.sys.vendor: TOSHIBA

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1169386/+editstatus and add the package name in the text box next to the word Package.

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

[Martin Pitt (pitti)]

Can you please follow the steps in /usr/share/doc/udev/README.keymap.txt to give me the scan code / intended meaning mapping and the precise name of your machine? Thanks!

[Martin Pitt (pitti)]

> 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.

What kind of notification is that? a LED on your keyboard, or a popup on the Ubuntu desktop?

[Mouhanad Alkallas (mouhanad12)]

I did as you said- Also noticed you are the other of the file :). Note : in this time frame i updated to ubuntu 13.10

Here is my result.

user@usrer-Satellite-A660:~$ /lib/udev/findkeyboards
AT keyboard: input/event3
Unknown type: input/event8
Unknown type: input/mouse1
--------Then I wrote down what happens with all 15 Fn fuctions----------------------
user@usrer-Satellite-A660:~$ sudo /lib/udev/keymap -i input/event3
Fn-Mute on/off -> works (does not show on terminal)
Fn-Lock -> works (does not show on terminal)
Fn-power option -> works (does not show on terminal) opens up power statistics
Fn-sleep -> works (does not show on terminal)
Fn-hibernate -> works (does not show on terminal)
Fn-change display (extended, duplicate) -> works (does not show on terminal) cycle through display options
Fn-brightness down -> works (does not show on terminal)
Fn-bightness up -> works (does not show on terminal)
Note: To enable brightness on nvidia 'Option "RegistryDwords" "EnableBrightnessControl=1"' was added in xorg.conf
Fn-wifi on/off -> works (does not show on terminal)
Fn-touch pad on/off -> Does not work (does not show on terminal), however button above touchpad does work not the Fn.
Fn-page zoom out-> Does not work (does not show on terminal)
Fn-page zoom in-> Does not work (does not show on terminal)
Fn-volume down-> Does work (does show on terminal)
scan code: 0xAE key code: volumedown
Fn-volume up-> Does work (does show on terminal)
scan code: 0xB0 key code: volumeup
Fn-keyboard backlight on/off -> Does not work (does not show on terminal)

Note: when I do press Fn+z (keyboard backlight) I get a ubuntu notification "notification-keyboard-brightness-high" on the top right hand of the screen.
----------------------------------

http://i.imgur.com/l54s5CP.jpg - Next i tried the keys labelled 3 in this image

Options bar:
Toshiba eco- Nothing happens (outputs on terminal)
got scan code event 0x8D without a key code event
got scan code event 0x8D without a key code event

Wifi on/off- Does toggle wifi (outputs on terminal)
got scan code event 0x8D without a key code event
got scan code event 0x8D without a key code event

Toshiba software- Nothing happens (outputs on terminal)
got scan code event 0x8D without a key code event
got scan code event 0x8D without a key code event

pause/play-Does toggle play (outputs on terminal)
scan code: 0xA2 key code: playpause
got scan code event 0x8D without a key code event
got scan code event 0x8D without a key code event

mute- Does toggle mute (outputs on terminal)
got scan code event 0x8D without a key code event
got scan code event 0x8D without a key code event
scan code: 0xA0 key code: mute

volume down- Does work (outputs on terminal)
got scan code event 0x8D without a key code event
got scan code event 0x8D without a key code event
scan code: 0xAE key code: volumedown

volume up-Does work (outputs on terminal)
got scan code event 0x8D without a key code event
got scan code event 0x8D without a key code event
scan code: 0xB0 key code: volumeup

[Michael (michael-f-shull)]

I have a Toshiba Satellite A665 which has the same bug going back to 10.04. I ran through the keymapping steps mentioned above and have identical results to Mouhanad. If there are any logs or testing I can do to help solve this I'd be happy to help. There's a huge thread in the Ubuntu Forums on this and a few users have found a workaround. By booting into a windows partition/MiniXP from Hiren's Boot CD, and toggling the backlight on, then rebooting into Ubuntu, the backlight will work but BIOS is the only way to turn it off. Plus, you have to repeat the process each time.

[KISS (keepitsimplestupid)]

I'm running UBUNTU 12.04 LTS Live CD and the backlight doesn't work. I have a Toshiba A665-s6057 which normally doesnt come with a backlight KB, but it works under Windows 7.

I have some info that might be of interest and possibly the source of confusion.

The service manual for the A660 series shows a bit called KBLED. It does not, however, tell you what the bit does.

My belief is that the Satellite Logo can be turned on and off and the KB Illumination can be turned On and Off.

It appears that when a backlit KB is detected, the illumination settings appear in the BIOS options.

Toshiba typically does a On/Off or Timed off when you hit a key.

In Windows the touch bar at the top of the keyboard can be completely illuminated or turned off as it is in UBUNTU, I ran Win 7 with the touch bar illuminated. In windows, if you touched, say the wireless button on the touch bar, the wireless button would go off briefly and then return to being on again.

Dunno, if the touch bar and Function events involk the same scan code.

ECO is a mode I really never played with in Windows.

I believe the keyboard Illumination comes on briefly when the laptop is booted from a powered down state.

I'm not in a position to check Win 7 behavior at this point in time. If I remember correctly the behavior of the KB can be set via the BIOS or through a Toshiba provided control panel. Thus there is likely more than one bit that defines the keyboard illumination behavior.

[Joseph J. Pollock (josephj)]

I have a Toshiba Satellite P755 S5182. It works/fails almost identically to the posters above (on kubuntu 12.04). One of the major reasons I selected this notebook was for the backlit keyboard (which works fine on Windows 7 - which I use only when forced to, but not on Linux.)

The main differences I see are 1) no files with illumination" in their names, 2) Fn+Z does not display anything, but the key does have a backlight icon on it.

The toshiba_acpi module is loaded, but lsmod says it's used by none. The source code for it on my machine appears to be very old (2010) 386 code and a cursory scan of it did not show me anything that looked like it had to do with the keyboard backlight, but I'm not much of a C coder these days and I could easily have missed something.

If there is any code to test to diagnose or fix this problem, I'd be happy to help. I really need this feature.

I'm not ready to upgrade to a new distro release any time soon, but I have spare partitions where I can install another (newer) distro for testing purposes.

[Mouhanad Alkallas (mouhanad12)]

I guess it does help to mention that the backlight for the keyboard is directly linked to bios options. So if in windows I turn backlight on than it will change to on in the bios, There is an option for "on" "off" and "timer" in the BIOS. Timer is at default for 15 seconds, Toshiba program allows you to modify that.

Martin Pitt, do you know if anybody is working on it? Or if there is anything we can do?

[Martin Pitt (pitti)]

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.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1169386

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Mouhanad Alkallas (mouhanad12)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/

[Mouhanad Alkallas (mouhanad12)]

kernel-bug-exists-upstream

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Solomon Nadar (solomonsunder)]

I have a similar issue. The Front Operation Panel LED keys do not work on my Toshiba Qosmio F60. These are handled by quickstart it seems which are handled in Windows by PNP0C32 (Direct App Launch)

https://bugs.launchpad.net/ubuntu/+bug/252264

http://sourceforge.net/projects/quickstart/

[madbiologist (me-again)]

This should be fixed in the upcoming upstream 3.20 kernel - see http://lkml.iu.edu/hypermail/linux/kernel/1502.2/02418.html