LinuxQuestions.org - [SOLVED] Slackpkg kernel upgrade has borked Tap-to-Click on Touchpad

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackpkg kernel upgrade has borked Tap-to-Click on Touchpad (https://www.linuxquestions.org/questions/slackware-14/slackpkg-kernel-upgrade-has-borked-tap-to-click-on-touchpad-740592/)

[SOLVED] Slackpkg kernel upgrade has borked Tap-to-Click on Touchpad [SOLVED]

Hello Everyone,

Had a kernel upgrade to 2.6.29.6 today and after restarting I no longer have tap-to-click on my laptop touchpad. I know this is the Synaptics driver and it has always worked right away with every version of Slack I have used. I understand that xorg.conf is no longer being read by the system (unless I am mistaken), so I am not sure how to restore this.

Can anyone help?

Thanks in advance,

Bob

SOLVED

I guess I was incorrect. Editing the xorg.conf does still work for this kind of problem and I was able to solve the problem. Sorry for posting so quick...

But I am curious, does synclient get all of its parameters from xorg, or is it possible to edit these parameters outside of xorg? I saw the problem right away from synclient -l, but couldn't edit it.

Thanks
Bob

Have a look at the /usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi file ;)

What I added (then rebooted to make sure it is taken into account):

Code:

<merge key="input.x11_options.TapButton1" type="string">1</merge>

<merge key="input.x11_options.TapButton2" type="string">2</merge>

<merge key="input.x11_options.TapButton3" type="string">3</merge>

<!--Enable vertical scrolling when dragging with two fingers anywhere on the touchpad-->

<merge key="input.x11_options.VertTwoFingerScroll" type="string">false</merge>

Bob,

Mark [SOLVED] on the OP.

Quote:

Originally Posted by appzer0 (Post 3610172)

Have a look at the /usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi file ;)

What I added (then rebooted to make sure it is taken into account):

Code:

<merge key="input.x11_options.TapButton1" type="string">1</merge>

<merge key="input.x11_options.TapButton2" type="string">2</merge>

<merge key="input.x11_options.TapButton3" type="string">3</merge>

<!--Enable vertical scrolling when dragging with two fingers anywhere on the touchpad-->

<merge key="input.x11_options.VertTwoFingerScroll" type="string">false</merge>

You shouldn't edit the fdi files in /usr/share directly. It's preferable to copy them to /etc first and then edit those files.
That way you will have a backup of the original, in case anything goes wrong.

I got this also i don't know how it happend but after the upgrade i had the file /etc/modprobe.d/psmouse~.conf that had the "options psmouse proto=imps" line uncommented.
So i needed to remove that file.

Quote:

Originally Posted by Nille_kungen (Post 3611085)

If you're going to run -current, you're obligated to read the ChangeLog.txt:

Code:

mingdao@paul:~$ less /backup2/ftp/pub/Linux/Slackware/slackware-current/ChangeLog.txt

+--------------------------+

Wed Jul 15 20:51:29 CDT 2009

<snip>

a/udev-141-i486-3.txz:  Rebuilt.  Added aic94xx to /etc/modprobe.d/blacklist.

  Change config files in /etc/modprobe.d/ to use a .conf suffix in preparation

  for newer versions of module-init-tools.

  Let the psmouse module load with the default kernel configuration, rather

  than forcing proto=imps.  If this causes problems with your KVM, uncomment

  the line in /etc/modprobe.d/psmouse.

So now you know you should have commented that line, rather than removing the
entire file. What are you going to do when module-init-tools is updated?

I did read the ChangeLog.txt and thats not the same thing as i described.
I had the /etc/modprobe.d/psmouse.conf thats correct but there was also an /etc/modprobe.d/psmouse~.conf that shouldn't be there that had the line uncommented.
The /etc/modprobe.d/psmouse.conf in current has "options psmouse proto=imps" commented out so there shouldn't be any need to comment out that line.
So i posted that i got an rubbish file when i updated current last time and someone else might have the same problem.

You might have a "rubbish file" because you did something incorrectly in the upgrade.

Here are three boxen with the latest Slackware64 -current and Slackware -current
updates that you describe. None has a /etc/modprobe.d/psmouse~.conf file.

Code:

mahui@china:~$ ls -l /etc/modprobe.d/

total 20

-rw-r--r-- 1 root root 6251 2009-07-15 10:38 blacklist.conf

-rw-r--r-- 1 root root  443 2009-04-21 07:01 isapnp.conf

lrwxrwxrwx 1 root root  16 2009-07-10 21:37 modprobe.conf -> ../modprobe.conf

-rw-r--r-- 1 root root  265 2009-07-15 11:54 psmouse.conf

-rw-r--r-- 1 root root  244 2008-12-01 10:00 usb-controller.conf

mahui@china:~$ cat /etc/modprobe.d/psmouse.conf

# PS/2 mouse support:

# The default options when the psmouse module can cause problems with KVM

# switches.  If you experience this, you may want to uncomment the line

# below to use a more basic mouse protocol with the psmouse module:

#options psmouse proto=imps



mahui@china:~$

Code:

mingdao@silas64:~$ ls -l /etc/modprobe.d/

total 24

-rw-r--r-- 1 root root 6251 2009-07-15 10:38 blacklist.conf

-rw-r--r-- 1 root root  443 2009-04-21 07:01 isapnp.conf

lrwxrwxrwx 1 root root  16 2009-06-26 01:59 modprobe.conf -> ../modprobe.conf

-rw-r--r-- 1 root root  265 2009-07-15 11:54 psmouse.conf

-rw-r--r-- 1 root root  64 2009-06-26 19:40 sound.conf

-rw-r--r-- 1 root root  244 2008-12-01 10:00 usb-controller.conf

mingdao@silas64:~$ cat /etc/modprobe.d/psmouse.conf

# PS/2 mouse support:

# The default options when the psmouse module can cause problems with KVM

# switches.  If you experience this, you may want to uncomment the line

# below to use a more basic mouse protocol with the psmouse module:

#options psmouse proto=imps



mingdao@silas64:~$

Code:

mingdao@jeremiah:~$ ls -l /etc/modprobe.d/

total 32

-rw-r--r-- 1 root root 6250 2009-07-17 10:40 blacklist.conf

-rw-r--r-- 1 root root 6267 2009-07-17 10:32 blacklist.conf~

-rw-r--r-- 1 root root  39 2009-07-17 12:15 bluetooth.conf

-rw-r--r-- 1 root root  443 2009-04-21 07:01 isapnp.conf

lrwxrwxrwx 1 root root  16 2009-07-14 00:19 modprobe.conf -> ../modprobe.conf

-rw-r--r-- 1 root root  265 2009-07-15 11:54 psmouse.conf

-rw-r--r-- 1 root root  244 2008-12-01 10:00 usb-controller.conf

mingdao@jeremiah:~$ cat /etc/modprobe.d/psmouse.conf

# PS/2 mouse support:

# The default options when the psmouse module can cause problems with KVM

# switches.  If you experience this, you may want to uncomment the line

# below to use a more basic mouse protocol with the psmouse module:

#options psmouse proto=imps



mingdao@jeremiah:~$

My box didn't have that "rubbish file" before i ran 'slackpkg update gpg' 'slackpkg update' and 'slackpkg upgrade-all'.
And this box isn't upgraded from 12.2 it's an relative fresh install of current.(2009-06-24)