mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Gene Heskett" <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Touchpad problems with latest kernels
Date: Mon, 14 Aug 2006 11:53:04 -0400	[thread overview]
Message-ID: <d120d5000608140853t5a27b522ra7b29aeb0e318efa@mail.gmail.com> (raw)
In-Reply-To: <200608141134.32714.gene.heskett@verizon.net>

On 8/14/06, Gene Heskett <gene.heskett@verizon.net> wrote:
> On Monday 14 August 2006 11:13, Dmitry Torokhov wrote:
> >HI Gene,
> >
> >On 8/14/06, Gene Heskett <gene.heskett@verizon.net> wrote:
> >> I'm having similar problems with an HP Pavilian dv5220, and with a
> >> bluetooth mouse dongle plugged into the right side usb port it works
> >> just fine.  What I'd like to do is totally disable that synaptics pad
> >> as its way too sensitive,
> >
> >Are you using synaptics X driver? It can be tweaked to adjust
> >sensitivity and lots of other things.
>
> No, I've tried to totally disable any references to it in the xorg.conf.
> Unsuccessfully it would appear, even so far as to say no effect from doing
> so.

Ok, so you are most likely using mousedev emulation mode. Not the best
choice with ALPS/Synaptics. I recommend usig specialized driver for X
(see below).

>
> >> making it impossible to type more than a line or 2
> >> without the cursor suddenly jumping to someplace else in the message,
> >> often highliteing several lines of text as it goes, and the next
> >> keystroke then deletes wholesale quantities of text, thoroughly
> >> destroying any chance of actually writing a cogent, understandable
> >> email response to anyone.
> >
> >Have you tried synclient utility? It temporarily disables the touchpad
> >when you start typing and re-enables it when you done.
> >
> Its not installed that I know of.  Availability?
>

http://web.telia.com/~u89404340/touchpad/
It is a part of Synaptics X driver. And I apologize, it is called
syndaemon, not synclient.

> >> Unforch, my questions along those lines have been treated as the
> >> ravings of a lunatic and ignored.  The bios has no place to disable it,
> >> dumbest bios I've seen in quite a while, and it has been updated in the
> >> last 3 months.
> >>
> >> I don't *think* I'm a lunatic, but I'm equally sure that the synaptics
> >> is a pain in the ass and should be capable of being totally disabled
> >> somehow, hopefully short of opening the lappy up and unplugging or
> >> cutting every lead to it until such time as it can be made to behave
> >> instead of responding to every thumb waved 1/2 to 3/4" above it.  I've
> >> gotten hand cramps trying to hold my thumbs far enough away from that
> >> abomination to stop such goings on.
> >>
> >> So count this as a vote FOR doing something about the synaptics
> >> touchpad situation.
> >
> >There are ways to disable it:
> >
> >echo -n "manual" > /sys/bus/serio/devices/serioX/bind_mode
> bash: /sys/bus/serio/devices/serioX/bind_mode:  No such file or directory
> >echo -n "none" > /sys/bus/serio/devices/serioXdrvctl
> bash: /sys/bus/serio/devices/serioXdvrctl: Permission denied
>
> The above is from a root bash shell while X is running the KDE desktop.
> >
> >This should disable it completely.
>
> next step? :)
>

serioX is the name of serio port your touchpad is connected to
(serio0, serio1, etc) You will have to look which port is bound to
psmouse driver.

-- 
Dmitry

  reply	other threads:[~2006-08-14 15:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 13:58 Luke Sharkey
2006-08-14 14:36 ` Dmitry Torokhov
2006-08-14 15:18   ` Dave Jones
2006-08-14 14:38 ` Gene Heskett
2006-08-14 15:06   ` Ian Stirling
2006-08-14 15:19     ` Gene Heskett
2006-08-14 15:41       ` Ian Stirling
2006-08-14 15:13   ` Dmitry Torokhov
2006-08-14 15:25     ` Mattia Dongili
2006-08-14 15:34     ` Gene Heskett
2006-08-14 15:53       ` Dmitry Torokhov [this message]
2006-08-14 16:33         ` Gene Heskett
2006-08-14 16:59           ` Dmitry Torokhov
2006-08-14 15:20   ` Andreas Mohr
2006-08-14 15:41     ` Dmitry Torokhov
2006-08-14 15:54       ` Andreas Mohr
2006-08-14 16:06         ` Dmitry Torokhov
2006-08-14 20:06           ` Polling for battery stauts and lost keypresses (was: Touchpad problems with latest kernels) Giuseppe Bilotta
2006-08-14 20:17             ` Dmitry Torokhov
2006-08-16  7:31               ` Polling for battery stauts and lost keypresses Giuseppe Bilotta
2006-08-19 15:50                 ` Dmitry Torokhov
2006-08-19 16:02                   ` Arjan van de Ven
2006-08-21 11:56                     ` Giuseppe Bilotta
2006-08-21 12:34                     ` Dmitry Torokhov
2006-08-21 12:52                       ` Arjan van de Ven
2006-08-24 20:31                 ` Pavel Machek
2006-08-14 19:30       ` Touchpad problems with latest kernels Dmitry Torokhov
2006-08-14 17:09 Voluspa
2006-08-14 19:27 ` Dmitry Torokhov
2006-08-15  3:06   ` Voluspa
2006-08-15 14:57   ` Luke Sharkey
2006-08-15 16:33     ` Voluspa
2006-08-15 17:12       ` Dmitry Torokhov
2006-08-15 19:00         ` Voluspa
2006-08-15 17:10     ` Dmitry Torokhov
2006-08-16 13:59       ` Luke Sharkey
2006-08-16 14:42         ` Dmitry Torokhov
     [not found]           ` <BAY114-F39F04F7AD7901A482EB648FA4D0@phx.gbl>
2006-08-17 15:28             ` Dmitry Torokhov
2006-08-27 21:26 Javier Kohen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d120d5000608140853t5a27b522ra7b29aeb0e318efa@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®