Touchpad on/off and screen brightness Mint16 [SOLVED]

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
dollyp
Level 2
Level 2
Posts: 63
Joined: Sun Jul 24, 2011 4:50 pm

Touchpad on/off and screen brightness Mint16 [SOLVED]

Post by dollyp » Wed Jan 08, 2014 1:44 pm

Although Mint16 KDE recognises the buttons for sound on my Lenovo notebook, the touchpad on/off and brightness +/- keys do not work. How do I make them work? Or what key combinations would bring this functionality? (Mate15 recognised the brightness buttons.)

Not being able to control the touchpad is driving me to despair as it is impossible to type on the keyboard!

Regards
David

UPDATE: See the last post for an updated solution for xfce.
Last edited by dollyp on Thu Mar 27, 2014 11:42 am, edited 2 times in total.

User avatar
roblm
Level 10
Level 10
Posts: 3268
Joined: Sun Feb 24, 2013 2:41 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by roblm » Wed Jan 08, 2014 2:44 pm

Which keys are used with the Fn key to control touchpad on/off and brightness?

Would you open the Terminal and type each command below, pressing Enter after each one:
cat /sys/class/dmi/id/sys_vendor
cat /sys/class/dmi/id/product_name

Then you need to open the Synaptic Package Manager and install evtest.
Then open the Terminal and type: sudo evtest
Copy the screen.

Post all the results.

dollyp
Level 2
Level 2
Posts: 63
Joined: Sun Jul 24, 2011 4:50 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by dollyp » Wed Jan 08, 2014 5:55 pm

roblm wrote:Which keys are used with the Fn key to control touchpad on/off and brightness?
Touchpad on/off: <Fn>F6
Brightness up: <Fn>F12
Brightness dn: <Fn>F11
(<Fn> is the key immediately to the right of <Ctrl>)
Would you open the Terminal and type each command below, pressing Enter after each one:
cat /sys/class/dmi/id/sys_vendor
cat /sys/class/dmi/id/product_name
LENOVO Ideapad U410
Then you need to open the Synaptic Package Manager and install evtest.
Then open the Terminal and type: sudo evtest
Copy the screen.
Post all the results.
Result:

Code: Select all

david@david-Lenovo-U410:~ > sudo evtest
[sudo] password for david: 
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      Lid Switch
/dev/input/event1:      Power Button
/dev/input/event2:      Power Button
/dev/input/event3:      AT Translated Set 2 keyboard
/dev/input/event4:      Logitech Unifying Device. Wireless PID:400a
/dev/input/event5:      Video Bus
/dev/input/event6:      Video Bus
/dev/input/event7:      Ideapad extra buttons
/dev/input/event8:      HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event9:      HDA Intel PCH Headphone
/dev/input/event10:     HDA Intel PCH Mic
/dev/input/event11:     Lenovo EasyCamera
/dev/input/event12:     SynPS/2 Synaptics TouchPad
Select the device event number [0-12]:
Hope this helps

David

User avatar
roblm
Level 10
Level 10
Posts: 3268
Joined: Sun Feb 24, 2013 2:41 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by roblm » Wed Jan 08, 2014 6:10 pm

Open the Terminal and again type: sudo evtest
Type the number 7 in the bottom line that says “Select the device event number” and press Enter.
This is the event number of the “Ideapad extra buttons” device.

Then press the Fn+key combinations that don't work correctly, which are Fn+F6, Fn+F11, and Fn+F12. Then press Ctrl+Z to
stop the program. Use the cursor to select all the information on the Terminal screen from the end to the beginning and copy it.
Then post the output by selecting “code” in the Mint forum reply window menu and pasting the info between the two code words.

dollyp
Level 2
Level 2
Posts: 63
Joined: Sun Jul 24, 2011 4:50 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by dollyp » Thu Jan 09, 2014 10:46 am

roblm wrote:Open the Terminal and again type: sudo evtest
Type the number 7 in the bottom line that says “Select the device event number” and press Enter.
This is the event number of the “Ideapad extra buttons” device.

Then press the Fn+key combinations that don't work correctly, which are Fn+F6, Fn+F11, and Fn+F12. Then press Ctrl+Z to
stop the program. Use the cursor to select all the information on the Terminal screen from the end to the beginning and copy it.
Then post the output by selecting “code” in the Mint forum reply window menu and pasting the info between the two code words.
I'm very grateful for your help with this. The output:

Code: Select all

david@david-Lenovo-U410:~ > sudo evtest
[sudo] password for david: 
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      Lid Switch
/dev/input/event1:      Power Button
/dev/input/event2:      Power Button
/dev/input/event3:      AT Translated Set 2 keyboard
/dev/input/event4:      Logitech Unifying Device. Wireless PID:400a
/dev/input/event5:      Video Bus
/dev/input/event6:      Video Bus
/dev/input/event7:      Ideapad extra buttons
/dev/input/event8:      HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event9:      HDA Intel PCH Headphone
/dev/input/event10:     HDA Intel PCH Mic
/dev/input/event11:     Lenovo EasyCamera
/dev/input/event12:     SynPS/2 Synaptics TouchPad
Select the device event number [0-12]: 7
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
Input device name: "Ideapad extra buttons"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 148 (KEY_PROG1)
    Event code 149 (KEY_PROG2)
    Event code 186 (KEY_F16)
    Event code 192 (KEY_F22)
    Event code 193 (KEY_F23)
    Event code 202 (KEY_PROG3)
    Event code 203 (KEY_PROG4)
    Event code 212 (KEY_CAMERA)
    Event code 227 (KEY_SWITCHVIDEOMODE)
    Event code 238 (KEY_WLAN)
    Event code 240 (KEY_UNKNOWN)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
^Z
[1]+  Stopped                 sudo evtest
[148]david@david-Lenovo-U410:~ > 
Nothing at all happened when I pressed the key combinations Fn+F6, Fn+F11 or Fn+F112. Interestingly I redid the test using the Fn+F1 to Fn+F3, which control sound and do work, and there was no output in Konsole but the correct popups appeared on screen.

David

User avatar
roblm
Level 10
Level 10
Posts: 3268
Joined: Sun Feb 24, 2013 2:41 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by roblm » Thu Jan 09, 2014 1:42 pm

Would you repeat the steps with evtest but this time type 3 in the bottom line for the event number. This is for the AT keyboard.

dollyp
Level 2
Level 2
Posts: 63
Joined: Sun Jul 24, 2011 4:50 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by dollyp » Thu Jan 09, 2014 4:01 pm

roblm wrote:Would you repeat the steps with evtest but this time type 3 in the bottom line for the event number. This is for the AT keyboard.

Code: Select all

david@david-Lenovo-U410:~ > sudo evtest
[sudo] password for david: 
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      Lid Switch
/dev/input/event1:      Power Button
/dev/input/event2:      Power Button
/dev/input/event3:      AT Translated Set 2 keyboard
/dev/input/event4:      Logitech Unifying Device. Wireless PID:400a
/dev/input/event5:      Video Bus
/dev/input/event6:      Video Bus
/dev/input/event7:      Ideapad extra buttons
/dev/input/event8:      HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event9:      HDA Intel PCH Headphone
/dev/input/event10:     HDA Intel PCH Mic
/dev/input/event11:     Lenovo EasyCamera
/dev/input/event12:     SynPS/2 Synaptics TouchPad
Select the device event number [0-12]: 3
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab41
Input device name: "AT Translated Set 2 keyboard"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 1 (KEY_ESC)
    Event code 2 (KEY_1)
    Event code 3 (KEY_2)
    Event code 4 (KEY_3)
    Event code 5 (KEY_4)
    Event code 6 (KEY_5)
    Event code 7 (KEY_6)
    Event code 8 (KEY_7)
    Event code 9 (KEY_8)
    Event code 10 (KEY_9)
    Event code 11 (KEY_0)
    Event code 12 (KEY_MINUS)
    Event code 13 (KEY_EQUAL)
    Event code 14 (KEY_BACKSPACE)
    Event code 15 (KEY_TAB)
    Event code 16 (KEY_Q)
    Event code 17 (KEY_W)
    Event code 18 (KEY_E)
    Event code 19 (KEY_R)
    Event code 20 (KEY_T)
    Event code 21 (KEY_Y)
    Event code 22 (KEY_U)
    Event code 23 (KEY_I)
    Event code 24 (KEY_O)
    Event code 25 (KEY_P)
    Event code 26 (KEY_LEFTBRACE)
    Event code 27 (KEY_RIGHTBRACE)
    Event code 28 (KEY_ENTER)
    Event code 29 (KEY_LEFTCTRL)
    Event code 30 (KEY_A)
    Event code 31 (KEY_S)
    Event code 32 (KEY_D)
    Event code 33 (KEY_F)
    Event code 34 (KEY_G)
    Event code 35 (KEY_H)
    Event code 36 (KEY_J)
    Event code 37 (KEY_K)
    Event code 38 (KEY_L)
    Event code 39 (KEY_SEMICOLON)
    Event code 40 (KEY_APOSTROPHE)
    Event code 41 (KEY_GRAVE)
    Event code 42 (KEY_LEFTSHIFT)
    Event code 43 (KEY_BACKSLASH)
    Event code 44 (KEY_Z)
    Event code 45 (KEY_X)
    Event code 46 (KEY_C)
    Event code 47 (KEY_V)
    Event code 48 (KEY_B)
    Event code 49 (KEY_N)
    Event code 50 (KEY_M)
    Event code 51 (KEY_COMMA)
    Event code 52 (KEY_DOT)
    Event code 53 (KEY_SLASH)
    Event code 54 (KEY_RIGHTSHIFT)
    Event code 55 (KEY_KPASTERISK)
    Event code 56 (KEY_LEFTALT)
    Event code 57 (KEY_SPACE)
    Event code 58 (KEY_CAPSLOCK)
    Event code 59 (KEY_F1)
    Event code 60 (KEY_F2)
    Event code 61 (KEY_F3)
    Event code 62 (KEY_F4)
    Event code 63 (KEY_F5)
    Event code 64 (KEY_F6)
    Event code 65 (KEY_F7)
    Event code 66 (KEY_F8)
    Event code 67 (KEY_F9)
    Event code 68 (KEY_F10)
    Event code 69 (KEY_NUMLOCK)
    Event code 70 (KEY_SCROLLLOCK)
    Event code 71 (KEY_KP7)
    Event code 72 (KEY_KP8)
    Event code 73 (KEY_KP9)
    Event code 74 (KEY_KPMINUS)
    Event code 75 (KEY_KP4)
    Event code 76 (KEY_KP5)
    Event code 77 (KEY_KP6)
    Event code 78 (KEY_KPPLUS)
    Event code 79 (KEY_KP1)
    Event code 80 (KEY_KP2)
    Event code 81 (KEY_KP3)
    Event code 82 (KEY_KP0)
    Event code 83 (KEY_KPDOT)
    Event code 85 (KEY_ZENKAKUHANKAKU)
    Event code 86 (KEY_102ND)
    Event code 87 (KEY_F11)
    Event code 88 (KEY_F12)
    Event code 89 (KEY_RO)
    Event code 90 (KEY_KATAKANA)
    Event code 91 (KEY_HIRAGANA)
    Event code 92 (KEY_HENKAN)
    Event code 93 (KEY_KATAKANAHIRAGANA)
    Event code 94 (KEY_MUHENKAN)
    Event code 95 (KEY_KPJPCOMMA)
    Event code 96 (KEY_KPENTER)
    Event code 97 (KEY_RIGHTCTRL)
    Event code 98 (KEY_KPSLASH)
    Event code 99 (KEY_SYSRQ)
    Event code 100 (KEY_RIGHTALT)
    Event code 102 (KEY_HOME)
    Event code 103 (KEY_UP)
    Event code 104 (KEY_PAGEUP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 107 (KEY_END)
    Event code 108 (KEY_DOWN)
    Event code 109 (KEY_PAGEDOWN)
    Event code 110 (KEY_INSERT)
    Event code 111 (KEY_DELETE)
    Event code 112 (KEY_MACRO)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 117 (KEY_KPEQUAL)
    Event code 118 (KEY_KPPLUSMINUS)
    Event code 119 (KEY_PAUSE)
    Event code 121 (KEY_KPCOMMA)
    Event code 122 (KEY_HANGUEL)
    Event code 123 (KEY_HANJA)
    Event code 124 (KEY_YEN)
    Event code 125 (KEY_LEFTMETA)
    Event code 126 (KEY_RIGHTMETA)
    Event code 127 (KEY_COMPOSE)
    Event code 128 (KEY_STOP)
    Event code 140 (KEY_CALC)
    Event code 142 (KEY_SLEEP)
    Event code 143 (KEY_WAKEUP)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 157 (KEY_COMPUTER)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 166 (KEY_STOPCD)
    Event code 172 (KEY_HOMEPAGE)
    Event code 173 (KEY_REFRESH)
    Event code 183 (KEY_F13)
    Event code 184 (KEY_F14)
    Event code 185 (KEY_F15)
    Event code 191 (KEY_F21)
    Event code 212 (KEY_CAMERA)
    Event code 217 (KEY_SEARCH)
    Event code 224 (KEY_BRIGHTNESSDOWN)
    Event code 225 (KEY_BRIGHTNESSUP)
    Event code 226 (KEY_MEDIA)
    Event code 245 (KEY_DISPLAY_OFF)
    Event code 247 (KEY_RFKILL)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
  Event type 17 (EV_LED)
    Event code 0 (LED_NUML)
    Event code 1 (LED_CAPSL)
    Event code 2 (LED_SCROLLL)
Properties:
  Property type 20 (EV_REP)
    Property code 0 (REP_DELAY)
      Value    250
    Property code 1 (REP_PERIOD)
      Value     33
Testing ... (interrupt to exit)
Event: time 1389297506.761755, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1c
Event: time 1389297506.761755, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1389297506.761755, -------------- SYN_REPORT ------------
Event: time 1389297530.077464, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1389297530.077464, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1389297530.077464, -------------- SYN_REPORT ------------
Event: time 1389297530.341407, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1389297530.341407, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 2
Event: time 1389297530.341407, -------------- SYN_REPORT ------------
Event: time 1389297530.378390, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1389297530.378390, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 2
Event: time 1389297530.378390, -------------- SYN_REPORT ------------
Event: time 1389297530.394097, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2c
Event: time 1389297530.394097, type 1 (EV_KEY), code 44 (KEY_Z), value 1
Event: time 1389297530.394097, -------------- SYN_REPORT ------------
^Z
[1]+  Stopped                 sudo evtest
[148]david@david-Lenovo-U410:~ > 
Again, pressing the Fn F keys did not produce any output, but the info produced looks more hopeful.

Regards
David

User avatar
roblm
Level 10
Level 10
Posts: 3268
Joined: Sun Feb 24, 2013 2:41 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by roblm » Thu Jan 09, 2014 5:25 pm

Unfortunately no scan codes were generated when you pressed the special keys. Without them we can't go to the next step.
I would like to try another utility to get scan codes. Press Ctrl+Alt+F1 to enter the tty1 virtual console and then type this
command and press Enter: showkey -s

Press Fn+F6, Fn+F11 and Fn+F12
Wait 10 seconds for the program to end.

Then type this command to get a screenshot: sudo screendump 1 > screenoutput.txt
The file “screenshot.txt” will be found in your /home/user-name directory.

dollyp
Level 2
Level 2
Posts: 63
Joined: Sun Jul 24, 2011 4:50 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by dollyp » Fri Jan 10, 2014 4:17 pm

Output was:

Code: Select all

Linux Mint 16 Petra david-Lenovo-U410 tty1
david-Lenovo-U410 login: david
Password:
Last login: Fri Jan 10 17:27:45 GMT 2014 on tty1
david@david-Lenovo-U410:~ > showkey -s
kb mode was UNICODE
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]

press any key (program terminates 10s after last keypress)...
0x9c
0xe0 0x4c 0xe0 0xcc
0xe0 0x4c 0xe0 0xcc
0xe0 0x54 0xe0 0xd4
david@david-Lenovo-U410:~ > showkey -s
kb mode was UNICODE
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]

press any key (program terminates 10s after last keypress)...
0x9c
0x3e
0xbe
0x3e
0xbe
david@david-Lenovo-U410:~ > sudo screendump 1 > screenoutput.txt
[sudo] password for david:
Showkey produced no output from Fn+F6 despite several tries. Fn+F11 that ends 0xcc appears twice because I'm too slow and the key repeats very fast. Given that there is no output for Fn+F6 I ran showkey a second time and produced the output for Fn+F4 (again twice) as that could be an alternative key for turning the pad off and on.

Thanks for your continued interest in this.

Regards
David

User avatar
roblm
Level 10
Level 10
Posts: 3268
Joined: Sun Feb 24, 2013 2:41 pm

Re: Touchpad on/off and screen brightness in KDE (Mint16)

Post by roblm » Fri Jan 10, 2014 10:10 pm

The scan codes generated when you pressed Fn+F4 don't look right, so it probably won't work.
For Fn+F11 the codes were: 0xe0 0x4c 0xe0 0xcc. This is how it should look.
For Fn+F4 the codes were: 0x3e 0xbe

Copy the following lines. They contain the scan codes generated by showkey:

Code: Select all

# Lenovo Ideapad U410 
keyboard:name:Ideapad extra buttons:dmi:bvn*:bvr*:bd*:svnLENOVO*:pnIdeapad*U410:pvr*
KEYBOARD_KEY_be=touchpad_toggle      # Fn+F4  
KEYBOARD_KEY_cc=brightnessdown	       # Fn+F11	
KEYBOARD_KEY_d4=brightnessup	       # Fn+F12
Open the file “60-keyboard.hwdb” with this command in the Terminal:
gksudo kate /lib/udev/hwdb-d/60-keyboard.hwdb EDITED: should be: gksudo kate /lib/udev/hwdb.d/60-keyboard.hwdb
Go down to the Lenovo section and paste the lines at the bottom of it just before the Logitech section.
So your file will look like this:

Code: Select all

# IdeaPad
keyboard:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*IdeaPad*U300s*:pvr*
KEYBOARD_KEY_f1=f21
KEYBOARD_KEY_ce=f20

# Lenovo Ideapad U410 
keyboard:name:Ideapad extra buttons:dmi:bvn*:bvr*:bd*:svnLENOVO*:pnIdeapad*U410:pvr*
KEYBOARD_KEY_be=touchpad_toggle      # Fn+F4  
KEYBOARD_KEY_cc=brightnessdown	       # Fn+F11	
KEYBOARD_KEY_d4=brightnessup	       # Fn+F12

###########################################################
# Logitech
###########################################################
Save the file and then open the Terminal and type: sudo udevadm hwdb --update
Reboot and test the keyboard keys. If that fails then change the word in the second line, at the end, from pnIdeapad to pnIdeaPad.
Repeat saving the file and updating.

If that fails then repeat the steps with these lines:

Code: Select all

# Lenovo Ideapad U410 
keyboard:dmi:bvn*:bvr*:bd*:svnLENOVO*:pnIdeapad*U410:pvr*
KEYBOARD_KEY_be=touchpad_toggle      # Fn+F4  
KEYBOARD_KEY_cc=brightnessdown	       # Fn+F11	
KEYBOARD_KEY_d4=brightnessup	       # Fn+F12
If that fails then change the word in the second line, at the end, from pnIdeapad to pnIdeaPad

If that fails then you can change the scan codes in these lines:

Code: Select all

KEYBOARD_KEY_be=touchpad_toggle      # Fn+F4
KEYBOARD_KEY_cc=brightnessdown	       # Fn+F11	
KEYBOARD_KEY_d4=brightnessup	       # Fn+F12
to these:

Code: Select all

KEYBOARD_KEY_3e=touchpad_toggle     #Fn+F4  
KEYBOARD_KEY_4c=brightnessdown	       # Fn+F11	
KEYBOARD_KEY_54=brightnessup	       # Fn+F12
If you have a startup problem then restart and at the GRUB boot menu select “Recovery mode”.
If no menu shows then hold down the shift key while starting. In the menu go down to the line that starts with “root”. When asked
for the root password, just type your user password. Change the file permissions to read and write by typing this command:
mount --options remount,rw /
Then type: nano /lib/udev/hwdb-d/60-keyboard.hwdb EDITED: should be: nano /lib/udev/hwdb.d/60-keyboard.hwdb
Remove the lines that were added. Press Ctrl+X. Type “Y” for Yes. Press Enter. Type “exit”. Select “resume”.
Last edited by roblm on Sun Jan 12, 2014 9:29 pm, edited 1 time in total.

dollyp
Level 2
Level 2
Posts: 63
Joined: Sun Jul 24, 2011 4:50 pm

Touchpad on/off and screen brightness in KDE (Mint16) [SOLVE

Post by dollyp » Sun Jan 12, 2014 5:24 pm

Hi roblm

Many thanks for your help. The first part of your reply worked and I now have the brightness keys working as they should. The attempt to make Fn+F4 toggle the touchpad did not work but oddly Fn+F6 now works as it should. So my problem is now solved. I will keep your notes for future use when I have to reinstall.

Again my thanks
David

For anyone following:

roblm's instruction

Code: Select all

Open the file “60-keyboard.hwdb” with this command in the Terminal:
gksudo kate /lib/udev/hwdb-d/60-keyboard.hwdb

This leads to a new file on my system. I had to go find the file in Dolphin and open it with Kate. I also had to change the file permissions in Dolphin through right click>root actions>ownership to active user menu option in order to be able to save the changes.

User avatar
roblm
Level 10
Level 10
Posts: 3268
Joined: Sun Feb 24, 2013 2:41 pm

Re: Touchpad on/off and screen brightness Mint16kde [SOLVED]

Post by roblm » Sun Jan 12, 2014 9:24 pm

David,

I found out why you had trouble opening the “60-keyboard.hwdb” file. I made a mistake in the path to the file. It should be
“/lib/udev/hwdb.d”, not “/lib/udev/hwdb-d”. I'm surprised everything still worked. You should add the scan code lines to the file
in the correct location and delete the other one. I edited my last post.

I assume the text editor Kate is spelled with a small letter "k" when used in a command?

For your information and others trying to use showkey to get scan codes, looking at the scan code when Fn+F11 was pressed
generated: 0xe0 0x4c 0xe0 0xcc
Pressing the keys generated: 0xe0 0x4c
Releasing the keys generated: 0xe0 0xcc
The 0xe0 is just a so called prefix. The release code 0xcc is used but the 0x is dropped, giving the scan code: cc
This is only for Mint 16.

Also, in case you have another situation where you can't disable the touchpad while typing, open the Terminal (Konsole) and
type this command: synclient PalmDetect=1

It can be tested immediately and if it works then it can be added to a startup program. Mint Cinnamon has Startup Applications
but I'm not sure if KDE has a similar program.

dollyp
Level 2
Level 2
Posts: 63
Joined: Sun Jul 24, 2011 4:50 pm

Re: Touchpad on/off and screen brightness Mint16kde [SOLVED]

Post by dollyp » Mon Jan 13, 2014 9:57 am

roblm wrote: Also, in case you have another situation where you can't disable the touchpad while typing, open the Terminal (Konsole) and
type this command: synclient PalmDetect=1
Thanks roblm

This is good to know. As a practical measure I'm also concerned that I can enable the touchpad in a situation where the mouse is faulty and I need to enable the touchpad to gain access to the laptop. Would I be right to assume that synclient PalmDetect=0 would reenable it?

Regards David

User avatar
roblm
Level 10
Level 10
Posts: 3268
Joined: Sun Feb 24, 2013 2:41 pm

Re: Touchpad on/off and screen brightness Mint16kde [SOLVED]

Post by roblm » Mon Jan 13, 2014 8:56 pm

David,

The command "synclient PalmDetect=1" doesn't actually disable normal touchpad functions. It prevents accidental touches of
the user's palm while typing from registering as touchpad events. It's monitoring for wider areas of contact instead of just the
finger tips. So if you type the command “synclient PalmDetect=0”, then you'll have the same problem trying to type as you
described in your first post, unless you disable the touchpad with Fn+F6.

dollyp
Level 2
Level 2
Posts: 63
Joined: Sun Jul 24, 2011 4:50 pm

Re: Touchpad on/off and screen brightness Mint16kde [SOLVED]

Post by dollyp » Thu Mar 27, 2014 11:38 am

For anyone finding this post, shortly after the above discussion I reinstalled Mint 16 but with the XFCE desktop. The touchpad toggle didn't work and neither did the code shown above. I eventually found a clue on a Ubuntu forum post and here is the sequence:

Code: Select all

gksu gedit /lib/udev/hwdb.d/60-keyboard.hwdb
Scroll down to the Lenovo section and add the following lines:

Code: Select all

# IdeaPad U410
keyboard:dmi:bvn*:bvr*:svnLENOVO*:pn*IdeaPad*U410*:pvr*
 KEYBOARD_KEY_be=!touchpad_toggle
After saving update the udev hwdb by executing

Code: Select all

sudo udevadm hwdb --update
Restart.

Regards
David

Post Reply

Return to “Hardware Support”