SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had a little trouble getting my Synaptics touch pad working with Slackware 13 so I decided to take a moment and post the settings. The changed settings from Slackware 12.2 are in bold.
What wasn't too obvious is that the "TapButton1" setting is now required to make tapping the pad produce a mouse click. In Slackware 12.2 that worked without the "TapButton1" setting being specified. I also noticed that the values for "MinSpeed", "MaxSpeed" and "AccelFactor" have to be about 3 times higher in Slackware 13 to produce the same amount of cursor movement as in Slackware 12.2. If your mouse cursor seems slow you probably need to adjust those settings.
This was actually my next post on my "todo" list. Its really annoying when tapping isn't working.
I added the TapButten1 line to xorg.conf (That by the way can be generated using Xorg -config. The output will be /root/xorg.conf.new for every one out there looking for /etc/X11/xorg.conf ), and it worked like a charm on my aspire one.
The "tap to click" feature was disabled by default in the driver itself for any hardware that has real buttons along with the touchpad - this is because for most users (myself included), that "tap to click" is a bug rather than a feature if there are real mouse buttons above/below the touchpad.
Is there any particular reasons why we should enable this in HAL instead of xorg.conf? hal configuration is WAY to ugly for me to start configuring stuff, unless I get some really great extra benefits. I will avoid hal configuration as long as I can.
The "tap to click" feature was disabled by default in the driver itself for any hardware that has real buttons along with the touchpad - this is because for most users (myself included), that "tap to click" is a bug rather than a feature if there are real mouse buttons above/below the touchpad.
On the contrary Rob, I find the the absence of the "tap to click" feature quite annoying - to each his own I guess . Anyway, the important thing is that we have options to turn it on or off .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.