public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Juergen Quade <quade@hsnr.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [RFT/PATCH] Toshiba Satellite, Synaptics & keyboard problems
Date: Mon, 8 Nov 2004 09:33:34 -0500	[thread overview]
Message-ID: <d120d50004110806334f69507c@mail.gmail.com> (raw)
In-Reply-To: <20041108083531.GA17236@hsnr.de>

On Mon, 8 Nov 2004 09:35:31 +0100, Juergen Quade <quade@hsnr.de> wrote:
> On Mon, Nov 08, 2004 at 01:54:52AM -0500, Dmitry Torokhov wrote:
> > Hi,
> >
> > If anyone experiencing keyboard getting "stuck" when you use Synaptics
> > touchpad in native mode on Toshiba Satellite type notebooks it seems that
> > lowering rate to 40 pps (which is roughly the same as standard PS/2 rate
> > bytewise) helps.
> >
> > Please try the patch below (should apply to -mm tree) and see if it helps
> > any. If not using -mm tree just use "psmouse.rate=40" or "modprobe psmouse
> > rate=40" to check if fix is working for you and let me know.
> 
> I have problems with "no keyboard" since Kernel 2.6.9.
> I am not using a -mm tree and booting with "psmouse.rate=40" does
> _not_ fix the problem :-(   (tested with 2.6.9 and 2.6.10-rc1).
> 
> As soon as X is started I have no keyboard.
> My box is a Acer Travelmate 290 notebook with synaptics/alps
> touchpad.
> 

Well, this one is pretty easy - make sure that you have a recent
version of Synaptics X driver and change protocol in your XF86Config
to "auto-dev". (most likely you wree using /dev/input/exentX as your
device and in 2.6.9 your keyboard and touchpad swapped their
event devices).

-- 
Dmitry

  reply	other threads:[~2004-11-08 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08  6:54 [RFT/PATCH] Toshiba Satellite, Synaptics & keyboard problems Dmitry Torokhov
2004-11-08  8:35 ` Juergen Quade
2004-11-08 14:33   ` Dmitry Torokhov [this message]
2004-11-08 18:18     ` Juergen Quade

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=d120d50004110806334f69507c@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quade@hsnr.de \
    --cc=vojtech@suse.cz \
    /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