So are you saying that if the whole word “Satellite” is not in capital letters then the brightness keys don't work? I was
wondering about that myself when I asked you to get the output of this command:
and the result was: SATELLITE C75-A
which is all in capital letters, but if you look in the “60-keyboard.hwdb” file there are four Toshiba laptop models listed and
only one of them has the word in all capital letters.
I guess the reason I didn't mention the update command is because I was still thinking too much about the previous method
used to solve these kind of problems. That method also has a command to update the system but it was only needed to get
an immediate update without rebooting, otherwise upon rebooting the update took place automatically. A big problem for me
is that I don't have a laptop to do this kind of testing.
In the other post tato11 also said that when he pressed the keys for brightness control then “switchvideomode” was also activated.
This didn't happen to you?
I noticed that you changed the lines for the scan codes 13e and 13f to the lines tato11 used. If you look at the output from running
evtest in your third post:
Code: Select all
Event: time 1389015640.465468, type 4 (EV_MSC), code 4 (MSC_SCAN), value 13e
Event: time 1389015640.465468, type 1 (EV_KEY), code 205 (KEY_SUSPEND), value 1
Code: Select all
Event: time 1389015700.085980, type 4 (EV_MSC), code 4 (MSC_SCAN), value 13f
Event: time 1389015700.085980, type 1 (EV_KEY), code 227 (KEY_SWITCHVIDEOMODE), value 1
the scan code 13e was mapped to the keycode 205 which is SUSPEND, and the scan code 13f was mapped to the keycode 227,
which is SWITCHVIDEOMODE. Were these functions not working with the original setting?
I rechecked tato11's topic and I think I found out how he decided on the syntax to use on the line:
keyboard:name:Toshiba input device:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSatelliteS75D-A:pvr*
after looking at his second post after running the command:
sudo udevadm info --export-db > Escritorio/udev-db.txt
If you have some extra time could you do this procedure. It may help in solving these kind of problems. Repeat typing
“sudo evtest” in the Terminal and typing the event number, but don't press any keys. Press Ctrl+Z to stop the program.
Then type this command to generate a device dump: udevadm info --export-db > /tmp/udev-db.txt
Then open the file “udev-db.txt” with this command: gedit /tmp/udev-db.txt
Press Ctrl+A to select the whole file and copy it. Post the output.